I get translation queue when clicking to add translation

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.

This topic contains 7 replies, has 3 voices.

Last updated by nadavS 4 years, 4 months ago.

Assisted by: Dražen.

Author	Posts
January 27, 2021 at 12:35 pm
nadavS	When I click to add a translation to a page I get the translation queue instead of the classic editor.
January 27, 2021 at 1:53 pm
January 27, 2021 at 2:07 pm #7941969
Sumit Supporter Languages: English (English ) Timezone: Asia/Kolkata (GMT+05:30)	Hi, Thank you for contacting the support forum. Before your ticket is assigned to one of my colleagues, please allow me to walk you through some initial debugging steps. This will help speed up the support process. I can not log in to the site, please disable Wordfence so our team can log in to the site. It is possible that jobs are assigned to a translator. Please make sure the current user is the translation manager and translator then send the job again to the local translator and then try to translate. Does it work? Ref: https://wpml.org/documentation/translating-your-contents/how-to-set-up-local-translators-and-language-pairs/ Thanks
February 3, 2021 at 5:33 am #7992585
nadavS	I'm not trying to send the translation. I'm trying to load the classic editor and add the translation myself.
February 3, 2021 at 8:08 am #7993137
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello, thanks for getting back. I will be taking over the ticket and helping you out. In order to investigate this issue and to understand it better, I would need to access your website. Please make a full backup of your site (files and database) and confirm it in your next reply. I might need to enable/disable plugins, switch themes and access your website database. I would need to access both your site's wp-admin and FTP account. Be sure to provide both. I have enabled the private username and password fields in your next reply. You can safely add your information into these fields. Thanks, Drazen
February 4, 2021 at 5:57 am #8002891
nadavS	Hi Drazen, Please sync with George Botsev. He already tried all that and the issue was not resolved. I don't mind giving access again, but want to make sure we're not just waisting time for both sides. Thank you.
February 4, 2021 at 6:57 am
February 4, 2021 at 6:58 am #8003135
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Please check my private reply above, and provide the needed info in your next reply. Thanks, Drazen
February 7, 2021 at 4:40 am
February 8, 2021 at 8:14 am #8028955
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello, thanks for getting back. In order to be able to translate, you first need to set up the correct Translation pairs for the user,(WPML > Translation Management > Translation Roles). Even then, I could still see the issue, if I create a new page and then click the "+" icon to add a new translation I am taken to the Translation queue. Then If I click the cog icon or on the Translation queue I click "Take and translate" it works fine. The reason why this is happening is because, in order for WPML to open the Translation editor, it first needs to create a Translation Job and then redirect to the Translation editor. In your case, it is probably failing due to hosting caching or security permission. In my opinion, it is probably caused by either object cache or security plugin. I have tested on a clean sandbox site from our side and it works fine. Can you please try the next steps: - For the current staging site disable WPEngine must use plugins and check if the issue happens. - create a new clean website with only WPML plugins, enable same settings for must use plugins like WPENGINE security and cache plugins you have now - Check if the issue happens there as well Let me know how it goes. Kind regards, Drazen
February 10, 2021 at 12:32 pm #8051759
nadavS	Disabling the object cache seems to have solved it. Thank you!