[DOCU-2854] Default/Fallback Language should be a pointer, not a separate field Created: 27/Sep/23 Updated: 27/Sep/23 Resolved: 27/Sep/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Patrick Fehr | Assignee: | Unassigned |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Reporter Name: | Patrick Fehr |
| Email: | patrick.fehr@quatico.com |
| Description |
|
We use i18n. A page(node) can be edited/shown in multiple languages. However, we have the use case that the default/fallback language can change for a node and its children. This leads to unintended consequences. Dialogs are empty or contain the wrong language values. Visitors see a particular language version in the wrong language.
The reason is simple: Magnolia uses a concept of a fallback/default language. It can(should) not be changed. The node name itself is stored in this default language.
This improvement suggest to change this so that the "default language" is not a separate field but indeed a pointer to one of the language versions. This would make it easy to change the default langauge for any node/children. It would separate concerns and avoid unintended consequences.
Since this is a deeply rooted architectural decision, I am sceptical about the success of tis ticket, however. |
| Comments |
| Comment by Jonathan Ayala [ 27/Sep/23 ] |
|
Hi patrick.fehr, Thanks a lot for sharing your proposal for improvement. Unfortunately, this is not the appropriate channel to raise this kind of requests. Instead, you can submit your idea by following our standard procedure. Regards, |