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.
