I don't know, but try something as this to the help_text:
class RegistrationFormTOSAndUniqueEmail(RegistrationFormTermsOfService,
RegistrationFormUniqueEmail):
class MyUserAdminForm(forms.ModelForm):
def __init__(self, *args, **kwargs):
self.fields['is_staff'].help_text = _("Test.")
2010/7/9 Alexandre González <a...@mirblu.com>
> Hi!
>
> Perhaps you can do it easily with signals instead override the save method,
> take a look to this:
> http://www.ibm.com/developerworks/opensource/library/os-django-admin/index.html
>
>
> <http://www.ibm.com/developerworks/opensource/library/os-django-admin/index.html>Good
> luck and ask again if they don't work,
> Álex González
>
>
> On Fri, Jul 9, 2010 at 01:40, Jacob Fenwick <jacob.fenw...@gmail.com>wrote:
>
>> I tried something like this:
>>
>> *models.py
>> class MyUser(User):
>> pass
>>
>> *admin.py
>> class MyUserAdminForm(forms.ModelForm):
>> is_staff = models.BooleanField(_('staff status'),
>> default=True, help_text=_("Test."))
>>
>> class Meta:
>> model = User
>>
>> class MyUserAdmin(UserAdmin):
>> form = PublisherAdminForm
>>
>> admin.site.register(MyUser, MyUserAdmin)
>>
>>
>> Any idea why the help text wouldn't show up in the admin for this?
>>
>> Jacob
>>
>> On Thu, Jul 8, 2010 at 7:08 PM, Jacob Fenwick <jacob.fenw...@gmail.com>wrote:
>>
>>> So one method I found is to use the custom validation from a form in the
>>> ModelAdmin:
>>>
>>> http://docs.djangoproject.com/en/1.2/ref/contrib/admin/#adding-custom-validation-to-the-admin
>>>
>>> However, this only seems to work on edits, not on adds.
>>>
>>> How can I make this work on adds?
>>>
>>> Jacob
>>>
>>>
>>> On Thu, Jul 8, 2010 at 6:33 PM, Jacob Fenwick
>>> <jacob.fenw...@gmail.com>wrote:
>>>
>>>> I'm looking for a way to automatically set is_active to true for new
>>>> users that are added through the admin interface.
>>>>
>>>> I tried to subclass the User class and set the is_active default to true
>>>> but apparently you can't override fields in a parent model:
>>>>
>>>> http://docs.djangoproject.com/en/1.2/topics/db/models/#field-name-hiding-is-not-permitted
>>>>
>>>> Is there some sort of ModelAdmin magic that could solve this problem?
>>>>
>>>> Or is there some other method that can be arrived at through subclassing
>>>> the User object?
>>>>
>>>> Jacob
>>>>
>>>
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To post to this group, send email to django-us...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/django-users?hl=en.
>>
>
>
>
> --
> Please, don't send me files with extensions: .doc, .docx, .xls, .xlsx, .ppt
> and/or .pptx
> http://mirblu.com
>
--
Please, don't send me files with extensions: .doc, .docx, .xls, .xlsx, .ppt
and/or .pptx
http://mirblu.com
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
