ATR not showing 100%

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are trying to complete a translation with ATE, but the progress is stuck at 94% and cannot be completed. You suspect it might be related to the WP ROCKET plugin, as cached content appears on the frontend even when logged in as an admin.
Solution:
We recommend clearing any site cache, either from WordPress or your hosting panel, to see if the translation shows up immediately. If WPML successfully pulls the translation from ATE, the issue might be related to caching affecting the frontend rendering. If clearing the cache does not resolve the issue, consider disabling and then re-enabling the WP ROCKET plugin, and ensure you have updated it to the latest version.

If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.

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.

Tagged: Exception

This topic contains 12 replies, has 2 voices.

Last updated by Bruno Kos 1 month, 2 weeks ago.

Assisted by: Bruno Kos.

Author	Posts
October 17, 2024 at 12:38 pm #16300154
thibaultG	Background of the issue: I'm trying to complete a translation with ATE. All fields are translated but it's still stuck at 94% and cannot complete translation. Link to a page where the issue can be seen: hidden link Symptoms: The translation progress is stuck at 94% and cannot be completed. Questions: Why is the translation stuck at 94%? How can I complete the translation to reach 100%?
October 17, 2024 at 1:45 pm #16300492
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	Can you go to wp-admin/admin.php?page=wpml-tm-ate-log Do you see any logs there, for either 116186640 or 116186905?
October 17, 2024 at 1:50 pm #16300555
thibaultG	Hi, nothing in the error logs. Last one is: 2024/10/09 5:10:43 AM ATE Server Communication Gateway Timeout
October 18, 2024 at 4:04 am #16302549
thibaultG	Can I please get help? Thank you
October 18, 2024 at 12:21 pm #16304659
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	Is there any way you can provide me with WordPress access? Other than that I have no other suggestions.
October 18, 2024 at 12:52 pm #16304866
thibaultG	Yes I can however I need your plan of actions of what you will exactly do steps by steps due to sensitive content and data. I also need written confirmation that you will not: - Install any plugin - duplicate / clone the site - Deactivate any plugins or themes even momentarly. Thank you,
October 21, 2024 at 7:49 am #16310512
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	Can you do this: 1. Add this to your `wp-config.php` file, just before the line `/* That's all, stop editing! Happy publishing. */`: define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); - After turning on the debug logs, try publishing the translation again and then check the `wp-content/debug.log` file for any errors. 2. Check if the translated content is being saved correctly in the database (probably in the `wp_posts` or `wp_postmeta` tables). This will show if the translation is being saved but not displaying. As for the WordPress credentials, we will not make any changes without your explicit permission. If possible only install https://wordpress.org/plugins/pexlechris-adminer/ so we could check for the translated content in database.
October 22, 2024 at 5:16 am #16314945
thibaultG	Hi, I checked the debug log, nothing relevant. I checked the DB and I can see the post and all changes everytime I update the translation. So it looks like it's an issue on the frontend rendering. Thank you,
October 22, 2024 at 7:33 am #16315333
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	If WPML pulls the translation from ATE successfully, then it may be something within the caching that is responsible for the frontend rendering. We have a very similar, if not the same, case with another client at the moment. They use Elementor and say that after completing the translation in ATE, they just browse through the backend of the site and the translation starts showing or shows after few hours if no such action is done, but in their case the translation is also stored in database. Can you try clearing any site cache, either from WordPress or the hosting panel and see if the translation shows up immediately?
October 22, 2024 at 7:35 am #16315342
thibaultG	I have already cleared all possible caches and numerous times. These are the first actions I have done and I've done it multiple times.
October 22, 2024 at 7:36 am #16315344
thibaultG	Also please note this issue seems localized to blog posts only. I don't have such issues with theme pages or woocommerce products for example.
October 22, 2024 at 8:08 am #16315578
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	I see, what are the options of sharing the site or the site access for local debugging? Perhaps this? https://wpml.org/faq/provide-supporters-copy-site/ Let me know.
November 6, 2024 at 9:49 am #16370815
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	Hi, I reopened the ticket, I got information there is something related to this issue you want to share with us?
November 6, 2024 at 9:52 am #16370820
thibaultG	I think it was related to WP ROCKET plugin. Somehow cached content were returning on frontend even though I was logged in as user / Admin (shoudln't be any cache on frontend). Disabling / renabling the plugin solve the issue. I also updated to last plugin version but can't confirm it was a fix or not in a recent plugin update.