#23314: Docs should stay consistent and only recommend custom users for custom
authentication and authorization, not profile data
--------------------------------------+------------------------------------
Reporter: gavinwahl | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version:
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"b3f6a0f5a1b88a9a96080531b7391f6a3a0ce5aa"]:
{{{
#!CommitTicketReference repository=""
revision="b3f6a0f5a1b88a9a96080531b7391f6a3a0ce5aa"
[1.7.x] Fixed #23314 -- Tempered recommendation of storing profile data on
custom user.
Thanks gavinwahl for the report.
Backport of 3569536491 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23314#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.e42727ed47e3f8cc46849aafae543ab7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
