#19412: Document that custom user models require a `user_permissions` M2M
---------------------------------+--------------------------------------
Reporter: cdestigter | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 1.5-beta-1
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by Russell Keith-Magee <russell@…>):
In [changeset:"311bd0055d6302ce42d3831f95d8b255986ddc40"]:
{{{
#!CommitTicketReference repository=""
revision="311bd0055d6302ce42d3831f95d8b255986ddc40"
[1.5.X} Fixed #19412 -- Added PermissionsMixin to the auth.User heirarchy.
This makes it easier to make a ModelBackend-compliant (with regards to
permissions) User model.
Thanks to cdestigter for the report about the relationship between
ModelBackend and permissions, and to the many users on django-dev that
contributed to the discussion about mixins.
Backport of 47e1df896b17aaaa97b73ef64010a7df4ea3d8d6 from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19412#comment:5>
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 https://groups.google.com/groups/opt_out.
