Ideas
Give us your best ideas!
Give us your best ideas!
Give us your best ideas!
In Litium for the language configuration we have the ability to add fallbacks. This is only really used for backoffice and not use in any way for the content.
However if every field could have a configuration switch called "languageFallback" as a boolean value. Then we could on a field level control if the field should fallback if it is not set.
This might not really be possible and might need significant changes to Litium as we don't have a way to "reset" a field to it's default value on a content item. However this would be really nice as most other content platforms allow for language fallbacks.
Absolutely, we have a case where the editor wants to fallback fields on a page.
For example we have a text field which is culture specific. So the editor can add text in different languages. But in cases where they don't have translated texts yet or do not have them at all they want to show the text from a fallback language.
For example a German site that has a page but are missing some fields and would like them to fallback to its primary fallback, which is English. So the text is displayed in English for the user.
It would be great if the field could have an option to toggle this behaviour, as it might not be good if it is always the case, but only in specific cases where the editor wants fallback. (or maybe something in backoffice that can fallback the value of the field if the editor wants it to take the value from the fallback language).
Hi,
Thanks for your feedback!
Can you describe the need more in detail. Is the need to be able to fallback to another language on the public site for certain fields, or is it for the backoffice?