From 541a30c3768fa86ecb85ceea8545af175bada4fb Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 4 Jul 2013 10:19:00 -0400 Subject: [PATCH] [1.6.x] Fixed #20134 -- Correct list of fields that UserManager requires. Thanks semenov and pegler. Backport of da5069f68f from master. --- docs/topics/auth/customizing.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index ee1aedbd8c..eb2fff05f5 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -623,8 +623,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