diff options
| author | Luke Plant <L.Plant.98@cantab.net> | 2009-03-23 16:37:25 +0000 |
|---|---|---|
| committer | Luke Plant <L.Plant.98@cantab.net> | 2009-03-23 16:37:25 +0000 |
| commit | 4e2533436ef08ce81516e4cfd47ccbb1dddac5f8 (patch) | |
| tree | 7f1e1f2bc17c8f3805687984883d8c7dd32a57aa /docs | |
| parent | 7db24dd2b080f727cd9753161e88faa308514aad (diff) | |
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
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.1-alpha-1.txt | 8 |
1 files changed, 1 insertions, 7 deletions
diff --git a/docs/releases/1.1-alpha-1.txt b/docs/releases/1.1-alpha-1.txt index 11ce442787..fa6f494a48 100644 --- a/docs/releases/1.1-alpha-1.txt +++ b/docs/releases/1.1-alpha-1.txt @@ -74,13 +74,7 @@ Other new features and changes introduced since Django 1.0 include: ``CsrfMiddleware`` class (which does both) remains for backwards-compatibility, but using the split classes is now recommended in order to allow fine-grained control of when and where the CSRF processing - takes place. Decorators are provided for selectively turning it off for - 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. + takes place. * :func:`~django.core.urlresolvers.reverse` and code which uses it (e.g., the ``{% url %}`` template tag) now works with URLs in Django's administrative |