#13819: django.conf.urls.i18n must allow param language as GET
-----------------------------------+----------------------------------------
Reporter: anonymous | Owner: nobody
Status: closed | Milestone:
Component: Translations | Version: SVN
Resolution: wontfix | Keywords: i18n, set_language, get,
post
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Changes (by zerok):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
{{{This force to be form (or doing an ajax hack) and it's not possible
with links.}}}
Which is pretty much the point of it. When you change the language you
change the state of the application and therefor this should be handled
using HTTP POST instead of HTTP GET. You don't fetch new data but change
it. If you take a look at the django-users mailinglist, you will see that
this has been discussed quite a lot. Just a few examples:
* http://groups.google.com/group/django-
users/browse_thread/thread/8326ff0a8fef0279/5ec2fe2e3c065524
* http://groups.google.com/group/django-
users/browse_thread/thread/2cab5496ca00ff64/c51971675b2d835d
You can also find some more details in the original ticket: #3651
If you don't like the form approach, you can easily create your own view
that handles the language switch via GET (although that goes against the
specs) or go with solutions like http://code.google.com/p/django-
localeurl/ et al.
--
Ticket URL: <http://code.djangoproject.com/ticket/13819#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
