Hey guys,
could you explain this a little bit further? Does it mean I don’t need to duplicate a global block anymore to translate it? Last time your support told me that a global block is an unique id and so it is not translatable.
Thank you.
Hey guys,
could you explain this a little bit further? Does it mean I don’t need to duplicate a global block anymore to translate it? Last time your support told me that a global block is an unique id and so it is not translatable.
Thank you.
I’m sorry about that, it’s not the most descriptive line item. I’ll make a note to adjust it. The problem was that if you used a Global Block in a page, that usage of the Global Block wouldn’t take on the translation of the current page.
Sorry but I have to ask again for clarify:
For example I have a website in german and english and I am using a Global Block to show a book now widget. This Global Block with ID 1 is in german. Right now I have to duplicate this Global Block to translate it and then change the ID to 2 in the english version of a page.
This bug got fixed and the time of creating separate Global Blocks per language its over?! Right? 
Hi @RSMG,
This only adds automatic language switching when a global block is rendered on the builder or on a live page. It will switch to the translation you have created within the builder ( through clicking language flags ).
If there is no translation, it will default to the original copy. So your separated global blocks will not be affected, but make sure they don’t have translations within or they will automatically switch too.
Thanks!