Background of the issue:
I am trying to edit a complete translation using the translation editor (pencil icon).
Symptoms:
The translation editor shows empty fields or fields flagged for later with original texts, even though the front-end displays the translations correctly.
Questions:
Why does the translation editor show empty fields or original texts when the front-end displays translations correctly?
How can I ensure that the translation editor reflects the completed translations?
just to update you. I checked with the devs and they told we need to wait a bit longer. Apparently there were many edge cases that need handling and it seems it may take few more days before any update or fix.
I just wanted to ask if you think it is safe to keep working on the (copied) staging site. Just on the original language posts, we need to make some adjustments to adapt the contents to the new template.
Our team has resolved the issue, and the “flag for later” problem is now fixed. You can resend the jobs for translation — you should no longer encounter the issue and will be able to translate and save the jobs without any problems.
Unfortunately, the issue with segments reverting to the original language is a separate problem, and our team is currently working on it.
In the meantime, the best we can do is offer some credits so you can move forward and re-translate the affected content. Since I’m not sure how many pages you need to re-translate, could you please provide an estimate? Once I have that, I’ll check with my team.
thanks for your update. I'm glad to hear the "flag for later" issue is solved, but I 'd like to exhaust all possibilities of recovering the translations. If lost, many hours of translation and revision work would be wasted. If there were no other option, the credits would be a good alternative, but only as a last resort.
Sure, that makes total sense, and I understand your point.
Let me check again with my team to confirm when the fix will be included and whether there are any options for restoring the translation, as well as to get an expected ETA.
Once I have more information, you and your team can decide whether it’s worth waiting or if you should proceed with credits option.
I checked, and at the moment it seems there’s no way to recover the lost translation.
The best we can do is offer you translation credits so you can automatically re-translate the content and save some time.
On this website I see around 34k credits used, but I’m not sure if that will be enough for the re-translation — depending on the impact, the amount needed may be significantly higher.
Thanks for your feedback. Is there a way to calculate the amount of credits needed to translate the site? This is not the expected result but it is better to review an automatic translation rather than translating from 0.
Drazen is not available now, so I'll be handling this ticket while he's away.
To have a word count and credit consumption estimate, you can go to WPML > Translation Dashboard and select the all the untranslated items from the list. After selecting, you can see the estimate at the bottom of the page.
Please note that this word count does not consider already translated segments saved in memory, so it's a "worst case scenario". It will cost that amount, or less.
thanks for your feedback. I'm not sure if you are aware of the issue we are facing. I was wondering if maybe the problem is that we used the legacy translation editor on most of the affected posts. While reviewing again the issue, I noticed a change on the WPML settings page design, especially on the translation editor set up, that now includes a check to use legacy editor translations on the new ate. Could be this the issue? In our case, this setting is not checked.
I'd like to know if it is worth/safe to try, and the consequences it might have, obviously after a full db backup.
