Fixed #18476 - Added use of {% url %} tag to tutorial.

All the poll app cares about is its relative path, not its absolute path.

Removing hardcoded URLs in templates

------------------------------------

Remember, when we wrote the link to a poll in our template, the link was

partially hardcoded like this:

.. code-block:: html+django

    <li><a href="/polls/{{ poll.id }}/">{{ poll.question }}</a></li>

To use the decoupled URLs we've just introduced, replace the hardcoded link

with the :ttag:`url` template tag:

.. code-block:: html+django

    <li><a href="{% url 'polls.views.detail' poll.id %}">{{ poll.question }}</a></li>

When you're comfortable with writing views, read :doc:`part 4 of this tutorial

</intro/tutorial04>` to learn about simple form processing and generic views.

    {% if error_message %}<p><strong>{{ error_message }}</strong></p>{% endif %}

    <form action="/polls/{{ poll.id }}/vote/" method="post">

    <form action="{% url 'polls.views.vote' poll.id %}" method="post">

    {% csrf_token %}

    {% for choice in poll.choice_set.all %}

        <input type="radio" name="choice" id="choice{{ forloop.counter }}" value="{{ choice.id }}" />

  selects one of the radio buttons and submits the form, it'll send the

  POST data ``choice=3``. This is HTML Forms 101.

* We set the form's ``action`` to ``/polls/{{ poll.id }}/vote/``, and we

* We set the form's ``action`` to ``{% url 'polls.views.vote' poll.id %}``, and we

  set ``method="post"``. Using ``method="post"`` (as opposed to

  ``method="get"``) is very important, because the act of submitting this

  form will alter data server-side. Whenever you create a form that alters

    {% endfor %}

    </ul>

    <a href="/polls/{{ poll.id }}/">Vote again?</a>

    <a href="{% url 'polls.views.detail' poll.id %}">Vote again?</a>

Now, go to ``/polls/1/`` in your browser and vote in the poll. You should see a

results page that gets updated each time you vote. If you submit the form

            ListView.as_view(

                queryset=Poll.objects.order_by('-pub_date')[:5],

                context_object_name='latest_poll_list',

                template_name='polls/index.html')),

                template_name='polls/index.html'),

            name='poll_index'),

        url(r'^(?P<pk>\d+)/$',

            DetailView.as_view(

                model=Poll,

                template_name='polls/detail.html')),

                template_name='polls/detail.html'),

            name='poll_detail'),

        url(r'^(?P<pk>\d+)/results/$',

            DetailView.as_view(

                model=Poll,

  ``"pk"``, so we've changed ``poll_id`` to ``pk`` 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 the

* We've added the ``name`` argument to the views (e.g. ``name='poll_results'``)

  so that we have a way to refer to their URL later on (see the

  documentation about :ref:`naming URL patterns

  <naming-url-patterns>` for information). We're also using the

  :func:`~django.conf.urls.url` function from

    return HttpResponseRedirect(reverse('poll_results', args=(p.id,)))

The same rule apply for the :ttag:`url` template tag. For example in the

``results.html`` template:

.. code-block:: html+django

    <a href="{% url 'poll_detail' poll.id %}">Vote again?</a>

Run the server, and use your new polling app based on generic views.

For full details on generic views, see the :doc:`generic views documentation