Problem: The client is unable to respond to an open support ticket and is experiencing two issues: a redirection problem on their multilingual site and a critical error when trying to create a new translation. Solution: 1. We recommend clearing your browser's cache or trying an alternative browser to resolve the issue with responding to the ticket. 2. Update your WPML plugins to the latest version (4.6.11) to address the redirection issue and critical error. You can find the update instructions here. Ensure to backup your database before updating. If updates are not visible, click on the "Check for updates" button in the Plugins → Add New Plugin → Commercial tab. If the problem persists after updating, try deactivating other plugins that might interfere, such as the Redirection plugin.
If these solutions do not resolve your issues or if they seem outdated or irrelevant to your case, 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 our support forum at https://wpml.org/forums/.
Problem: The client reported that GTINs and MPNs stopped appearing in the translated XML feeds of their WooCommerce Google Product Feed after a few weeks, potentially due to an update. This issue was only occurring with products that have multiple attributes as variations. Solution: We confirmed that the WooCommerce Google Product Feed plugin is officially compatible with WPML, as detailed on our compatibility page: https://wpml.org/plugin/woocommerce-google-product-feed/. The client decided to manually input all GTINs and MPNs into the relevant fields to resolve the issue, indicating that the plugin might not update these fields instantly.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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, you can also visit our support forum: WPML Support Forum.
Problem: You are trying to register your website with WPML but are unable to do so because the site key does not match. Additionally, there is a connection error indicated in the 'Advanced Translation Editor Error Logs' showing a cURL error, suggesting that WPML cannot connect to its servers.
Solution: First, ensure that there are no security modules on your website that might be blocking requests. You may need to whitelist the following domains with your hosting provider:
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 needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to update or reinstall WPML after deleting it due to an unresponsive 'Unregister WPML from this site' button, following a URL change and database update on a multisite. Additionally, the client needed to activate a new WPML license purchased under a different account. Solution: We recommended the following steps to resolve the issue: 1. Deactivate all plugins to prevent any interference. 2. Install the Adminer plugin to access and modify the server database directly. 3. Delete the old site key from the server database to remove any conflicts with the new license. We asked the client to confirm that they have a backup before proceeding with these steps. After these adjustments, the client should attempt to register the new site key.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Additionally, please check the related 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, you can also visit our support forum.
Problem: The client is experiencing issues with SSL validation for different language domains using WPML and SAM SSL. Initially, all domains were validated, but now they face intermittent validation failures, with error messages about security in incognito mode. Solution: 1. We recommend following the steps outlined in our guide on setting up different domains per language, which can be found here: https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/. It's possible that the validation message is a false positive. Try unchecking the validation checkboxes, save the settings, and then test your domains again. 2. Update your WPML plugin to the latest version (4.6.11) and all related add-ons. This update includes bug fixes and improvements that might help resolve your issue. Update instructions can be found here: http://wpml.org/faq/install-wpml/. Make sure to back up your database before making any changes.
If these steps do not resolve the issue, or if the solution provided here becomes outdated or seems irrelevant 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 at WPML support forum for further assistance.
Problem: The client reported that after activating the WPML Multilingual CMS, the search preview functionality provided by the 'FiboSearch - AJAX Search for WooCommerce' plugin stopped working on their live site, although it worked fine on the staging site. Solution: We recommended that after activating the WPML plugin, the client should navigate to WooCommerce > FiboSearch > Indexer and click on 'Rebuild Index'. This action should restore the search form's functionality in the frontend.
If this solution does not resolve the 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. Should further assistance be needed, please open a new support ticket at WPML support forum.
Problem: The client reported that the href attributes of linkable images in hexagon shapes were missing in the Hungarian translations of their website pages. This issue occurred after using the Advanced Translation Editor (ATE) and was consistent across multiple pages. The site uses Bricks builder. Solution: We temporarily fixed the issue by manually editing the images and applying the URLs on a staging version of the site.
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 (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 is experiencing an issue where the page in the secondary language displays an outdated version with old pictures and layout. Solution: We recommend updating the WPML plugin to the latest version (4.6.11) and all related add-ons to ensure you have the latest bug fixes and improvements. You can find the latest versions in your WPML account under My Account -> Downloads. If updates are not visible, click on the 'Check for updates' button in the Plugins → Add New Plugin → Commercial tab. Before updating, make sure to back up your database. After updating, if the issue still persists, try to update the page translation by slightly modifying the original page, saving it, and then navigating to the WPML translation editor to complete the translation.
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 problems continue, please open a new support ticket at WPML support forum for further assistance.
Problem: You need to translate elements like headers and footers created with GeneratePress and Blocks. Solution: We recommend following our detailed guide on how to translate these elements using WPML. You can find the guide here: Translating GeneratePress Theme Using WPML.
If this solution does not apply to your case, or if it seems outdated, please check the 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. We highly recommend opening a new support ticket if you need further assistance. You can do so at WPML support forum.
Problem: The client is experiencing an issue with a translated Gravity Form in English where one product field is missing after translation, despite working correctly in the original Estonian version. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to WPML-> String Translation 2. Search for
4. Clear the cache and check if the issue is resolved.
Please note that this solution might be outdated or not applicable to your specific case. If the problem 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: The client is trying to always retrieve the English slug names of a taxonomy for CSS purposes in different languages using the WPML plugin. They are using the
wpml_get_translated_slug
filter but are encountering issues where the slug is not consistently returned in English across different language settings. Solution: We advised the client to ensure they are using the correct parameters with the
wpml_get_translated_slug
filter. For retrieving the English version of a taxonomy slug, the code should look like this:
Additionally, we suggested checking the WPML > Settings > Taxonomy Translation to ensure that the English slug is correctly copied to other languages. If issues persist, we recommended testing the problem on a clean WordPress installation to isolate the issue. Further assistance with custom code, which is beyond WPML support scope, could be sought from certified WPML contractors, available here: https://wpml.org/contractors/
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.
Problem: The client is experiencing an issue where custom ACF fields in the primary menu are not translating correctly on a multilingual site. While the menu items themselves translate correctly, the custom ACF fields return null when viewed in Chinese, despite displaying data correctly in English. Solution: We recommend following the steps outlined in the ACF documentation for adding and displaying fields in menus. Specifically, you can modify the
functions.php
file in your theme folder to include the following code:
add_filter('wp_nav_menu_items', 'my_wp_nav_menu_items', 10, 2);
function my_wp_nav_menu_items( $items, $args ) {
// get menu
$menu = wp_get_nav_menu_object($args->menu);
// vars
$menu_text = get_field('test_menu_field', $menu);
// append html
$items = $menu_text . $items;
// return
return $items;
}
For further guidance, refer to the ACF documentation on adding fields to menus and displaying fields. If this solution does not resolve your issue, or if the documentation links are outdated, we recommend opening a new support ticket. Additionally, 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. If further assistance is needed, please contact our support forum.
Problem: The client is experiencing issues with the 'WooCommerce Quantity Discounts, Rules & Swatches' plugin on their multilanguage site using WPML. While the discount rules work correctly on the default English version of the site, they do not apply correctly on the translated versions of the product pages. Additionally, the second price option is not selected by default in the foreign languages as it is in English. Solution: We resolved the issue by ensuring that the discount rule values are copied to other languages: 1. Navigate to WPML > Settings > Custom Fields Translation and click on "Show system fields". 2. Search for the field "_wqm_tiers" and set the preference to "Copy", then save the changes. 3. Edit the product in the English language and click on Update to apply these changes to the translations. For the issue of the default quantity option not being selected, follow these steps: 1. Set the custom field "_wqm_settings" preference to "Translate". 2. Update the product in the original language and its translation to ensure the default quantity option is copied to the translated product pages. Refer to the documentation on translating custom fields for more details. Note: The 'WooCommerce Quantity Discounts, Rules & Swatches' plugin is not listed in our compatible plugins directory. We recommend contacting the plugin author to join our Go Global program to ensure full compatibility with WPML. Learn more about the program here: Go Global program.
If this solution does not resolve your issue or seems outdated, 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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client was experiencing a 404 error on the Portuguese homepage of their website after translation. Additionally, the header and footer were not visible on the translated pages.
Solution: 1. We identified a plugin conflict causing an infinite redirect and disabled the 'Redirect 404 to Homepage' plugin to resolve the initial access issue. 2. We discovered that the 'Edibbee' page, set as the front page, lacked translations in Portuguese and Spanish. We recommended translating this page to resolve the 404 errors. 3. For the URL structure, the language code 'pt-pt' is used as it is set in WPML -> Languages -> Edit Languages. We suggested creating a custom language for a different URL code if desired. 4. We addressed template translation issues by directing the client to https://wpml.org/documentation/plugins-compatibility/elementor/#translating-elementor-templates for guidance on translating Elementor templates. 5. We increased the WordPress memory limit from 40MB to match the PHP memory limit of 2GB, which resolved issues with saving translations.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise 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 https://wpml.org/forums/forum/english-support/.
Problem: If you're experiencing issues on your mobile site where internal links and tour package links do not redirect to the correct translations, this might be due to specific configurations that differ between desktop and mobile versions. Solution: First, navigate to Appearance->Menus in your WordPress dashboard to check if you are using a separate menu for the mobile version. If so, ensure that this menu is also translated. If you're not using a different menu for mobile, check if you are using a template for the menu area and confirm that this template is translated as well. Since you are using Elementor, we recommend following our guide on how to translate Elementor templates with WPML.
If this solution does not resolve your issue or seems irrelevant due to updates or different configurations, 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. We highly recommend opening a new support ticket if the problem persists. You can do so at WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
