[MGNLDEMO-69] Tours and Destinations text in Nav use wrong i18n mechanism Created: 25/Jun/15  Updated: 15/Apr/16  Resolved: 25/Jun/15

Status: Closed
Project: Magnolia Demo Projects
Component/s: None
Affects Version/s: 0.5
Fix Version/s: 0.6

Type: Bug Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Christopher Zimmermann
Resolution: Fixed Votes: 0
Labels: 541backlog, pm
Remaining Estimate: 1h
Time Spent: Not Specified
Original Estimate: 1h

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
Epic Link: Travel Demo
Sprint: Sprint 2 (Basel)
Story Points: 1

 Description   

The category menu headers "Destinations" and "TourTypes" are translated based on the logged in user's language - rather than website content language.



 Comments   
Comment by Christopher Zimmermann [ 25/Jun/15 ]

Navigation headers for Tours and Destinations now i18n-ized by content locale instead of user locale.

I didn't see a nice way to get the "content locale" from within the model - so the models now simply return the i18n key and the template can translate it with simple usage of i18n[].

Generated at Mon Feb 12 05:15:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.