#19412: Document that custom user models require a `user_permissions` M2M ---------------------------------+-------------------------------------- Reporter: cdestigter | Owner: nobody Type: Bug | Status: new Component: Documentation | Version: 1.5-beta-1 Severity: Release blocker | Resolution: Keywords: | Triage Stage: Accepted Has patch: 1 | Needs documentation: 1 Needs tests: 1 | Patch needs improvement: 1 Easy pickings: 1 | UI/UX: 0 ---------------------------------+-------------------------------------- Changes (by ptone):
* needs_better_patch: 0 => 1 * has_patch: 0 => 1 * needs_tests: 0 => 1 * needs_docs: 0 => 1 Comment: I think we could make the backend more resilient by changing the behavior to return no permissions for user models that don't define the permission related fields. Essentially - a user that doesn't define permissions, has no permissions - but doesn't raise any error. I've attached a patch demonstrating this - and can test and document if this seems a valid approach. -- Ticket URL: <https://code.djangoproject.com/ticket/19412#comment:2> 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.