Translation Service

Problem:
If you're trying to fix technical SEO issues like improper URLs and need these changes to propagate to different language versions of your site, you might encounter issues where changes do not always apply. This could be due to issues in the Media Translation add-on, specifically causing double slashes (//) in media links.
Solution:
First, ensure you have a backup of your site. Then, if you're comfortable with code changes, you can manually edit the file at

/wpml-media-translation/classes/media-translation/class-wpml-media-image-translate.php

. Around line 211, modify the code as follows:

$filename = array_pop($file_subdirectory_parts);<br />if (!empty($file_subdirectory_parts)) {<br />    $image_url_parts[] = implode('/', $file_subdirectory_parts);<br />}

Save the changes. However, this is a temporary workaround. We have released WPML 4.9.3, which includes a permanent fix for this issue. You can download the new version from https://wpml.org/account/downloads/. After updating, you can remove the manual code edit.

If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket at WPML support forum.

Problem:
The client was experiencing issues with translations not updating correctly on their website. This problem was particularly prevalent with posts and product pages that were originally created using the Classic Editor and later attempted to be updated after the transition to the Gutenberg Editor. The translations would appear correctly in the Advanced Translation Editor (ATE) but not on the actual page.
Solution:
We discovered that the root cause was due to the posts being registered as 'Gutenberg' packages by WPML, despite being created with the Classic Editor, which led to WPML not processing the translations correctly. To resolve this, we recommended the following steps:
1. Open the post in the default language in the editor.
2. Click anywhere in the text.
3. Click on "Convert to blocks".
4. Make any updates needed in the default language and save the changes.
5. Then update the translation.
This workaround should allow the translations to display correctly. We are also working on a permanent fix to address this issue systematically in future updates.

Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, please open a new support ticket at WPML support forum for further assistance.

Problem:
If you're experiencing issues with WPML's XLIFF export splitting Elementor headings containing HTML line breaks (

<br>

) into separate segments, which affects the context for translators and the formatting upon reimporting, we can help.
Solution:
Initially, we suspected the issue might be with WPML’s XLIFF generation, but after testing and coordination with Lilt, it was determined that the problem was on the translation service side or the connector handling the file. We resolved this by disabling segmentation for the specific setup, which preserved the

<br>

tags within a single segment. We recommend resending the translation job to see if it processes correctly now.

Please note that this solution might be outdated or not applicable to your case. If the issue persists, 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 further assistance is needed, please open a new support ticket at WPML support forum.