Background of the issue:
I am trying to import translations into WPML's Translation Management on our staging site: hidden link. The source language is English, and the target language is French. The XLIFF file was exported from Weglot and converted to WPML format to manage updates in WPML.
Symptoms:
When I upload the XLIFF file via the 'Import translations' button, WPML shows an error: 'Import failed! The uploaded xliff file does not seem to be properly formed.'
Questions:
Why does WPML show an error when importing the XLIFF file?
How can I fix the XLIFF file to be properly formed for WPML?
Is there a way for WPML to report a specific schema/validation error in the XLIFF file?
After your advice, export now works once I switch the theme from Oceanwise to Twenty Twenty-Five.
I have imported a Weglot XLIFF that I converted to WPML 1.2. The WPML shows “Imported one job.” (Screenshot 5)
However, when I open that job in the Advanced Translation Editor (ATE), it asks for credits (as if no target text exists), instead of showing the imported target segments ready to “Complete.” (Screenshot 1)
What I expected -
Since the XLIFF contains source + target for EN→FR, I expected ATE to open with all segments pre-filled (green) so I could just complete without consuming credits. (Screenshot 2)
What I see -
Job status in the Translations Queue is created/updated, but in ATE, the job appears as untranslated/needs credits.
Front-end and the FR post do not show the imported target until I manually translate or spend credits.
Samples -
I have attached the samples also for the original file and the weglot fixed file, which is imported in my WPML.
1) I am afraid import of XLIFF does not work like that. It is expected that it does not show in ATE, it will not show there as they do not share same translation memory. You would need to retranslate via ATE if you wish them to show in ATE editor.
You can still manually edit translated pages or use Classic translation editor (legacy).
2) Edit the translated page and check if import was done, if yes you should see your translated content there.
3) If not, then I need to further check the files you are using, as I am not sure how did you correct the weglot files and why it fails.
Please share:
- access to your staging site where I can check and debug issue safely
- page URL you are trying to translate
- Original exported WPMl XLIFF file of that translation job and original Weglot XLIFF file you wish to import. You can share them via WeTransfer or Google disk.
We’ve decided to proceed with manual translation. However, I’m encountering an issue: when I duplicate a page or blog post, some fields are missing in the ATE (as shown in the screenshot). Could you please provide the steps to resolve this?
Also, in the other screenshot, certain fields (e.g., “widget”) are locked and marked as “this field is copied from the default language.” I need to edit the title and description, which are currently synced with the default language (as shown in the screenshots). Could you advise how to change these as well?
I have already translated some pages, so please save the settings in a way that the other pages are not affected.
Thank you.
New threads created by Dražen and linked to this one are listed below:
