Problem: The client is experiencing issues with translation jobs in the Advanced Translation Editor (ATE) showing as "In progress" even after completion, and an error message stating "The Advanced Editor jobs synchronization has failed". Additionally, the client is redirected to the translation queue page instead of the ATE when starting new translations.
Solution: 1. Ensure you have a full backup of your website and database. 2. Update all WPML plugins to the latest versions. 3. Cancel any existing translation jobs that are stuck in progress by following this documentation: How to cancel translation jobs. 4. If the issue persists, deactivate all plugins except for WPML and its add-ons to check if there is a conflict. 5. Reactivate each plugin one by one to identify any conflicting plugin. 6. If the problem continues, repeat the steps with a default WordPress theme.
If these steps do not resolve the issue, or if the solution provided here is outdated or not applicable to your case, we highly recommend checking the related 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 in the WPML support forum.
Problem: The client is seeking a way to automatically translate updated content on their English page without overwriting previous manual edits made to automatic translations.
Solution: 1. We recommend reviewing the documentation on Translation Memory to understand how WPML tracks translations. Content edited in the Advanced Translation Editor (ATE) can be saved to Translation Memory, ensuring it won't be translated again unless the original content changes. However, changes made using the WordPress Editor instead of the WPML editor will not be stored in Translation Memory and will be overwritten by automatic translation. Translation Memory documentation.
2. If the client has manually corrected the content in the ATE and clicked "Complete", the edits are saved to the Translation Memory. There is no need to click "Save to translation memory" separately.
3. To avoid overwriting manual edits, it's best to make changes or edits to the automatic translation directly in the ATE, as these will then be saved in the Translation Memory for future use.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, we encourage you to open a new support ticket. We also 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 need further assistance, please contact us in the WPML support forum.
French and German are showing as unavailable for automatic DeepL translation. The following message shows.
Your selected automatic translation engines do not support the following language(s).
Solution:
The problem was the mapping of the languages. When I went to WPML -> Languages -> Site Languages and pressed the 'Edit languages' option, I saw that the related languages were not mapped. So I mapped them accordingly. Please read more about mapping languages with automatic translation here.
Problem:
I am using the Theme and plugins localization screen to scan for strings to translate, but it does not pick up strings in .twig templates, for example:
{{ __('Example heading to translate', 'example-domain') }}
How can we translate the strings in all the .twig files in the theme, ideally from the String translation screen? Solution:
Can you please try to go to WPML -> String Translation and enable the option: Look for strings while pages are rendered.
Then try to access the site somewhere that text is available and go back to the String Translation screen to see if those texts will be available for translation now.
