From 48edb177edf04854999355dfdfe23fc6ee312d7b Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Mon, 4 Jan 2010 21:55:52 +0000 Subject: Fixed #12053 - form examples don't validate according to w3c Thanks to skyl for the report. git-svn-id: http://code.djangoproject.com/svn/django/trunk@12086 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/contrib/comments/example.txt | 2 +- docs/ref/contrib/comments/index.txt | 4 ++-- docs/ref/contrib/csrf.txt | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/contrib/comments/example.txt b/docs/ref/contrib/comments/example.txt index e9445353ca..ec600f7219 100644 --- a/docs/ref/contrib/comments/example.txt +++ b/docs/ref/contrib/comments/example.txt @@ -103,7 +103,7 @@ But let's look at a simple example:: - + {{ form }} diff --git a/docs/ref/contrib/comments/index.txt b/docs/ref/contrib/comments/index.txt index 9f53f06299..319dadff08 100644 --- a/docs/ref/contrib/comments/index.txt +++ b/docs/ref/contrib/comments/index.txt @@ -218,7 +218,7 @@ you can use in the template:: A complete form might look like:: {% get_comment_form for event as form %} - + {{ form }} @@ -239,7 +239,7 @@ You may have noticed that the above example uses another template tag -- form. This will always return the correct URL that comments should be posted to; you'll always want to use it like above:: - + Redirecting after the comment post ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/ref/contrib/csrf.txt b/docs/ref/contrib/csrf.txt index ea76fc3739..e635a0380b 100644 --- a/docs/ref/contrib/csrf.txt +++ b/docs/ref/contrib/csrf.txt @@ -49,7 +49,7 @@ To enable CSRF protection for your views, follow these steps: 2. In any template that uses a POST form, use the :ttag:`csrf_token` tag inside the ```` element if the form is for an internal URL, e.g.:: - {% csrf_token %} + {% csrf_token %} This should not be done for POST forms that target external URLs, since that would cause the CSRF token to be leaked, leading to a vulnerability. -- cgit v1.3