Problem: You are unable to translate certain pages on your website using the Advanced Translation Editor or automatic translation. You receive an error message indicating that WPML tried to translate the page three times and failed. Solution: The issue might be caused by your hosting provider blocking the request through a firewall or another security layer, or the specific page may contain data or content that causes the translation job submission to fail. We recommend: 1. Updating the problematic widget on the original page by recreating it. 2. Alternatively, consider keeping and using the duplicated page instead of the original one.
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.
Problem: The client was unable to translate elements of the homepage after moving the site to a new domain. Despite the frontend displaying translated text, backend translation functionalities were not working. Solution: 1. We requested access to the client's site to investigate the issue further. For security, we advised the client to back up their site and provided a link to our privacy policy: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/. 2. After gaining access, we utilized WPML's troubleshooting tools which resolved the issue, allowing the homepage to be opened and translated. 3. We identified potential issues with unusually long HTML strings related to Figma, which might have affected content processing. By duplicating and re-translating the page, the problem was resolved. 4. We suggested the client check with their hosting provider for any firewall or security rules that might be blocking requests, as this could explain the inconsistent behavior.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum.
Problem: You are working on a multilingual website using WPML, with Greek as the default language and Bulgarian as a secondary language. You've translated most pages into Bulgarian, but several pages are stuck in an incorrect translation status. Specifically, some Bulgarian translations display a gear icon, indicating they are "assigned to a local translator", despite being fully translated. After saving, these translations still show as incomplete, and you cannot reset or create new translations. Solution: We have identified that the issue is due to incorrect database entries. Here's how we recommend you resolve this: 1. Access your database and navigate to the
wp_postmeta
table. 2. Search for entries with the meta key
icl_lang_duplicate_of
and remove them. 3. In the
icl_translations
table, remove entries where
element_id
is set to
NULL
. Before proceeding, ensure you back up your database for safety. If you're not comfortable performing these steps, or if the issue persists, please visit our support forum at WPML Support Forum for further assistance.
Please note that this solution might be outdated or not applicable to your specific 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 problem continues, do not hesitate to open a new support ticket.
Problem: The client has a bilingual website with pages in both Chinese and English. Some pages that are not translated into English still generate English URLs (/en/), which appear as errors in site audits, showing as redirects or broken links. Solution: We identified that the issue stems from the WPML settings. Specifically, the 'Link to home of language for missing translations' option was enabled in WPML → Languages, causing untranslated pages to generate English URLs. To resolve this, we adjusted the WPML settings to not link to the home of the language for missing translations. Additionally, ensure that the post type is set to only show translated items in WPML → Settings.
If this solution does not fully resolve the issue or seems outdated, we 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 problems persist, please open a new support ticket.
Problem: You might be experiencing an issue where translations disappear after migrating from Divi 4 to Divi 5. This problem results in empty content in the original language and missing pages in other languages. Solution: We recommend the following steps to resolve this issue: 1. Revert your site to the state it was in before the migration. 2. Update all WPML plugins. Alternatively, you can use the workaround provided in our errata here: https://wpml.org/errata/divi-5-migrating-from-divi-4-can-result-in-empty-content-in-the-original-language/ 3. Run the migration again.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are unable to change translated slugs even after adjusting the settings in Translated documents options for Page URL to Translate. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Make a small change to the original content (for example, add a letter to the title). 2. Update the page. 3. Revert the change and update the page again. 4. Then open the translation and complete it if needed. For more details, you can refer to our forum post here: https://wpml.org/forums/topic/i-cant-change-the-translated-slugs/#post-18018569
Please note that this solution might be outdated or not applicable to your specific 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.
Problem: If you're experiencing issues where text blocks appear as single units on your webpage and UI builder but are incorrectly split into fragments when opened for translation in Crowdin, causing loss of context for translators, this might be due to line breaks in the Text Block Element of WP Bakery Page Builder. Solution: We recommend adding the following code to the
functions.php
file of your theme to prevent automatic addition of paragraph tags which might be causing this issue:
After adding this code, please modify the page content or add new content and test the changes. If the problem persists, it might be due to inherent behavior of the WP Bakery Page Builder in conjunction with Crowdin, and changes in the source text might be necessary to resolve the issue.
Please note that this solution might be outdated or not applicable to your specific 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 continues, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing a critical error when clicking on WPML during the plugin setup, preventing the completion of the installation. Solution: 1. We recommended that the client should first attempt to uninstall and then reinstall WPML to ensure it was set up correctly. 2. Navigate to WPML → Support and click on the Troubleshooting link. 3. In the Reset section of the Troubleshooting page, select the I am about to reset all translation and language data checkbox. Then, click the Reset and deactivate WPML button. 4. If the problem persists, we advised the client to provide admin and FTP access for further investigation. 5. After receiving access, we reinstalled and configured WPML, resolving the issue.
Please note that this solution might be outdated or not applicable to your specific case. If you're still experiencing 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 at WPML support forum.
Problem: If you're experiencing issues where changes in the image order in a property's media gallery are not synchronizing across translations in different languages, this might be due to a compatibility issue between WPML and the Houzez theme. Solution: We recommend taking the following steps to address this issue: 1. Ensure you have a full backup of your site before proceeding. 2. Add the following code to your theme’s functions.php file:
// WPML - Workaround for compsupp-8361
add_action( 'save_post_property', function( $post_id ) {
// check if the property has translations
$trid = apply_filters( 'wpml_element_trid', null, $post_id, 'post_property' );
if ( ! $trid ) {
return;
}
// Get the translations
$translations = apply_filters( 'wpml_get_element_translations', null, $trid, 'post_property' );
// Get the gallery images
$fave_prop_images = get_post_meta( $post_id, 'fave_property_images', false );
foreach ( (array) $translations as $lang => $translation ) {
// delete the gallery
delete_post_meta( $translation->element_id, 'fave_property_images' );
foreach ( $fave_prop_images as $image_id ) {
// translate the image if needed
$image_id = apply_filters( 'wpml_object_id', $image_id, 'attachment', true, $lang );
// Re-add the image to the gallery
add_post_meta( $translation->element_id, 'fave_property_images', $image_id );
}
}
}, 1000 );
3. Update the properties once to reflect the changes.
Please note that this solution might become outdated or may not apply to your specific case. If this solution does 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You have a WooCommerce product that you only want to appear in the Danish language, but it is showing in English and German as well. Solution: If you're experiencing this issue in the backend and can see the product in other languages there, we recommend you go to Products → All Products, switch to the desired language, and delete the product translations from those languages. However, if in the backend you only have the product in Danish, but on the frontend it still appears in other languages, then please go to: WPML → Settings → Post Types Translation and set Products (product) to: “Translatable – only show translated items” This will ensure that products only appear in languages where an actual translation exists.
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, we encourage you to open a new support ticket at WPML support forum.
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 you still need help, please open a new support ticket at WPML support forum.
Problem: The client needed advice on handling external redirects, especially since the LiExtension was conflicting with WPML. Solution: If you're experiencing similar issues with external redirects and are using an Apache server, we recommend adding the redirects using the
.htaccess
file. Alternatively, you can use the Redirection plugin. Always ensure to verify the plugin’s compatibility with WPML by checking here.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML support forum.
Problem: The Slider Revolution (SR7) homepage slider works correctly on the English version of the site but fails on the German and Romanian translations. The issue manifests as the slider not appearing on the frontend of the translated pages, and JavaScript errors indicating 'Cannot read properties of undefined (reading 'slide')' are observed in the browser console. Solution: We have identified that the current version of Slider Revolution (SR7) is not fully compatible with WPML. To resolve this issue, we recommend downgrading to a previous version of Slider Revolution that is known to be compatible. You can confirm the compatible versions and detailed steps for setting up multilingual sliders by referring to our guide on creating multilingual sliders with Revolution Slider and WPML.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also 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 contact us directly through the WPML support forum.
Problem: The client reported that some ACF Field Groups were duplicated when new languages were added to their site. They inquired whether it was safe to delete these duplicates and how to prevent such duplication in future projects. Solution: We identified that the duplication occurred because the ACF Field Groups were set as translatable in the WPML settings. To resolve this, we advised the client to set the ACF Field Groups to 'Not Translatable' in the WordPress Dashboard under WPML > Settings > Post Type Translation. This change prevents future duplications by ensuring that field groups do not create copies when new languages are added. The client should safely remove any existing duplicates, as they are no longer necessary.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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, please visit our support forum at WPML Support Forum.
Problem: The client's subscription was automatically renewed, and they no longer require the WPML plugin. They were not notified about the renewal and now wish to request a refund. Solution: If you're experiencing a similar issue with an unwanted subscription renewal, we recommend contacting our sales team directly to handle your refund request. Please email them at hello@wpml.org.
Remember, if you encounter any technical issues or need assistance with WPML in the future, we are always here to help.
Please note that this solution might be outdated or not applicable to your specific 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 this does not resolve your issue, please do not hesitate to open a new support ticket with us.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
