Actually I have discussed with my team management they said at this position we can't provide you the staging or live site access as we already provided you all the required information, if possible what your team found please share with us so we can review and check at our end?
Can i disable ate jobs status. I dont want want to track status of jobs, I think it will help to minimize the queries and php execution.
Note: We are using duplicate translations on single posts edit page. Once user create parent post then they will create duplicate translations by checked all languages and process the duplication. instead of using wpml translation editors, we are using wordpress default post editor.
Let me update asap and suggest any idea to reduce execution & sql queries.
As I already mentioned, the issue has been escalated to our developers and will be fixed in future versions of our plugins. I'll let you know when the fix is included in a new version. That said, the issue that has been escalated seems to be the same issue that you are experiencing, but we cannot be certain for sure because you didn't provide all the information we needed.
I presented your question to our second-tier supporter and will update you once I have his reply.
First, I don't think there is a way of disabling just the status tracking. Perhaps if you disable the use of Advanced Translation Editor, it will stop checking, but the same applies if all jobs are translated, and no new jobs are sent to ATE or expected to be translated.
You mentioned that you are using native editor and duplication, so it makes no sense that ATE is running, and we don't believe that this issue is because of ATE.
And so, we think that the query that you mentioned is more generic in nature, and disabling ATE won't do any good.
We have escalated a similar issue to our developers, and the ticket is being worked on. So, I cannot suggest anything else unless you decide to cooperate more with us and provide site access or, even better, a site dump.
The context of my previous reply was to seek assistance in optimizing php processing. However, for now, please disregard ATE and let's return to the issue at hand. Please let me know how I can help you debug or resolving the issue related to query generation.
Could you please provide a secure form where I can share access to my website's staging environment? We have replicated the issue there, and I'd like to share it with you for a detailed review.
If you need further help with this, please share the access details to your site with me.
I'm enabling a private message for the following reply.
Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
To investigate this issue further, you can install migration plugins such as Duplicator or All In One Migration to take a copy of your site. Please rest assured that any data accessed will remain strictly confidential and will not be viewed, shared, or used beyond the scope of this investigation.
After trying two different migration plugins and several attempts to take a copy of your site, I finally have it. I've sent it to our second-tier supporter and will update you once I have news from him.
Our second-tier supporter has debugged the issue on the copy of your site. He found out that the main performance issue occurs (at least on his server with the copy of your site) due to \Custom_Permalinks_Frontend::make_redirect in wp-content/plugins/custom-permalinks/includes/class-custom-permalinks-frontend.php, and not because of WPML. He says this WPML issue does not inflict any performance problems on your site. Our second-tier supporter adds that your site may benefit from the fix that our developers are working on when it will be released. So, at this point, all we have to suggest is to wait for the version with the fix. I'll update you here once it is released.
