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
_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.
