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

[1.0.X] Fixed #7011 -- Clarified what User.is_active really means in the documentation. 

Backport of r9176 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9179 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2008-10-06 11:26:59 +00:00
parent 378dadc210
commit 6a30f5a2ea
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/topics/auth.txt
View File

@ -89,8 +89,15 @@ Fields
.. attribute:: models.User.is_active
Boolean. Designates whether this account can be used to log in. Set this
flag to ``False`` instead of deleting accounts.
Boolean. Designates whether this user account should be considered
active. Set this flag to ``False`` instead of deleting accounts.
This doesn't control whether or not the user can log in. Nothing in
the authentication path checks the ``is_active`` flag, so if you want
to reject a login based on ``is_active`` being ``False``, it is up to
you to check that in your own login view. However, permission checking
using the methods like :meth:`~models.User.has_perm` does check this
flag and will always return ``False`` for inactive users.
.. attribute:: models.User.is_superuser