[Resolved] WPML Multilingual CMS not working with Elemento V3.26
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with the Elementor editor becoming unusable after updating to version 3.26 when WPML Multilingual CMS is active. Additionally, toggling WPML on and off results in the creation of new articles, complicating troubleshooting. Solution: We recommend reverting your website to a recent backup before proceeding with any changes. Once restored, update all Elementor plugins and ensure that any WPML beta versions are removed. Install the production version of WPML. Here are the steps: 1. Go to WP > Plugins. 2. Deactivate WPML and then reactivate it. 3. Check if the issue with Elementor persists and if new articles are still being created unexpectedly. If the problem continues, it might be due to outdated information or a unique case not covered by this solution. 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 these steps do not resolve the issue, please open a new support ticket at WPML support forum for further assistance.
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 trying to update the Elementor plugin to V3.26, but the Elementor editor becomes unusable. Elementor support identified WPML Multilingual CMS as the cause and suggested contacting WPML for a fix. They also mentioned that I could open an issue on their Github account (hidden link) for further assistance. Additionally, when I turn the WPML Multilingual CMS plugin off and then on, it creates new articles, increasing the count from 365 to 452 (French articles in the English panel), which complicates troubleshooting.
Symptoms:
The Elementor editor bugs and cannot be used after updating to V3.26. Turning WPML Multilingual CMS off and on creates new articles, increasing the count unexpectedly.
Questions:
How can I fix the compatibility issue between WPML Multilingual CMS and Elementor V3.26?
Why does turning WPML Multilingual CMS off and on create new articles?
Switching the WPML plugin on and off will not create duplicates. It could be caused by a conflict with another plugin.
I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.
Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.
Your upcoming reply will be treated with confidentiality and will only be visible to you and me.
✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.
I can see the issue now. Could you please revert the Website to your backup? Then, update all Elementor plugins and remove all WPML beta versions. Then, install the production version as shown in the attached screenshot.
Go to WP > Plugins > Deactivate WPML and reactivate the plugin. Check and see if the issue persists.
I did what you said and with the production version of WPML, Elementor V3.26 works fine.
However, as I had to deactivate WPML, it created 87 new articles in the English version (even though the articles are French or English).
I found them and deleted them manually. To be sure that everything was working properly, I then deactivated and reactivated WPML Multilingual CMS. And all seems working fine now. No new articles were automatically created.
I will stay in production version from now on to avoid such problems in the future,
Alright then, I will keep this ticket open for a couple of days to see if the issue comes back. If everything works well as a couple of days, feel free to mark this ticket as resolved.
