Problem: The client is setting up a French mirror of a .com site using WPML with integrated WooCommerce. The goal is to translate products and display French archives (categories and product types) with the same content as in English. However, the French category and type pages remain empty. In WPML → Support → Troubleshooting → Translatable custom posts linking, the product line shows --select-- and does not offer 'Products (product)'. After correction, Product types (product_type) = Not translatable, but the French archives remain empty and the client cannot start translation via duplication.
Solution: We recommend updating to WooCommerce Multilingual 5.5.3, as manual modifications in VariationMeta.php are no longer active due to updates overriding custom changes. Please follow these troubleshooting steps:
1. WooCommerce Multilingual – Troubleshooting Go to: wp-admin/admin.php?page=wpml-wcml&tab=troubleshooting Perform the following actions as shown in the screenshot provided.
2. WPML – Troubleshooting If the issue persists, go to: wp-admin/admin.php?page=sitepress-multilingual-cms/menu/troubleshooting.php Then in WPML → Support → Troubleshooting, perform the following actions:
Synchronize taxonomies of posts (first for products then for variations)
Clear the cache in WPML
Delete ghost entries from translation tables
Set language information
Correct the term count
Correct the content type assignment for translations
After these steps, please test a product in English and confirm: * Do the variations reappear on the product page? * Has the 'Out of stock' message disappeared?
If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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 at WPML support forum.
Problem: Si estás usando WPML en tu sitio y te aparece un mensaje cada vez que intentas editar algo, y no deseas usar la traducción automática. Solution: Este mensaje suele aparecer cuando intentas editar una traducción que fue creada usando el WPML Translation Editor con el Divi Builder. Para evitar esto, debes crear las traducciones manualmente usando el WPML Translation Editor. No es posible editar una traducción creada con el WPML Translation Editor utilizando el Divi Builder. Si prefieres usar Divi para crear una traducción desde cero, debes activar la opción adecuada, como se explica en este enlace. Para desactivar la traducción automática, ve a WPML > Translation Dashboard. Allí encontrarás un banner grande y visible para desactivar esta opción.
Si esta solución no resuelve tu problema o si la información parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: The client was unable to make WPML recognize Divi Builder's custom fields in the backend, despite them being visible on the frontend. The custom fields were not appearing as translatable, and the layout was not updating correctly. Solution: We resolved the issue by fixing specific data in the client's database, which allowed the Divi content to be recognized by WPML. To ensure that the texts are registered correctly, we recommended that the client update the original pages on Divi by making a small edit to a text and saving it. This action should help in syncing the translations properly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client manually installed the WPML Multilingual & Multicurrency for WooCommerce plugin, which is updated to version 5.5.3. However, the plugin appears as 'Not installed' in WPML and the WordPress support panel, causing issues with product variation translations and missing WPML features like the 'Multilingual e-commerce' menu. Solution: We recommend deactivating all plugins except for WPML to check for conflicts. This should be done in small batches, about 10 at a time, to ensure that any settings causing the issue are reset. After deactivating and reactivating, the variations should appear as expected. It is crucial to always have a backup before performing these steps. Additionally, always clear all caches after publishing a product and its translations to prevent similar issues. If the problem persists, please visit our support forum at https://wpml.org/forums/ for further assistance.
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 issue continues, do not hesitate to open a new support ticket.
Problem: If you're experiencing issues with translating a WooCommerce Bundled product where the translated product is missing settings like layout and pricing options, this might be due to the default language settings for certain variables. Solution: We recommend checking the settings for the min and max bundle size variables in your WPML settings. Here's how you can do it: 1. Navigate to WPML > Settings > Custom Fields Translations, and click on Show System Fields. 2. Set both
_wcpb_max_qty_limit
and
_wcpb_max_qty_limit
to Copy. This action will ensure that future translations copy over the value correctly.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
