Changes between Version 125 and Version 126 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
09/14/07 02:39:02 (7 years ago)
Author:
mtredinnick
Comment:

Added set-language change.

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v125 v126  
    3737 * [6057] Sept. 6, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#archive_yeargenericviewnolongerperformsanorder_byonthepassedqueryset archive_year generic view no longer performs an order_by() on the passed queryset]
    3838 * [6075] Sept. 9, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#django-admin.pyandmanage.pynowrequiresubcommandstoprecedeoptions django-admin.py and manage.py now require subcommands to precede options]
    39 
     39 * [6177] Sept. 14, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#django.views.i18n.set_languagerequiresaPOSTrequest django.views.i18n.set-language requires a POST request]
    4040
    4141== Database constraint names changed ==
     
    374374Now, options must come after the subcommand:
    375375{{{django-admin.py runserver --settings=foo.bar}}}
     376
     377== django.views.i18n.set_language requires a POST request ==
     378
     379In [6177], the {{{set_language()}}} view was changed to only change the caller's locale if called as a POST request. Previously, a GET request was used. The old behaviour meant that state (the locale used to display the site) could be changed by a GET request, which is against the HTTP specification's recommendations.
     380
     381Code calling this view must ensure that a POST request is now made, instead of a GET. This means you can no longer use a link to access the view, but must use a form submission of some kind (e.g. a button).
Back to Top