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

Removed erroneous changes to 1.1 alpha 1 release notes. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@10120 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Luke Plant 2009-03-23 16:37:25 +00:00
parent 7db24dd2b0
commit 4e2533436e
1 changed files with 1 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/releases/1.1-alpha-1.txt
View File

@ -74,13 +74,7 @@ Other new features and changes introduced since Django 1.0 include:
``CsrfMiddleware`` class (which does both) remains for ``CsrfMiddleware`` class (which does both) remains for
backwards-compatibility, but using the split classes is now recommended in backwards-compatibility, but using the split classes is now recommended in
order to allow fine-grained control of when and where the CSRF processing order to allow fine-grained control of when and where the CSRF processing
takes place. Decorators are provided for selectively turning it off for takes place.
certain views.
Also, these middleware are now enabled by default when creating new projects.
It is recommended to add these middleware, if not already present, to existing
projects, to provide protection for the admin (which has no other CSRF
protection) and other apps.
* :func:`~django.core.urlresolvers.reverse` and code which uses it (e.g., the * :func:`~django.core.urlresolvers.reverse` and code which uses it (e.g., the
``{% url %}`` template tag) now works with URLs in Django's administrative ``{% url %}`` template tag) now works with URLs in Django's administrative