Problem: You are trying to delete language content from the database but are encountering issues where the content does not delete from the front end and the process gets stuck. Solution: First, try to deactivate the language in WPML. A dialog should appear under WPML > Languages > Language Setup which allows you to remove old translations. If this does not resolve the issue, you may need to remove the contents manually from the backend. For more detailed guidance, please read our documentation on deleting languages and plugin data.
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 WPML support forum.
Problem: You are working on a site under development and need to translate the Elementor header for mobile view using WPML. Solution: If your mobile header was created using an Elementor template, we recommend following the steps described in this section of our guide to translate it: Translating Elementor Templates.
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: You are trying to translate strings on your site using WPML, but the translations only work when 'Look for strings while pages are rendered' is enabled. This issue is likely due to recent changes in how WordPress handles language files, which affects themes and plugins. Solution: 1. This problem is not directly caused by WPML but by changes in WordPress. A solution might be to downgrade your WordPress to the previous version. Follow these instructions to downgrade: Downgrade WordPress. 2. If downgrading does not resolve the issue, WPML has released a temporary fix for this problem. Please check the errata here: WPML String Translation fix.
If these solutions do not work for you or seem outdated, we recommend opening a new support ticket. Also, check related known issues at WPML 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: WPML Support Forum.
Problem: The client was experiencing an issue where activating the WPML String Translation plugin caused products to disappear from the WooCommerce product category archives in the secondary language.
Solution: We found that within WooCommerce > WooCommerce Multilingual > Multicurrency settings, the option "Show only products with custom prices in secondary currency" was enabled. This setting was causing the products to not display because there were no products with manually set prices in the secondary currency. By deactivating this setting, the translated products started to appear correctly in the translated category archives.
If you're experiencing this issue, we recommend checking the Multicurrency settings in WooCommerce Multilingual and ensuring that the "Show only products with custom prices in secondary currency" option is disabled unless you are manually adding prices in the secondary currency for each product.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. 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 the problem persists, please open a new support ticket with us.
