Problem: You are facing an issue where the translated content is not appearing in the Advanced Translation Editor (ATE) on your translation editor page, although it displays correctly on the frontend. This occurs when you open the translation page using the WordPress editor. Solution: This behavior is expected when translations are created and imported using XLIFF files. These translations can be edited using the Classic Translation Editor (CTE) but will not appear in the ATE. The reason is that ATE requires its own translation package and metadata, which are not created when translations are imported via XLIFF. If you need to manage these translations with ATE, you should resend the content for translation and choose to overwrite the existing translation to create a new ATE translation package. For more details, please refer to our documentation on How to Edit Translations You Upload via XLIFF Files.
Unfortunately, there is no way to migrate existing translations from CTE to ATE due to the different translation systems and data storage formats used by each editor.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported a critical error when opening the translation editor page in WPML, which occurred due to issues with a specific translation job (ID 5130) and a missing media item in the Gutenberg/page-builder content. Solution: For the translation job issue: 1. Ensure WordPress, WPML Multilingual CMS, String Translation, and any WPML add-ons are fully updated. 2. Navigate to WPML → Support → Troubleshooting. 3. Run the following options: - Clear the cache in WPML - Remove ghost entries from the translation tables 4. Return to the affected original page/post, make a minor edit to the title or content, save it, and then try opening/sending the translation again. 5. If the issue persists with one page, cancel the current translation job and create a new one from WPML → Translation Management / Translation Dashboard.
For the media translation error: - The error
Call to a member function get_id() on null
suggests a missing media reference in Gutenberg/page-builder content. We need detailed steps to reproduce the error and access to the site to investigate further.
If these solutions do not resolve the issues or if they seem outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.
Problem: You are working on a site and notice that some translated content is not visible in the Advanced Translation Editor (ATE) of WPML, appearing as empty boxes, although it is visible in the Classic Translation Editor (CTE). Solution: If you switch to the ATE, translations done previously in the CTE will not appear in the ATE. These translations will still display correctly on the front-end of your site. To reuse existing translations, you can manually copy them from the front-end or use the Translate automatically option within the ATE to quickly re-translate the content. For more details, visit https://wpml.org/documentation/automatic-translation/.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket for further assistance.
