[Resolved] Exported to XLIFF but all strings are clustered together
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues with exporting translations to XLIFF where strings appear clustered together or included by codes or tags, especially when using tools like Phrase and Trados, this might be due to the timing of job creation and page edits. Particularly, this issue arises when using Elementor for page building. Solution: We recommend the following steps to resolve this issue: 1. Avoid editing pages while translation jobs are in progress. If you must make changes, resend the job for translation to ensure the XLIFF file is generated correctly. 2. Resend the translation jobs for your pages after ensuring no recent edits interfere with the translation process. 3. Consider using the Advanced Translation Editor (ATE) which can parse the XLIFF file and divide them into smaller segments. 4. Alternatively, use an advanced XLIFF editor software that can help in separating each unit into smaller segments. 5. If using Elementor, try to use one paragraph per widget to help break down the page into more manageable units for translation.
If these steps do not resolve your issue, or if the solution seems outdated or not applicable 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 the problem persists, 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.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello,
I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Please, let me know if you need any additional details. Have a nice day.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello there,
The fields should have been available in the previous reply.
But let's try a different approach.
I suspect this could be a compatibility or conflict issue. To pinpoint the exact cause, we need to isolate variables by replicating the issue in a sandbox environment.
Login link: hidden link
Here's what is needed to be done:
1- Install Essential Components Only: In the sandbox login link provided above, please install your theme and only the plugins necessary to replicate the issue, a single page where we can export the XLIFF and see the issue is enough. Avoid importing the entire site.
2- Set Up the Page and Configurations: Mirror your current setup that's causing the issue, focusing on this specific issue, we only need the site to be partially replicated up to a point where we can debug the problem.
3- Notify Us Once Done: After replicating the issue in the sandbox, inform us through this ticket so we can proceed with further analysis.
The goal here is to identify if the problem is indeed a compatibility issue, reproducing it in a controlled environment.
We appreciate your cooperation in this matter. Let us know once you've set up the sandbox.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello there,
A quick follow-up. The issue is not happening in the sandbox. The XLIFF is being generated with separate fields.
Can you please check if you'll be able to see the private fields now? We need to access the site once more so that we can continue to debug this issue directly in the site.
This is necessary given the fact we're unable to replicate the issue in the test site.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hi,
I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at this issue and will try to find a solution.
I will get back to you as soon as I get an answer from them.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hi there,
Thank you for your patience while we checked this.
We have investigated the issue and found that it is likely related to the timing of job creation and page edits. Some of the jobs you sent for translation appear to be stale, and it was likely created before making recent edits with Elementor. This can cause the text to be merged into a single field, as seen in your XLIFF file.
It is important to try to avoid editing the pages while translation jobs are in progress. If you need to make changes to the page, make sure to send the job for translation again.
I have re-sent the "About" page for translation in our test environment, and the XLIFF was generated correctly with separate fields.
Please resend the translation jobs for your pages and let us know if the issue persists.
I used the WordPress Editor sometimes, and the Elementor Editor if neccessary. Both have pros and cons. You can also see the Elementor Editor button in your screenshot.
I also tried resending my other pages, such as About or Portfolio sections, which all have the same XLIFF issues.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello there,
I checked those pages and they seem to be properly exported now. I also asked our 2nd tier support to double-check that it is in fact correct.
If we take for example the page 'About'. The segmentation of the XLIFF does not contain one paragraph or similar element as a single unit. Instead, it works with a unit per field. In practice, a unit is:
• WordPress Editor => Post Body is a single unit
• Page builder => Unit per widget. (You add a text widget; it is a single unit regardless how many paragraphs or HTML dividers you add in there there.)
There are a few options to overcome that:
1- Use ATE to translate the content. ATE parse the XLIFF file and divide them in smaller segments.
2- Use an advanced XLIFF editor software that can separate each unit into smaller segments.
3- Use one paragraph for each Elementor widget/break your Elementor page down into more widgets.
