#11154: Inconsistency with permissions for proxy models
-------------------------------------+-------------------------------------
Reporter: Dave Hall | Owner: (none)
Type: Bug | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: proxy contenttype | Triage Stage: Accepted
permission |
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Stephen Wolff):
For anyone else struggling with this, we've solved it by writing
migrations to add the permissions (django 1.8) by creating the 'model':
{{{
migrations.CreateModel(
name='XYZUserProxyModel',
fields=[
],
options={
'verbose_name': 'User (XYZ User)',
'managed': False,
'proxy': True,
'verbose_name_plural': 'Users (XYZ Users)',
},
bases=('proxyapp.user',),
managers=[
('objects', django.contrib.auth.models.UserManager()),
],
),
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/11154#comment:57>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.25223ccd8849405538f4b79e9278f5d2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
