The client was experiencing issues with automatic translations getting stuck in the queue after moving their webshop to a new host. Despite trying several troubleshooting steps such as deregistering and registering the site with a new key, and enabling auto translation, the problem persisted.
Solution:
We discovered that the issue was due to a conflict between the IDs of translation jobs and the site ID on our ATE server. Our developers resolved this conflict, ensuring that the automatic translation functioned correctly.
If you're experiencing similar issues, we recommend checking for potential ID conflicts or reaching out for support.
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.
The client is interested in AI automatic translation between Dutch and German using WPML.
Solution:
We have recently updated WPML AI to include automatic translation from Dutch to German. We recommend you try this new feature and provide us with your feedback.
Please note that this 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 you still need assistance, please open a new support ticket at WPML support forum.
You are experiencing issues with WPML's AI Auto Translate feature not working, encountering an API error stating 'No sitekey found for this website', and translations are stuck in the queue.
Solution:
First, ensure that you have the correct sitekey configured for your website as it is essential for the AI Auto Translate feature to function properly. If you are unsure about how to check or update your sitekey, please refer to our documentation here: WPML Documentation.
Additionally, we have recently updated our AI Auto Translate feature to support new language pairs such as Dutch to English and French. We recommend trying this updated feature to see if it resolves your issue.
If the problem persists or the solution provided here is not relevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client was unable to translate attributes in WooCommerce Multilingual & Multicurrency. Despite setting the taxonomy language to Dutch, the translation pencil icon was unresponsive, and an E_ERROR was encountered in the WPML plugin files. Solution: We recommended checking the documentation on translating and synchronizing global attributes in WooCommerce Multilingual, available here: https://wpml.org/documentation/related-projects/woocommerce-multilingual/#translate-and-synchronize-global-attributes.
The client resolved the issue by switching the "copy taxonomies to translation" on and off. Set all taxonomies to Dutch (because they were somehow registered as English). Then the client sent all products for translation (automatic > publish without review) and selected the already translated content to "Overwrite existing translations". After that, navigate to the Taxonomies translation and select the taxonomies one at a time and press the sync button at the bottom.
If this solution does not resolve your issue or seems outdated, please visit our known issues page at https://wpml.org/known-issues/ to check for any updates or related problems. We also recommend confirming that you have the latest versions of themes and plugins installed. If problems persist, do not hesitate to open a new support ticket for further assistance.
