Author: lukeplant
Date: 2011-04-09 11:47:59 -0700 (Sat, 09 Apr 2011)
New Revision: 16023

Modified:
   django/trunk/docs/releases/1.2-alpha-1.txt
   django/trunk/docs/releases/1.2.txt
Log:
Fixed #15780 - Broken link in old release notes regarding CSRF upgrade

Thanks to Aryeh Leib Taurog for the report.

Modified: django/trunk/docs/releases/1.2-alpha-1.txt
===================================================================
--- django/trunk/docs/releases/1.2-alpha-1.txt  2011-04-07 22:01:23 UTC (rev 
16022)
+++ django/trunk/docs/releases/1.2-alpha-1.txt  2011-04-09 18:47:59 UTC (rev 
16023)
@@ -32,9 +32,14 @@
 
  * All contrib apps use a ``csrf_protect`` decorator to protect the view. This
    requires the use of the ``csrf_token`` template tag in the template, so if 
you
-   have used custom templates for contrib views, you MUST READ THE 
:ref:`UPGRADE
-   INSTRUCTIONS <ref-csrf-upgrading-notes>` to fix those templates.
+   have used custom templates for contrib views, you MUST READ THE UPGRADE
+   INSTRUCTIONS to fix those templates.
 
+   .. admonition:: Documentation removed
+
+      The upgrade notes have been removed in current Django docs. Please refer
+      to the docs for Django 1.3 or older to find these instructions.
+
  * ``CsrfViewMiddleware`` is included in :setting:`MIDDLEWARE_CLASSES` by
    default. This turns on CSRF protection by default, so that views that accept
    POST requests need to be written to work with the middleware. Instructions
@@ -195,9 +200,14 @@
 ``CsrfResponseMiddleware`` and ``CsrfViewMiddleware`` has likewise been
 deprecated.
 
-Also, the CSRF module has moved from contrib to core, and the old imports are
-deprecated, as described in the :ref:`upgrading notes 
<ref-csrf-upgrading-notes>`.
+Also, the CSRF module has moved from contrib to core, and the old
+imports are deprecated, as described in the upgrading notes.
 
+.. admonition:: Documentation removed
+
+   The upgrade notes have been removed in current Django docs. Please refer
+   to the docs for Django 1.3 or older to find these instructions.
+
 ``SMTPConnection``
 ------------------
 

Modified: django/trunk/docs/releases/1.2.txt
===================================================================
--- django/trunk/docs/releases/1.2.txt  2011-04-07 22:01:23 UTC (rev 16022)
+++ django/trunk/docs/releases/1.2.txt  2011-04-09 18:47:59 UTC (rev 16023)
@@ -435,9 +435,14 @@
 
  * All contrib apps use a ``csrf_protect`` decorator to protect the view. This
    requires the use of the ``csrf_token`` template tag in the template. If you
-   have used custom templates for contrib views, you MUST READ THE 
:ref:`UPGRADE
-   INSTRUCTIONS <ref-csrf-upgrading-notes>` to fix those templates.
+   have used custom templates for contrib views, you MUST READ THE UPGRADE
+   INSTRUCTIONS to fix those templates.
 
+   .. admonition:: Documentation removed
+
+      The upgrade notes have been removed in current Django docs. Please refer
+      to the docs for Django 1.3 or older to find these instructions.
+
  * ``CsrfViewMiddleware`` is included in :setting:`MIDDLEWARE_CLASSES` by
    default. This turns on CSRF protection by default, so views that accept
    POST requests need to be written to work with the middleware. Instructions
@@ -861,9 +866,13 @@
 ``CsrfViewMiddleware``, has likewise been deprecated.
 
 Also, the CSRF module has moved from contrib to core, and the old
-imports are deprecated, as described in the :ref:`upgrading notes
-<ref-csrf-upgrading-notes>`.
+imports are deprecated, as described in the upgrading notes.
 
+.. admonition:: Documentation removed
+
+   The upgrade notes have been removed in current Django docs. Please refer
+   to the docs for Django 1.3 or older to find these instructions.
+
 ``SMTPConnection``
 ------------------
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to