Problem: You are experiencing an unwanted popup warning when editing translated articles in WordPress using the LILT translation service and the Classic Editor. The popup warns that edits will be lost when the page is sent for translation again. Solution: To stop the popup warning, you need to switch your translation settings to manual mode. This can be done by following the steps in the WPML documentation on using different translation editors for different pages, which you can find here: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages. Additionally, you can deactivate the automatic translation engines in WPML --> Settings as shown in the instructional video provided by our support team.
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 for further assistance.
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 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.
Problem: You are using WPML version 4.7.4 and have noticed that after translation, the process shows a gear icon instead of the pencil icon, indicating that translations are being sent to a local translator instead of completing directly. Solution: We recommend updating your WPML to the latest version, which is 4.7.6. After updating, please test the functionality again. If the issue persists, follow these steps: 1. Go to WPML → Settings and ensure that the WPML Advanced Translation Editor is activated. 2. Navigate to WPML → Translation Management, select a job, and send it for automatic translation. 3. Verify that you are listed as a translator under WPML → Translation Management → Translators. If these steps do not resolve the issue, the solution might be 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.
Problem: You are experiencing an issue where your site is appearing twice in the WPML Automatic Translation dashboard. Solution: If you're encountering this problem, we recommend you try the following steps: 1. Navigate to Plugins -> Add New -> Commercial on your website. 2. Unregister WPML by clicking the unregister link. 3. Visit https://wpml.org/account/sites/ 4. Delete the existing site key. 5. Return to Plugins -> Add New -> Commercial on your website. 6. Click the register link.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please 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. For further assistance, you can contact us directly through our support forum at WPML support forum.
Problem: The client is trying to transfer translation credits from one WPML install to another but cannot find the settings option under the Translation Tools tab, despite following the documentation. Solution: 1. Ensure that both sites involved in the transfer are registered under the same WPML account. 2. Visit your WPML.org account and follow the guide on how to assign automatic translation credits to your sites, which can be found here: https://wpml.org/documentation/automatic-translation/how-to-assign-automatic-translation-credits-to-your-sites/. This guide includes a step where you can remove credits from one site and then reassign them to another.
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 the problem persists, please open a new support ticket with us for further assistance.
Problem: The client needs to create pages with different templates while keeping the 'Synchronize Page Template' option active in WPML, which is necessary for sending pages for translation. However, enabling this option forces all linked translations to use the same template, which conflicts with the need for different templates on individual pages. Solution: We recommend manually translating the pages that require different templates. This approach allows you to maintain different templates on individual pages while keeping the 'Synchronize Page Template' option active for other needs. You can find detailed instructions on how to manually translate pages here: Using different translation editors for different pages.
If this solution does not fully address your issue, or if it 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client is working on a multi-language project using WPML and needs to create custom language codes (e.g., fr_ml for French, de_ml for German) for their website. They are concerned about how these custom codes will affect translations sent to the third-party service Lilt and whether it impacts the default locales. Solution: 1. If you're using custom language codes, you need to inform us so we can map these codes in our proxy. Please contact us with the codes and corresponding languages. Additionally, you should notify the translation service (Lilt) to make necessary adjustments. 2. The custom language code itself does not significantly impact the process as long as it is correctly mapped. However, it might affect existing translations of plugin/theme strings that are specific to standard language codes (e.g., fr instead of fr_ml). 3. We will handle the mapping of these custom language codes in our proxy to ensure they correspond to the correct languages.
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 further assistance is needed, please open a new support ticket.
