This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues with WPML's Advanced Translation Editor (ATE) such as receiving errors like 'Unable to retrieve job details' and 'finalCallback.incompleteResponse' after trashing an incorrectly assigned post and its translation, and then creating a new post with the same title and content in the correct language. Solution: We recommend the following steps: 1. Ensure that you have deleted the trashed post completely. 2. Visit WPML > Support > Troubleshooting and run the options to remove ghost entries and cancel in-progress automatic jobs. 3. If the issue persists, try duplicating the post to give it a different job ID and attempt the translation again. 4. If none of the above resolves the issue, it may be necessary to escalate this to our second-tier support or perform further debugging.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket 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.
Background of the issue:
I am trying to translate a post using WPML's Advanced Translation Editor (ATE) after an editor added a new post under the wrong language. I trashed the incorrect post and its translation, then created a new post with the same title and content in the correct language. I also cancelled the pending translation jobs from Translation Management.
Symptoms:
When I try to translate the post with ATE, I get the error 'Unable to retrieve job details'. Additionally, I see an error 'finalCallback.incompleteResponse' in the console tab in my browser's DevTools. There are no errors in WP debug.log or the ATE error log.
Questions:
How can I resolve the 'Unable to retrieve job details' error in ATE?
What does the 'finalCallback.incompleteResponse' error mean and how can I fix it?
After further research, the issue is related to the content of this specific post itself, either there is an element (Widget, block...) that is causing an unexpected issue, or there is a lot of code in it, like a lot of empty HTML tags, uselessly nested tags, etc...
To better know that, either share an admin access to your side with the promise to not change anything, we are just going to try sending the same post again ourselves and monitor what happens in the backend,
If that's not possible, could you at least share the XLIFF file of this translation job, to get that, simply go to WPML > Translation management > Select the concerned post > Select translate myself/or assign to translator > Go to the translation basket and assign the translation job to yourself > Go to WPML > Translation > Select the concerned JOB and export to XLIFF 1.0 as shown here : hidden link
Please share this file so we can see the content of the post,
I'm escalating this to our 2nd tier, and I suggest to do the following test :
1- Open ATE (Advanced Translation Editor) on any other page that works
2- At the top right corner, click on the settings icon
3- On the settings tab, you can Disable "Big segmentations" and revert back to the previous ATE version (GEN2)
The design of ATE will change to the previous version, could you now resend the translation job again and see if it opens with this version?
I would like to run the following test, could you try it?
As of now, we do not see which exact part is causing such behavior, on the concerned post, could you remove parts gradually from the post to see if there is anything that's blocking the job retrieval? Start deleting the content block by block or widget by widget, and each time save and test if the translation editor opens.
Also, is it possible to prepare a staging environment of your site so we can freely test on it?
As of today, I am no longer to reproduce the error.
There was however an empty segment visible in the ATE, right before the H2 block. I noted that the previous paragraph was ending with two spaces, followed by non-breaking space " ". There were also other paragraphs ending with non-breaking space. But they were not followed by empty segments in ATE.
I belive these non-breaking spaces are unintentional artifacts from Word-to-WP conversion. With that said, shouldn't non-breaking spaces be shown as <wpml_nbsp> in ATE? At least that is what I have seen before.
Must have sent the wrong link. It is this one: hidden link
Anyway, I restored the revision of the original that had empty sections in ATE but ATE is not show that (empty section) anymore. Is there anything left to do at this point?
