Details
-
Improvement
-
Resolution: Not an issue
-
Neutral
-
None
-
None
-
None
-
None
-
Patrick Fehr
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.