Opened 11 years ago
Closed 10 years ago
#22295 closed Cleanup/optimization (fixed)
admin/base.html only shows #user-tools when user is staff
Reported by: | Owned by: | ||
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Normal | Keywords: | user-tools admin base template |
Cc: | jeffrey@…, tanner | Triage Stage: | Ready for checkin |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The build-in Django Admin ships with the admin/base.html template. This template is, among other things, responsible for rendering the #user-tools div that contains the 'log out' and 'change password' buttons. The user tools are only rendered if user.is_active and user.is_staff are True, see:
https://github.com/django/django/blob/2bc51438664b5ffbbd1430b4f9f3307f18b2b9db/django/contrib/admin/templates/admin/base.html#L27
This check makes sure that #user-tools is only rendered when the user is actually authenticated for use of the admin. This is required because the login template (admin/login.html) eventually inherits from admin/base.html. If the check would be omitted, the #user-tools would become visible if the user was yet to be authenticated resulting in a situation where the user could 'log out' without being 'logged in' first.
This check is therefore relevant, but is it the wrong check and breaks inheritance in the following case:
Lets say you want to inherit from django.contrib.admin.sites.BaseSite to create a customized admin for special users that are not necessarily staff members. You can override the BaseSite.has_permission method. Currently this method holds the condition: request.user.is_active and request.user.is_staff
. You might change this to request.user.is_active and request.user.is_a_special_user_but_not_staff
. This user would now be allowed to access this customised admin without having access to the default admin.
The problem is that the user cannot log out from this special admin because the #user-tools are only rendered if the user is a staff member.
I can think of two solutions:
- Use the BaseAdmin.has_permission to do this check
- Create a block called user-tools in the template and override this block in the admin/login.html to be empty
In my opinion solution number 2 would be the best approach :-).
Change History (13)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:3 by , 10 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:5 by , 10 years ago
Patch needs improvement: | set |
---|
I left comments for improvement on PR. Please uncheck "Patch needs improvement" when you update it, thanks.
comment:6 by , 10 years ago
Owner: | removed |
---|---|
Status: | assigned → new |
comment:7 by , 10 years ago
I have updated my PR https://github.com/django/django/pull/3762 to include the requested improvements and also implemented solution 2.
comment:8 by , 10 years ago
Cc: | added |
---|
comment:9 by , 10 years ago
Please uncheck "Patch needs improvement" when you update your pull request so the ticket appears in the review queue.
comment:10 by , 10 years ago
Patch needs improvement: | unset |
---|
comment:12 by , 10 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
comment:13 by , 10 years ago
Owner: | set to |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Yes, option 2 sounds like a better approach if the goal is simply to hide this block.
But what about people who extend this template and rely on the current implementation to hide the block?
Even for small things, it's important to consider backwards compatibility.