Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#25744 closed Bug (fixed)

Documentation of customizing authentication references to wrong place

Reported by: Tomi Owned by: Anderson Resende
Component: Documentation Version: 1.8
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

In documentation on page topics/auth/customizing/#writing-an-authentication-backend it says "The Django admin system is tightly coupled to the Django User object described at the beginning of this document." but I think this is not true. The User object is not described on that page but it is described on topics/auth/default/#user-objects.

This is present on all versions since 1.5 at least. I think this is an easy one to fix, just check if this is really a bug and then rephrase the sentence and link to correct part of the documentation.

Change History (5)

comment:1 by Tim Graham, 8 years ago

Triage Stage: UnreviewedAccepted
Type: UncategorizedBug

Yes, the auth documentation was reorganized at some point.

comment:2 by Anderson Resende, 8 years ago

Owner: changed from nobody to Anderson Resende
Status: newassigned

comment:3 by Tim Graham <timograham@…>, 8 years ago

Resolution: fixed
Status: assignedclosed

In ce4914ea:

Fixed #25744 -- Corrected reference to User object in auth docs.

comment:4 by Tim Graham <timograham@…>, 8 years ago

In 2a4a9e31:

[1.8.x] Fixed #25744 -- Corrected reference to User object in auth docs.

Backport of ce4914eab4688ace4b97d14a8c271887235ebb3f from master

comment:5 by Tim Graham <timograham@…>, 8 years ago

In 0ec32850:

[1.9.x] Fixed #25744 -- Corrected reference to User object in auth docs.

Backport of ce4914eab4688ace4b97d14a8c271887235ebb3f from master

Note: See TracTickets for help on using tickets.
Back to Top