Skip to content

Commit

Permalink
Fixed #20134 -- Correct list of fields that UserManager requires.
Browse files Browse the repository at this point in the history
Thanks semenov and pegler.
  • Loading branch information
timgraham committed Jul 4, 2013
1 parent f407f75 commit da5069f
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions docs/topics/auth/customizing.txt
Expand Up @@ -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
Expand Down

0 comments on commit da5069f

Please sign in to comment.