Problem: The client was experiencing issues where the page broke after using WPML's automatic translation feature. This problem was often due to differences in page or theme settings between the original and translated versions, or sometimes due to resource limitations. Solution: 1. Check Page-Specific Settings: Ensure that layout, sidebar, or theme-related settings are consistent between the original and translated pages. 2. Increase WordPress Memory Limit: Modify the
wp-config.php
file to increase the memory limit to at least 256M. 3. Increase MaxInputVars: Contact the hosting provider to increase
max_input_vars
to 10000 for handling complex pages. 4. Adjust Internal Links: Use WPML’s tool to update internal links. 5. Check Custom Fields for Bricks Content: Ensure WPML is set to translate custom fields used by page builders like Bricks. 6. Perform a Conflict Test: Disable all plugins except WPML and the page builder, and switch to a default theme to check if the issue persists. If these steps do not resolve the issue, it might be due to outdated solutions or specific circumstances not covered here. 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 the problem continues, please open a new support ticket at WPML support forum.
Problem: You are trying to translate a description taxonomy on your WordPress site using WPML, but the translation is not appearing on the frontend. Solution: We recommend checking the WPML settings to ensure that the “Adjust IDs for multilingual functionality” option is enabled. This setting is crucial for the theme to function correctly. You can enable this option by navigating to WPML >> Languages. Once enabled, this should resolve the issue with the translation not appearing on the frontend.
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 do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to edit the category slug, but it is not saving. Solution: First, ensure you back up your site. Then, navigate to Plugins > Add New and select the Commercial tab. Here, click on Search for Updates and install the latest versions of our plugins. After updating, test to see if the issue with the taxonomy slug not saving is resolved. Additionally, check if a third-party plugin, such as Taxonomy Switcher, might be causing the issue by temporarily deactivating it and testing again.
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 problems persist, please do not hesitate to open a new support ticket with us at WPML support forum.
Problem: You are unable to access your store's orders from the WooCommerce app when WPML is activated, although products are synchronizing correctly. Solution: 1. Ensure you have a backup of your site. 2. Disable all other plugins, leaving only WPML plugins and WooCommerce active. 3. Switch to the WordPress default theme. 4. Check if the issue with order synchronization in the WooCommerce app persists. 5. If the problem continues, provide access to a staging site for further investigation.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: If you're trying to change the language on a WooCommerce order-pay page and encountering issues where the URL does not translate correctly, leading to the incorrect template being loaded. Specifically, the '?pay_for_order=true' parameter is missing in the translated URL, which causes WooCommerce to change the template. Solution: We recommend using WPML's feature to preserve URL arguments. You can find this setting under WPML -> Languages -> Language switcher options. Enabling this option will ensure that the 'pay_for_order' argument is preserved when switching languages on an order page. For more details, please check the documentation on preserving URL arguments here.
If this solution does not resolve your 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 further assistance is needed, please open a new support ticket here.
Problem: You are trying to use the WPML plugin to translate content, but the translator is not opening at all. It remains stuck and does not load the content. The error log shows a status of 503, indicating a server-side issue. Solution: We recommend that you test the translator again to see if the issue has been resolved. It is possible that the problem, which was related to a server error, has already been fixed.
If the problem persists, it might be due to an outdated solution or a different issue not covered here. 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 none of these steps resolve the issue, please open a new support ticket at WPML support forum for further assistance.
