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
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.
Problem: The client sent a page for translation through Smartling after updating WPML. The translation was completed and downloaded, but when trying to view the site in Spanish, the content was still in English, except for the page title which was correctly displayed in Spanish. Solution: First, we recommended checking with Smartling to ensure the translation job was marked as completed. If confirmed, the client should: - Return to WPML - Trigger a resync/update of the translation status This should allow WPML to fetch and import the completed translation. Additionally, we suggested clearing the browser, site, or server cache as the issue might have been caused by caching.
If these steps do not resolve the issue or if the solution becomes irrelevant due to updates or different circumstances, 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client is experiencing high translation costs due to WPML translating backend/admin strings, which are not necessary for their site's frontend. They need a way to disable backend/admin translations to save on translation credits. Solution: We recommend excluding specific backend/admin string contexts from automatic translation to prevent unnecessary credit usage. This involves identifying the contexts that are not required for frontend display, such as 'woocommerce-wc-admin-app', 'litespeed-cache', and others listed by the client. To implement this, you can modify the WPML String Translation settings to exclude these contexts.
Additionally, to address issues with menu items on translated pages not functioning correctly (e.g., the 'Products' menu item URL changing to '/es/#'), we suggest adding a code snippet to your theme's functions.php file or a custom plugin. This code will ensure that anchor-only URLs (like '#') are not translated, preserving their functionality across different language versions:
/**
* Skip URL conversion for anchor-only URLs (# or #something)
* This prevents WPML from converting # to /es/# on translated pages
*/
add_filter( 'wpml_skip_convert_url_string', function( $skip, $url, $lang_code ) {
if ( strpos( $url, '#' ) === 0 ) {
return true;
}
return $skip;
}, 10, 3 );
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 for further assistance.
Problem: The client de-authenticated Skrivanek and deleted the connection, but all translation jobs are still pending and cannot be canceled, showing the error: 'This action does not apply to any of the selected translation jobs'. Solution: If you're experiencing this issue, we recommend you try the following steps: First, check if the translation job can be canceled: 1. Go to WPML → Translation Management → Jobs. 2. Check whether the translation jobs are listed there and see if you can cancel them. If you are unable to cancel the job from there: 1. Go to WPML → Translation Management. 2. Select the page for which you want to cancel the translation job. 3. Send it again for translation. 4. Choose Translate myself, and you should then be able to translate it manually from WPML → Translations.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. 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. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: You have synchronized your translations from Crowdin and they appear correctly on the front-end. However, after making a small update to a single string in some languages, you opened the Advanced Translation Editor (ATE) only to find that none of your strings were visible, as if the page was not translated at all. Solution: If you're experiencing this issue, we recommend switching from the Advanced Translation Editor to the Classic Translation Editor. Translations created using Translation Services and XLIFF files do not appear in ATE. To switch, navigate to WPML → Settings → Translation Editor and select the Classic Translation Editor. This should allow you to view and manage your translations properly.
Please note that this solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum for further assistance.
