#29281: In some cases i18n set_language does not change url language
     Reporter:  Nikita Delyukov      |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:                       |                  Version:  1.11
  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 Beda Kosata):

 * status:  closed => new
 * resolution:  needsinfo =>



 I have been bitten by the same issue and I think I have found the culprit
 or at least a way to reproduce the error. The trick is having two
 windows/tabs open with the same website and then changing the language in
 one of them.

 The page in the active window is properly redirected to the new language
 version. However, trying to do the same in the other tab no longer works.
 The reason is that the code that tries to find if the URL should be
 rewritten ({{{translate_url}}}) uses {{{resolve}}} to try to find the
 matching URL, but because the language has been already changed in the
 session, it does not match the original URL and no translation is done.

 I hope this is enough information to have the issue reopened. Otherwise I
 would be happy to provide more info if needed.


Ticket URL: <https://code.djangoproject.com/ticket/29281#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to