I know that source, it's the one that actually made me open this ticket. On that source page, Nicolas V. says on March 11, 2026 at 10:09 pm that the issue should be resolved and you shouldn’t encounter this issue for new translations. But I still do. So what’s your actual status? Resolved or still a known issue?
Please name the permalink of the original affected content, and I will be glad to take a look into this.
I'd like to request temporary access (wp-admin and FTP) to the website to investigate the issue further.
You'll find the necessary fields below the comment section if you log in to leave the next reply. The information you provide will be private, meaning only you and I can see and access it.
IMPORTANT
Please be sure to create a backup of the website and database before granting us access.
If you don't see the "wp-admin / FTP" fields, your login credentials for the post and website will be set to "PUBLIC." Do NOT publish the data unless you see the required wp-admin / FTP fields.
The private reply form looks like this: hidden link
When replying again, click "I still need assistance".
Video: hidden link
Please note that we are required to request this information individually on each ticket. We are not permitted to access any login information that was not specifically provided in the private reply form for this ticket.
I'm sorry I don't have an example now, so I don't think it's very useful to create a staging site.
There are two other sites that need translations coming up in the next weeks. When it also happens with them, I can let you know so you have an actual example. Can we keep this ticket open for that?
I am investigating the slow behaviour. It started after activating WPML, but I don't know why. In another ticket your colleague couldn't find any issue and said it was server resources. However, the old site with the same set of plugins on the same hosting account didn't have that issue. I created a staging site from the old site, removed all (classic) translations, revised the complete design, pushed it life last week without any issue. Then I activated wpml again with PTC and it became slow. Nothing changed in the hosting account. I know it's fixed if I increase server resources, so I need to figure out where all resources go. If you have any ideas, please do let me know.
We truly need to investgiate this further, but I need to be able to see the issue, then investgiate the relevant original content and try to replicate on a sandbox.
We might not need a staging site at this point. I just need to know how the original content was built, which theme and plugins are involved, and I should be able to replicate it.
This is an ATE (Advanced Translation Editor) issue that seems to have occurred in many different use cases, and the current fix might not have covered every situation. The ATE runs on an external server, which means no plugin updates would be needed for a fix. Our ATE devs fix such things externally on our own server.
OK, I am really not sure why those clean-up messages are sent out. I will follow up with the systems team about this. The ticket usually should remain open for another 14 days. Only to what you are reporting, it seems the time range was changed to 7 days.
I have followed up with the systems team, and it appears that the timeframe was changed to 7 days. Which means, from today, the ticket will remain open for another 7 days.
Were you not yet able to replicate the issue again?
This ticket was opened almost three weeks ago, and I have been able to investgiate the reported issue.
I would really appreciate you could simply reopen a new ticket once you are able to replicate this issue, as it will not look good on my stats if I leave this ticket unattended in my queue.
I am sorry, but I don't really want to start over again with a new ticket.
You couldn't properly investigate this because I had already fixed the 'marked for later' segments.
Support is for helping users.
I understand the stats, but you can explain.
It was never an issue before when I asked to keep a ticket open a little longer.
