This thread is resolved. Here is a description of the problem and solution.
Problem: The "AREA RISERVATA" from "Full Menu" shows untranslated in the Front End due to a compatibility issue with dynamic fields from the Lottie widget. Solution: If you're experiencing this issue, we recommend creating a full website backup first. Then, add the following code to your functions.php file:
This solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
I sent your ticket to our development team, to get a second opinion on what the solution can be. As soon as I have a feedback from them, I'll let you know.
Hi Lucas,
I've tried to create another popup, as you can see now, but still the same problem. only the button AREA RISERVATA can't be translated by wpml.
I really can't understand why.
Please help me....
thank you
Hey there, thank you for sharing your results. I'm in touch with our developers, we'll take a more profound look and get back to you as soon as we have new information. Thank you for your patience.
Thank you so much for your patience. We are still investigating, but haven't gotten into anything conclusive yet. We noticed that without the amination JSON file, the issue is not reproducible, but we are still investigating. I'll update you as soon as possible.
Thank you for waiting. We found that the issue was indeed a compatibility issue between, we still don't support dynamic fields from the Lottie widget. As a workaround, please create a full website backup and add the following code to your functions.php file:
only a question, now you've found this "bug" and I think you're gonna fix it in the next WPML update, isn't it?
If so, should I keep this code in the functions.php or it would be better to erase it (of course, only when the update will work perfectly...)?
It's best to keep the code in your functions.php file. Even though it will be fixed in the next releases, we do not have a specific date, so to keep your website working properly, you can keep the code there 🙂