Problem: You are running a multilingual WooCommerce site and encountered an error stating that 'Some taxonomies in your site are forced to be untranslatable.' This issue is affecting the functionality of your multilingual site. Solution: First, ensure you have a backup of your site. Then, navigate to WooCommerce > WooCommerce Multilingual > Status to check for any messages or errors. Next, go to WPML > Settings > Taxonomy Translation. Here, ensure all related product taxonomies are set to either
'Translatable - only show translated items'
or
'Translatable - use translation if available or fallback to default language'
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please contact us through our support forum.
Problem: If you're experiencing issues where your product URLs do not display the correct translated slug in secondary languages initially, and only correct themselves after switching languages back and forth, this might be due to the fallback feature. Solution: We recommend two steps to address this issue: 1. Disable the fallback for products to prevent untranslated products from showing in the default language. For guidance on this step, please refer to our documentation: Disable fallback for products. 2. Duplicate the products to ensure they appear in all target languages. This can be efficiently done using WPML's bulk duplication feature. For more details, visit: Duplicate products.
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 you need further assistance, please open a new support ticket at WPML support forum.
