The error you’re encountering is usually caused by an improperly formatted XLIFF file. This can happen when the identifiers or essential tags within the XLIFF file are not correctly configured.
Please review the general structure of XLIFF as outlined in the link below to ensure the file you’re importing follows the required structure:
- hidden link
Additionally, the XLIFF file you’re importing must have an ID that matches the one in the XLIFF file exported from your site. Make sure to verify that the ID in your XLIFF file aligns with the requirements.
The issue should be resolved by ensuring that the XLIFF file is correctly configured. However, if you’re still experiencing problems, please upload the XLIFF file to Google Drive or OneDrive and share the link with me. I’ll review the file and guide you on the next steps.
Hello There,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
Thank you for the update. Please let me know if the suggestion helped you identify the issue, or if you need any further assistance. I’m happy to help.
We've done a test with 1 file and now the file is imported, so it seems to work.
However, I do not see the 'impact'. How of where can I see the translations of the file?
Hello There!
I hope you're doing well. Sorry for the delay in responding due to the weekend.
If the XLIFF file has been imported successfully, you should immediately see the translation when accessing the translated version of the page. Additionally, when you open the translated page in the WordPress editor, the translated content should be visible there.
If the translation does not appear, it’s possible that the imported XLIFF file does not contain the translation. You can verify this by opening the XLIFF file in an editor and checking the content within the `<target>` tags, which should contain the translation.
Furthermore, if you exported a page that includes custom fields, ensure that the translation preference for those fields is set to "Translatable" before exporting the XLIFF. You can configure this by going to "WPML > Settings > Custom Field Translation".
Once you’ve confirmed that the exported XLIFF file is correctly formatted and the imported XLIFF contains the translation, the translation should appear on the frontend. If you have any questions or need further assistance, please feel free to let me know—I’ll be happy to help!
We've tested again with another file and now it uploads and says that the translation is "voltooid' (completed): hidden link
However, when I want to access it, there is no translation: hidden link
If you’ve imported an XLIFF file and the translation job appears as completed, it indicates that the XLIFF file was successfully imported, and the translation should display correctly. However, as mentioned in my previous response, the translation will be visible in the Frontend if correct and only be editable from the WordPress editor. It is expected to not see the translation in the advanced translation editor, as the translation wasn’t created using that editor.
The reason is that translation memory isn’t shared between different translation methods. If the translation is created using the Advanced Translation Editor, it will appear when you open the Advanced Translation Editor. However, translations created using other methods won’t be visible in the translation editor.
If the translation appears correctly on the frontend after importing XLFF, you’ll need to edit it through the WordPress editor if needed.
I hope you can understand. Feel free to let me know if you have any other queries or need clarification. I'll be happy to help.
Yes, I can see it in the standard translation editor.
But I can not see it on the front end - it always redirects back to the front page.
Am I missing something?
Thank you!
The translation should appear on the frontend if it’s available in the backend. However, when I tried accessing the French version of your site, it redirected back to the default version. This typically happens if:
- The language is set to "Hidden", or
- The translated page/post is saved as a Draft or not published yet.
Please follow these steps to troubleshoot and resolve the issue:
1. Navigate to "WPML > Languages" and scroll down to the **Hidden Languages** section.
- Ensure that the "French" language is not set to hidden.
2. Go to "Pages > All Pages".
- Open any page that you’ve translated using XLIFF.
- Verify that the translated page and the default page are properly connected.
3. Return to "Pages > All Pages".
- Use the language switcher in the top admin bar to switch to the "French" language.
4. Click the "Quick Edit" button under the page name.
- Ensure that the "Status" of the page is set to "Published".
Please also add a language switcher to your site by following this guide to make it easier to switch languages.
Please try and let me know how it goes. I'll be happy to help if you need further assistance in this matter.
Thank you.
The page is published, but it still doesn't show.
We also use Elementor, so perhaps that is causing the problem? I can for example not edit the page in Elementor.
So aftwards, when we need to do other changes, do we always need to load a new XLIF-file?
If so, I think in the long end, it will be easier to just use the WPML editor?
Also, I do not want to add a language switcher to the site yet, for we are still testing how we best do all this, so only a couple of pages are translated for the moment.
Hello Olivier,
Thank you for sharing the access details.
I checked the specific link you shared and found that the following error occurred when saving the page:
Updating failed. The response is not a valid JSON response.
This error can happen for several reasons, but the most common cause is broken permalinks, which can also affect the loading of the Elementor editor.
Could you please follow the suggestions provided in the article below and check if they help resolve the issue?
- hidden link
I also noticed that two of the pages have been translated into French, and both are showing the same errors. Besides these, no other pages have been translated into French yet. This could explain why the French version is not loading and redirects back to the Dutch version. Once the "Valid JSON" issue is resolved, please translate the remaining pages, and they should display correctly in the French version.
Additionally, I would like to point out that changing the "Language URL format" to “Language name added as a parameter”, under "WPML > Languages" allows the French page to save and display correctly. This suggests that the "language directory" setting might be not working well with another configuration on your site. I hope the guide mentioned earlier can help in identifying the cause.
Regarding your query about using XLIFF for updating content: it is true that when you choose the XLIFF translation method, you’ll need to send the XLIFF file each time, even for content updates. This method is recommended for pages that do not require frequent updates. For pages that need continuous updates, it’s better to use the "WPML Translation Editor" or add translations directly using the "WordPress editor".
I hope you can understand. Feel free to let me know if you need further assistance or clarification. I'll be happy to help.
Best regards,
Prosenjit
The topic ‘[Closed] Import XLIFF files’ is closed to new replies.
