[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:
Result How to fix this: BasicTransformer.deriveLocaleAwareName decides which locale should be used. This can't be overwritten. |