ACF Field Groups are sent for auto translation despite being set to "Not translatable"

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
-	12:00 – 14:00	12:00 – 14:00	12:00 – 14:00	12:00 – 14:00	12:00 – 14:00	-
-	17:00 – 21:00	17:00 – 21:00	17:00 – 21:00	17:00 – 21:00	17:00 – 21:00	-

Supporter timezone: Europe/Vienna (GMT+01:00)

This topic contains 3 replies, has 0 voices.

Last updated by Bigul 4 days, 19 hours ago.

Assisted by: Bigul.

Author	Posts
February 28, 2025 at 3:40 pm #16761722
berntE	Background of the issue: I am trying to resolve an issue related to ACF Field Groups being sent for auto translation despite being set to 'Not translatable'. This is a follow-up to a previous issue discussed at https://wpml.org/forums/topic/php-fatal-error-uncaught-error-call-to-a-member-function-get_source_language_code-in-functions/ which was closed before I could troubleshoot further. Symptoms: We're seeing fatal errors in our log file because ACF Field Groups are sent for translation despite being set to 'Not translatable'. You can see the stack trace in the previous thread. Questions: Why are ACF Field Groups being sent for translation despite being set to 'Not translatable'? How can I prevent fatal errors related to this issue? I tried hooking into the 'wpml_send_jobs_batch' hook to remove any elements that have post type 'acf-field-group'. But sometimes all elements in the batch have this type, and the WPML_TM_Translation_Batch class throws an error if I try to instantiate it with an empty element array.
March 1, 2025 at 5:45 pm #16764302
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hello, Welcome to the WPML support forum. I will do my best to help you to resolve the issue. Please upgrade to WPML 4.7.1 version after a full site backup {mandatory}, and make sure the problem exists or not. May you have to visit Plugins>>Add New>>Commercial tab and click on the Check for updates button to get the WPML automatic upgrade links of the latest version. This step will help us refresh the installer caches. If the problem remains, a couple of requests for tracking this bug. 1) Please let us know the exact steps to replicate the problem on your site. 2) Please fill the private details fields after a full site backup. I would like to access the admin area of your site for further checking. Refer to the following links for more details about our private information sharing policies. https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ hidden link -- Thanks! Bigul
March 4, 2025 at 2:26 pm #16774640
berntE	Hi again, I have updated to the newest version of the plugin, and I continue to see the error. 1) It's difficult for me to give exact steps, since the problem happens in the background. But as far as I can see, here is how to reproduce it: - Go to #WPML > Translation Management" which shows the "X translations left in queue" - Wait for 1-2 minutes, since it doesn't always happen immediately - Check the debug.log file I then see that the fatal error has occurred. 2) I'm not sure we can give you access to the backend. I'll talk to the rest of the team and the business side to see if this is possible.
March 4, 2025 at 5:43 pm #16775393
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hello, Thank you for the updates. This requires further debugging. So it will be great if you can consider a staging/dev site (a clone copy of the live site) for further debugging. So we can troubleshoot the bug without affecting the live site. -- Thanks! Bigul