Home›Support›English Support›[Waiting for user feedback] Random pages of my site are opening the clasic editor instead of ATE (follow up - solution did not w...
[Waiting for user feedback] Random pages of my site are opening the clasic editor instead of ATE (follow up - solution did not w...
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.
Background of the issue:
I am trying to resolve an issue with the Advanced Translation Editor (ATE) in WordPress. When I attempt to open ATE to update transaltions, the WordPress editor opens instead of the ATE. I have tried different recommendded solutions with no luck. The settings are right and I have tried to fix it by selecting the middle icon (WPML translation) in individual pages, it does not work.
Symptoms:
Random pages of my site are opening the wordpress editor instead of the ATE. I expected the ATE to open, but instead, the WordPress page opens.
Questions:
Why are random pages opening the WordPress editor instead of the ATE?
How can I ensure the ATE opens instead of the WordPress page?
Thanks for your reply. I've tested it and I'm able to edit the translations using the Advanced Translation Editor without issues as shown in the attached screen recording. hidden link
Thanks for your reply. Could you please grant me full administrative access to your Website? Also, I need your permission to deactivate 3rd party plugins.
Thanks for your reply. It looks like ATE is not able to identify your Website. Could you please generate a new sitekey https://wpml.org/account/sites/ for this domain ? hidden link
Then, share your sitekey with me here and I will recheck.
Thanks for your reply. Not sure why the site is down today when I checked. Could you share FTP access here for this site hidden link so that I could check why it's down?
Thanks for your reply. It seems to work fine when I tested it hidden link . Could you try clearing your browser cache or try logging in using my login credentials?