Changes between Initial Version and Version 1 of Ticket #28070


Ignore:
Timestamp:
Apr 12, 2017, 2:29:37 AM (8 years ago)
Author:
Monsieur Cellophane
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #28070 – Description

    initial v1  
    88What this means is that if language selection is made from a language-neutral URL (say /about/), selecting english as language the redirection in set_language will land the user to /en/about.
    99
    10 If - however - a new language selection (say de) is now made from /en/about/, the landing spot will be (again) /en/about, rather than the expected /de/about; the new language is now, however, memorised in the user's session.
     10If - however - a new language selection (say de) is now made from /en/about/, the landing spot will be (again) /en/about, rather than the expected **/de/about**. The new language (de) is now, however, memorised in the user's session.
    1111
    1212**What should happen:**
    13 Invoking set_language from a language prefixed page with an empty next parameter should redirect to the language-neutral URL, allowing the session based url selection to kick in.
     13Invoking set_language from a language prefixed page with an empty ''next'' parameter should redirect to the language-neutral URL, allowing the session based url selection to kick in.
    1414
    1515**What would help:**
    1616
    17 Of course, being able to reference the current language-neutral url as the next parameter to set_language would achieve the result. However,  language-neutral urls aren't availble in templates (or anywhere I looked); so one's best hope is writing a custom template filter that strips the language prefix from a URL and hen use the stripped request.path o request.get_fulL_path as the next parameter to the POST.
     17Of course, being able to reference the current language-neutral url as the ''next'' parameter to set_language would achieve the result. However,  language-neutral urls aren't availble in templates (or anywhere I looked); so one's best hope is writing a custom template filter that strips the language prefix from a URL and hen use the stripped request.path (or request.get_fulL_path) as the ''next'' parameter to the POST.
Back to Top