#11154: Inconsistency with permissions for proxy models
-------------------------------------+-------------------------------------
Reporter: etianen | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: proxy contenttype | Triage Stage: Accepted
permission | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by clay.evil@…):
hi, after reading all the comments, i'm not sure if this is fixed or not
in 1.4, however i have found another issue with this.
I have tracked it to sites.py line 338 has_module_perms =
user.has_module_perms(app_label).
The problem is that the admin site won't even start to look for
model_admin.get_model_perms(request) because i don't have permission to
the "foo" module (as the permissions created are under "auth".
I know you busy, but this I think is a serious issue if someone has to
make use of the build in admin site, and won't have an superuser (because
an superuser is very evil).
Thank you.
--
Ticket URL: <https://code.djangoproject.com/ticket/11154#comment:44>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
