#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 charettes):
I think that allowing
[https://code.djangoproject.com/browser/django/trunk/django/contrib/contenttypes/models.py#L29
`ContentTypeManager.get_for_model`] to return a proxy model (using a
boolean kwarg to bypass the `ContentTypeManager._get_opt` part) could fix
issues. Defaulting this boolean flag to `false` would preserve backward
compatibility.
The auth framework could then use that flag to create the missings
permissions for proxy model. Plus it would allow polymorphic solutions
that saves the object ct to be retreived calling
{{{ContentTypeManager.get_for_model('app', 'label', True)}}}. I think the
addition of this new feature/approach should be discussed on django-dev
since it involves a design decision.
--
Ticket URL: <https://code.djangoproject.com/ticket/11154#comment:27>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
