WPML String Translation creates conflict with Avada options

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing issues with the WPML String Translation plugin, which disrupts the CSS and affects the display of Avada options in the backend.
Solution:
We recommend checking if the Avada parent theme, Avada Core, and Avada Builder plugins are updated to their latest versions. If after updating, the problem still persists, it might be helpful to check for conflicts with other plugins. Updating all plugins can resolve such issues. If the issue continues, we suggest providing access to your site for further investigation. Please ensure to back up your site files and database before providing access. For more details on privacy and security, visit our privacy and security policy.

If this solution does not apply to your case, or if it seems outdated, please check the 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 for further assistance 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.

Tagged: Compatibility

This topic contains 3 replies, has 0 voices.

Last updated by aurelienJ-2 6 months, 3 weeks ago.

Assisted by: Itamar.

Author	Posts
December 1, 2024 at 3:32 pm #16463371
aurelienJ-2	Background of the issue: I am trying to access Avada options, but the WPML String Translation plugin is causing issues. Symptoms: When the WPML String Translation plugin is activated, it messes up the CSS completely, affecting the display of Avada options in the backend. Questions: What's the issue? I've never seen this on any other clients' websites. We need to be able to view the Avada options correctly. Thanks in advance for your help,
December 1, 2024 at 9:06 pm #16463736
Itamar WPML Supporter since 02/2016 Languages: English (English ) Timezone: Asia/Jerusalem (GMT+03:00)	Hi, We suspect a collision with the theme or another plugin might cause this problem. If possible, get your site into a minimum environment, switching to the parent Avada theme and having no plugins activated except WPML. First, you must check if the problem persists when just the theme is switched to the Avada parent theme. If it persists, deactivate all plugins except WPML, its add-ons, and the Avada plugins (Avada Core and Avada Builder). Then, please check if the problem persists. If it does not persist, start by activating the plugins individually and checking when the issue comes back, then report to me which plugin was the culprit. ** Important! Please make a full site backup (files and DB) before you proceed with those steps * If your site is live, you might want to try those procedures in a staging environment or a snapshot of your site on your local server or another server. *** Regards, Itamar.
December 1, 2024 at 9:54 pm #16463765
aurelienJ-2	Hi Itamar, I've tried the troubleshooting steps you've mentioned but your "WPML String Translation" still creates this conflict, only with the Avada > Options. What solutions do we have?
December 2, 2024 at 8:38 am #16464570
Itamar WPML Supporter since 02/2016 Languages: English (English ) Timezone: Asia/Jerusalem (GMT+03:00)	Hi, and thanks for trying my suggestions. What about Avada's parent theme? Has it been updated to its latest version? The same question applies to the Avada Core and Avada Builder plugins. Have they been updated to the latest versions? If so, and the problem persists, please share access to your site so I can investigate further. I'm enabling a private message for the following reply. Privacy and Security Policy We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ IMPORTANT - - Please backup the site files and database before providing us access. -- -- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.-- Regards, Itamar.
December 2, 2024 at 9:49 am #16464952
aurelienJ-2	Looks like it may have been another conflict somewhere as updating all remaining plugins seems to have fixed it. Thanks for your help!