Fixed #4409 -- Fixed a typo in tutorial (thanks, mitch.hunt.007@gmail.com
). Also updated the reverse() documentation to reflect that it can take function references or strings for function names. git-svn-id: http://code.djangoproject.com/svn/django/trunk@5401 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
9a40cfda16
commit
eb29552b20
|
@ -67,7 +67,7 @@ So let's create a ``vote()`` function in ``mysite/polls/views.py``::
|
|||
# Always return an HttpResponseRedirect after successfully dealing
|
||||
# with POST data. This prevents data from being posted twice if a
|
||||
# user hits the Back button.
|
||||
return HttpResponseRedirect(reverse('results', args=(p.id,)))
|
||||
return HttpResponseRedirect(reverse('mysite.polls.views.results', args=(p.id,)))
|
||||
|
||||
This code includes a few things we haven't covered yet in this tutorial:
|
||||
|
||||
|
@ -104,7 +104,8 @@ This code includes a few things we haven't covered yet in this tutorial:
|
|||
'/polls/3/results/'
|
||||
|
||||
... where the ``3`` is the value of ``p.id``. This redirected URL will
|
||||
then call the ``'results'`` view to display the final page.
|
||||
then call the ``'results'`` view to display the final page. Note that
|
||||
you need to use the full name of the view here (including the prefix).
|
||||
|
||||
For more information about ``reverse()``, see the `URL dispatcher`_
|
||||
documentation.
|
||||
|
|
|
@ -564,10 +564,11 @@ code, Django provides the ``django.core.urlresolvers.reverse()``. The
|
|||
|
||||
reverse(viewname, urlconf=None, args=None, kwargs=None)
|
||||
|
||||
The view name is either the function name or the `URL pattern name`_.
|
||||
Normally you will not need to worry about the ``urlconf`` parameter and will
|
||||
only pass in the positional and keyword arguments to use in the url matching.
|
||||
For example::
|
||||
The view name is either the function name (either a function reference, or the
|
||||
string version of the name, if you used that form in ``urlpatterns``) or the
|
||||
`URL pattern name`_. Normally you will not need to worry about the
|
||||
``urlconf`` parameter and will only pass in the positional and keyword
|
||||
arguments to use in the url matching. For example::
|
||||
|
||||
from django.core.urlresolvers import reverse
|
||||
|
||||
|
|
Loading…
Reference in New Issue