Problem: The client is experiencing an issue where the URL slug is encoded instead of copying the original English slug when translations are published from MemoQ, despite WPML being configured to "Copy from original language if translation language uses encoded URLs". The client is also seeking guidance on configuring the integration between WPML and MemoQ using Custom XML Configuration. Solution: First, we asked the client to provide an example of the encoded URL slug and the XLIFF file from MemoQ. We also suggested testing the issue with only WPML plugins enabled to rule out any conflicts. After further investigation, we tested the feature locally and found that it worked correctly for the Ukrainian language without using a translation service. We suggested that the client try translating a page themselves to see if the issue persists and to confirm whether they are using a regular WordPress custom post type. We then conducted additional tests to simulate the process of exporting and importing XLIFF files and found that the feature worked as expected. We recommended that the client try with a new page or make minor changes to the original language of an existing page, then download and import the XLIFF file again to see if the issue is resolved. If the solution provided here does not apply or is outdated, or if you're still facing issues, 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.
