SOLVED: WPML template element use translated version

JUVO_Justin · October 19, 2023, 12:33pm

It seems that template conditions are not synced correctly between translations.

Also when translating a page that has another template embedded the translated version of that template is not used. Currently, our front page has both german and english translations. Translation works flawless, except for the template. That one keeps in german.

I provided login credentials already via your contact form, but i did not receive an answer or auto reply yet. Maybe i had a typo in there.

charaf · October 19, 2023, 1:55pm

Hi @JUVO_Justin,

Can you please check your spam inbox as I sent you a reply yesterday, which may have been lost.

To reshare my answer here:

I have created an internal ticket to address the templates translations syncing issue. For now you could do it manually just as a temporary workaround.

Regarding the second point, I’m not enitrely sure how feasible it would be to make sure that templates added through the template element get dynamically assigned the correct language but I’ve also created a ticket to investigate this and see if we could provide a solution.

Let me know if you have any questions

JUVO_Justin · October 19, 2023, 4:29pm

Hi @charaf thank you very much for getting back.

For the second option, i see two possible ways that should in theory be relatively easy to achieve.

Inside the code part where you are parsing the widgets on a page, use wpml hooks to check if for the given template a translation exists, if so use the translation id instead of the original one. Of course, this is only an unsophisticated and rough explanation based on some explorations I had in bricks code.
If you do not want to automatically replace the template without giving the user control, simply add templates to the translation control of wpml. I have done the same thing for some shortcodes in other projects. It should be possible to make the “id” of the template widget translatable. I think there even is a way to hide the field by default and make it only vsisible if you search for it in wpml´s translation editor. This way the user can actually control if the original template or the translated version should be rendered

Do you have a rough ETA? Will this be tackled with 1.9.2 release?

charaf · October 20, 2023, 9:27am

Hi @JUVO_Justin,

Yup I think it makes more sense if they get translated automatically if the template has a translation. Otherwise either use the default as a fallback or just don’t render it depending on WPML’s settings for the templates CPT. Though I can’t really provide a concrete ETA, but it won’t be in 1.9.2 as that was just released today.

JUVO_Justin · October 22, 2023, 3:48pm

I am really looking forwards to this “feature/fix” thing

JUVO_Justin · November 9, 2023, 7:49pm

Sorry to bother you again, but we still have this bug which is blocking us from setting a project live. Do you have a rough estimate?

charaf · November 10, 2023, 1:06pm

Hi @JUVO_Justin, sorry I can’t give any promises but it should realistically be included either in the next release or the one after it. As a workaround, you can set the correct template in the translated pages manually which I know is not ideal if you have a large number of these instances or if you’re doing frequent automatic translations.

charaf · November 14, 2023, 2:43pm

Hi @JUVO_Justin,

The template’s auto-translation should be included in the next release (1.9.4) once you translate a page with the translations editor, it will automatically use the translated version of the template element, and if it doesn’t exist, it will use the original as a fallback.

Regarding the template conditions syncing issue, are you still experiencing it? I’m unable to replicate it anymore so I wonder if it was a bug with an earlier version of WPML. Let me know if this is still an issue for you.

timmse · December 8, 2023, 9:46am

Hi Justin,

We’ve fixed this issue in Bricks 1.9.4, now available as a one-click update in your WordPress Dashboard.
Changelog: Bricks 1.9.4 Changelog – Bricks

Please let us know if you are still experiencing issues.

Best regards,
timmse

ardi · December 20, 2023, 10:29am

Hi,
This issue still persists for us . How was this resolved?
We’re using the latest Bricks 1.9.4.

We have the following setup
1.FRONT Page and inside it we use
2. Template elements with conditions for rendering specific language.

Using WPML and the translations are done, but when changing the language, it doesn’t render translated template.
BUT when I open up the template in preview mode and change language there, it works.

ardi · December 20, 2023, 11:07am

Ok I think I figured it out how to use it.
The issue were that

We were waiting on the translations from Translation Service Crowdin for the Specific Page (not template).
Couldn’t create translatable content for a specific Page language

Solution:
Step 1.

Delete (we did this) or complete the translation files in Translation Service (for us it’s Crowdin) for pages which are still in waiting/pending status in WP.
Sync new translations from “Translation Management”
Under WPML → Support → Troubleshooting “Clear the cache in WPML” & “Remove ghost entries from the translation tables”

These steps opened up the possibility to modify the pages for different languages again.
Step 2:

In WP Pages view, Click on the “Add translations to ‘XLang’” , where ‘XLang’ representing whatever language you need. This will open up WPML editor, complete it and the translations should now work when using templates inside of pages.

JUVO_Justin · August 10, 2024, 12:55pm

@charaf and @timmse i still noticed an issue with the template conditions on 1.10 . When translating an archive template with wpml which has a condition to be displayed on a specific term, the term in the original language is copied to the condition of the translation.

This leads to a lot of side effects, including the requirement to manually fix all the conditions and also refixing them after the translation is updated, especially through the automatic translation service.

charaf · August 11, 2024, 9:32am

@JUVO_Justin The current report specifically addresses the template element, so the issue you’re mentioning is unrelated. Regarding the template conditions issue, you’ve already raised this report, and it remains a work in progress: WIP: WPML Individual Exclude Rule not adjusted - #2 by charaf.