The page WPML -> Settings -> Translation Management not only pulls data from the database but also connects with the Advanced Translation Editor (which is a service). It checks several things; if it throws an error, it may break the execution. I saw errors in WPML -> Support -> ATE Error Logs, so I wanted to discard that. Thanks for testing.
Now that we confirmed that the tables are created and discarded problems with the key, I took a fresh copy of your test site and deployed it again locally.
In my local copy of your site, the TM loads correctly.
Please follow the instructions mentioned on this page: https://wpml.org/documentation/support/debugging-wpml/
Then, go to WPML -> Translation Management and check your installation's **wp-content** folder to see if a file named **"debug.log"** was created (it will only be generated if a server error occurs).
If the file was created, please upload it to a platform like **Google Drive** or **Dropbox** (whichever you usually use) and share the link with me (make sure it is publicly accessible) so I can analyze it.
Also, please make sure your server allows the site reaching the following API endpoints:
- wpml.org
- cdn.wpml.org
- api.wpml.org
- ate.wpml.org
- ams.wpml.org
Thank you for the update, and I’m truly sorry I couldn’t be of more help in this case.
I’ll go ahead and close this ticket on our side, but we’ll continue investigating the matter internally with our second-tier team to better understand what may have caused the issue and ensure everything works smoothly moving forward.
Thanks again for your patience throughout the process.
