Hey,
I’m having an issue using translations (WPML plugin) with Bricks Builder on Front Landing Page.
Other templates and pages work fine when selecting different languages that have been translated, but only on the front landing page (I’ve included 2 section templates there) the language switcher doesn’t render the content. It’s just blank. No errors in the console. No log errors that I found from debug.
Header/Footer are translated… also when opening up the templates individually and changing the language, the content is being rendered.
For templates, I’ve added conditions to be displayed on entire website.
On front landing page, I’m displaying those templates based on selected language (e.g. Current URL does not contain ‘lang=de’ ).
Also tried removing the conditions, but didn’t help.
I don’t know what to try or check as I’ve tried to finish all the steps from WPML translations side and other templates & pages are displaying everything properly.
Picture illustrate what I see on default front landing page and when I select another language that has been already translated, like ‘lang=et’ .
After playing around and trying different options I found a solution was to Select Different Language from Admin Dashboard header.
Only there, I could open up the Front Landing page for the specific language and then I had to insert the wanted template in the editor and find the correct template language reference…
This is confusing because this action wasn’t required for other pages. Those were automatically translated and selected in whatever language I switched to.
The question is why did Bricks or WPML create different language translations and pages for other pages(and templates included) and not for the front landing page ?
Hey,
Additional information thanks to WPML team.
I managed to get the pages automatically rendered, but I had to add at least 1 string on the page (additionally to the existing templates) for it to work (to generate & display translated templates when switching language).
Steps to bypass the bug:
I added a Heading element for base language view.
Sent and finished translation jobs (in Crowdin)
Set Heading element to ‘display: none’.
Now switching to a new language works without having to generate the language page manually.
So the issue is as I described, not being able to render translated template content on page if no other elements are present on the page.
Is this something Bricks team could look into ? Seems like a bug on Bricks side.
Hey,
Another find 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.
I was able to reproduce the same issue and have created a task to tackle this.