"is not reflecting the translation in the front end."
So the DeepL thing that you modify to all our pages were useless ? Could you show us what you changed in case we would need to revert back to before ?
The only workaround for us would be to duplicate page for other language and separate, and manually translate it in the builder per language 🙁
I also tried with a new translation from scratch for your new page Bcorp : hidden link
I translated it in French, but the spacing between elements seems not good : hidden link
Finally, perhaps there is a conflitc/bug with Bricks Builder page ? Everything was working before by the way as you can see on all our others pages.
The first issue was not related to the front end actually, it was an issue inside the advanced translation editor, where it did not show the translations that you had before there onvthe right side.
We fixed that issue by the language mapping and the DeepL thing. Nothing to do anymore there as it is fixed and you do not see that problem anymore.
Now the other issue that you correctly identified is that when you edit a translation it does not show int he front end of the website.
As it is now front end, it might be a compatibility issue or not but I am not sure. that is why i asked the second-tier support to take a look.
i am waiting for their answer nd will come back to you as soon as I have news.
"We fixed that issue by the language mapping and the DeepL thing. Nothing to do anymore there as it is fixed and you do not see that problem anymore."
It didn't fix the bug of our empty field and lost translation. With your solution, the empty fill is filled now by the automatic translation by DeepL, not by our lost translations.
"The second tier support asked for a copy of the website. Am I allowed to copy the website to our server for further investigation?"
We do our best here and I understand that it takes a long time.
Now we have an answer for the front end of the website not reflecting the translation and unfortunately this is a bug with Bricks which you use.
We already are in contact with them and they are working to find a solution for this.
For now the only solution is to switch to classic translation editor from the settings which means you can not access the translations you did in advanced translation editor in the first place.
We do not have any other workaround at the moment and waiting for the Bricks developers to provide a solution.
Ok, I see Bricks Builder released a new updated version this week. And I see some WPML fixes in their last version : hidden link
I will try to update the theme and will write here if it's solved or not.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Hello there!
Please watch this video: hidden link
This should explain the automatic translation that was made, why it was made and why the segments were empty BEFORE that translation was made.
In short, you made a few changes on April 5th more or less but back then you only updated the French version. you opened and updated the Dutch and German version only months after, on Oct 7th, when you had received credits from us (we added free credits to everyone back then) and the "automatic translation by default" feature kicked in.
-----------
However, I tested the Advanced Translation Editor on the about us page, on your live site and it did update the content normally.
I wanted to check your revisions of the page to understand better if the info i have matches your site's but it seems you have revisions disabled so I couldn't verify it. however, the video should be very detailed on what happened to that page.
We can check other pages if you want but i suspect one issue that will be recurring is the seopress segments that appear on your site because you started modifying something from the plugin, maybe adding a SEO description or something similar.
Thank you for your video, it was great, thank you.
Yes you're right, now we were able to update the translation of the NL "about us" page, it seems that updating yesterday Bricks Builder from 1.10.3 to 1.11 solved the bug as you can see on their official changelog hidden link
Thank you for disabling the automatic translation.
Now we are still see some empty fields even if these fields was already translated on the website. (See attached file)
I made a short video to show you an example of the archive product page with the empty fields of already translated field (Bricks template => Archive Products main => NL translation ) : hidden link
And I put some images in attached files if you prefer images than videos.
EN: hidden link
NL : hidden link
So I do not know if this bug of missing translations comes from Bricks or WPML.
And to answer your question from your video about OUR STORY svg translations of the about page, don't worry, my customer wanted to keep OUR STORY for all languages. On the other hand, for some other pages that my client wanted to translate SVG, I had applied this code that I had posted on the Bricks forum while waiting for the Bricks team to correct this bug that I reported a long time ago: hidden link
The code was still working on Bricks 1.10.3 but I do not tested yet on Bricks 1.11.
The same thing Alejandro mentioned in the previous video happened on the archive page too.
Original text:
“Nats Rawline is a range of raw, vegan snacks that everyone's crazy about. But above all, it's a highly personal project with the overarching goal of bringing pleasure to people and helping to preserve our mental and physical health as well as our beautiful natural world.”
Current text:
“Nats Rawline offers a range of raw, vegan treats that everyone’s crazy about. More importantly, it’s a deeply personal project with a mission to bring joy to people while supporting both mental and physical well-being, and helping to protect our beautiful natural world.”
"is" changed to "offer" in the original language.
This means that the whole paragraph is changed and the behavior of showing an empty for translation is correct as it is a new paragraph with changed text and it needs your translation.
The changes happened around March 2024 and only the French language actually was translated with the changed Engish content and the other languages were neglected at that time.
That means, as there is no change in the NL version it will still show the previous translation. But as soon as you try to translate NL, it will show the changes as empty as it expects you to give the new translation for the changed English text.
The behavior here is expected and that is how WPML works.
Thanks.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
