I have tried translating pages to other languages than english as I have done before, but now I get a spinning wheel of death on the screen and the updates is not finished allthough actually having been translated.
I am sure you will know what I mean by the screenschot attached.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hi there,
Thanks for your contact.
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.
Please follow these steps:
- Just to be safe, make sure to have a website backup before proceeding
- Go to WPML -> Support in your admin dashboard
- Click the “troubleshooting” link bellow the plugin versions list
- Look for the “Clean up” section and hit these buttons:
# Clear the cache in WPML
# Remove ghost entries from the translation tables
# Fix element_type collation
# Synchronize local job ids with ATE jobs
# Synchronize translators and translation managers with ATE
# Set language information
# Fix post type assignment for translations
Then, try to translate that page again and check if it'll work fine this time.
I followed your instructions, and it made my site go weird with adding pages (see screenshot). I know have 23 pages named like that, and with no page content. So this seems to have happened only for the 2 pages with spinning wheels of death. The other page had this happen to both french and spanish. Have in mind that my main language is set to english, but while it is still on main language the page titles here are the translated version to spanish.
The spinning wheels are still spinning.
So, it didnt resolve the issue, but created new ones.
I can revert it back to yesterday, but will wait your instruction.
It appears that a conflict has resulted in multiple corrupted versions of a page being created and displayed in the English version. Such issues can arise if you are using a plugin that can duplicate pages or posts. If you have a backup available, I recommend restoring the site from that backup and then proceeding with the following steps to address the 'Stuck' issue.
- Please ensure the WPML Plugin is updated to the most recent version, 4.6.7. If the update notification isn't visible, you can obtain the latest version from your WPML account at https://wpml.org/account/downloads/ and install it on your website.
- After updating the plugin, clear the cache for all languages.
- Verify whether the Translation update icon (a curved arrow) continues to be displayed.
Thank you for your guidance. I have followed all of the steps from restoring backup, and making sure to have the latest version 4.6.7 installed, clearing the cache for all languages, and it didnt work. I still had the spinning wheel going...
Then I tried the next step, and it doesnt work as I am not even allowed to update the page.
Status quo: I have spinning wheel on pages' wpml translation is in the original screenshot.
Hello Aske,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
Thank you so much for trying out the suggestions. As the issue persists, a closer inspection will be required to understand the root cause of the issue.
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. With the access information, please share the name of the pages where I can see the issue. It would be better to have a testing site where the issue is replicated.
You will find the needed fields below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
-Please backup site files and database before providing us access.
-If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Hello Aske,
Thank you for sharing the access information.
I'm pleased to let you know that I've successfully resolved the issue on the Staging site. The problem was linked to the Instant Indexing feature(more specifically, the Bing API) of the SEOPress plugin, which prevented me from saving changes in the "Basics" page and also affected the translation saving process. After implementing the following adjustments, I'm now able to save changes, and the translations are updating smoothly without any problems.
- I navigated to the "SEO > Instant Indexing > Settings" page.
- Clicked on "Generate Key" in the "Bing Indexing API key" field and saved the newly generated key.
- Then, I went to "Pages > All Pages".
- I opened the "Basics" page and made a minor change.
- Finally, I updated both the changes and the translation.
I hope the steps above will help to solve the issue on the main site as well. But, feel free to let me know if you need further assistance. I will be happy to help.
It worked. I followed your instruction, and it worked immediately! Thank you very much:-)
My I ask how you figured out that this could be the problem? I know it is not your job to answer this, but if you have some kind of article that explains how to debug this kind of thing I would be very interested in learning about it:-)
I'm glad to explain how I identified the problem. Initially, I conducted a plugin conflict test to pinpoint the primary source of the issue. This test revealed that deactivating the "SEOPress" plugin resolved the issue. I then reactivated "SEOPress" and began examining its Modules. By deactivating these modules one at a time, I discovered that turning off the "Instant Indexing" module resolved the issue.
Turning off the entire module isn't an optimal solution, so I left the module active and continued investigating. I discovered that when I disabled the Bing/Yahoo indexing, the issue also got resolved. Upon examining their configuration, I noticed that the key in the field did not match the key structure generated by the plugin. Therefore, I created a new key, and this action ultimately resolved the issue.
I hope you can understand. Feel free to let me know if you need further clarification. I will be happy to assist.
