Problem: The client is unable to translate certain parts of the new WooCommerce checkout block using WPML, specifically the strings stored in JSON files which do not translate through the usual String Translation interface. Solution: Please ensure that WooCommerce is updated to the latest version, as version 9.2.3 includes updates that might resolve translation issues on the checkout page.
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 for further assistance.
Problem: You are using WPML > String Translation to translate contents from an Option page created with Jet Engine, aiming to update data on various pages like the homepage on a Spanish website. While you can translate the labels, the values remain in the default language. Solution: We recommend using the standard string translation method to translate these option values into English. You can find a detailed guide on how to do this by following this link: guide.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to translate the WooCommerce Gateway descriptions and titles using WPML, but despite the strings appearing in String Translations, they still display in the main language (German). Additionally, the client is experiencing issues with the Quick Edit functionality in English and different translation masks for shop products. Solution: We recommend resaving the default language settings or fields to ensure that the translations are correctly reapplied. It is essential to use the WooCommerce Multilingual plugin, as it is necessary for WooCommerce to function correctly with WPML. If you're experiencing issues with specific parts of the plugin or its functionality, we suggest opening a new support ticket to discuss possible workarounds.
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 do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to delete all content for a particular language using the instructions from https://wpml.org/faq/how-to-completely-remove-a-language-from-your-site/, but the process is slow and the number of assets decreases only slightly. Solution: If the number of assets is decreasing, even slowly, it indicates that the process is working. The speed of deletion depends not on WPML but on your hosting/server resources. We recommend disabling all other plugins temporarily to see if this speeds up the process. Additionally, consider contacting your hosting provider to discuss upgrading to a more robust hosting package. Please be aware of a known issue where taxonomies are not deleted when using the 'Delete content from database' option, detailed here: https://wpml.org/errata/taxonomies-are-not-deleted-with-the-delete-content-from-database-option/.
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.
Problem:
The client is experiencing 500 Internal Server Errors on translation pages (/ru and /en) when WPML Multilingual CMS is active. The issue persists despite disabling other plugins, updating permalinks, and checking .htaccess configurations.
Problem: The client was unable to reassign credits from live websites back to available credits in their WPML account. Solution: We advised the client to unregister WPML using the old keys and then re-register it with new keys. Here are the steps we recommended: 1. Visit https://wpml.org/account/sites/ and remove the current site key. 2. Generate a new key for each site. 3. Go to the website's backend, navigate to Plugins > Add New > Commercial, and unregister WPML from the old key. 4. Re-register WPML using the new key. 5. Follow the steps outlined in https://wpml.org/documentation/automatic-translation/how-to-assign-automatic-translation-credits-to-your-sites/ to add credits to each site.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're trying to translate products on your site using WPML and find that clicking the + icon from the 'All Products' page leads you to the translation queue instead of the advanced translation editor, this summary is for you. Solution: We recommend you follow these steps: 1. Make a complete backup of your site. 2. Navigate to WPML → Support and click on the Troubleshooting link. 3. Click 'Synchronize local job IDs with ATE jobs' and 'Synchronize translators and translation managers with ATE'. If this does not resolve the issue, proceed with the following steps: 1. Go to WPML → Translation Management → Translators tab. 2. Add your user account as a translator and assign the language pairs. 3. Check if you can now use the Advanced Translation Editor.
If the solution provided here 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 these steps not resolve your issue, please do not hesitate to open a new support ticket at our support forum.
Problem: If you're unable to find and translate the placeholder text 'Search entire site' to French in your WPML setup, even after trying to enable auto-register strings. Solution: First, ensure that you scan your theme files for strings that might not appear on the WPML String Translation page. You can find detailed instructions on how to do this here: Scan the Theme or Plugin. If the string still doesn't appear, you might need to access the 'Translating Strings From Admin and Settings' section to add the string manually to String Translation. Detailed steps can be found here: Translate Admin and Settings Strings. Lastly, if the strings appear reversed in different language versions of your site, ensure that you have correctly assigned the languages to each string in the WPML String Translation interface.
If this solution does not resolve your issue or 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 WPML Support Forum.
Problem: You are trying to use a variable within functions.php in a custom shortcode for your WordPress site, but the text within the variable is not being recognized by WPML for translation. Solution: The strings you are attempting to translate are not following the WordPress localization standards, which is why WPML cannot register them for translation. To resolve this, you need to modify your code to adhere to these standards. Here is how you can update your code:
_e( 'Congratulations! Shipping is on us :', 'my-theme' )
_n('Free delivery on orders of %s or more.', wc_price( $min_amount ), 'my-theme' )
After updating, ensure to perform a full site backup. Then, scan the theme for the strings to translate by following the instructions here: Scanning the theme or plugin.
If this solution does not apply to your case, 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 WPML Support Forum.
Problem: When cancelling a WooCommerce Booking in wp-admin, a fatal error occurs related to the cancellation email. This issue is due to a conflict between WooCommerce Multilingual & Multicurrency and WPML Multilingual CMS.
Solution: We recommend modifying the code in the WooCommerce Multilingual plugin to handle null values correctly. Specifically, in the file
If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, please check the related known issues 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: When using the Woodmart theme with the Layout Builder, product variations display correctly in the main language but show as 'This product is currently out of stock and unavailable' on the translated page. The issue persists even after edits in the
class-wcml-synchronize-product-data.php
file. Solution: If you're experiencing this issue, we recommend checking if the 'Show only products with custom prices in secondary currencies' option is enabled. If it is, please disable this option. This should resolve the problem where product variations do not display correctly on the translated page.
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: If you're experiencing a fatal error when accessing the Pronamic plugin in the admin site, particularly when a custom post type has no posts, this might be due to a specific configuration issue.
Solution: We have identified that the issue is not directly caused by WPML. However, setting
'hierarchical' => false
in the Pronamic Pay with Rabo Smart Pay for WooCommerce plugin's custom post type (CPT) registration can prevent this issue. This adjustment addresses the root of the problem by modifying how the CPT is handled.
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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is working on a site under development using WPML and has encountered an issue where two URLs point to the same product category, but one of them should not be available as it is intended for the English site. Solution: We reviewed the site's configuration in WooCommerce Multilingual and WPML Settings and found no initial misconfigurations. However, we identified that a custom permalink plugin might be altering the permalink settings for categories and archives, potentially causing the issue. We recommend: 1. Disabling the "Custom Permalinks" plugin. 2. Resaving the permalink structure by navigating to Settings > Permalinks on your dashboard. 3. Checking if the issue persists after these changes. If the problem continues, consider setting up a testing site to replicate the issue, allowing us to troubleshoot without affecting your main site.
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. We highly recommend opening a new support ticket if needed at WPML support forum.
Problem: You are trying to get embedded Hubspot contact and subscribe forms to translate automatically on your site. You have created separate instances for each language, but you prefer an automatic translation solution. You are also unable to find the embedded content after moving scripts and creating shortcodes.
Please note that this solution might be irrelevant if it's 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 was unable to translate the 'Listings' & 'Reviews' tabs under their Profile page on the BuddyBoss theme and BuddyBoss Pro, which are created by the Geodirectory plugin. They could not find these tabs in string translation or admin text. Solution: We resolved the issue by registering the specific strings for the 'Listings' and 'Reviews' tabs in the WPML String Translation. The client should now see these tabs correctly translated into French in their profile section. If you're experiencing this issue, we recommend checking if the strings are properly registered and translated in the WPML String Translation.
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 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
