Imported XLIFF files not loading all translations

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

Problem:
The client is trying to import XLIFF files to their WordPress site, but some sections of the language pages are still displaying in English, despite being translated.
Solution:
If you're experiencing issues with parts of your language pages showing in English after importing XLIFF files, we recommend the following steps:
1. Send the affected page to translation.
2. Export the XLIFF file for that page.
3. Compare the original XLIFF file with the translated one.
4. Ensure that the

extradata

, including both

resname

and

package id

, are identical in both the exported and translated XLIFF files. For example:

<trans-unit extradata="fusion_title: content" resname="package-string-255-9472024" restype="string" datatype="html" id="package-string-255-9472024"></trans-unit>

5. Make any necessary changes to the translated XLIFF file, not the exported one.
6. Attempt to re-import the XLIFF file.
If this solution does not seem relevant to your issue, please open a new support ticket with us.

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: Exception

This topic contains 20 replies, has 2 voices.

Last updated by Laura 12 months ago.

Assisted by: Laura.

Author	Posts
November 29, 2023 at 4:27 pm #14954157
maureenS-2	We don't use automatic translation. I exported the XLIFF files and they're sent to our internal translation team. I tried importing the translated versions to see if they would work on the dev site that we're currently testing on.
November 29, 2023 at 5:24 pm #14954509
Laura Supporter Languages: English (English ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	That's strange, because translation done only with xliff do not show in the Advanced Editor. However, I don't think it matters here. I'm asking a second opinion since Avada should be full compatible with WPML.
November 30, 2023 at 9:16 pm #14967721
maureenS-2	Thank you, Laura! I appreciate your support on this. We used the XLIFF process for all the pages on our site. We only encountered this issue segments of translations not importing on 3-5 webpages.
December 1, 2023 at 12:04 pm #14972341
Laura Supporter Languages: English (English ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	These pages have something in common? Same modules, etc?
December 4, 2023 at 6:41 pm #14990731
maureenS-2	Hi Laura, Some of the modules are the same among our pages. But that doesn't explain why translation segments are loading fine on other pages with these modules (most of the time), and sometimes not loading on other pages with these modules.
December 6, 2023 at 11:44 am #15007121
Laura Supporter Languages: English (English ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	You can try this: - send the Venue page (or any other affected page) to translation - export the xliff - compare the original xliff with the translated one - note the extradata: both "resname" and "package id" needs to be the same in the exported and translated xliff <trans-unit extradata="fusion_title: content" resname="package-string-255-9472024" restype="string" datatype="html" id="package-string-255-9472024"> - change the translated xliff, not the exported one - try to reimport