Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hi Peter,
I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at this issue and will try to find a solution.
I will get back to you as soon as I get an answer from them.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hi Peter,
Thank you very much for your patience.
Upon further inspection, we have discovered that the website has a user with an invalid e-mail: 'do-not-remove@wordpress.c0m' - notice the '0' instead of 'o'. This is what made ATE to throw out errors and not synchronize translators.
We have applied this workaround to the staging website:
- Get access to your database and go to the wp_users table
- Search for the user with this e-mail: do-not-remove@wordpress.c0m
- Change it to a proper email
- Then update any translator so that the translators are synced with ATE
It might be necessary to do a small modification to the original language content, and resend it to translation. We have checked some posts and they seem to be working fine. Could you please review it and confirm that the issue is solved? Thanks!
Hi Marcus,
I can see this user was deleted from testing site.
But now when I clic to Edit some translation, the page is refreshing but stay on Posts page, it is not going to ATE, and didnt shows any error.
Can you let me know which steps you did exactly when you were verifying the functionality, to be able to reproduce it?
And how is possible the email address of some user cause this type of error?
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hey there,
About how a not-valid email could cause this issue, it's related to how ATE is synced. If a translator (sometimes even a regular user which is not assigned as a translator) does not have a proper email settled, the synchronization won't work well and the jobs will be stuck.
Now, about the post translations still not working, for example, the jobs for the post 'testing 2' were stuck, and we had to do a minor modification (like an extra space) to the original content, in order to refresh the translations. By checking it now, it still works if we click to edit the translations from here: hidden link
The ATE is also working for the post that we were debugging in the beginning: hidden link
Please check it: hidden link
Could you please show us an example of a post that is not working well?
I have one question, we have setup Autotranslate without Review, but we have a lot of articles in review, how could I close those reviews.
When Im trying to select them (in WPML->Translateions) and chose bulk action: Approve Translation Review, its not working. Still have 663 posts in review.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello Peter,
Glad that we were able to resolve the original problem.
Regarding the new issue with the reviews of the translations, we have just checked and there were 59 jobs on the 'review' status. By approving some of them, the number was reduced to 39. Please check it:
hidden link - 59 items before approval action hidden link - 39 after the approval action
Are you still experiencing this issue? If the answer is yes, could you please tell us the exact step by step to reproduce it? Thanks!
Hi Mateus,
I make some investigation and:
1. There is 0 job in pending review (after filtering)
2. There are 30 posts in "available for translate" - why those are not translated automatically if we have Auto-Translate activated?
3. There is 1 in progress - how to move it to "completed" state?
4. We have some articles that seems to be translated but stuck in "In Progress" even when on front-end everything seems to be good - how to avoid those "blocks"?
It is this article, and is accessible only if you are logged in (and well translated) if you are not logged in its 404: hidden link
We have set auto-translation ON for post and without reviews needed, to make it as automatically as possible.
I prepared second testing environment, with actual version of production site, in here: hidden link please use the same credentials as before.
Hi Matheus,
this is only testing environment as I told you.
All those errors are in production web where we have enought credits (see the screen).
So the current problems:
2. There are 30 posts in "available for translate" - why those are not translated automatically if we have Auto-Translate activated?
3. There is 1 in progress - how to move it to "completed" state?
4. We have some articles that seems to be translated but stuck in "In Progress" even when on front-end everything seems to be good - how to avoid those "blocks"?
It is this article, and is accessible only if you are logged in (and well translated) if you are not logged in its 404: hidden link
We have set auto-translation ON for post and without reviews needed, to make it as automatically as possible.
I found those two articles were in draft state, how is that posible?
We normally create articles, put in Draft state, and once we want to make it public, publish them.
So my expectations are the article should be published in all language, right?
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hi Peter,
Thank you for the clarifications.
Could you please try the following procedure on the live website (since the staging does not have enough credits, it won't have the same effects if we try to apply it there):
- Make sure to have a complete website and database backup
- Remove the WPML plugins and reinstall them. In this step, please make sure that you have our updated versions (https://wpml.org/account/downloads/)
- Go to WPML -> Support -> Troubleshooting
- Click on this button 'Synchronize local job ids with ATE jobs'
- Now visit the WPML -> Translation Management -> Translators and edit any translator, in order to refresh and sync them
Then, please check if the posts will be automatically translated this time. If still not solved, would it be possible to give us once again the live website credentials? I'm afraid that it'll be necessary to check better there.
About the drafted posts, we can't tell for sure what might have caused this. It can be, for instance, a conflict with a plugin. Regardless, this is a different issue and we would need to debug it in another ticket or chat (due to our support policy of having one issue per case).
Keep us posted about your results. Thanks!
Regards,
Mateus.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
