diff options
| author | Russell Keith-Magee <russell@keith-magee.com> | 2012-11-24 13:53:44 +0800 |
|---|---|---|
| committer | Russell Keith-Magee <russell@keith-magee.com> | 2012-11-24 14:27:11 +0800 |
| commit | 24582f18ff3aeb263f951dd2acf56f0a857fda17 (patch) | |
| tree | 9cd2b240a31da447bc17e687f8e12f36544c847a | |
| parent | 3fd8458fb3a30ea9fc6b3e7c08ff2d66a63e5067 (diff) | |
[1.5.x] Fixed #19218 -- Added documentation note on limitations of signals with custom User models.
Thanks to kunitoki@gmail.com for the report.
Backport of fdb5c98d7ee54c7f89ec10b0203263f1f5b37510.
| -rw-r--r-- | docs/topics/auth.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/topics/auth.txt b/docs/topics/auth.txt index aed482f710..3aac19f7ab 100644 --- a/docs/topics/auth.txt +++ b/docs/topics/auth.txt @@ -2148,6 +2148,13 @@ If your project uses proxy models, you must either modify the proxy to extend the User model that is currently in use in your project, or merge your proxy's behavior into your User subclass. +Custom users and signals +~~~~~~~~~~~~~~~~~~~~~~~~ + +Another limitation of custom User models is that you can't use +:func:`django.contrib.auth.get_user_model()` as the sender or target of a signal +handler. Instead, you must register the handler with the actual User model. + A full example -------------- |