Skip to content
Browse files

[1.5.x] Fixed #20134 -- Correct list of fields that UserManager requi…


Thanks semenov and pegler.

Backport of da5069f from master.
  • Loading branch information...
1 parent 82a6a95 commit 25d987b21e3af11b3ab3e37478a2dfd32f886d97 @timgraham timgraham committed
Showing with 3 additions and 2 deletions.
  1. +3 −2 docs/topics/auth/customizing.txt
5 docs/topics/auth/customizing.txt
@@ -601,8 +601,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

0 comments on commit 25d987b

Please sign in to comment.
Something went wrong with that request. Please try again.