#23314 closed Cleanup/optimization (fixed)
Docs should stay consistent and only recommend custom users for custom authentication and authorization, not profile data
| Reported by: | Gavin Wahl | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The docs mostly recommend using the profile pattern for profile data and only using a custom user for custom authentication and authorization:
<https://docs.djangoproject.com/en/dev/topics/auth/customizing/#extending-the-existing-user-model>
<https://docs.djangoproject.com/en/dev/topics/auth/customizing/#specifying-a-custom-user-model>
However, this paragraph is consistent:
<https://docs.djangoproject.com/en/dev/topics/auth/customizing/#extending-django-s-default-user>
It should recommend using a OneToOneField for profile data, like the rest of the docs.
Attachments (1)
Change History (6)
comment:1 by , 10 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|---|
| Type: | Uncategorized → Cleanup/optimization |
by , 10 years ago
| Attachment: | 23314.diff added |
|---|
comment:2 by , 10 years ago
| Has patch: | set |
|---|
comment:3 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
In 3569536491f16c9d112959d23cf3c18417063c54: