Problem: The client is experiencing issues with translations from LILT not automatically synchronizing into WordPress through WPML. Instead, translations appear as 'Translation ready to download' in the WPML → Translation Jobs list, and the client has to manually click 'Download' to import them. They have set the 'Translation pickup mode' to 'The site will fetch translations manually' due to server stability issues when multiple translations were processed simultaneously. Solution: This setting requires manual intervention to download translations. Currently, WPML does not support automatic fetching via API or cron jobs for LILT translations, and there are no alternative methods provided within WPML for automatic synchronization in this scenario. To manage translations, you should use the 'Check status and get translations' button in the Translation Dashboard.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum.
Problem: You are trying to connect the Translated service to your CMS using the WPML plugin, but the API key provided by Translated doesn't work. Solution: We recommend regenerating a new API key. Ensure that only the WPML plugin is active on your site when you try this new key. Additionally, you might need to provide Translated with a screenshot of your installed languages for mapping purposes. You can find more details on what is required here.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: The client is experiencing issues with WPML's Batch Delivery failing when using the Smartling Connector. The jobs are not accepted by Smartling, and no notification emails are sent regarding job cancellations. Solution: 1. We checked the jobs and found that Smartling did not accept them due to a validation error indicating that the batch was not suitable for adding files because its status was 'COMPLETED'. 2. We corrected an incorrect language configuration that was causing the issue. We recommend the client to send another job to see if the issue is resolved. 3. For future errors where no email notifications are received, we advise opening a new support ticket for assistance.
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 problem persists, please open a new support ticket at WPML Support Forum for further assistance.
Problem: You are managing and monitoring translation jobs in WPML and encounter several issues: some jobs show TP ID as 0, others have valid TP IDs but the batch URL shows NaN, and all such entries remain stuck 'In Progress'. Solution: 1. We have escalated the issue to our translation proxy team for further investigation. This process might take a day or two. 2. To attempt a fix on your own, navigate to WPML -> Support -> Troubleshooting. Here, locate the 'Fix WPML Translation Jobs "tp_id" field. Enter the IDs of the problematic jobs in the format "25941, 25942, 25943, ..." and then click the button to apply the fix. If this does not resolve the issue, we recommend sharing your site credentials with us for deeper investigation.
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 problem persists, please open a new support ticket at WPML support forum.
