Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed #9718 -- Removed a reference to oldforms FormWrapper object in …

…the user authentication docs.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@9595 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit ff3e1a7d40c783e9df3d38f327548d3ad2edcfab 1 parent b76d7c1
Gary Wilson Jr. authored December 08, 2008

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

  1. 28  docs/topics/auth.txt
28  docs/topics/auth.txt
@@ -253,8 +253,8 @@ Manager functions
253 253
     .. method:: models.UserManager.create_user(username, email, password=None)
254 254
 
255 255
         Creates, saves and returns a :class:`~django.contrib.auth.models.User`.
256  
-        The :attr:`~django.contrib.auth.models.User.username`, 
257  
-        :attr:`~django.contrib.auth.models.User.email` and 
  256
+        The :attr:`~django.contrib.auth.models.User.username`,
  257
+        :attr:`~django.contrib.auth.models.User.email` and
258 258
         :attr:`~django.contrib.auth.models.User.password` are set as given, and the
259 259
         :class:`~django.contrib.auth.models.User` gets ``is_active=True``.
260 260
 
@@ -360,11 +360,11 @@ Anonymous users
360 360
       ``False`` instead of ``True``.
361 361
     * :meth:`~django.contrib.auth.models.User.has_perm()` always returns ``False``.
362 362
     * :meth:`~django.contrib.auth.models.User.set_password()`,
363  
-      :meth:`~django.contrib.auth.models.User.check_password()`, 
364  
-      :meth:`~django.contrib.auth.models.User.save()`, 
  363
+      :meth:`~django.contrib.auth.models.User.check_password()`,
  364
+      :meth:`~django.contrib.auth.models.User.save()`,
365 365
       :meth:`~django.contrib.auth.models.User.delete()`,
366  
-      :meth:`~django.contrib.auth.models.User.set_groups()` and 
367  
-      :meth:`~django.contrib.auth.models.User.set_permissions()` raise 
  366
+      :meth:`~django.contrib.auth.models.User.set_groups()` and
  367
+      :meth:`~django.contrib.auth.models.User.set_permissions()` raise
368 368
       :exc:`NotImplementedError`.
369 369
 
370 370
 In practice, you probably won't need to use
@@ -682,7 +682,7 @@ the following line to your URLconf::
682 682
 
683 683
         * ``form``: A :class:`~django.forms.Form` object representing the
684 684
           login form. See the :ref:`forms documentation <topics-forms-index>`
685  
-          for more on ``FormWrapper`` objects.
  685
+          for more on ``Form`` objects.
686 686
 
687 687
         * ``next``: The URL to redirect to after successful login. This may contain
688 688
           a query string, too.
@@ -691,7 +691,7 @@ the following line to your URLconf::
691 691
           :class:`~django.contrib.sites.models.Site`, according to the
692 692
           :setting:`SITE_ID` setting. If you're using the Django development version
693 693
           and you don't have the site framework installed, this will be set to the
694  
-          value of ``request.META['SERVER_NAME']``. For more on sites, see 
  694
+          value of ``request.META['SERVER_NAME']``. For more on sites, see
695 695
           :ref:`ref-contrib-sites`.
696 696
 
697 697
     If you'd prefer not to call the template :file:`registration/login.html`,
@@ -1037,7 +1037,7 @@ Fields
1037 1037
 fields:
1038 1038
 
1039 1039
 .. attribute:: models.Permission.name
1040  
-    
  1040
+
1041 1041
     Required. 50 characters or fewer. Example: ``'Can vote'``.
1042 1042
 
1043 1043
 .. attribute:: models.Permission.content_type
@@ -1046,7 +1046,7 @@ fields:
1046 1046
     which contains a record for each installed Django model.
1047 1047
 
1048 1048
 .. attribute:: models.Permission.codename
1049  
-    
  1049
+
1050 1050
     Required. 100 characters or fewer. Example: ``'can_vote'``.
1051 1051
 
1052 1052
 Methods
@@ -1069,7 +1069,7 @@ The currently logged-in user and his/her permissions are made available in the
1069 1069
    :setting:`TEMPLATE_CONTEXT_PROCESSORS` setting contains
1070 1070
    ``"django.core.context_processors.auth"``, which is default. For more, see
1071 1071
    the :ref:`RequestContext docs <subclassing-context-requestcontext>`.
1072  
-   
  1072
+
1073 1073
 Users
1074 1074
 -----
1075 1075
 
@@ -1099,7 +1099,7 @@ in the ``foo`` app::
1099 1099
 
1100 1100
     {{ perms.foo }}
1101 1101
 
1102  
-Two-level-attribute lookup is a proxy to 
  1102
+Two-level-attribute lookup is a proxy to
1103 1103
 :meth:`User.has_perm <django.contrib.auth.models.User.has_perm>`. This example
1104 1104
 would display ``True`` if the logged-in user had the permission
1105 1105
 ``foo.can_vote``::
@@ -1153,7 +1153,7 @@ The API is simple:
1153 1153
 
1154 1154
     To create a new message, use
1155 1155
     ``user_obj.message_set.create(message='message_text')``.
1156  
-    
  1156
+
1157 1157
     To retrieve/delete messages, use
1158 1158
     :meth:`user_obj.get_and_delete_messages() <django.contrib.auth.models.User.get_and_delete_messages>`,
1159 1159
     which returns a list of ``Message`` objects in the user's queue (if any)
@@ -1313,7 +1313,7 @@ Custom auth backends can provide their own permissions.
1313 1313
 
1314 1314
 The user model will delegate permission lookup functions
1315 1315
 (:meth:`~django.contrib.auth.models.User.get_group_permissions()`,
1316  
-:meth:`~django.contrib.auth.models.User.get_all_permissions()`, 
  1316
+:meth:`~django.contrib.auth.models.User.get_all_permissions()`,
1317 1317
 :meth:`~django.contrib.auth.models.User.has_perm()`, and
1318 1318
 :meth:`~django.contrib.auth.models.User.has_module_perms()`) to any
1319 1319
 authentication backend that implements these functions.

0 notes on commit ff3e1a7

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