Problem: If you're experiencing issues with product variations disappearing or being duplicated in different languages after updating WooCommerce Multilingual, it might be due to a language mismatch in the icl_translations table.
Solution: First, ensure that the post type
1
product_variation
is set to "Translatable - only show translated items" in WPML > Settings > Post Types Translation. If the variations are still incorrect, you may need to: 1. Remove all translated variations. This can be done by removing all translated products, which will also remove their variations. 2. Change the language of the affected variations to match the original product language using an SQL query:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
#First we obtain the language andstore it asa variable
SET @language_code = ( SELECT language_code FROM wp_icl_translations WHERE element_type = 'post_product'AND source_language_code IS NULL LIMIT 1 );
#We get here the post_product IDs forease of use
CREATE TEMPORARY TABLE temp_ids AS
SELECT element_id
FROM wp_icl_translations
WHERE element_type = 'post_product'AND source_language_code IS NULL;
# We update the post_product_variations based on the post_parent in wp_posts
UPDATE wp_icl_translations
SET language_code = @language_code
WHERE element_id IN (
SELECT ID
FROM wp_posts
WHERE post_parent IN (SELECT element_id FROM temp_ids)
) AND element_type LIKE "post_product_variation";
#Here we clear the temporary table so that we leave no trace
DROP TEMPORARY TABLE IF EXISTS temp_ids;
Alternatively, you can remove and re-create the variations in the original language products. 3. After making these changes, you can update WooCommerce Multilingual to the latest version and re-update products in the original language.
Please ensure you back up your database and website before making any changes. If the variations are still not displaying correctly after following these steps, you may need to re-translate the product to ensure the variations are correct in the secondary languages.
If this solution does not apply to your situation, or if it seems outdated, 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 issue persists, please open a new support ticket with us.
Problem: The client is experiencing critical errors when trying to translate products after importing them using the WooCommerce Multilanguage Plugin. The errors indicate deprecated functions and type errors. The client prefers using the classic editor and notices that manually created products can be translated without issues, whereas imported products cannot.
Solution: We first asked the client to import the products on a test site provided by us to see if we could recreate the issue. We also requested the import files for further examination. After testing, we found that the translation worked as expected on our test site. We then suggested the client create a staging site and perform the following steps: 1) Disable all plugins not related to WPML and test again. 2) If the issue persists, switch to a default theme like Twenty Twenty-One to check if the theme is causing the issue. 3) If the problem is still unresolved, reactivate plugins one by one or in small groups to identify the problematic plugin. If the issue continues with a default theme and only WPML plugins are active, we offered to investigate further by requesting access to the client's site.
Please note that this solution might be outdated or not applicable to your case. If you're experiencing similar issues, we recommend checking the related known issues, verifying the version of the permanent fix, and ensuring you have the latest versions of themes and plugins installed. If the problem persists, please open a new support ticket with us for further assistance.
Problem: The client was experiencing an issue where they had to retranslate product variation terms every time they made changes to a product in a non-original language. The variations were originally in Dutch and needed to be translated into other languages, but the translations were reverting back to Dutch after any update.
Solution: We reviewed the translation settings for the Variations post type and found that it was set to "Not Translatable." We changed this setting to "Translatable - only show translated items" from WPML > Settings > Post Type Translation and updated the English translation of the variations accordingly. After this adjustment, the variation translations remained intact even after updates to the Dutch product. We recommend the client to try updating their products again to see if the issue is resolved.
If you're experiencing a similar issue, we recommend checking the translation settings for your Variations post type and ensuring that it is set to "Translatable - only show translated items." Then, update your translations accordingly. If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
Problem: The client was experiencing a critical error when trying to translate a product in WordPress using WPML. He did a reset and got a new error in the dashboard.
Solution:
1. We recommended performing another reset as was no translations done and before reactivating WPML or configuring it, to deactivate all plugins and switch to the default theme. 2. If the error continued, we advised checking the guide on missing database tables at https://wpml.org/errata/missing-_icl_strings-_icl_string_translations-data-tables/. It's important to back up the database before making any changes. 3. We asked the client to verify if the
1
_icl_strings
table existed in their database and if so, to try closing the error message. 4. We suggested checking for the problematic string in WPML → String Translation and deleting it from there. 5. If the issue was still unresolved, we recommended deactivating all plugins except for WPML, WooCommerce Multilingual & Multicurrency, and WooCommerce, and then attempting to close the message again.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue 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 necessary, please open a new support ticket with us for further assistance.
