Thanks - that is what I am doing. I am starting to think there is a lot of tailor-made code in this solution which is messing with the way Umbraco handles this. I will need to dig deeper.
Thanks - yes looks the same. So not actually only related to "forms" but to any document type.
Note that it does work fine on the live site (ie the labels on the form change language), and also in the "preview" - for example with a url like "site/umbraco/preview/?id=1593&culture=da"; but it does not work when displaying the node in the backoffice (which would be a "nice to have" for the content editors).
Yes, it indeed is nice to have for a content editor, it would be addressed on the roadmap to v17. However, I’m not sure if it will be prioritized immediately.
Umbraco forms multi language
Hi - it is possible to localise texts (eg. field captions) on a form by using the dictionary, and key names like "#FormFieldFirstname".
This works fine when browsing the live site - showing the English, German, or French field captions for example.
But when previewing the page/form, then only the English language texts are displayed. Changing the current language in the backoffice does not help.
What am I doing wrong? The editors want to see the captions in the relevant language in the backoffice preview.
Sure, just add text with # at start #Name will use Name from tranlsations
Thanks - that is what I am doing. I am starting to think there is a lot of tailor-made code in this solution which is messing with the way Umbraco handles this. I will need to dig deeper.
I think you are having the same issue as in here
Issue
Thanks - yes looks the same. So not actually only related to "forms" but to any document type.
Note that it does work fine on the live site (ie the labels on the form change language), and also in the "preview" - for example with a url like "site/umbraco/preview/?id=1593&culture=da"; but it does not work when displaying the node in the backoffice (which would be a "nice to have" for the content editors).
Yes, it indeed is nice to have for a content editor, it would be addressed on the roadmap to v17. However, I’m not sure if it will be prioritized immediately.
is working on a reply...