Translate content button disabled after WPML update (WooCommerce products)

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	-	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00
-	-	-	-	-	-	-

Supporter timezone: America/Lima (GMT-05:00)

Tagged: ATE, WCML

This topic contains 39 replies, has 0 voices.

Last updated by Andreas W. 12 hours, 31 minutes ago.

Assisted by: Andreas W..

Author	Posts
April 16, 2026 at 6:46 am #17972805
adrienL-15	Hi Andreas, Thank you for your update. I tested this on the staging site after your synchronization, including in a private browser session, but the issue still persists on my side. The button remains greyed out when using the Translation Dashboard. Could you please confirm if this is still working on your side? Best regards, Adrien
April 16, 2026 at 7:19 am #17972941
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	I can not confirm this. See screenshot.
April 20, 2026 at 7:32 pm #17982053
adrienL-15	Hi Andreas, Thank you for your screenshot. I can confirm that on my side, the issue still persists on the staging environment. When I follow the same steps in WPML → Translation Management and select products for automatic translation, the system does not calculate the word count properly and the button remains greyed out. This happens even in a private browser session. Since it works in your session but not in mine, it seems the behavior may depend on user configuration or permissions. Could you please confirm which user role and translator settings you are using when testing? Best regards, Adrien
April 21, 2026 at 9:17 am #17983395
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	I could see the issue today again, and it appears not to occur only for products. I can see the issue even when testing only with WPML when trying to send any post to automatic translation. I have deleted and then installed WPML again, as I was unable to see all the translation engines. This solved the issue about the translation engines, but the issue on the dashboard persisted. I would first of all recommend that you register WPML on your site: https://wpml.org/faq/install-wpml/#2-register-wpml-on-your-website If this does not solve the issue, I suspect that the issue is related to Clouflare. Could you please ask Cloudflare Support if they see any issues in the server error log or regarding the server's firewall?
April 24, 2026 at 11:07 am #17992528
adrienL-15	Hi Andreas, Thank you for your suggestions. I can confirm that WPML is correctly registered on my site (see attached screenshot). Regarding Cloudflare, I contacted my hosting provider (Rocket.net), and they temporarily whitelisted my IP to bypass Cloudflare protection for testing purposes. Unfortunately, the issue still persists: - the word count is not calculated - the automatic translation button remains greyed out So it seems that Cloudflare is not the cause of the issue. Best regards, Adrien
April 24, 2026 at 12:19 pm #17992705
adrienL-15	Hi Andreas, Just a quick update on my side. Following your suggestion, I contacted my hosting provider (Rocket.net), who indicated that this type of issue is often related to AJAX or REST API failures within WordPress. I then ran tests using the browser network console and found that some WPML-related requests are returning a 500 error, including: - gettranslationstatus - get-words-to-translate-for-items This seems to explain why the word count is not calculated and why the automatic translation button remains greyed out. So it looks like the issue is caused by a server-side error when WPML tries to process these requests. Best regards, Adrien
April 24, 2026 at 7:12 pm #17993752
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Thank you for the updates! I will try to take a local copy of your site to confirm if the issue persists on a virtual server.
April 25, 2026 at 12:29 am #17994064
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	The issue does not occur on a local copy of your site. I would like to invite you to: - Create a local copy on your site - Complete the migration dialog while connecting the site with your current site so that they share translation credits - Register the site with a new site key Test again. If you are unaware of how to create a local copy, I can offer to create a server instance on Cloudways, where we could migrate your site for testing. Note that since the issue does not occur on my local install, it is very unlikely that it would occur on Cloudays. This confirms that this issue is caused by your server. We can try first to migrate to Cloudays, if you insist, but it would be more likely better to have your hosting support take another look at this problem.
April 29, 2026 at 9:46 pm #18004119
adrienL-15	Hi Andreas, Thank you for your reply and for your suggestion. Just a quick update on my side. I haven’t had the chance yet to run the local test, but I am planning to set up a local copy of the site and test the issue there as you suggested. I will get back to you as soon as I have results. Best regards, Adrien
April 29, 2026 at 10:46 pm #18004128
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	I could also offer to set up an installation on our Cloudways Server, where you could migrate the site using the Cloudways Migrator plugin.