Advanced Translation Editor not working properly

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: America/Los_Angeles (GMT-07:00)

Tagged: ATE

This topic contains 10 replies, has 0 voices.

Last updated by adrianK-24 1 day, 15 hours ago.

Assisted by: Bobby.

Author	Posts
March 31, 2026 at 2:31 pm #17940397
adrianK-24	Hello WPML Support Team, I am experiencing an issue with the Advanced Translation Editor (ATE) on my WordPress site — it is not opening when clicked. Issue details: - When I click the pencil icon to translate a page, the "Edit with ATE" button appears correctly. - However, when I click the "Edit with ATE" button, nothing happens — the editor does NOT open. - The only change is that a "#" symbol gets added at the end of the URL in the browser. - No error message is shown, the page just stays the same. Environment: - WPML Version: 4.9.2 - WordPress Version: 6.9.4 - Browser: Firefox 149.0 What I have already tried: - Cleared the website cache — issue still persists. Please help me fix this issue so the Advanced Translation Editor opens properly. Please refer my video: hidden link
April 2, 2026 at 6:26 am #17944857
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Thank you for the loom video! Please go to WPML->Support->ATE Error logs and share with me the top 3 errors logged. Did you recently migrate the site ? (staging to live, or vice versa)
April 6, 2026 at 1:16 pm #17951417
adrianK-24	Hi, Thank you for your message. Here are the screenshots of top 3 errors from ATE Error Logs. Yes, the site has been migrated multiple times between staging and live environments. Please let me know if this could be causing the issue and what steps we should take next. Thanks!
April 7, 2026 at 6:53 pm #17955085
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Thank you for sharing! Let's start by increasing the WP MEMORY LIMIT Please add the following to your wp-config.php: define('WP_MEMORY_LIMIT', '256M'); define('WP_MAX_MEMORY_LIMIT', '256M'); Once done go to WPML->Support->Troubleshooting and clear the WPML Cache then test again and let me know your results, please. Also, while in the troubleshooting at the very top of the page share with me the AMS ID. NOTE: I did locate duplicate records on our ledger for the website URL which I have now fixed as well.
April 13, 2026 at 1:56 pm #17966404
adrianK-24	Hi, Thank you for your response. I followed your instructions and updated the WP memory limit in the `wp-config.php`, and also cleared the WPML cache from Troubleshooting. However, the issue is still not resolved. Also, here is the AMS ID: ecea9a27-77d8-4a12-8c8e-5b87259083c9#WNIU3sM0d95kg5bMOOe69gtt Thanks!
April 13, 2026 at 1:58 pm #17966415
adrianK-24	Duplicate — please disregard.
April 13, 2026 at 6:19 pm #17966825
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Thank you, please try again and let me know your results now. If it persists, I would like to request temporary access (wp-admin and FTP) to your site to test the issue. (preferably to a test site where the problem has been replicated if possible) Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/ You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you enter is private which means only you and I have access to it. NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin. Thank you, Bobby
April 17, 2026 at 7:31 am #17976089
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Thank you for the access details! When I attempt to work on the pages I get the following error: Failed to load plugin: fullscreen from url hidden link I have tested with both a minimal version and with WPML deactivated, however, the issue remains Please check if this file exists: /wp-includes/js/tinymce/plugins/fullscreen/plugin.min.js
April 17, 2026 at 2:38 pm #17977138
adrianK-24	Thank you for checking. I have verified the path you mentioned, and the file plugin.min.js does exist at: /wp-includes/js/tinymce/plugins/fullscreen/plugin.min.js So the file is present on the server, which means the issue is likely not due to a missing file. Also, I noticed that several plugins on the site, including WPML-related components, have been deactivated. Could you please confirm if this was done on your end while working on the translation issue? If you have temporarily deactivated them for troubleshooting, please ensure they are reactivated once the work is completed so the site continues to function properly. Thanks!
April 17, 2026 at 5:31 pm #17977346
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Yes, and apologies for that everything should have been re activated! The problem I am facing is that when I attempt to edit any page we get that error I shared, regardless if WPML is activated or deactivated. This type of issue can some times happen after a migration. Can you please review and possibly re migrate the site from live? See here for example: hidden link
April 17, 2026 at 8:23 pm #17977530
adrianK-24	Hi, Thank you for your update. Alternatively, we can take a full backup of the site and restore it on the same dev environment to test this theory. We are using All-in-One WP Migration for backup and restore. The process would be to take a complete site backup (files + database) and then restore it on the same dev setup to check if the issue still persists. Please confirm if this approach is fine to validate your suggestion. If yes, we will proceed with the test.