Problem: In a WooCommerce shop with multiple languages, the 'product-category' slug was translated for different languages. However, for the German language, setting the slug to 'produkte' results in a 404 error when visiting the page. The backend shows the Dutch translation instead.
Solution: We analyzed the issue and determined it is not directly related to WPML or WooCommerce, but rather to the permalink structure used. WordPress uses specific rules to determine what content to display based on the URL visited. If both single products and product categories share a similar permalink base (e.g., site.com/products/), WordPress may struggle to differentiate between product requests and product category archive requests, leading to errors like the one experienced. We recommend changing the permalink structure so that products and product categories do not use the same base. For example, use 'products' for the product category base and '/product/%product_cat%/' for the custom product base. This adjustment should resolve the issue.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client has automatically translated their GravityForms using WPML and now needs to make slight changes to the translations. Solution: We recommend that the client sends the form again for translation and updates the translation in the WPML editor. This can be done by navigating to WPML -> Translation Management. For detailed instructions, please check the following documentation:
If this solution does not apply to your case, or if it seems outdated, we encourage you to open a new support ticket. We also 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. For further assistance, please visit our support forum: https://wpml.org/forums/forum/english-support/.
Problem: The client needed assistance with translating two custom menu items that were not automatically translated on their multilingual website. Solution: We advised the client that WordPress automatically displays an array of pages in the menu if no menu is set, even without WPML. To resolve the issue, the client should create a translated version of their menu. Once a menu in another language exists, they can manually add a translated label or custom item in the second language. We also reminded the client to refer to the documentation: https://wpml.org/documentation/getting-started-guide/translating-menus/#option-2-translating-menus-manually
Please note that this solution might not apply to your situation if it's outdated or not relevant to your 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 with us.
Problem: The client was experiencing issues with Advanced Custom Fields (ACF) data not displaying correctly when previewing a page. The site was already running on PHP 8.3, which is not fully compatible with WordPress and WPML.
Solution: 1. We recommended downgrading PHP to version 8.1 to check if the issue persists, as PHP 8.3 might cause compatibility issues. 2. We requested a copy of the client's website to escalate the issue to our second-tier support team. 3. We provided a workaround code to adjust the ACF data display and confirmed that the issue is a known bug and will be addressed in a future update of WPML.
Please note that the solution provided might be irrelevant due to it being outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, please open a new support ticket with us.
