We already have an open support ticket regarding a critical bug in the WPML Translation Editor, but have not received a satisfactory solution yet. We are escalating this via our master account.
Background – Translation Editor re-parse bug: every time we open the Translation Editor after any edit, WPML re-parses the entire page. Previously unified blocks are split into fragments, unmodified strings are flagged as changed, and existing translations disappear.
Current critical issue (show stopper!): after migrating our blog posts, English versions are visible on the frontend – but the Translation Editor shows empty fields for all imported posts. WPML does not recognize the existing translations. This makes it impossible to manage or update translations via the Translation Editor.
This has caused significant additional issues as we already tried to fix that:
- Translation credits were consumed without producing usable translations
- Blog post tags and taxonomy translations were lost during migration, requiring extensive manual cleanup
- Inconsistencies throughout the translated content that we are still resolving
Note: we have translated the majority of our blog posts manually, without using automatic translation. The credits that were consumed were therefore wasted due to the bug – not as a result of intentional automatic translation.
We are behind on our launch deadline and urgently need:
1. A fix for the Translation Editor showing empty fields on imported posts
2. Sufficient credits restored to properly translate our blog posts going forward
3. A working solution or reliable workaround for the Translation Editor re-parse bug
