[Resolved] Avada not saving in DE after installing WPML (EN works)
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is unable to save a page using the Avada page builder on the German version of their site after installing WPML. The saving process shows an infinitely rotating icon instead of a success message. Solution:
It was a compatibility issue with the RSS Aggregator plugin. Deactivating it fixed the problem.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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 problem persists, please open a new support ticket with us 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 save a page with my page builder Avada after installing WPML. The issue occurs on the DE version of the page. Here is the link to the page where the issue can be seen: hidden link
Symptoms:
Instead of seeing a green success message after saving, I encounter an infinitely rotating saving process in the top right.
Questions:
Why is the page not saving in DE after installing WPML?
How can I resolve the infinitely rotating saving process issue?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
It looks like you are editing original content.
Can you please confirm if this issue disappears once you disable WPML?
If so, I would like to request temporary access (wp-admin and FTP) to the website to investigate the issue further.
You can find the required fields below the comments section when you log in to leave the next reply. The information you provide is private, meaning only you and I can see and access it.
IMPORTANT
Please be sure to back up your website and database before granting us access.
If you can't see the "wp-admin / FTP" fields, your post and website credentials will be set to "PUBLIC." DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may need to install a plugin called "All In One WP Migration" to create a copy of the website so I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or a copy of the website from your server for this purpose.
If you have any questions about creating such a staging site, you can consult your hosting provider. Please note that WPML must also be registered on this staging site at https://wpml.org/account/websites/.
If you are unable to provide such a copy of the website for testing, please let me know on this ticket.
The private reply form looks like this: hidden link
Click "I still need assistance" the next time you reply.
Video: hidden link
Please note that we are required to request this information individually on each ticket. We are not permitted to access any credentials that were not specifically submitted on this ticket using the private response form.
1.
Please follow the instructions mentioned on this page: https://wpml.org/documentation/support/debugging-wpml/
Then, try to reproduce the issue and check your installation's **wp-content** folder to see if a file named **"debug.log"** was created (it will only be generated if a server error occurs).
If the file was created, please upload it to a platform like **Google Drive** or **Dropbox** (whichever you usually use) and share the link with me (make sure it is publicly accessible) so I can analyze it.
2.
And, if it is possible for you, do the following test to check for compatibility issues?
**IMPORTANT:** Please try this in a staging environment or at least with a backup of your site files and database before continuing.
Disable all plugins except WPML-related and Avada add-ons.
Is the issue resolved with these settings? If so, please reactivate one by one to see which conflicts.
I also did a compatibility check and the bug happens as soon as Avada, WPML and RSS Aggregator are active. As it pops up in debug.log I suspect RSS is doing some things wrong. I'll try to reach their support again, they have not answered me yet.
