Problem: If you're experiencing issues with incorrect item numbers displaying in the Brand filter across multiple languages, it might be due to the translation settings of your 'Product Brand' post type. For instance, if the Brand filter shows 45 products for a brand that only has 9, this could be because the product count is being multiplied by the number of languages. Solution: We recommend checking the translation preference for the 'Product Brand (product_brand)' post type within your WPML settings. Navigate to WPML > Settings and in the 'Post Type Translation' section, change the translation preference for 'Product Brand' to 'Translatable - only show translated items'. After making this change, retranslate the product. This should ensure that the Brand count reflects the correct number of products assigned to the brand in the active language.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with WooCommerce product variations not appearing in the Advanced Translator after making changes. Despite updating images and text in the product variations, these changes were not reflected in the translation interface.
Solution: We advised the client to ensure that the translation preferences for the fields were set to Translate in "WPML > Settings > Custom Field Translation". It was also important to update the product after making changes to the variations and to clear both site and browser caches. If the issue persisted, we recommended running a troubleshooting tool available under WooCommerce > WooCommerce Multilingual > Status and selecting specific options to synchronize the data.
If this solution does not resolve the issue or 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 the problem continues, please open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing issues with importing product attributes in multiple languages using WP All Import. While test imports work fine, during real imports with many attributes, only some attributes are correctly transferred to the translated product. The client has tried synchronizing attributes, deleting products, and re-importing, but the issue persists. Solution: We identified that the problem arises because the attribute names in the original and translated imports are the same. According to our WP All Import guide, attribute names must differ between the original and translated versions during the import process. We recommend renaming the translated attribute names before import and, if necessary, renaming them back after the import is complete. For detailed steps and more information, please refer to our guide on importing multilingual terms with WP All Import and WPML: Importing Multiple Languages with WP All Import and WPML.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Additionally, please feel free to open a new support ticket for further assistance at WPML Support Forum.
Problem: Si estás experimentando un error fatal al activar el plugin WooCommerce Multilingual que indica: 'Fatal error in /wp-content/plugins/woocommerce/src/Internal/Traits/AccessiblePrivateMethods.php on line 164', y este error solo ocurre en el admin y no en el front. Solution: Te recomendamos actualizar el plugin WooCommerce a su última versión, que actualmente es la 9.1.4. Asegúrate también de que la versión más reciente de WooCommerce Multilingual (5.3.6) esté instalada en tu sitio.
Si esta solución no resuelve el problema o si parece no ser relevante debido a que está desactualizada o no se ajusta a tu caso, te sugerimos abrir un nuevo ticket de soporte. Te recomendamos encarecidamente revisar los problemas conocidos, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: If you're experiencing issues with the WooCommerce shopping cart not adding more than 2 products or forgetting products when the WooCommerce Multilingual & Multicurrency plugin is enabled, this might be due to a plugin conflict. Solution: We recommend following the steps outlined in the WPML support forum to resolve this issue. You can find the detailed steps here: WPML support forum thread.
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. Should these steps not resolve your issue, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: You are using the Flatsome theme with WooCommerce, and you've added 'Top Content' and 'Bottom Content' using Flatsome UX Blocks on your product pages. These blocks display correctly in the default language but are missing on the translated pages. Solution: We manually inserted the UX Blocks for the translated product category pages. Please verify if the blocks now appear as expected on your translated pages. If the blocks are still not displaying correctly, this might be due to a configuration issue or a compatibility problem between the theme and WPML.
This solution might be outdated or not applicable to your specific case. 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.
