[MAGNOLIA-2077] Magnolia admin tags use language from MgnlContext Created: 26/Feb/08  Updated: 17/Mar/09  Resolved: 11/Jun/08

Status: Closed
Project: Magnolia
Component/s: templating
Affects Version/s: 3.5.4
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Philippe Marschall Assignee: Philipp Bärfuss
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

The Magnolia administration tags (<cms:newBar>, <cms:editBar>, <cms:mainBar>) use the language from the Magnolia context for message translation. This is "the language of the page". For example with i18n enabled this is the language extracted from the URL. The language that should be used instead is the language from the current Magnolia user.



 Comments   
Comment by Magnolia International [ 03/Apr/08 ]

todo: verify. if this indeed happens, edit subject: tags use language from AggregationState while they should use the user's language.
(MgnlContext.getLocale() returns the user's locale)

Comment by Philippe Marschall [ 26/May/08 ]

This is a mistake on our side. We set the content language of the Magnolia Context not the Aggregation State.
Can be closed.

Comment by Magnolia International [ 11/Jun/08 ]

(removing fix version, since this is not an issue....)

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