Problem: If you're experiencing a 503 error when trying to edit pages with the WPML plugin active, and the issue persists even after deactivating other plugins and switching to a default theme, it might not be directly related to WPML. Solution: First, check if JavaScript errors related to other components appear in your browser's console.
These errors might be visible on your staging site as well. Next, inspect the browser's developer tools to analyze the request headers and the specific POST request that is failing. The issue might be linked to server-side problems, such as those involving the WordPress REST API or admin-ajax.php, rather than WPML itself. If admin-ajax.php returns a 503 error, this indicates a server-side issue that needs addressing by your hosting provider or developer.
Here is an example of a specific request that could be failing:
The payload includes data from WPML and other sources, confirming that WPML is functioning correctly in terms of translation workflow. If the server environment is unstable, it could affect the performance of WPML and other plugins.
If this solution does not resolve your issue or seems irrelevant due to being 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
