We are still reviewing this for you.As you can imagine this ticket has been escalated the appropriate team and I am simply waiting for their tests to finalize and update you here.
Based on a recent conversation with the team, would you be able to implement object caching, and if yes, does this help at all with the performance you are experiencing?
One of the issues that we discovered (and you confirmed from the logs we sent you), was that due to the sheer amount of auto translations, some translations were stuck in eternal loops.
(Object) caching is not going to solve that!
Can you please focus on what WPML needs to fix in the ATE, instead of sending the client useless suggestions?
Based on our review, the issue seems related to ATE’s segmentation process, potentially combined with site performance limitations.
To move forward, please:
1. Implement object caching if not already done.
2. Provide us with new access or possibly Share a DB dump and a list (or archive) of active plugins so we can continue work on a staging site rather than your live site.
3. Optionally, review and reduce glossary entries if possible.
Once we have those details, we can run additional checks to confirm whether the slowdown originates from ATE or external code.
I have not heard back from the client about giving you renewed superadmin access to the network.
Regarding your points:
re 1) we migrated the network from WP Engine to Kinsta, which has all the bells and whistles when it comes to caching
re 2) in the beginning of this ticket I told you the database is 10mio rows; there is no such thing as a DB dump where you can do anything with. List of (active) plugins you should have already as I shared the Debug Information with you.
re 3) Really?! Now the problem is the Glossary?! It contains 188 entries. Show me published documentation please where it states what an acceptable number is!
You KNOW the slowdown/failure to complete translations originates from the ATE! Please stop insulting our intelligence!
As soon as I hear from the client about whether or not to give you access, I will let you know. It would be helpful though when you can give a specific window of how long you will need access for after the client has given permission.
The ATE team has reviewed this. While it’s not the outcome you hoped for, it’s possible a previous XLIFF-related issue in ATE contributed to the problem. That issue has since been fixed and the update is now live.
We’ve successfully tested several jobs from your site, including validation checks — all passed.
Please try resending the jobs for translation on your end and share your results.
We are abandoning this support thread not because the problem is resolved but because it is moot and our time is valuable and limited.
Client has spoken directly to WPML developer Ivan and he clearly understands that WPML chokes when trying to initiate Translate Everything on a 12,000-post site.
