[MAGNOLIA-6431] Fallback locale must not be saved differently to other languages Created: 03/Nov/15  Updated: 04/Mar/19

Status: Open
Project: Magnolia
Component/s: i18n
Affects Version/s: 5.4
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Lars Fischer Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: i18n
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File i18n_1.png     PNG File i18n_2.png    
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   

The fallback language taken from the site confguration in a single tree setup is saved in a different way in JCR compared to the other available languages.

Translated items in the fallback language are stored without underscore while other languages have one:

This leads to all kinds of problems:

  • if the default / fallback language is ever changed, saved data in the tree are not adjusted so it moves into an inconsitent state
  • the content translation tool fails because it shows text in the wrong column
  • you possibly cannot reuse translated nodes in other trees depending on the language configuration for the tree


Generated at Mon Feb 12 04:14:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.