Good Morning. The original issue here is resolved and I need assistance with an issue of importing translations from our translaor service. They are saying that there is an issue with exporting the translations back from there system into WPML. They stated the folllowing...
"We can rule out that there is an issue with the file or with GlobalLink’s processing of it since the same file under the same process previously succeeded.
The problem then is that the check status button is being unresponsive. This is something that WPML support need to comment on."
Not sure if there is a way to include there support people in on this converstion? Please let me know where my options are there.
You should have access to the staging site to login and review this with the credentials i supplied above.
It could be that during our tests, we created a new job for those translation and therefore the job_ID in their file don't match the new job ID. Could you please request again the XLIFF files so I can edit them and compare the job ID?
- I activated the Duplicator private field, please use it to upload a zip folder with all your XLIFF files.
- I will also activate the private field to share credentials to this new ticket that way I can continue to work on your site for this ticket.
Thanks for the access, I tried few troubleshooting options but unfortunately I wasn't able to find a solution. I have forwarded your ticket to the second tier support. I'll get back to you as soon as I have some feedback.
This issue has been fixed. Here is the feedback received:
The steps I took to solve it, I collected all the jobs with TP-ID = 0 and I went to WPML -> Support -> Troubleshooting and set them in the Fix WPML Translation Jobs "tp-id" field, then I downloaded the translation by clicking the check status and get translations button.
I'm not sure what could have caused this issue in the first place.
- Maybe 2 batches with the same name have been sent to translation (this shouldn't happen with recent versions of WPML, but it could be a glitch or something).
- Maybe you sent too many jobs at once and the server timed out and created this issue.
In short please try to send smaller batches with unique names.
