#11154: Inconsistency with permissions for proxy models
------------------------------+------------------------------------
Reporter: etianen | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: SVN
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by danny.adair@…):
@danols: That's exactly the inconsisteny described in this ticket. The
"change_myflatpage" permission has the app label of your class
("yourapp.change_myflatpage") but when django admin checks it will use the
app_label of the parent class ("contrib.change_myflatpage"). Look at the
database tables "auth_permission" and "django_content_type". In the
latter, your proxy model is listed with "myapp" as the app_label. When
django admin checks the permission though, it traverses up to the parent
of myflatpage and then uses _that_ app_label, and a combination of
"contrib" and "change_myflatpage" is not in your permissions table.
--
Ticket URL: <https://code.djangoproject.com/ticket/11154#comment:31>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
