[MAGNOLIA-2888] Using default i18n support with country specific lang codes results in endless loop Created: 09/Oct/09  Updated: 23/Jan/13  Resolved: 26/Feb/10

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.1.1
Fix Version/s: 4.3

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed 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

 Description   

Currently if one uses DefaultI18ContentSupport and specify for example de_DE as a supported locale, but remove the de locale, the DefaultI18nContentSupport will end in the endless loop as soon as it hits the content that doesn't have localized node (e.g. the one with the name pattern name_de_DE).
The work around is to specify a locale without the country subcode for each language_country locale.


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