Problem: The client is experiencing a critical error when attempting to use the advanced editor for translating a page from English to French. The error message indicates a missing site key and issues with the WPML Translation Editor, potentially due to conflicts with hidden builder metadata or cached layout data from Visual Composer. Solution: We recommend creating a new page and manually copying the content from the problematic page to the new one. This approach often helps clear out any residual builder metadata that might be causing the issue. If this solution does not resolve the problem or if it seems outdated or irrelevant to your current setup, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If issues persist, we highly recommend opening a new support ticket for further assistance.
Problem: After a recent WPML update, you are unable to manually translate products in WooCommerce. When attempting to translate, you encounter an error stating 'The translator could not be assigned to the job,' and you are redirected to the 'translation queue' page instead of the product edit page. Solution: This issue is due to missing fields in the database table wp_icl_translate_job. To resolve this, please ensure you back up your entire server first for safety. Then, run the following database query to add the necessary fields:
ALTER TABLE `wp_icl_translate_job`
ADD `wpml_words_to_translate_count` int unsigned NULL,
ADD `wpml_automatic_translation_costs` int unsigned NULL AFTER `wpml_words_to_translate_count`;
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking for 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 the problem persist, please do not hesitate to open a new support ticket with us for further assistance.
Problem: The client's website, with a default language of German, was experiencing issues with mismatched product counts across other languages (Spanish, English, and French). Additionally, the translation process was getting stuck at 12 products. Solution: 1. We discovered that some products set to 'Draft' in translations were causing the mismatch. We advised the client to: - Go to products. - Switch to the secondary language and check for 'Draft' status. - Change the status to 'Publish' either by 'edit-> publish' or 'quick edit-> publish'. - Ensure all products have the correct status. 2. For the translation getting stuck, it was due to an invalid site key: - Visit the account page at https://wpml.org/account/sites/ - Delete the old key. - Unregister and re-register WPML on the site to get a new key. 3. We also optimized SQL queries and tweaked the code to improve performance and resolve server errors. Reference for code changes can be found here: https://wpml.org/errata/possible-performance-issue-highlighted-by-unexpected-calls-to-gzuncompress/
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 issues persist, please open a new support ticket at WPML support forum.
Problème : Vous travaillez sur un site en développement et rencontrez un problème où la traduction automatique avec WPML ne démarre pas. Solution : Nous avons résolu ce problème en renvoyant les pages bloquées vers la traduction automatique via le tableau de bord de gestion des traductions WPML. Il semble que cela pourrait être dû à un problème de connexion temporaire. Si vous rencontrez à nouveau ce problème, nous vous recommandons de tenter la même démarche.
Il est possible que cette solution devienne obsolète ou qu'elle ne s'applique pas à votre cas. Nous vous conseillons vivement de consulter les problèmes connus, de vérifier la version de la correction permanente et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support en visitant notre forum de support.
Problem: The client was experiencing issues with the Advanced Translation Editor (ATE) in WPML, specifically receiving errors such as 'Unable to retrieve job details' and 'Jobs could not be loaded' while trying to translate Search & Filter fields using ACF and Elementor Pro. Solution: 1. Ensure all WPML plugins are updated to the latest versions by navigating to Plugins → Add New → Commercial tab. 2. Clear all caches, including WPML's cache, by going to WPML → Support → Troubleshooting and using the provided tools. 3. Verify the ATE API connection under WPML → Settings → Translation Editor. 4. Use WPML's troubleshooting tools to remove ghost entries and fix database collation issues. 5. Check Elementor widgets for excessively long strings or complex content that might be causing issues. 6. Install and activate the ACF Multilingual plugin, set ACF field translation preferences, and update original posts/pages to trigger new translation settings. 7. If issues persist, manually inspect WPML job queues and database for stalled or corrupted translation jobs. 8. Review for known WPML/ACFML conflicts, especially with Elementor, and check logs for related errors.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client was unable to activate the 'Translate Everything Automatically' option in the WPML Translation Dashboard despite having sufficient credits. Solution: We recommend following these steps if you're facing a similar issue: 1. Navigate to WPML >> Translation Dashboard. 2. Select a page, such as the Welcome (Front page), and send it for automatic translation. 3. Once the translation is completed, the option to 'Enable Translate Everything Automatically' should become available. Please check the translation of the Front page to ensure it meets your expectations before enabling the 'Translate Everything Automatically' option.
If this solution does not resolve your issue, or if it 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues with glossary terms being ignored during PTC auto-translation in WPML. Specifically, terms exceeding 40 characters are not being translated, and an 'IGNORED' warning appears in the Glossary Dashboard. Solution: The 'IGNORED' label in the Glossary Dashboard indicates that the glossary term has been ignored because it exceeds the 40-character limit. To resolve this, ensure that your glossary terms are under 40 characters. If the issue persists or if the terms are not duplicates and still being ignored, we recommend checking the 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 this solution does not apply or is outdated, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where the 'Translate Everything Automatically' option is missing on their https://beckerpumps.com/ca subsite, preventing the start of automatic translation. Solution: 1. Ensure the subsite is connected to an automatic translation credit account. This can be done by sharing credits from another site in the network, such as https://beckerpumps.com/latam/. 2. Check the automatic translation engine settings under WPML → Settings and ensure an engine like Google Translate is selected. 3. Refresh the WPML registration by navigating to Plugins → Add New → Commercial tab to verify the registration status.
If these steps do not resolve the issue, it might be due to a deeper configuration or compatibility problem. We recommend visiting our known issues page, verifying you have the latest versions of themes and plugins, and checking the version of the permanent fix. If the problem persists, please open a new support ticket with us.
Problem: You are trying to translate articles using WPML, but even when they are 100% complete, they remain pending. You attempted to delete a translation to recreate it from scratch, but it does not appear among the translated pages, although it is still visible in WPML. You also tried disconnecting and reconnecting WPML and making slight changes to the text or title. Solution: The issue seems to be related to the server environment rather than WPML itself. Here are the steps we recommend you try: 1. Temporarily deactivate any server cache mechanisms like NGINX Direct Delivery and any caching plugins (e.g., SG Optimizer if active). 2. Clear all caches: server, plugin (if present), and browser. 3. Go to WPML --> Translation Dashboard --> Translation Jobs and delete the ongoing translation job. 4. Make a minor edit to the original page in Italian. 5. Reopen the Translation Editor and try to complete/save the translation.
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 the problem persists, please open a new support ticket.
