test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #20134 -- Correct list of fields that UserManager requires. 

Thanks semenov and pegler.
This commit is contained in:
Tim Graham 2013-07-04 10:19:00 -04:00
parent f407f75aae
commit da5069f68f
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/topics/auth/customizing.txt
View File

@ -589,8 +589,9 @@ The following methods are available on any subclass of
been called for this user. been called for this user.
You should also define a custom manager for your ``User`` model. If your 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 ``User`` model defines ``username``, ``email``, ``is_staff``, ``is_active``,
default ``User``, you can just install Django's ``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`` :class:`~django.contrib.auth.models.UserManager`; however, if your ``User``
model defines different fields, you will need to define a custom manager that model defines different fields, you will need to define a custom manager that
extends :class:`~django.contrib.auth.models.BaseUserManager` providing two extends :class:`~django.contrib.auth.models.BaseUserManager` providing two