Author: timo
Date: 2011-01-22 06:43:50 -0600 (Sat, 22 Jan 2011)
New Revision: 15281
Modified:
django/trunk/docs/ref/signals.txt
django/trunk/docs/releases/1.3-beta-1.txt
django/trunk/docs/topics/auth.txt
Log:
Fixed #15133 - Some markup issues in the docs; thanks Aryeh Leib Taurog for the
report.
Modified: django/trunk/docs/ref/signals.txt
===================================================================
--- django/trunk/docs/ref/signals.txt 2011-01-21 22:25:50 UTC (rev 15280)
+++ django/trunk/docs/ref/signals.txt 2011-01-22 12:43:50 UTC (rev 15281)
@@ -12,7 +12,7 @@
The :doc:`comment framework </ref/contrib/comments/index>` sends a
:doc:`set
of comment-related signals </ref/contrib/comments/signals>`.
- The :ref:`authentication framework <topics-auth>` sends :ref:`signals when
+ The :doc:`authentication framework </topics/auth>` sends :ref:`signals when
a user is logged in / out <topics-auth-signals>`.
Model signals
Modified: django/trunk/docs/releases/1.3-beta-1.txt
===================================================================
--- django/trunk/docs/releases/1.3-beta-1.txt 2011-01-21 22:25:50 UTC (rev
15280)
+++ django/trunk/docs/releases/1.3-beta-1.txt 2011-01-22 12:43:50 UTC (rev
15281)
@@ -61,7 +61,7 @@
If you provide a custom auth backend with ``supports_inactive_user`` set to
``True``, an inactive user model will check the backend for permissions.
This is useful for further centralizing the permission handling. See the
-:ref:`authentication docs <topics-auth>` for more details.
+:doc:`authentication docs </topics/auth>` for more details.
Backwards-incompatible changes in 1.3 alpha 2
=============================================
Modified: django/trunk/docs/topics/auth.txt
===================================================================
--- django/trunk/docs/topics/auth.txt 2011-01-21 22:25:50 UTC (rev 15280)
+++ django/trunk/docs/topics/auth.txt 2011-01-22 12:43:50 UTC (rev 15281)
@@ -657,10 +657,10 @@
Login and logout signals
------------------------
-The auth framework uses two :ref:`signals <topic-signals>` that can be used for
-notification when a user logs in or out.
+The auth framework uses two :doc:`signals </topics/signals>` that can be used
+for notification when a user logs in or out.
-**:data:`django.contrib.auth.signals.user_logged_in`**
+.. data:: django.contrib.auth.signals.user_logged_in
Sent when a user logs in successfully.
@@ -675,7 +675,7 @@
``user``
The user instance that just logged in.
-**:data:`django.contrib.auth.signals.user_logged_out`**
+.. data:: django.contrib.auth.signals.user_logged_outs
Sent when the logout method is called.
@@ -1537,11 +1537,11 @@
ADMIN_LOGIN = 'admin'
ADMIN_PASSWORD = 'sha1$4e987$afbcf42e21bd417fb71db8c66b321e9fc33051de'
"""
-
+
supports_object_permissions = False
supports_anonymous_user = False
supports_inactive_user = False
-
+
def authenticate(self, username=None, password=None):
login_valid = (settings.ADMIN_LOGIN == username)
pwd_valid = check_password(password, settings.ADMIN_PASSWORD)
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
