Changeset 5649

Timestamp:

07/11/07 19:33:44 (1 year ago)

Author:

jacob

Message:

Fixed #4615: corrected reverse URL resolution examples in tutorial 4. Thanks for the patch, simeonf.

Files:

• django/trunk/docs/tutorial04.txt (modified) (3 diffs)

django/trunk/docs/tutorial04.txt

@@ -194 +194 @@
-        (r'^$', 'django.views.generic.list_detail.object_list', info_dict),
-        (r'^(?P<object_id>\d+)/$', 'django.views.generic.list_detail.object_detail', info_dict),
-
+, 'poll_results'
-        (r'^(?P<poll_id>\d+)/vote/$', 'mysite.polls.views.vote'),
-    )
@@ -209 +209 @@
-      from the URL to be called ``"object_id"``, so we've changed ``poll_id`` to
-      ``object_id`` for the generic views.
+
+    * We've added a name, ``poll_results``, to the results view so that we have
+      a way to refer to its url later on (see `naming URL patterns`_ for more on
+      named patterns).
+      
+.. _naming URL patterns: http://www.djangoproject.com/documentation/url_dispatch/#naming-url-patterns
-
-By default, the ``object_detail`` generic view uses a template called
@@ -256 +262 @@
-context instead of ``poll``.
-
+The last thing to do is fix the url handling to account for the use of generic
+views. In the vote view above we used the ``reverse()`` function to avoid
+hard-coding our URLs. Now that we've switched to a generic view, we'll need to
+change the ``reverse()`` call to point back to our new generic view. We can't
+simply use the view function anymore -- generic views can be (and are) used
+multiple times -- but we can use the name we've given::
+    
+    return HttpResponseRedirect(reverse('poll_results', args=(p.id,)))
+
-Run the server, and use your new polling app based on generic views.
-