Problem: You are experiencing an issue where WPML did not manage to translate a page, and you see a message indicating this failure. This issue occurred unexpectedly without any recent changes made by you.
Solution: Here are the steps we recommend to potentially resolve this issue: 1. Cancel the Stuck Translation Job: * Go to WPML → Translation Dashboard. * Click on the Jobs tab. * Find the translation job for the page that's stuck and cancel it. 2. Make a Small Edit to the Original Page: * Navigate to the original page in your WordPress editor. * Make a very minor change, like adding a space or a period at the end of a sentence. * Save the page. 3. Resend the Page for Translation: * Now, resend the page for translation, either by clicking the plus icon in the language meta-box or sending it from the Translation Dashboard again.
After following these steps, please check if the page translates successfully. If the problem persists or if these steps do not apply to your situation, it might be due to a temporary issue on our servers which we are currently addressing. Please check back in a few hours.
If the issue continues or if the solution provided here is outdated or not relevant 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 open a new support ticket at WPML support forum.
Problem: The client was unable to update or edit pages using WPML due to an error stating 'WPML didn't manage to translate this page.' This issue was linked to an operational disruption with Amazon Web Services (AWS) affecting services hosted in the N. Virginia region. Solution: We identified that the problem was due to an AWS outage impacting our services. We monitored the situation and engaged with AWS Support for urgent mitigation. Once AWS services were restored, we advised the client to resend the content for translation.
If this solution does not resolve your issue, or if it seems outdated, we recommend checking for related 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 open a new support ticket.
Problem: You are experiencing missing translations on local pages after making changes in the default language, and you are also facing issues with opening WPML and the WPML Translation Editor. Solution: To determine if a page’s content was initially created using the Classic Translation Editor or the Advanced Translation Editor, first check if the content appears in the Advanced Translation Editor. If it does, the translations were done using the Advanced Translation Editor. If the frontend shows content but the Advanced Translation Editor is empty, check the Classic Translation Editor. If the content appears there, it means the page was translated using the Classic Translation Editor. If the frontend shows content but both the Advanced Translation Editor and the Classic Translation Editor are empty, then further troubleshooting is necessary as this situation is usually not possible.
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.
