Problem: The client was unable to open WPML to translate a page and was experiencing this issue across all pages.
Solution: We asked the client to check the ATE Error logs by navigating to WPML->Support->ATE Error logs and to share the top 5 errors. We also inquired if the issue occurred with all translations and what the results were when attempting to add a translation for a different page/post.
We requested temporary access to the client's site, both wp-admin and FTP, emphasizing the importance of taking a full backup before proceeding. We suggested using the Duplicator plugin for this purpose.
After receiving access, we performed some troubleshooting actions from WPML->Support->Troubleshooting. The issue was resolved, and the client was advised to go to Pages, click on the "gear icon" to open the ATE translation editor, and proceed with the translation.
If you're experiencing a similar issue, we recommend checking the ATE Error logs and trying the troubleshooting actions available in WPML->Support->Troubleshooting. If the problem persists, please ensure you have a full backup and consider providing temporary access to our support team for further assistance.
Please note that the solution provided might be 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. If the issue remains unresolved, do not hesitate to open a new support ticket. You can reach our support forum here.
Problem: The client has completed translations on every page, but they are not visible when switching languages, although the menu does change. This suggests there might be a URL issue. Solution: We found that the translations were not marked as 100% complete. We have created a video tutorial to explain why this is important and how to resolve the issue: Video Tutorial. We have already applied the solution to your homepage, which is why it is now working correctly: Homepage.
If this solution does not seem relevant to your issue, please feel free to open a new support ticket with us here.
