Problem: You are trying to have the 'free shipping note' and product custom fields translated and stored separately for each language on your WooCommerce + WPML site. Despite setting problematic fields to 'Translate' in WPML settings and editing each product in every language, the value is still overwritten globally. Additionally, some fields are not available in WPML String Translation. Solution: We recommend enabling the 'Show "Multilingual Content Setup" meta box on post edit screen' option in WPML > Settings > Custom fields. After enabling this, go to your default language product, scroll to the bottom, click 'Show system fields', find the related fields, set them to 'Translatable', and save. This should allow each field to hold and display its value independently for every language.
If this solution does not resolve your issue or seems outdated, please check the related known issues and verify that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at WPML support forum.
If this solution does not resolve your issue or seems irrelevant, 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 for further assistance.
If you're experiencing PHP deprecated warnings in your WooCommerce Multilingual plugin, similar to the ones reported where the required parameter $wpdb follows an optional parameter $post_translations in the file class-wcml-products.php, this summary is for you.
Solution:
We have escalated this issue to our developers, and a fix will be included in a future version of the WooCommerce Multilingual & Multicurrency plugin (most probably in 5.5.1). We recommend waiting for this update, which will address the deprecated parameter order issue.
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 problem persists, please open a new support ticket.
If you're experiencing an HTTP 500 error when trying to generate the core WordPress sitemap (https://cdn.wpml.org/wp-sitemap.xml) with WPML String Translation activated, it might be due to a conflict or a specific issue with the plugin setup.
Solution:
We recommend checking if you are using any SEO add-on plugins that might conflict with WPML, such as Broken Link Checker by AIOSEO
Additionally, setting up a staging or development site, a clone of your live site, allows us to safely troubleshoot the issue without affecting the live environment. This is especially helpful when testing with only the essential plugins active and a default theme enabled.
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.
Problem: You are unable to translate specific text appearing on your website. Solution: We recommend following these steps to ensure the text is properly registered for translation: 1. Navigate to WPML → String Translation. 2. Enable the Look for strings while pages are rendered option. 3. Visit the page where the untranslated text appears. 4. Return to WPML → String Translation and verify if the new text has been registered. 5. Proceed to translate the newly registered text. For more detailed guidance, please refer to our documentation on Finding Strings that Don’t Appear on the String Translation Page.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are experiencing inconsistent translations and sometimes missing text blocks when translating product descriptions using WPML String Translation. Solution: We recommend not using WPML → String Translation for translating product descriptions directly. Instead, navigate to WooCommerce → WooCommerce Multilingual & Multicurrency, and click on the translation icon. This will open the translation editor, where you can make translations directly in the editor.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific 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.
