#28667 closed Cleanup/optimization (fixed)
Documentation for extending UserCreationForm doesn't work with UserAdmin
Reported by: | Nathanael Gordon | Owned by: | Swatantra |
---|---|---|---|
Component: | contrib.auth | Version: | 2.2 |
Severity: | Normal | Keywords: | add_fieldsets UserAdmin UserCreationForm Custom Auth User Model |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
In the docs for customising the Auth User model it does not fully outline the link between the UserCreationForm and the UserAdmin - specifically the fact that the UserAdmin's add_fieldsets
will be used rather than the fields
attribute in the Meta
for the custom UserCreationForm
.
At the end of this section (https://docs.djangoproject.com/en/1.11/topics/auth/customizing/#custom-users-and-the-built-in-auth-forms) it specifies that one can simply override the fields
in the Meta
of one's UserCreationForm
. However, as the UserAdmin uses a custom get_fieldsets
method which uses its add_fieldsets
attribute instead, overriding fields
does nothing.
Change History (11)
comment:1 by , 7 years ago
Summary: | Lack of clear documentation for custom UserCreationForm when using a custom User model → Documentation for extending UserCreationForm doesn't work with UserAdmin |
---|---|
Triage Stage: | Unreviewed → Accepted |
Type: | Bug → Cleanup/optimization |
comment:2 by , 6 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 6 years ago
comment:4 by , 6 years ago
I'm having a hard time creating a test app with a UserCreationForm
for a model based on the django.contrib.auth.admin.UserAdmin
class. Is this not the class. Is there any example code anyone can show me?
At the end of this section (https://docs.djangoproject.com/en/1.11/topics/auth/customizing/#custom-users-and-the-built-in-auth-forms) it specifies that one can simply override the fields in the Meta of one's UserCreationForm.
Above this example it is stated that it only works if the model is a simple subclass of AbstractUser
. Do we want another example for UserAdmin
or what are we looking for? Maybe I'm not the right person for this issue, I don't know. If any of you guys know anything or can clarify please let me know.
comment:5 by , 6 years ago
Owner: | removed |
---|---|
Status: | assigned → new |
comment:6 by , 6 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:7 by , 6 years ago
Owner: | removed |
---|---|
Status: | assigned → new |
Given the lack of updates I'm going to de-assign this issue so someone else looking can pick it up.
comment:8 by , 5 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
I plan to be done with this at the end of October.