Problem: The client was experiencing an issue where the translation of a page containing a shortcode was getting stuck. The specific page in question was 'My Wishlist' which was not translating and was showing a 504 error after some time. Solution: We recommended the following steps to resolve the issue: 1. Edit the 'My Wishlist' page and make a small change in the content, then save the changes. 2. Navigate to WPML -> Translation Management. 3. Select the 'My Wishlist' page and assign it to your user for translation. 4. Check if you can now translate the page or cancel the translation job. Additionally, for translating specific strings, go to WPML -> String Translation or WPML -> Translation Management -> Strings section at the bottom.
If these steps do not resolve your 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.
Problem: The client is experiencing issues with brand translations in WooCommerce after setting the Brands taxonomy to 'Translatable'. Brands appear multiple times when adding a product, and translated brand pages show a 404 error. Solution: 1. Set the Brands taxonomy to 'Translatable' in WPML -> Settings -> Taxonomies Translation. 2. Navigate to Products → Brands and filter by language. Delete the translations of the Brands. 3. Set the Brands taxonomy back to 'Not Translatable'.
If you need to set Brands translatable, use a temporary workaround, add brand to the Product brand base in Settings → Permalinks and save the changes. This should improve the URL behavior temporarily for Brands until a complete fix is released in future updates of the WooCommerce Multilingual plugin.
Please remember to make a backup before making these changes. If this solution does not resolve your issue or seems outdated, we 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: You are experiencing a 404 error when accessing product category URLs in Dutch on your WordPress site using WPML. The issue arises because the URL does not translate correctly. Solution: We recommend checking the translation settings in WPML for your product categories. Specifically, go to WPML → Taxonomy Translation → Product Categories and ensure that the Plural translation field is not left empty. Filling in the missing translation should resolve the 404 error.
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.
Problem: The client is experiencing an issue where not all products are displayed in the menu on their multilingual site using WPML. Specifically, in the default language (Dutch) and some other languages, certain products like 'Ingeblikt fruit', 'ingeblikte groente', and 'Olie' are missing. The client also uses B2BKing and has ensured that each product category has all visibility options set. Although the WPML Menu synchronization shows all items, they do not appear on the website's front end. Solution: We recommend contacting the authors of B2BKing, as the issue might be related to how B2BKing interacts with WPML. It would be beneficial for B2BKing to join our Go-Global program to achieve WPML certification, which could potentially resolve compatibility issues.
If this solution does not apply because it is outdated or not relevant 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 issue persists, please open a new support ticket.
Problem: The client is facing an issue where changing the status of a product to 'Draft' in the Dutch version does not automatically change the status in other language translations. The client desires that when the primary language product is set to 'Draft', all translated versions should automatically reflect this status. Solution: We explained that by default, WPML does not synchronize the post statuses across translations as per user feedback. However, to achieve the desired behavior, the client can add a custom code snippet. This code should be added to the functions.php file of a child theme or a Code Snippet Plugin. The code ensures that when the status of a product is changed in the primary language, it automatically updates the status in all other translations to match. Here is the code snippet.
If this solution does not apply or is outdated, we 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 issues persist, please open a new support ticket.
Problem: The client is experiencing an internal error 500 on their website, which is indicated by the PHP error log showing 'AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error.' This issue arises from a probable misconfiguration in the .htaccess file. Solution: We recommend updating the permalinks as a potential solution to resolve the internal redirects issue. This action can reset any incorrect settings in the .htaccess file that might be causing the problem. If you're experiencing this issue, try updating your permalinks and check if the error resolves.
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 WPML support forum for further assistance.
Problem: The client is unable to automatically translate the attributes of products on their WooCommerce site using WPML. The attributes for one product are not translating at all, despite following the relevant WPML documentation.
Solution: We recommend trying the following steps to resolve the issue: 1. Create new attributes. 2. Create simple and variable products. 3. Add attributes to these products and create variations for the variable products. 4. Attempt to translate these attributes automatically.
If the products were imported, they might not translate automatically. In this case, manually translate the attributes from WooCommerce -> WCML -> Attributes and then synchronize them by: - Ensuring the attributes are properly assigned to the fully translated product. - Navigating to WooCommerce > WooCommerce Multilingual ⇒ Attributes - Selecting the attribute assigned to the product. - Scrolling down and clicking on the "Synchronize attributes and update product variations" button.
Repeat these steps for each attribute assigned to the products.
If this solution does not resolve your issue or seems irrelevant due to being 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.
