#26556: set_language with i18n_patterns doesn't work all the time
-------------------------------------+-------------------------------------
Reporter: hchargois | Owner: nobody
Type: Bug | Status: new
Component: | Version: 1.9
Internationalization |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
The description makes sense. (I didn't attempt to reproduce.)
The reason why set_language shouldn't be in i18n_patterns is discussed in
#18472:
> I've seen people get confused by including the `set_language` URL within
their `i18n_patterns` and wondering why it doesn't work (the form `POST`
turns into a redirected `GET` request which fails); we should probably add
a warning to ensure that this URL is locale-independent
(There's nothing else about this issue in that ticket.)
--
Ticket URL: <https://code.djangoproject.com/ticket/26556#comment:1>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.2d7453b753ba8747644f5bc45d6b0813%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
