Open
Overview of the issue
In some translations jobs in the Advanced Translation Editor (ATE), certain segments appear as “Flagged for later” even though the translator did not mark them manually.
When this happens, these flagged segments prevent the translation job from being marked as complete, leaving the page in a pending or partially translated state.
Workaround
If you encounter this issue:
- Open the translation job in the Advanced Translation Editor.
- Locate the segments marked as “Flagged for later.”
- Uncheck the “Flag for later” option manually for each affected segment.
- Save and complete the translation again.
This will allow the translation job to be completed and synchronized correctly.
Our development team is investigating the root cause to ensure that ATE does not automatically flag segments.
Found this problem on a couple sites of mine and confused me since I never used the “flag for later” functionality. Glad that the team is checking this up
\When I click the “Flagged for later” I get a blank screen, so I can’t unflag them.
In the console I get these errors:
Uncaught SecurityError: Failed to read the ‘cssRules’ property from ‘CSSStyleSheet’: Cannot access rules (https://e.ate.wpml.org/index.js?v=3.30.3)
Hi Nathan,
Could you please open a ticket on our support forum? This will help us take a closer look at the issue. Our dev team is still working on it, so any real-case examples or feedback is helpful.
From the error, it looks like some CSS might be injected into the ATE page. Maybe from a browser extension? Could you try accessing it from a different browser to see if the issue persists?
Hi,
What is the status of this known issue, and do you have an estimated timeframe for a fix?
Best regards,
Peter Eistrup
Hi Peter,
Thanks for reaching out. We don’t have a confirmed ETA yet, this issue has already been prioritized for an upcoming ATE release.
On a positive note, ATE releases are independent of WPML releases and usually happen more frequently.
We are now 6 months later and we still need to through every single translation to manually uncheck the “flagged for later” tags that appear randomly. That is a huge loss of time and very frustrating.
What is the status of the fix for this?
Hi Karel,
This issue should be resolved now. However, if the segment was already flagged you will need to unflag it manually. But you shouldn’t encounter this issue for new translations. If the issue persist for you, please open a new ticket on our forum, we will be happy to assist you.
Hi, Nicolas V. says on March 11, 2026 at 10:09 pm that the issue should be resolved. However, today is April 9 2026 and I still see the issue. This is on a new site that I just started translating with the ATE and PTC. It happens most with media meta data, but sometimes also with other text.
Hi John,
Could you please open a ticket on our support forum. Our team will be able to assist you and escalate in case there are some issues left.
Hi Nicolas,
I already have here https://wpml.org/forums/topic/ate-marked-for-later/
But they refer me back to this page.
Now here you said 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 I opened that ticket, and then in that ticket they say it’s a known issue. So what’s your actual status? Resolved or still a known issue?
Thanks
John,
The errata refers to the general fix, and new translations should no longer be affected. Since you’re still experiencing the issue, Andreas requested a package so we can verify whether this is the same issue (regression) or a different one with similar symptoms. Please continue in the ticket, and we’ll investigate it further.