Problem: You are experiencing an issue where string translations revert to previous versions even after clearing the cache in WPML and the W3 Total Cache plugin, and deactivating the latter. The server does not have cache functions. Solution: The issue might be related to how textdomains are loaded in your theme or plugins, especially with the changes introduced in WordPress 6.7. We recommend checking if your theme or any plugins are using an outdated method to call textdomains. You should discuss this with your theme's developer. For more details, see the discussion on WordPress support.
If this solution does not apply to your case, or if it becomes outdated, we highly recommend checking related known issues at WPML 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.
Problem: The client is unable to activate the OTGS Installer for the WPML plugin on their new server, despite it working on a previous site. They are also unsure if they need to install the String Translation plugin along with the WPML Multilingual CMS for full functionality. Solution: If you're experiencing issues with activating the OTGS Installer, we recommend downloading the plugins manually. You can do this by visiting https://wpml.org/account/downloads/ and clicking on "Download WPML manually" at the bottom of the page. Regarding your query about the String Translation plugin, yes, you need to install it to translate strings from themes and plugins or to handle page builder content.
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.
Problem: You are trying to translate WP Forms but only one out of five forms is available for translation. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Ensure that the WPForms Multilingual plugin is active on your site. 2. Open one of the forms in the editor that isn’t appearing in Translation Management. 3. Make a small change to the form, then save it. 4. Check if the form now appears in Translation Management. This process helps propagate the language settings to the form, which often resolves the issue.
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 are trying to translate a button on your homepage into Spanish, but it is not displaying the translation. The button is part of an ACF link called 'Button' from the 'Two Column' ('two-col-all') ACF module, and it is inside the 'CTA' ACF Repeater. Solution: First, ensure that your fields are set correctly in WPML's Custom Field Translation Settings. The Repeater Field should be set to 'Copy once', and the Link field should be set to 'Copy' if you want to use the same link in both languages, or 'Translate' if you need different URLs for each language. You can find more details on setting these options in the documentation. After adjusting these settings, edit the link field on the original content, save the page, and then translate it again. If necessary, use the text search field in the WPML Advanced Translation Editor to find and translate the specific link.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current setup, 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 further assistance is needed, please open a new support ticket.
Problem: You are experiencing instability with the Yoast Redirects feature when the WPML SEO plugin is active. Errors occur when saving new redirects, and the domain of the Redirect To URL is missing when both plugins are active. Solution: We recommend disabling the WordPress guess redirects to resolve this issue. You can do this by adding the following code to your
After adding the code, go to Settings -> Permalinks in your WordPress dashboard and update the permalinks. This should help stabilize the Yoast Redirects feature.
If this solution does not resolve your issue or seems irrelevant due to being 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 problems persist, please open a new support ticket.
Problem: You are managing translations in the backend of your WordPress site and notice a discrepancy: the translation queue shows no translations, yet a notification indicates that one translation is waiting for review. Clicking on the notification leads to a screen with no translations. Solution: We recommend following these steps to resolve the issue: 1. Navigate to WPML -> Support -> Troubleshooting. 2. On the troubleshooting screen, sequentially press the following buttons, waiting for each process to complete before proceeding: - 'Disable cache for language switcher templates' - 'Clear the cache in WPML' - 'Remove ghost entries from the translation tables' - 'Fix element_type collation' - 'Set language information' - 'Assign translation status to duplicated content' - 'Set language information' - 'Fix terms count' - 'Fix post type assignment for translations' Then, recheck to see if the issue persists.
If this solution does not resolve your issue or seems irrelevant due to being 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 problem continues, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to display translation flags on their website despite deactivating all plugins except WPML and using the standard WordPress theme. The issue persists even after removing all custom CSS. Solution: We discovered that the footer language switcher is actually present but hidden. We recommend checking the settings in the custom CSS section of your theme, which can be accessed here: Theme Custom CSS settings. For the main menu, ensure that the locations are correctly set to display the mega menu where the language switcher should appear.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket.
Problem: You are experiencing a 404 error on the homepage of your site when it is set to the English language. Solution: First, check if there is an /en folder where WordPress is installed. Next, navigate to WPML->Languages->Language URL format and switch to 'language as a parameter' URL format to see if the English page appears correctly. Additionally, we recommend trying the workaround detailed in this documentation: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/.
If these steps do not resolve the issue, it might be because the solution is 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 persists, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with product variants disappearing after updating WooCommerce Multilingual & Multicurrency to version 5.3.9, it might be due to conflicts with other plugins or themes. Solution: We recommend the following steps to troubleshoot and resolve the issue: 1. Ensure that only WooCommerce, WPML, and our addons are enabled when updating to the latest version of WooCommerce Multilingual & Multicurrency. 2. If the issue persists, try enabling all plugins and the child theme again to check if the problem still does not occur. 3. On your live site, delete any minified files created by Assets Cleaner PRO and clear the site's cache before updating. 4. Check for configuration issues under WooCommerce > WooCommerce Multilingual & Multi-Currency > Status. 5. Go to WPML > Settings > Post Type Translation and set "Variations (product_variation)" to "Translatable - only show translated items" and save the settings. 6. In WPML > Settings > Custom Fields Translation, click "Show system fields" and set the field
_crosssell_ids
to "Translate". If these steps do not resolve the issue, the 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 persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to translate certain strings in Gravity Forms using WPML on their website built with Beaver Builder. Specifically, strings like 'First', 'Last', 'Required', 'Enter Email', 'Confirm Email', and others are not being picked up for translation. Solution: We recommended the client to ensure they have a backup of their site, which can be done using the UpdraftPlus plugin. Next, we advised trying to translate the strings directly through WPML's String Translation interface. This can be accessed from the WPML menu in the WordPress admin area. The client should search for the strings under the 'gravityforms' text domain and add translations as needed. It was also noted that some strings, such as 'Choose file' and 'Max file size', are browser-dependent and therefore cannot be translated through WPML as they will appear in the language set by the user's browser.
If this solution does not resolve the issue or seems outdated, or if it does not apply 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 further assistance is needed, please open a new support ticket.
Problem: The client reported that WPML overwrites Gravity Form in the latest versions of Gravity Forms Multilingual, despite a previous workaround. They requested a new solution for this recurring issue. Solution: We revisited the previous workaround and found it still applicable. Here are the steps to implement the solution: 1. Open the file at /gravityforms-multilingual/inc/gravity-forms-multilingual.class.php. 2. On line 685, replace:
$snh = new GFML_String_Name_Helper();
with:
$snh = new GFML_String_Name_Helper();
// WPML workaround for compsupp-7768
$check = new \WPML\Utils\DebugBackTrace();
if ($check->is_class_function_in_call_stack('GFFormDisplay', 'process_form')) {
return $form;
}
3. Repeat the same replacement on line 822.
If this solution does not resolve your issue or seems outdated, we 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, visit our support forum at https://wpml.org/forums/.
Problem: You have translated your site from Danish to English and added links in the main menu. However, when switching languages, two of the links, 'Going on' and 'about', revert to the Danish version despite re-translating the menu. Solution: To ensure that all menu links remain in English when switching languages, you should not attempt to translate templates or menus directly within the site editor. Instead, navigate to WPML > Translation Management > Dashboard. Use the filter on the top left to select the post type you wish to translate. After selecting your content, send it to translation. If you are translating the content yourself, you will need to access the translation at WPML > Translations. For further guidance, refer to our documentation on translating content created using the Gutenberg editor and full site editing at Translating sites that use full site editing.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: After reinstalling WPML, the client encountered an error where a necessary folder for storing .mo files was not being created, and thus, the folder was not writable. This issue persisted even after the hosting company attempted to intervene by increasing site memory and manually adding the folder. Solution: We recommended manually creating the folder path for WPML's .mo files using an FTP program or through the admin control panel. This step ensures that the folder exists and can be checked for the correct writable permissions. Additionally, we suggested running a troubleshooting tool available at WPML's troubleshooting page to resync translations and verify if automatic translation functions correctly after these adjustments.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your current setup, 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. Should the problem persist, please do not hesitate to open a new support ticket with us for further assistance.
Problem: The client was unable to change the 'read more' and search placeholder texts in the Dutch language using the Kadence Builder, despite the strings being translated in WPML's String Translation section.
Solution: We discovered that the issue was related to how Kadence Builder's custom fields were registered with WPML. To resolve this, our team created a custom XML configuration to ensure these fields are recognized and translatable by WPML. Here are the steps we followed:
1. We examined the content inside the database of the main query post type to understand how the blocks were structured.
2. We created a custom XML configuration and added it to WPML > Settings > XML config tab. The XML code used was:
3. After saving the XML configuration, we made a small edit and saved the default language edit page, then updated the translated version with the correct placeholder text.
This solution allowed the 'read more' and search placeholder texts to display correctly in both languages on their respective pages.
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 created a variable product in WooCommerce and needs to translate the name of the default variation. After translating, the product appears empty in the frontend. Solution: 1. Ensure the WooCommerce Multilingual & Multi Currency plugin is installed and activated. You can download it from here. 2. Edit the variable product in the default language ensuring that the "WPML Translation Editor" is enabled. 3. Translate the secondary language product using the WPML Translation Editor. For detailed steps, refer to this documentation. 4. If the variation still does not show in the frontend, follow these troubleshooting steps: - Clear the cache in WPML. - Synchronize posts taxonomies. - Remove ghost entries from the translation tables. - More steps can be found in the WPML Support Troubleshooting page. 5. Consider creating global attributes and translate them either during the product translation or via WooCommerce >> WooCommerce Multilingual & Multicurrency > Attributes tab.
If these steps do not resolve the issue, we 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
