why is ate so painstakingly slow?

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.

Tagged: ATE

This topic contains 10 replies, has 2 voices.

Last updated by Waqas Bin Hasan 11 months ago.

Assisted by: Waqas Bin Hasan.

Author	Posts
January 18, 2024 at 7:43 am
bjornL-7	why is ate so painstakingly slow? It takes forever to open up the advanced editor..
January 18, 2024 at 8:43 am
January 18, 2024 at 12:21 pm #15199647
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for your patience and cooperation. 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? 3) Check this guide https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/#how-do-i-check-the-installer-support-log-for-errors, enable debugging or check your server logs for any related errors (see the error table for details in this guide). Please let me know and I'll further investigate for the issue.
January 18, 2024 at 2:31 pm #15200527
bjornL-7	Hi, 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. 2. I have no idea what this means, but I think a previous support ticket might be relevant: https://wpml.org/forums/topic/this-site-has-moved-to-a-new-location-14/ 3. I'm sure you can see this yourself as you have login credentials to our staging site? hidden link
January 19, 2024 at 6:19 am #15202966
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for the updates. I am working on this and 'll get back to you as soon as I find something or have a solution.
January 19, 2024 at 1:28 pm
January 22, 2024 at 8:17 am #15209712
bjornL-7	Migration has been started (from our staging site to Cloudways). Will let you know when it has been completed.
January 22, 2024 at 9:20 am #15210014
bjornL-7	Migration has now been completed.
January 22, 2024 at 12:26 pm #15211286
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for the updates. I am working on it and 'll get back to you accordingly.
January 23, 2024 at 8:01 am #15214496
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for your patience and cooperation. I was able to reproduce the same issue on the CW site, even with my own site-key. I've escalated the matter to our 2nd tier team for investigation, I'll update you as soon as there's a progress.
January 23, 2024 at 9:31 am #15215148
bjornL-7	Thank you. Looking forward to a solution.
February 1, 2024 at 5:24 am #15252807
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for your patience. I just wanted to update you that our 2nd tier team has investigated the issue in much detail and have further escalated the issue to our dev team. I'll update you as soon as there's more progress.
February 1, 2024 at 12:14 pm #15254819
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for your patience and cooperation. 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. Please let me know.