This thread is resolved. Here is a description of the problem and solution.
Problem: You are experiencing issues with importing XLIFF files for translation on a site that has recently switched from Polylang Pro to WPML. The import fails for two of the pages, and you suspect it might be related to a plugin conflict. Solution: We recommend temporarily deactivating the YoastSEO plugin and its Pro version, then attempting the XLIFF import again. Ensure you perform a full website backup before making these changes. If the problem persists or occurs with other XLIFF imports, please contact us for further assistance.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue continues, do not hesitate to open a new support ticket.
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.
Background of the issue:
I'm testing a site for a client where we moved from Polylang Pro to WPML. The site is maintained by a web development agency, and we handle localization. I exported 3 pages as XLIFF for translation and tried importing them back.
Symptoms:
For two of the pages, WPML says 'import failed'.
I've enabled the private fields. You will likely find them under the message box. Here, I only need the download link, since it's a copy, there's no need to share access, ok?
Thank you for waiting. I found out that the issue is being caused because of a conflict with YoastSEO and WPML. Since this is a very specific situation that's only happening to two products, what I can recommend is for you to temporarily deactivate YoastSEO and the Pro version, and upload the translations. That should solve it. Don't forget to have a full website backup before proceeding.
We can keep this ticket open for a couple days more, to monitor if that's happening again for other XLIFF imports, which is unlikely. May that be the case, please let me know so I can continue support.
Thank you for looking into it - that is indeed strange. At any rate, in the meantime I've figured out how to update WPML components, and then the XLIFF imported fine. Not sure why, but at least it works.
