[MAGNOLIA-2114] Language fallback rules for request per locale? There seems to be an issue with expected language fall back Created: 15/Apr/08  Updated: 23/Jan/13  Resolved: 24/Apr/08

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.5.3, 3.5.4
Fix Version/s: 3.5.5, 3.6

Type: Improvement Priority: Major
Reporter: Tyronne Mae Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

unix/linux/xp


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)
Date of First Response:

 Description   

There seems to be an issue with expected language fall back behaviour relating to the correct language response per locale specific request.

typically a request for content should be returned in the correct language_locale, with the appropriate fall-back mechanism as follows if requested locale not found:

Request --> de_lu ... try to return this language_locale, if not found fall back
de ... try to return this language, if not found fall back
en ( default language ) ... requested lang_locale not found so returning default

currently this is demonstrating incorrect behaviour as follows:

Request --> de_lu ... try to return this language_locale, if not found fall back
de ... FAILS TO CHECK!
en ( default language ) ... just returns default without checking



 Comments   
Comment by Philipp Bracher [ 24/Apr/08 ]
  • added a smarter fallback support
  • added a easier to extend abstract base class
  • added a default implementation for request local support
Generated at Mon Feb 12 03:33:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.