diff options
| author | Tim Graham <timograham@gmail.com> | 2013-07-04 10:19:00 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-07-04 10:19:00 -0400 |
| commit | da5069f68f9ec0cf80f50f6708d103afd56d23ae (patch) | |
| tree | e2bf0ef1ecb60f49fe13f42da934fd11390cedd2 | |
| parent | f407f75aae242d1bd8d4ac7f19c5d4075353c65e (diff) | |
Fixed #20134 -- Correct list of fields that UserManager requires.
Thanks semenov and pegler.
| -rw-r--r-- | docs/topics/auth/customizing.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 24c622f77f..f62dd597a9 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -589,8 +589,9 @@ The following methods are available on any subclass of been called for this user. You should also define a custom manager for your ``User`` model. If your -``User`` model defines ``username`` and ``email`` fields the same as Django's -default ``User``, you can just install Django's +``User`` model defines ``username``, ``email``, ``is_staff``, ``is_active``, +``is_superuser``, ``last_login``, and ``date_joined`` fields the same as +Django's default ``User``, you can just install Django's :class:`~django.contrib.auth.models.UserManager`; however, if your ``User`` model defines different fields, you will need to define a custom manager that extends :class:`~django.contrib.auth.models.BaseUserManager` providing two |
