This thread is resolved. Here is a description of the problem and solution.
Problem: The client was experiencing slow performance when opening the Advanced Translation Editor (ATE).
Solution: We identified that the issue was due to some duplicated records in the Translation Memory. We removed these records to resolve the problem. We recommend the client to clear all caches and cancel any existing jobs, then check the performance on the live site.
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, we encourage you to open a new support ticket. We also highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please contact us through 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.
I deactivated most of the plugins and switched theme to Avada (parent). I also updated WPML plugins to the latest and now ATE isn't loading for me at all.
I suspect a few things, can you please explain and fix:
1) Unregister WPML from this staging site and register again. There's a problem connecting to WPML and site key isn't matching.
2) See the attached image and let me know what is this? I never seen something like that. Is this not a real staging site but an alias of the live site? In this case, as per my understanding, if I am doing anything on the staging is affecting the live site also? And this could also be a reason for direct communication between your site and WPML servers?
1. Done. I had (as per the suggestion of wpml support) hard coded the live site-key in the wp-config.php file according to this guide: https://wpml.org/faq/automatic-wpml-registration-using-php-for-easy-moves-between-production-development-and-staging/ . This was previously done because we had major issues with ate when we pushed live to staging, and also pushed staging to live.
I have now removed that line from wp-config.php and added a new site key for the staging site.
Our team has fixed the problem, there seemed to be "some duplicated records in the Translation Memory", which we've removed and it should be working fine now.
I've checked in your dev/staging site, please check in your live site, by clearing all caches and canceling any existing jobs.