Problem: After installing WPML and WooCommerce Multilingual, all variable products changed to grouped products and lost their prices and variations. Solution: 1. Remove all entries in
icl_translations
where the type is
tax_product_type
using the SQL query:
DELETE FROM `m7ug_icl_translations` WHERE `element_type` = 'tax_product_type';
2. Update WPML to the latest version. 3. Complete the WPML setup. 4. Run the troubleshooting function from WPML by navigating to WPML>Support> Troubleshooting > Set language information. 5. Update the product only if necessary.
If the issue persists or if this solution becomes outdated, 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client has a multilingual WooCommerce site and needs to use different SKUs for products translated into Latvian, without losing the language switcher functionality. The client also inquired about managing SKUs in different languages using WPML. Solution: We explained that in WPML, product translations must share the same SKU to sync stock and prices effectively across different languages. To use different SKUs, the client would need to create separate, original products for each language, which would not be linked as translations and thus would not support the default language switcher functionality. However, the client can create a custom language switcher or button that links to the respective products in different languages. We also provided links to documentation for further customization using hooks:
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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: If you're experiencing an issue where updating a page in the Russian language causes an ACF field to throw an error like
Fatal error: Uncaught ArgumentCountError: 42 arguments are required, 2 given in /wpml-st-translations-file-registration.php:100
we recommend the following steps.
Solution: Firstly, ensure you take a full backup of your website and database. It's highly advised to perform these steps on a staging or development site first to avoid compromising your live website. - Update all WPML plugins, especially WPML String Translation, to the latest versions. - Update all other plugins, especially those involved in the process, to the latest versions. - If necessary, update your theme to the latest version. After these updates, if the problem persists: 1) Clear all caches. 2) Deactivate all plugins except for WPML, String Translation, ACF, and ACFML. 3) Switch to a standard theme, such as 2024. 4) Check if the issue still occurs.
If you continue to face difficulties, 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing an issue with WooCommerce Multilingual where new products were showing a refresh icon instead of a pencil icon, which used to open the advanced translations editor for older products. Instead, clicking the refresh icon opened the default WordPress editor for the whole product. Solution: We identified that the refresh icon indicates that the default product has been updated, but the translation needs to be refreshed to match these changes. A known issue had been causing the advanced translation editor not to open for duplicated translated products, reverting to the native WordPress editor instead. This was documented in our Errata:
The issue was resolved in WooCommerce Multilingual version 5.3.3. We asked the client to confirm that they are using this version or a newer one to ensure the fix is applied. If the problem persists, we requested the WPML Debug information to better understand the site and system setup. The client can find guidance on how to provide this information here:
If the solution provided here is not relevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also highly suggest 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.
