Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#24780 closed Bug (fixed)

custom-users-and-signals docs out of date

Reported by: Tom V Owned by: nobody
Component: Documentation Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The Custom users and signals docs say:

Another limitation of custom User models is that you can’t use django.contrib.auth.get_user_model() as the sender or target of a signal handler. Instead, you must register the handler with the resulting User model. See Signals for more information on registering and sending signals.

Which isn't really helpful, as you can now use the model label, as mentioned higher on the page:

post_save.connect(post_save_receiver, sender=settings.AUTH_USER_MODEL)

So maybe just remove the quoted para? (it was created in this ticket, 2 years ago, when passing models by label wasn't allowed yet)

Happy to create a patch once we're decided.

Change History (3)

comment:1 by Tim Graham <timograham@…>, 9 years ago

Resolution: fixed
Status: newclosed

In 8e86d9d:

Fixed #24780 -- Removed outdated discussion of signals and custom users.

comment:2 by Tim Graham <timograham@…>, 9 years ago

In d92eaeb:

[1.7.x] Fixed #24780 -- Removed outdated discussion of signals and custom users.

Backport of 8e86d9d3dfd68bebbfd1dd5006e0c25696855269 from master

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

In d3a8f36:

[1.8.x] Fixed #24780 -- Removed outdated discussion of signals and custom users.

Backport of 8e86d9d3dfd68bebbfd1dd5006e0c25696855269 from master

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