
Tagged: wpml translation avia
-
AuthorPosts
-
August 6, 2025 at 5:40 pm #1487656
Hey I’m working on a multilingual site using Enfold together with WPML, and I’ve run into a frustrating issue regarding translated content not showing up properly.
Here’s the situation:
– I created a page using the Avia Layout Builder (default language: Dutch).
– I translated the page using WPML’s Classic Translation Editor (CTE) to GermanHowever, when I visit the translated page on the front-end, it still shows the original Dutch text — the translated strings aren’t displayed.
Also, when I try to edit the translated page, I don’t see the translated content in the Avia Builder at all — it’s either empty or still shows the original language.What I’ve already tried:
– Re-saving the translation
– Completing the translation again
– Deleting the translation and recreating it
– Clearing all caches (browser, WP, server)No luck so far.
Is this a known limitation when using Avia + WPML?
Is there any way to make Avia load the translated package strings, either in the builder or at least on the front-end?Would really appreciate any insight or tips from other users or the support team. It’s a bit of a blocker at the moment.
Thanks a lot.
August 8, 2025 at 9:38 am #1487730Hi guys, any chance of getting back to me about this issue? Please let me know.
August 11, 2025 at 1:05 pm #1487843Just following up on my message from 6th of august (see above). I haven’t heard back yet, and I’d really appreciate an update on this issue when you get a chance. Thanks a lot.
August 12, 2025 at 4:13 am #1487874Hi,
Apologies for the late response. Did you install the String Translation extension? You will need this WPML extension to properly translate pages created with the Advanced Layout Builder. Please check the following documentation for more information on how to translate using WPML.
— https://wpml.org/tutorials/2016/02/enfold-theme-and-wpml/
— https://kriesi.at/documentation/enfold/translationLet know if you need more info.
Best regards,
IsmaelAugust 12, 2025 at 1:35 pm #1487892Thanks for your reply, Ismael.
Yes, I have the String Translation extension installed, and WPML itself is working fine in the editor. The translations are showing correctly in WPML’s Classic Translation Editor and also in the String Translation interface. I can see that all package strings from the Avia Layout Builder (e.g. package-string-24-1054949) are translated.
However:
– On the front-end, the translated pages still display the original Dutch text instead of the translated text.
– In the Avia Layout Builder for the translated page, I also only see the original Dutch text ( the translated strings aren’t loaded)
– If I switch to the Advanced Translation Editor, I don’t see these translations there at all (they were originally done in the Classic Translation Editor).
—
It seems like the translated package strings from Avia are not being output or loaded for the translated page.
Is there a way to force Avia to load the translated package strings on the front-end and/or in the builder? Or is this a known limitation when switching from Classic Translation Editor to Advanced Translation Editor?Thanks for your help Ismael.
August 13, 2025 at 11:22 am #1487954Hi,
Thank you for the update.
Did you duplicate the page? Please make sure not to duplicate the page and avoid editing it directly using the Advanced Layout Builder. Translate it using the WPML Translation Editor directly, as described in the documentation.
We created a new page and translated it into other languages using the String Translation editor (see private field).
Best regards,
Ismael -
AuthorPosts
- You must be logged in to reply to this topic.