Home›Support›English Support›[Resolved] Errore di autenticazione, contatta il tuo responsabile delle traduzioni per verificare il tuo abbo...
[Resolved] Errore di autenticazione, contatta il tuo responsabile delle traduzioni per verificare il tuo abbo...
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing an authentication error ('Errore di autenticazione, contatta il tuo responsabile delle traduzioni per verificare il tuo abbonamento') while trying to translate a product using WPML, even though your license is valid, it might be due to a plugin conflict. Solution: We recommend deactivating the 'Add Admin CSS' plugin on your site, as it could be causing the conflict. After deactivating, please clear all caches (site, browser, server) to see if the issue resolves. Additionally, you may need to cancel any in-progress translation jobs at WPML -> Translation Dashboard -> Jobs. Test these steps and observe if the authentication error persists.
If this solution does not apply to your case, or if it seems outdated, 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 issue continues, please open a new support ticket at WPML support forum for further assistance.
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 product on my site hidden link using WPML. I checked the license, and it is valid. WPML is registered on this site using the following sitekey: ******XqU3. You will receive automatic updates until December 4, 2025.
Symptoms:
Errore di autenticazione, contatta il tuo responsabile delle traduzioni per verificare il tuo abbonamento.
Questions:
What language is the error message in?
Why am I receiving an authentication error when my license is valid?
How can I resolve the authentication error to continue using WPML?
After further testing on the staging site, it appears the plugin Add Admin CSS is causing a conflict. As soon as I reactivate that plugin, the errors come back. I deactivate it and I'm able to load the Advanced Translation Editor. Can you test deactivating that on your live site, clear all caches (site, broswer, server) and let me know if you see the same results? YOu may need to cancel in Progress jobs after deactivating that plugin as well at WPML -> Translation Dashboard -> Jobs.
I'm afraid that WPML is still broken, but now in a different way.
Background: to create the product: Kennerton Rognir MK2 I duplicated a similar product - Kennerton Arkona.
I have finished translating 100% of Kennerton Rognir MK2 and I went to check it on the front-end. In the English version I saw "Kennerton Arkona - copy" and not the "Kennerton Rognir MK2". I figured that maybe the title did not save or something, so I edited it directly in the product editor and fixed the name, but then I saw that it is really just a duplicate of the "Kennerton Arkona" product, just the images were correct (Rognir Images) all the rest of the page was all the original duplicated content, nothing was translated, or at least the translation does not appear on the front-end while showing 100% completed on the back-end.
I went into trouble shotting and clicked everything, cleared all cache, nothing!
even the URL is wrong: hidden link
Something is not right with WPML!
New threads created by Lauren and linked to this one are listed below:
While waiting for you I decided I will just delete the English version and redo the whole translation (on the live website).
So I switched to English in the back-end, then I deleted the English version (from trash too), then switched back to Hebrew and created a new translation using the "+" button. It was 100% and completed, But nothing appeared on the front end, and when switching the back-end to English there is no product there, there is no English version at all for the product.
The WPML is completely broken. What do I do? I need this product up and running right now.
I decided to try and redo the entire product.
I created a new Hebrew version, then created a translation which was 100% complete.
Same thing - no English product was created, there is only the Hebrew product. The translation is still 100%. I clicked all options on the trouble shotting page.
I have been working for hours on this, using ChatGPT.
Here is our current status outputted by ChatGPT, please read this carfully, it will save you so much work.
**Summary of tests and findings**
Initial symptom:
Translating products (e.g. Kennerton Rognir MK2) via the Advanced Translation Editor (ATE) shows 100 % complete, but no English version is created.
The product keeps showing a cogwheel icon instead of a “+” and no English post appears in the backend.
Troubleshooting actions already taken:
Cleared all caches (WP Rocket, WooCommerce, WPML).
Ran every relevant command in WPML → Support → Troubleshooting (sync job IDs, fix tp_id, remove ghost entries, clear cache).
Deleted old duplicated products and recreated new ones.
Confirmed the issue occurs even with a brand-new product, not duplicated from another.
Co*nfirmed WPML registration and license are valid (via Plugins → Add New → Commercial).
Tested both Advanced and Classic Translation Editors → only Classic successfully creates English posts.
ATE communication test:
Added a temporary MU-plugin to log incoming ATE REST requests.
Log shows successful callbacks such as
IN POST /wpml/tm/v1/ate/jobs/sync … OK
proving ATE → site communication is working and requests are accepted.
Key discovery:
When visiting hidden link
the site returns
rest_no_route / 404 (Not found)
meaning the REST route responsible for applying translated jobs is not registered in WordPress.
Conclusion:
The ATE jobs reach the site and get acknowledged, but cannot be applied because the /wpml/tm/v1/tp/apply-translations endpoint is missing.
This explains why all translations show 100 % complete yet no translated posts are created.
Next planned step:
Deactivate and reactivate WooCommerce Multilingual & Multicurrency (and WPML Translation Management if present) to re-register the /wpml/tm/v1/* REST routes.
Then retest /wp-json/wpml/tm/v1/ to confirm that tp/apply-translations is restored.
🧾 Summary of findings – WPML ATE not creating English product posts
Site: hidden link
WPML build: latest (as of November 2025)
Issue:
When translating WooCommerce products from Hebrew → English using the Advanced Translation Editor (ATE), the translation reaches 100 % but no English product is created.
In the Products list the cogwheel icon remains, and /en/product/... returns 404.
🔍 Diagnostic steps & results
1. Database and WPML tools check
Ran all “Fix…” and “Synchronize…” utilities in WPML → Support → Troubleshooting
→ No change.
Creating a fresh test product and translating also failed.
2. REST route verification
The route /wp-json/wpml/tm/v1/tp/apply-translations initially returned 404 when tested anonymously.
Dumped all WPML REST routes via /wp-json/wpml/tm/v1/ → the endpoint does exist.
Direct anonymous POST → returned 401 rest_forbidden (“אין לך הרשאות לעשות את זה.”).
✅ Confirms the route is active but requires authentication.
→ Response: [] (no error).
✅ Confirms the endpoint works perfectly when authenticated.
Conclusion:
ATE completes jobs but does not authenticate when calling /apply-translations, so the remote POST is rejected with 401.
That’s why translated products never appear, even though the translation status shows 100 %.
📎 Request to WPML team
Please investigate why ATE’s callback to
/wp-json/wpml/tm/v1/tp/apply-translations
is unauthenticated or missing its nonce/token.
The route itself works fine when called with valid credentials.
I think ChatGPT wasted hours of my time, he is not updated to your latest 4.8 version. take his input with a grain of salt, he might not know what he is doing.
I will spit the issue of the product not translating to a new ticket, since it is a separate issue. It seems the original issue of the error message has been resolved due to the plugin conflict. If so, please mark this ticket as resolved and we can continue the other issue in the other ticket.