Hey,
Might be correlated, but created a separate bug ticket for “Form” element placeholder translations. Original post here for issues with translations .
The issue with Form element is as follows:
regarding the automated translations related to not rendering the correct content.
When using Form Element, the texts inside placeholder are not being translated .
The translations have been completed and texts were found , but when switching the language, it’s still in original language.
Hi @ardi,
I’m unable to replicate this issue with the placeholders locally. Could you please share temporary admin access to help@bricksbuilder.io with a link to this forum thread using the same email address you used to purchase Bricks?
Alright,
We’ll send you temporary access from the original purchase email .
Thanks
Hi @ardi,
Thank you for sharing access and all the details 
I was unable to reproduce the issue, but I just noticed that the form element you created is saved as a “global element.” This is likely why the translations are not taking effect, affecting not only the placeholder but also the submit button text. For a global element, this behavior is expected, as any change to that global element affects the entire site.
Since you are creating this form in a section template, is there a need for it to be a global element? If not, I suggest creating a new section template with a form element without setting it as a global element. This approach should resolve the issue.
Let me know how it goes!
I was able to unlink it from Global Element, updated the translations and it works now.
Thank you.
What is the difference between global element and a simple section template ?
Hey ardi,
please have a look at this article: Global Elements – Bricks Academy
Ok, so I understand the template is for multiple elements bundled together and global element is for a single element.
But if a template is translatable what is the reasoning for a global element not to be? Essentially a template is a bundle of global elements.
Just asking out of curiosity and to better understand the framework.
The global element looks the same throughout the entire site. This means that the same text will be applied for all instances of that element. So it’s not a good idea to use it when you’re trying to translate text.
A template on the other hand is a custom post type that can be translated. When a template is translated through WPML a new post gets created for that new translation.
Alright, thanks for the help and the explanations.
Have a blessed day!
@charaf
One more thing , maybe would be a good idea idea to add the note somewhere in the documentation that global elements are not translatable.
Cheers!
