Background of the issue:
I want to be able to trust in WPML to translate Bricks Builder sites. I tried translation via the regular translation manager, but I found that some parts of Bricks are not really supported yet. Components are not yet supported at all. Bricks just launched components, which I wanted to use but couldn't, because the contents were not up for translation. So I unlinked them and went back to normal Sections. I am using Fluent Forms which is not really translatable, so I created two forms, one for every language. I wanted to translate the shortcode - element (Bricks native element) but that also was not translatable. I also couldn't find any of the above content in String Translation. So I had to switch the sites to be translated in WordPress (in Bricks itself). All that worked out fine for this small site. I don't really need an answer to this or any follow up. Just wanted to let you know about missing compatibility in hopes of future changes.
Symptoms:
Some parts of Bricks Builder are not supported for translation by WPML, including components and Fluent Forms. Shortcode elements are also not translatable.
Just following up on our earlier chat — it looks like you might not have seen my previous messages.
I understand you weren’t expecting a response, but since you’ve raised important points regarding Bricks components, Fluent Forms, and shortcode elements, it would really help if you could share more details with us in the forum thread. This way, we can involve our compatibility team and work with the developers to improve support for these features in WPML.
We rely on feedback like yours to keep things working smoothly, especially after new feature releases.
Thanks again for taking the time to share your experience — looking forward to your input!
hi @lucas, I created a video showing my current pains with Bricks and WPML. This is one of the first bricks sites I am attempting to translate and it's a very small one. So right now there's two bigger things:
- I need the "shortcode" element to be translatable
- It would be nice if you could offer translation for components, as they will probably not go away in the future.
hidden link
If you have any more questions or need admin access to that demo site, let me know.
Regards
Anja
Thank you so much for sharing the details. Shortcodes are, in theory, translatable by WPML, but since it's inserted via Bricks Builder, it's likely that it's not possible at the moment, or that it requires a workaround. We'll check that.
I have a couple more things to ask you, before proceeding:
1. Have you made contact with Bricks Builder authors regarding this issue? If so, please share their answer here;
2. Access to your website.
I would like to look at this directly on your site. For this I would need temporary access (WP-Admin and FTP) to your site, preferably to a test/staging site where the problem has been replicated if possible.
The required fields can be found below the comments section. The information you enter is private, i.e. only you and I can see it and have access to it.
I may need to replicate your website locally. To do this, I need to temporarily install a plugin called "Duplicator" or "All in One WP Migration" on your website. This will allow me to create a copy of your website and content. Once the issue is resolved, I will delete the local website. Let me know if this works for you.
IMPORTANT
Please make a backup copy of the site files and database before giving us access.
- If you do not see the wp-admin/FTP fields, this means your post and site login details are being made PUBLIC. DO NOT post your website details if you do not see the required wp-admin/FTP fields. If you do not, ask me to enable the private box. The private box looks like this:
Thank you Lucas,
sorry it took me so long. I had to find out that the host for my demo site does not allow me to create multiple ftp users to give specific access.
So thank you very much for looking further into it and creating that sandbox site.
I have installed Bricks and Fluent forms and added some content to the front page (sample page).
It now consists of a component (purple header) and a shortcode with the form.
That should recreate my problem.
Thanks again for being so patient and for checking it out!
If you need me to do anything else, let me know.
Thank you so much for your cooperation. I've sent the Sandbox to our compatibility team and will keep you updated. Please note that it might take a few weeks to get this sorted out. Usually it doesn't take that long.
Just to give you an update, we've already reached out to Bricks Builder's Authors, and we are working together on making the new features WPML compatible. We still don't have a good workaround for the time being. I'll keep you updated.
