Background of the issue:
I am trying to create new layouts in my Divi library and then translate them using WPML. Everything was working before, but now I cannot finish the translations.
Symptoms:
The translation process is stuck at 'in progress' status, and I cannot create my pages anymore.
Questions:
Why is the translation process stuck at 'in progress' status?
How can I resolve the issue to complete my translations?
You have the WP multisite installation. I can see that WordPress has been updated to its latest version, 6.7. But I can see which WPML and Strings Translation versions you are using. We have recently released PWML 4.6.14 and Strings Translation 3.2.15 to be compatible with WordPress 6.7.
Please check if your site has the latest WPML and Strings Translation versions. If not, please update our plugins and see if it solves the issue.
Yes, please update our plug-ins to their latest versions and see if it helps. If not, then please share access to your site and explain to me in details how to see this problem.
I'm enabling a private message for the following reply. Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
It might be that the site is registered with the wrong site key. It must match the site key you have here: https://wpml.org/account/sites/.
To be sure, you can unregister and then register this site again.
The following is how you go about it:
1. Go to Plugins → Add New and click the Commercial tab.
2. Click the 'Unregister site' option and approve.
3. Delete the currently registered site with the problem from your account here: https://wpml.org/account/sites/.
4. Then, back on your in the commercial tab, press the 'Get a key for this site' option. A new tab will open on your wpml.org account.
5. Reregister your site again and copy the new key.
6. Back in the admin, insert the new site key, and click the Register button.
Please try the following: While on the Advanced Translation Editor screen, click the gear icon in the top-right corner. A pop-up will show. Select the option 'Use the previous version of the Advanced Translation Editor.' Please see the attached screenshot. Then, check if you can complete the translation; it gets translated, and the pencil icon shows.
Thanks for the video. Please give me access (super-admin) to your site os I can check this issue.
If you need further help with this, please share the access details to your site with me. I'm enabling a private message for the following reply.
Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
Before I restore the website, maybe you can help me.
PROBLEM:
The Main Menu has disappeared ONLY in the admin of wordpress.
This Main Menu was still working on the frontend pages.
I tried to use WP Menu Sync to solve the issue and I got the Main Menu back in the backend.
But the issue is on the Frontend now, because there is 2 Main Menus instead of 1 on the secondary languages:
-> hidden link
-> hidden link
-> hidden link
I will stop touching at anything until I get your recommandations, I do not want to break anything more.
NOTES: I would prefer to recover the old menu because all the translations were done already.
Thanks for your help
New threads created by Itamar and linked to this one are listed below:
I'm glad that the original issue of this ticket is solved now.
In our technical support forum, we focus on one issue per ticket. Otherwise, tickets can get cluttered and confusing for users and supporters. Therefore, I split this ticket, and we will handle the new issue in the new ticket:
