Opened 16 years ago
Closed 12 years ago
#10206 closed Bug (wontfix)
admin/auth/user/* templates should be in django.contrib.auth app
Reported by: | izibi | Owned by: | Chris Beaven |
---|---|---|---|
Component: | contrib.admin | Version: | 1.0 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
In case somebody wants to create a own auth app with a user model he might get a problem with these templates in the admin.
So these templates should be moved to the django.contrib.auth app to prevent this problem.
Change History (5)
comment:1 by , 16 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:2 by , 14 years ago
Owner: | changed from | to
---|---|
Severity: | → Normal |
Status: | new → assigned |
Triage Stage: | Design decision needed → Accepted |
Type: | → Bug |
Admin specific, but completely in context to the auth application. If the auth app is not installed, these templates should technically not be accessible.
comment:5 by , 12 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
admin requires auth; "the auth app is not installed" isn't really possible.
The other way round is possible: you can use auth without the admin. In that case, the current templates wouldn't work, because they extend admin/base.html which wouldn't be accessible.
Therefore keeping these templates in the admin app is correct.
One could argue that "using the admin with an API-compatible re-implementation of auth that requires different templates" is possible, but that's much less common than "using auth but not the admin", all the more since Django now supports custom user models.
I'm pretty sure these templates are admin-specific.