[1.1.X] Fixed #12205 -- Corrected malformed reference links in the 1.1 and 1.1-alpha release notes, and corrected position of field lookup reference label. Thanks velmont and timo.

Backport of r11988 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@11989 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Gary Wilson Jr 2009-12-26 00:56:40 +00:00
parent a94d7e761f
commit 81f994583c
2 changed files with 13 additions and 11 deletions

View File

@ -85,13 +85,13 @@ Other new features and changes introduced since Django 1.0 include:
* The ``include()`` function in Django URLconf modules can now accept sequences * The ``include()`` function in Django URLconf modules can now accept sequences
of URL patterns (generated by ``patterns()``) in addition to module names. of URL patterns (generated by ``patterns()``) in addition to module names.
* Instances of Django forms (see `the forms overview <topics-forms-index>`_ now * Instances of Django forms (see :ref:`the forms overview <topics-forms-index>`)
have two additional methods, ``hidden_fields()`` and ``visible_fields()``, now have two additional methods, ``hidden_fields()`` and ``visible_fields()``,
which return the list of hidden -- i.e., ``<input type="hidden">`` -- and which return the list of hidden -- i.e., ``<input type="hidden">`` -- and
visible fields on the form, respectively. visible fields on the form, respectively.
* The ``redirect_to`` generic view (see `the generic views documentation * The ``redirect_to`` generic view (see :ref:`the generic views documentation
<ref-generic-views>`_) now accepts an additional keyword argument <ref-generic-views>`) now accepts an additional keyword argument
``permanent``. If ``permanent`` is ``True``, the view will emit an HTTP ``permanent``. If ``permanent`` is ``True``, the view will emit an HTTP
permanent redirect (status code 301). If ``False``, the view will emit an HTTP permanent redirect (status code 301). If ``False``, the view will emit an HTTP
temporary redirect (status code 302). temporary redirect (status code 302).
@ -99,7 +99,8 @@ Other new features and changes introduced since Django 1.0 include:
* A new database lookup type -- ``week_day`` -- has been added for ``DateField`` * A new database lookup type -- ``week_day`` -- has been added for ``DateField``
and ``DateTimeField``. This type of lookup accepts a number between 1 (Sunday) and ``DateTimeField``. This type of lookup accepts a number between 1 (Sunday)
and 7 (Saturday), and returns objects where the field value matches that day and 7 (Saturday), and returns objects where the field value matches that day
of the week. See `the full list of lookup types <field-lookups>`_ for details. of the week. See :ref:`the full list of lookup types <field-lookups>` for
details.
* The ``{% for %}`` tag in Django's template language now accepts an optional * The ``{% for %}`` tag in Django's template language now accepts an optional
``{% empty %}`` clause, to be displayed when ``{% for %}`` is asked to loop ``{% empty %}`` clause, to be displayed when ``{% for %}`` is asked to loop

View File

@ -388,13 +388,13 @@ Other new features and changes introduced since Django 1.0 include:
* The ``include()`` function in Django URLconf modules can now accept sequences * The ``include()`` function in Django URLconf modules can now accept sequences
of URL patterns (generated by ``patterns()``) in addition to module names. of URL patterns (generated by ``patterns()``) in addition to module names.
* Instances of Django forms (see `the forms overview <topics-forms-index>`_ now * Instances of Django forms (see :ref:`the forms overview <topics-forms-index>`)
have two additional methods, ``hidden_fields()`` and ``visible_fields()``, now have two additional methods, ``hidden_fields()`` and ``visible_fields()``,
which return the list of hidden -- i.e., ``<input type="hidden">`` -- and which return the list of hidden -- i.e., ``<input type="hidden">`` -- and
visible fields on the form, respectively. visible fields on the form, respectively.
* The ``redirect_to`` generic view (see `the generic views documentation * The ``redirect_to`` generic view (see :ref:`the generic views documentation
<ref-generic-views>`_) now accepts an additional keyword argument <ref-generic-views>`) now accepts an additional keyword argument
``permanent``. If ``permanent`` is ``True``, the view will emit an HTTP ``permanent``. If ``permanent`` is ``True``, the view will emit an HTTP
permanent redirect (status code 301). If ``False``, the view will emit an HTTP permanent redirect (status code 301). If ``False``, the view will emit an HTTP
temporary redirect (status code 302). temporary redirect (status code 302).
@ -402,7 +402,8 @@ Other new features and changes introduced since Django 1.0 include:
* A new database lookup type -- ``week_day`` -- has been added for ``DateField`` * A new database lookup type -- ``week_day`` -- has been added for ``DateField``
and ``DateTimeField``. This type of lookup accepts a number between 1 (Sunday) and ``DateTimeField``. This type of lookup accepts a number between 1 (Sunday)
and 7 (Saturday), and returns objects where the field value matches that day and 7 (Saturday), and returns objects where the field value matches that day
of the week. See `the full list of lookup types <field-lookups>`_ for details. of the week. See :ref:`the full list of lookup types <field-lookups>` for
details.
* The ``{% for %}`` tag in Django's template language now accepts an optional * The ``{% for %}`` tag in Django's template language now accepts an optional
``{% empty %}`` clause, to be displayed when ``{% for %}`` is asked to loop ``{% empty %}`` clause, to be displayed when ``{% for %}`` is asked to loop