Problem: The client reported issues with duplicate queries and missing translations in a multilingual WordPress setup using WPML and WooCommerce Multilingual (WCML). They also inquired about setting up a fallback option for untranslated products and categories. Solution: 1. We recommended deactivating WPML and WCML to check if the duplicate queries persist. After running WPML troubleshooting actions from WPML->Support->Troubleshooting, we identified that the remaining queries were not related to WPML. 2. For the fallback option, it can be enabled from WPML->Settings->Post Types Translation -> Translatable use translation if available or fallback to default language. We provided a link to our documentation for further guidance: documentation. 3. To address the issue of missing translations for product categories, we suggested setting certain taxonomies to "Translatable - only show translated items" from WPML -> Settings -> Taxonomies Translation.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, please check related known issues at https://wpml.org/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, you can also visit our support forum at WPML support forum.
Problem: The client needed to delete French and German languages from their site using MySQL because the backend option was not functioning properly. They had already started removing language entries from specific WPML tables but were unsure where else to look for remaining translated content. Solution: We advised that directly modifying the database to remove languages can be complex and risky, especially since WPML integrates deeply with WordPress's default tables. Instead, we suggested: 1. Re-enabling the languages in WPML. 2. Using the WordPress UI to filter and delete the content for each language. 3. Cleaning up any remaining entries from WPML's string tables using a query like:
DELETE FROM wp_icl_string_translations WHERE language='de';
4. Checking additional tables like
wp_postmeta
and
wp_termmeta
for any leftover data. If these steps do not resolve the issue, we recommended trying to clean up the site in a minimal setup or allowing us to assist further by providing temporary admin and FTP access.
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 at WPML support forum.
Problem: The client reported an issue with the SVI (Smart Variations Images) plugin for WooCommerce, which replaces the default WooCommerce gallery. The problem was that product photos were not benefiting from WPML's image translation feature, and translated attributes were not transferring over to the translated language.
Solution: After reviewing the documentation and conducting tests, we found that the issue is not related to WPML, as the metadata for images (such as alt text, description, title, etc.) was not being handled by the SVI plugin at all, even without WPML. We also informed the client about our Go-Global Program and that they could try to reach out to the plugin author for further compatibility assistance.
Please note that this solution might be outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking related known issues at WPML's known issues page, 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.
Problem: The client is trying to get "0 left" on all options in the WooCommerce Multilingual troubleshooting page but observes that after clicking "Start", and then refreshing the page, the options return to their previous count instead of remaining at "0". The client is unsure if this is the expected behavior or a problem.
Solution: We have confirmed that this behavior is expected. The counter shows the number of stocks that can be synced and does not indicate that those products are out of sync. The counter is meant to indicate progress; for example, if you have a thousand products, the counter will decrease to show when the syncing is done. Upon refreshing, the counter resets to the original count, which represents actual data that can be processed, not corrupted data.
We also inquired if the client is experiencing any issues with product translations, such as missing product variations, stock, or other product details on translated products, as this information would be important for us to know.
If this solution does not seem relevant to your situation, or if you are experiencing issues with product translations, please open a new support ticket with us.
