Background of the issue:
I am trying to translate French articles (default language) into English using ATE. The translator completes the translation, clicks 'Save to Translation Memory' and 'Done,' then returns to the admin and updates the page. We have set up a test server for investigation and are willing to reproduce this issue in production via screen sharing. The Translation Memory is shared with production, so we need to avoid making destructive changes to it.
Symptoms:
Translations do not always appear on the frontend. In WPML > Translation Management, the translation often remains stuck in 'In progress' status for hours or days, even after saving. The gear icon shows instead of the pencil in the language box, even if the translation is 100% complete in ATE. The frontend remains stuck on an outdated version, and then randomly, the correct translation appears later. Cache was cleared and disabled during tests, but the issue persists.
Questions:
Why do translations remain stuck in 'In progress' status for hours or days?
Why does the frontend display an outdated version even after completing the translation process in ATE?
This is Christopher. I have taken over this ticket and will communicate with you here.
Agnes gave me information about the problems and I am in the process of checking and validating the problems.
We also created an internal ticket to involve the second tier support.
I just wanted to give you an update here about this and tell you that we actively work on this and if needed I will get back with some questions for more clarification.
It might take time as the issue is complicated but we will do our best.
Thank you very much. I'm sure you will understand that we are now blind with this issue as we do not know where to look for as the first step to be able to troubleshoot anything is being able to reproduce the problem.
I informed the second tier support regarding your findings. I am not sure how helpful it will be for them but we will do our best to see if there is something that we can suggest for you to test.
This would be highly dependent on your production server environment most probably as the same thing does not happen on the other servers.
We tried our best and for now we have two suggestions.
1. Re-register WPML on the production.
- Make sure that you are logged in wpml.org.
- Go to "WordPress Dashboard > Plugins > Add New > Commercial (Tab)".
- Click the unregister link.
- Click the "Register WPML" at the right section of the screen.
- Click the "Get a key for this site" link annotated in the screenshot below.
- A new page will open up and the auto-generated key will show in pop-up.
- Copy the key and paste it into the "Site Key" input box annotated in the screenshot below.
- Click the "OK" button.
We suspect that a Varnish cache or an implementation like that might have something to do with the fact that only the production has the problem.
Kinsta has something similar Called Edge Caching:
hidden link
Can you either enable it on the staging website, or disable it on production and see if it has any effect?
Finally After you do the changes we will appreciate if you could provide a fresher copy of the production site (site dump) so we can see if there is anything that we can find?
Meanwhile, we still need that steps or something to be able to continue, as we are now blind and do not know even if we implement a workaround does it work? or not?
