Same here. I am pulling my hair now:(
Does anyone know if they work with other translation plugins or is this an issue with all?
Hello @charaf, can you give an update on the status of this issue? It seems many people are waiting for components to be translatable.
The fact that they are not, holds me back from using components at all:
- I cannot use them in multi-lingual projects as they are not translatable.
- For single language projects it is too big of a risk to use them, in case the client decides to make the site multi-lingual at a later moment.
In effect this makes components completely useless to me.
3 Likes
Is there any progress on this issue? We still canât use components on multilingual sites.
3 Likes
This is a much needed feature. Any ETA?
1 Like
Been waiting for WPML compatibility for Components since the beginning of the year. Any update on this ?
1 Like
Assuming no surprises, this should be ready for 2.1-stable
4 Likes
We fixed this issue in Bricks 2.1, now available as a one-click update in your WordPress Dashboard.
Please take your time to read the changelog entry before updating: Bricks 2.1 Changelog â Bricks + Bricks 2.1-beta Changelog â Bricks, and let us know if you continue to experience issues.
3 Likes
I have just tested it: GREAT!
that´s great, thank you!!
1 Like
Hi Sara, could you share where you found components translation? I updated to 2.1, but looked through everywhere and couldnât find my components anywhere. Thanks!
Hi @karinavsl! I duplicated an existing page and created a component from a section as a test. I also created properties and inserted text. Then I published the page and opened the translation. The test texts were there to be translated. Hope that helps! Otherwise, write me again!
1 Like
Hi @karinavsl,
You should be able to find this new âBricks componentsâ section in the Translation Dashboard:
If youâre unable to find it, please edit one of your components and re-save the builder then check again.
4 Likes
Thanks! Editing and saving it did the trick, before it wouldnât appear in WPML.
1 Like
Sorry for possible necro posting,
I have a component that the editors can supply with their own text using component properties.
How are the texts that they entered translatable i can only find the placeholder/default texts in the translation dashboard.
Hi @Odinn_k,
You should be able to translate the component instance property values when translating the page itself, since theyâre stored on the page, not globally. Let me know if youâre having issues with that!
i have tried a lot at the same time (very scientific), but i think this was the solution
i added a wpml-config.xml to my child theme with this as content:
<gutenberg-blocks>
<!-- multiple of these for each block -->
<gutenberg-block type="bricks-components/[ID OF COMPONENT]" translate="1">
<key name="properties">
<key name="*" />
</key>
</gutenberg-block>
</gutenberg-blocks>
<!-- 2) Bricks component definitions stored in wp_options (option_name: bricks_components) -->
<admin-texts>
<key name="bricks_components">
<key name="*">
<key name="category" />
<key name="desc" />
<key name="elements">
<key name="*">
<key name="label" />
<key name="settings">
<key name="text" />
<key name="suffix" />
</key>
</key>
</key>
<key name="properties">
<key name="*">
<key name="label" />
<key name="default" />
<key name="options">
<key name="*">
<key name="label" />
</key>
</key>
</key>
</key>
<key name="propertyGroups">
<key name="*">
<key name="name" />
</key>
</key>
</key>
</key>
</admin-texts>
Oh, I see what you mean now, so the issue youâre referring to was regarding components as blocks instance property values (I think I saw you mention this on Discord). Thatâs a bug 
, I have added this to our bug tracker so we can tackle it for the 2.2 stable release.
1 Like