[Resolved] Avada Element not translated and WPML caused design bugs
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is using the Avada theme with WPML to translate elements like the Container Pricing Table and a Flip Box. The elements are not translated correctly, and the English version displays different colors than the German original. Additionally, there were issues with accessing the backend after changing global settings, which were related to the hosting policy rather than WPML. Solution: We recommended creating a custom XML configuration to ensure that texts from custom Avada elements appear in the WPML translation editor. This solution focuses on text translation and should not affect styling. For more details on setting up the XML configuration, visit WPML documentation on maintaining Fusion Builder and Avada compatibility. For the issues related to backend access, we advised checking with the hosting provider as it seems to be a policy issue from their side, not related to WPML or Avada.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if problems persist. For further assistance, you can also visit the 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.
Background of the issue:
I am using the Avada theme with WPML to translate elements like the Container Pricing Table from Avada Studio and a Flip Box. I want these elements to be translated and maintain the same design as the original German version. Here is the link to the page where the issue can be seen: hidden link
Symptoms:
The Avada elements are not translated, and the English translation has different colors than the German original. Deactivating WPML to adjust colors manually did not work, and re-enabling WPML caused the site to malfunction, requiring a backup restoration.
Questions:
How can I translate the Avada elements without manually bypassing WPML?
But this is for the texts only and should not interfere with styling.
That being said, on this sandbox: hidden link
Can you install these Avada Studio elements, add simple columns (with the minimum amount of content) and these flip boxes on a page and translate, does anything appear in the translation editor? Also, does the styling still fail or it matches the original?
Hi Bruno
I added the elements in the sandbox sample page and there the translation AND the design are ok/it matches the original. hidden link hidden link
I think I have found an error, why the pricing table was'nt translated: I had saved the Avada container with the pricing table as a global element - maybe that was a problem. After I had set it to “not global” in the German version, the texts were displayed in the WPML translation pipeline and I was able to translate them there. After deleting the cache, it appeared translated in the frontend/live Website.
But in the English version the colors of two of the buttons have changed now from orange to grey and they are no longer 3d but flat. A few days ago I changed the colors of the German version in the global settings. This was not possible with the English version because of WPML. Could this have something to do with it? But why should the translation change the shape of the button? Please see here: hidden link
Addendum/emergency: After I just changed the global settings (color) for the “Flipbox” element in the German version, everything blew up in my face. I no longer have “Access denied by security police” access to the entire page. I can't even get into the backend/dashboard anymore. Could this have something to do with WPML (because there have always been problems with global settings and WPML)? What can I do? Help me.
It looks like a policy from hosting is causing some issue, please check with them. No WPML / Avada should not cause such issue or changing any option from them.
Once it is solved let me know and we can continue to help on the issue with Avada element not being correct translated.
Hello there
The problem with the hoster has been solved. Most of the other issues concerning Avada with WPML could also be fixed somehow.
Now I have the following final questions:
1. If, after the translations are done, I still have changes to the pages - both the translated pages and the original, such as correcting spacing, padding/margin as well as color adjustments and layout changes/elements-swapped. Are there any complications with WPML if I work directly on the translated pages (without changing the text)?
2. WP Forms is not translated.
3. Elements with mouse hover are not translated on the back (button with hover text)
4. With automatic translation, the “you” form (formal) is always used, although I have set “formal”. How can I change this? I always have to manually revise all automatic translations.
Since we limit 1 issue per ticket, can you please open new ticket / chat for other issue and we will be glad to help out. I would open it for you and take, but I am afraid I will not be able to handle it anytime soon.
1) Yes, you should not mix translation methods, as it may cause content to be lost / overwrite. If you wish to do manual adjustment you need to make switch to WordPress editor, as explained in our docs and continue to use that method.
