Issues importing XLIFF translations to my staging server that originated from my local environment.

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are trying to import translated XLIFF files into your staging server, specifically for 'Raw String' translations. The IDs of the string fields do not match between the local and staging environments, causing the import to fail even though it appears 'successful'.
Solution:
1. Ensure that only WPML plugins and the WordPress default theme are active to rule out any conflicts. Confirm the steps with our guide on a similar case: https://wpml.org/faq/the-uploaded-xliff-file-doesnt-belong-to-this-system/.
2. Alternatively, use the WPML > String Translation tool to export and then import the strings directly between environments. This method avoids the ID mismatch issue.

If these solutions do not resolve your issue or seem outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum: WPML Support Forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Documentation request

This topic contains 3 replies, has 0 voices.

Last updated by Dražen 1 week, 2 days ago.

Assisted by: Dražen.

Author	Posts
April 3, 2025 at 5:00 pm #16894296
peter-rF	Background of the issue: I am trying to import translated XLIFF files into my staging server. These translations originated from XLIFF exports created on my local server. My current process involves re-creating the translation job on the staging server, exporting the XLIFF file, and copying the headers from this file to the translated XLIFF file before importing. This process works well for posts/pages, but I've hit issues with String Translations. Symptoms: I am experiencing issues with String Translations where the 'batch-string-' id is mismatched against the original export, even after swapping headers. Questions: Do you have any advice or insight into how I could better approach this process? Is there something I'm totally missing or overlooking that could make this simpler?
April 7, 2025 at 7:47 am #16902598
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello, it should work fine, I advise checking with only WPML plugins and WP default theme, maybe there is some conflict and confirming steps with our guide for same/similar case: https://wpml.org/faq/the-uploaded-xliff-file-doesnt-belong-to-this-system/ Regards, Drazen
April 7, 2025 at 7:07 pm #16906021
peter-rF	Hey Drazen! Thank you for your time! The specific situation that I'm referring to is with 'Raw String' translations. I have a local environment and a staging environment that are not in sync with each other. When I export my raw string translations as XLIFF files from the local server, each specific string field in the XLIFF gets a dynamically generated ID applied to it. With other types of XLIFF exports, all I need to do is swap the headers of the XLIFF file so that they match up with a new job on the server that I'm importing into (like the article that you linked to me suggests). But with the string translations, even when the headers of the file match up, the ID's of the individual string fields don't match between the servers. So even though the import appears 'successful' none of the strings actually get translated. I assume this is the case because we have used WPML to scan the theme for strings in two completely separate environments. Would you have any suggestion for a workaround that could help me get this working or is the only solution to make sure that I export my raw string translation XLIFF files directly from the server that I'll be importing into? Thanks again!
April 8, 2025 at 6:45 am #16906901
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello, thanks for getting back. I understand, so basically you are trying to import/export string translation. For that, there is another way: go to WPML > String translation and export the translation and then from same screen on your other website, use the import tool and just import the string with translations. Hope this helps. Regards, Drazen