Problem: The client is experiencing unresolved issues with their WordPress site using WPML, specifically related to 404 errors when translating product brand slugs. Solution: If you're experiencing similar issues, we recommend trying the following workaround: Navigate to Settings > Permalinks in your WordPress dashboard, and manually set a static value for the brand slug. Initially, 'brand' will appear as a placeholder slug. To use 'brand' as a manually set slug, you must edit the field, type the value, and save it. This solution is based on a known issue which can be further explored here: Translating Product Brand Slug Can Lead to 404s.
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 persists, please open a new support ticket at WPML support forum for further assistance.
Problem: When creating a new product in WooCommerce and adding a link in the product description, then translating the product using WPML, the link in the translated version incorrectly points to the original language's target page instead of the translated page. Solution: 1. Navigate to WPML → Languages → Make themes work multilingual. 2. Enable the option 'Adjust IDs for multilingual functionality'. 3. Re-save the translated products to ensure the links point to the correct translated pages. Additionally, ensure that the URL in Settings → General matches the site's protocol (https://). If it is set to http://, update it by adding an 's' to make it https://. This adjustment can resolve issues with incorrect link redirection in translated content.
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 problems persist, please open a new support ticket.
Problem: If you're experiencing a 'page not found' error when trying to access product category pages on your translated WooCommerce site using WPML, the issue might be due to missing translations. Solution: We recommend checking the WPML → Taxonomy Translation → Product Categories to ensure that the Plural translation field is not empty. If it is, fill in the missing translation. Next, remove the product-category slug from String Translation, update the permalinks, and re-translate the slug. This should resolve the 404 error.
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 https://wpml.org/forums/ for further assistance.
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 needed to know if they should use the 'Store a language cookie to support language filtering for AJAX' option with their WPML setup that uses different languages in directories. Solution: We advised the client that it is necessary to keep the 'Store a language cookie to support language filtering for AJAX' option active, especially since their website is a WooCommerce site. This feature is crucial for various functions such as handling different currencies and add-to-cart functionalities. If you're experiencing similar concerns, we recommend that you ensure this option is checked.
For more details on enabling the language cookie for AJAX filtering, you can refer to our documentation here.
If this solution does not apply to your case, or if it seems outdated, please check the 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. Should you need further assistance, do not hesitate to open a new support ticket with us.
