[PAGES-150] Pages app fails after i18n changes Created: 13/Nov/17  Updated: 11/Mar/21  Resolved: 11/Mar/21

Status: Closed
Project: Magnolia pages module
Component/s: Pages app
Affects Version/s: 5.5
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Jan Schulte Assignee: Unassigned
Resolution: Obsolete Votes: 1
Labels: maintenance
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   

If a site is copied and gets a different i18n settings then the wrong language version is displayed on content edit.

Problem reproduction:

  1. Context Travel-Demo
  2. Duplicate the travel site in pages app
  3. Duplicate the travel site definition, adopt /travel/mappings/website@handlePrefix to travel0
  4. Change /travel0/i18n@fallbackLocale to de
  5. Edit /travel0/about

Result
The page itself is rendered in german. If a component is edited then english content is displayed. If the language is changed to eng then no content is displayed at all.

How to fix this:

BasicTransformer.deriveLocaleAwareName decides which locale should be used. This can't be overwritten.
To solve this simply move the logic into i18NAuthoringSupport.deriveLocalisedPropertyName


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