Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

[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
  • Loading branch information...
commit 6a30f5a2ea120d143b457a612ab9f1d1236256b6 1 parent 378dadc
Malcolm Tredinnick authored October 06, 2008

Showing 1 changed file with 9 additions and 2 deletions. Show diff stats Hide diff stats

  1. 11  docs/topics/auth.txt
11  docs/topics/auth.txt
@@ -89,8 +89,15 @@ Fields
89 89
 
90 90
     .. attribute:: models.User.is_active
91 91
 
92  
-        Boolean. Designates whether this account can be used to log in. Set this
93  
-        flag to ``False`` instead of deleting accounts.
  92
+        Boolean. Designates whether this user account should be considered
  93
+        active. Set this flag to ``False`` instead of deleting accounts.
  94
+
  95
+        This doesn't control whether or not the user can log in. Nothing in
  96
+        the authentication path checks the ``is_active`` flag, so if you want
  97
+        to reject a login based on ``is_active`` being ``False``, it is up to
  98
+        you to check that in your own login view. However, permission checking
  99
+        using the methods like :meth:`~models.User.has_perm` does check this
  100
+        flag and will always return ``False`` for inactive users.
94 101
 
95 102
     .. attribute:: models.User.is_superuser
96 103
 

0 notes on commit 6a30f5a

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