#29281: In some cases i18n set_language does not change url language
-------------------------------------+-------------------------------------
Reporter: Nikita Delyukov | Owner: nobody
Type: Bug | Status: closed
Component: | Version: 1.11
Internationalization |
Severity: Normal | Resolution: wontfix
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 Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
From Beda's description I recreated the issue: we set a language (once)
then try to reverse a URL from the old language when setting the language
again. This obviously fails.
Workarounds:
* keeping track of the old language and falling back to try that if the
lookup with the current language fails.
* Signalling across browser tabs that we already changed the language and
adjusting accordingly (???).
Both of these are out of scope for the in-built i18n. (The first would be
possible on a project basis — reimplementing e.g. `set_language` — if it
was deemed cost effective.)
I'm going to close this on that basis.
If a third option presents itself we could re-open/re-assess.
--
Ticket URL: <https://code.djangoproject.com/ticket/29281#comment:7>
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/066.372573eb6cedf2b6c463967fcdaa7de7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
