Thanks 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.

Hi guys, any chance of getting back to me about this issue? Please let me know.