Problem: The client is experiencing an issue where the automatic translation process via WPML is stuck, showing 0/xx pages and continuously spinning without completing. The process does not complete even after attempting to cancel and restart the translation jobs. Solution: 1. We checked the connection key between the client's website and our ATE server and fixed an issue. We recommend the client to try re-translating the pages later in the day. 2. We advised the client to disable object caching and security plugins temporarily while performing translations to avoid interference with the process. After completing the translations, these can be re-enabled. 3. If the problem persists, it might be due to ongoing issues with our ATE server, and we suggest trying again after a few hours.
Please note that the solution might be irrelevant if it's outdated or not applicable 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 at WPML support forum for further assistance.
Problem: The client was experiencing slow page load times on their WooCommerce site and was unsure about the necessity of the 'make it multilingual with ID' feature for their theme. They also encountered a PHP error related to the theme triggering a function incorrectly, which could affect WPML String Translation performance.
Solution: 1. We adjusted the WPML settings for 'product_variation' post type to 'Translatable - only show translated items' to ensure global product attributes can be translated. 2. We recommended running the troubleshooting options available under WooCommerce > WooCommerce Multilingual & Multi-Currency > Status > Troubleshooting to help improve site performance. 3. We deactivated the unsupported 'WPML All Import' addon and suggested removing unnecessary plugins. 4. We identified a PHP error caused by the theme related to the premature loading of text domains. We advised reporting this to the Porto Support Team and provided a link to further information on this issue: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/ 5. We tested the site with a default theme, which significantly improved the load time, suggesting the theme might be a contributing factor to the performance issues.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 issues persist, please open a new support ticket at our support forum.
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
1
'Translatable - only show translated items'
or
1
'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.
