[MAGNOLIA-825] Switching locale in mulit-language sites causes locale in AdminCentral to change Created: 25/Apr/06  Updated: 10/Sep/10  Resolved: 10/Sep/10

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 2.1.5
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Andreas Weder Assignee: Philipp Bärfuss
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

n/a


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

I have a multi-language site featuring one root page ("web") and several sub page for each supported language ("web/de", "web/fr"). I've written code to set the locale for the <fmt> tags of JSTL once a user switches the language:

Config.set(request.getSession(), Config.FMT_LOCALE, new Locale(desiredLanguage));

Like this, you may properly use .e.g the date formatting and parsing tags inside the templates

But a call to Config.set() also causes the user language in the AdminCentral interface to switch. If an author e.g. switches to the french language tree, the user language of AdminCentral is also switched to French, since the implementation of AdminCentral uses the same mechanism. The locale settings of AdminCentral and should be separated from the locale settings of the pages it administers.

Is there a standard mechanism for this? Can you define "locale namespaces"?



 Comments   
Comment by Philipp Bracher [ 25/Apr/06 ]

We decided to make the magnolia i18n mechanism in general working the same way as the JSTL one. Well ... we succeeded

Can you set the locale on the request instead of the session? At least in the admin mode.

Generated at Mon Feb 12 03:21:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.