[Resolved] Auto translation for all Woocommerce product
This thread is resolved. Here is a description of the problem and solution.
Problem: The client's WooCommerce site, set to 'Translate all' and 'Publish without revision,' was not automatically updating product translations after changes in the original language. Products updated by a third-party application were queued with 'Waiting for translator' status, and attempts to manually update translations resulted in an 'ateJobCreationError=101' error. Solution: We recommended ensuring that the WPML settings were configured correctly: 'Publish without review' should be enabled, and the Advanced Translation Editor set as the default. We also advised checking that 'pay as you go' was activated with sufficient credits. For the specific error 'ateJobCreationError=101', which indicated issues with the XLIFF files not belonging to the system, we suggested checking the ATE error logs for more details. If the problem persisted, we recommended manually making a small change to the affected products and updating them, which could help restart the automatic translation process. Additionally, disabling 'Translate Everything Automatically' temporarily could help manage and resolve stuck translation jobs in the WPML > Translation Management page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please 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. We highly recommend opening a new support ticket for further assistance 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.
I am writing to let you know that we have two possible workarounds that you can try.
You can:
- Make a small change to the affected posts and update them.
It should start working or you can send from WPML > Translation Management
OR
You can try to temporarily disable Translate Everything Automatically which would show the Jobs tab in WPML > Translation Management page.
Then you can go to Jobs and find the jobs that are not completed (Needs Translation status).
After you select them, you can select to Cancel in bulk (note you might want to repeat this a few times because there are many subpages with such jobs) and then you can force retranslate automatically from WPML > Translation Management or try to re-enable Translate Everything Automatically mode.
I hope this helps you progress with the project that you are working on.
Until now, I manually selected all the products that were stuck waiting for a translator to send them for translation. Last week, I was able to send all the products that hadn't been automatically translated, and I no longer had any products to translate. And since today, when I try to do the same thing, I get an error message:
"Submission for translation failed.
The jobs could not be created in the Advanced Translation Editor. Please try again or contact WPML Support for help."
(See attached file).
This is the first time I've had this message, and I installed version 4.7.3 this morning.
These products are therefore not automatically translated, and I can no longer send them for translation manually as I used to.
I visited your site, and I see one stuck job in the ATE log - for a product with ID 22610 that was not present on your site.
Did you perhaps do a migration of a sort? Like between staging and production? Or perhaps you removed some contents while WPML was disabled?
This was an automatic translation job that was stuck and attempted to be downloaded over and over again - but because there was no actual post - it was producing errors.
I canceled that job and it should not be bothering you anymore.
In addition, in your ATE comm log, I can see some errors that were probably caused due to communication issues with your server and ATE.
Maybe you should enable debugging (if not done already) and check for errors in the log and provide us with the output as this is probably a new issue.
Hello again!
Yes, this is the job that I was telling you it had missing the original language post.
You should not get any more entries related to that job.
Hello,
I'm getting back to you regarding the various issues raised in this ticket.
I no longer have the error message when I try to create a translation, however my initial problem still persists. I was able to translate all of my products, so yesterday I no longer had any products pending translation. Today,
following an update from my client on one of their products (in the original language), the translations for this product are not updating automatically. I manually sent the English translation to check if it was working, and the translation was successfully created. But I have to check every day if there are products pending translation and send them manually if they are, and I would like this process to be automatic.
Hello!
I am not sure why the translation was not started automatically.
From what I can see, a translation job was created only once yesterday evening for that post element - and I assume that this is your manual sending of the job.
How was the change of the original done?
Is it done via API or an automated logic? If this is the case, if the logic did not call the normal WordPress functions - that may be the issue and WPML may have not detected the change.
Another possible cause would be caching issues - so maybe you can test if a new job is created if you disabled the cache plugin and other potentially active server-side cache solutions.
And the third case would be if the change was very minor edit - what was exactly changed? It is possible if the change was just a letter, or perhaps a digit as a price for example, that the translations did not switch status to "needs update" status.
Hi,
Indeed, the changes are made via a module that allows the product database to be synchronized with EBP software. Apparently, the problem appears when a title change is made in EBP and the plugin synchronizes the name in the native language in woocommerce.
What I don't understand is that WPML detects the change, since the product appears as "needs update," but this update doesn't launch automatically; this seems like a bug. But if I understand correctly, there isn't much I can do, so I'll continue to send the translations manually for now, hoping this behavior can be fixed in a future version of WPML.
Thank you for your help and information.
Since the original issue is resolved, after discussing this with George it looks like this new behavior appears to be related to how the EBP integration updates product data.
From what we can tell, the EBP plugin likely updates titles directly in the database, bypassing WordPress hooks. WPML detects the change and flags the translation as "needs update," but auto-translation isn’t triggered because our logic depends on standard WordPress hooks, which aren’t fired in this case. This is expected and avoids potential performance issues.
As this is a workflow-specific case, we recommend opening a new ticket so we can look into it separately and evaluate possible solutions if any at the moment.
Please let me know if you would like to proceed and I can split the ticket for us.
Okay, Yes I would like you to split the ticket for us.
The EBP plugin is developed by a third-party company, and it's indeed possible that they make changes directly to the database.
However, we should only have the problem with product titles, because the descriptions are entered directly by my client in WooCommerce, which guarantees normal WPML functionality for updating this field. Apparently, only title changes are made via EBP and are imported into WooCommerce via this plugin.
Thanks for your follow-up.
New threads created by Bobby and linked to this one are listed below:
