Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing issues with translating ACF fields in Gutenberg blocks using WPML. Although some fields were translated after re-running the translation process, not all ACF fields were picked up.
Solution:
1. Ensure that ACFML is installed and set to the correct translation mode. For more details on translating ACF blocks with WPML, visit Translating ACF Blocks with WPML.
2. Provide WPML support debug information from your site by following these steps:
- Log in to your site and navigate to WPML → Support.
- Click on the 'debug information' link at the bottom of the page.
- Copy the entire content of the text box and paste it in the WPML support forum.
For more information, visit Provide Debug Information for Faster Support.
3. Create a new test page and add 1-2 ACF blocks to see if they are translated correctly.
4. If the issue persists, switch to the WordPress default theme, disable all plugins except for WPML and ACF, and test again by creating a new page with 1-2 ACF blocks.
5. Send a page for translation from WPML > Translation Management to ensure a new translation job is created.

If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your case, 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 needed, please open a new support ticket 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.

Tagged: 

This topic contains 5 replies, has 0 voices.

Last updated by Dražen 3 weeks ago.

Assisted by: Dražen.

Author Posts
March 20, 2025 at 7:06 pm #16841718

mikeR-33

Background of the issue:
We have built a number of Gutenberg blocks using Advanced Custom Fields (ACF) on our site hidden link. We are trying to automatically translate these ACF fields using WPML. All of the field sets are set to use 'Same fields across languages'.

Symptoms:
After running the automatic translation process, none of the ACF fields on Gutenberg blocks were translated nor are they available in the advanced translation editor. Native fields added using InnerBlocks are translated, but the ACF fields do not appear under WPML > Settings > Custom Fields Translation.

Questions:
Is there any way to make the Gutenberg block ACF fields available for automatic translation?
If it's not possible to automatically translate ACF fields, is there any plan to allow it in the future?

March 24, 2025 at 7:12 am #16849834

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

yes, they are translatable and if you are using ACFML and have set correct translation mode, it should work.

- https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/translating-acf-blocks-with-wpml/

1)  In order to expedite handling your support requests, can you please share WPML support debug information from your site.

- To give debug information, login to your site and go to WPML → Support. From there click on the “debug information” link at the bottom of the page.
- Once on the “debug information” page, select the entire content of the text box and copy it.
- Now go back to our support forum, find debug information box and paste it.

More information on the link: https://wpml.org/faq/provide-debug-information-faster-support/

2) Please create a new test page add 1-2 ACF blocks and see if it works.

Regards,
Drazen

March 24, 2025 at 2:37 pm #16852698

mikeR-33

Hi Drazen,

The fields are translatable, that's not the issue. What we would like to know is if it's possible to automatically translate the ACF fields on the Gutenberg blocks using the AI Automatic Translation process: https://wpml.org/documentation/automatic-translation/. According to this blog post (hidden link) it should be possible, however on our automatically translated pages none of the ACF text fields were translated, although native controls we added using InnerBlocks did get translated properly. Our process was similar to the one in the blog post so I'm not sure what we might have missed.

Thank you,
=Niraj

March 25, 2025 at 7:32 am #16854866

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello Niraj,

yes, it works fine with automatic translation and should be translatable.

I advise following next steps in order to see from where / what is causing the issue. It could be custom code or similar.

1) Please create a new test page add 1-2 ACF blocks and see if it works.

2) Switch to WP default theme and keep enabled only WPML plugins and ACF; disable all other. Creata a new test page and add 1-2 blocks, check if the issue still happens.

This will tell us if the issue is with WPML configuration or maybe your custom code / other plugin is causing issues.

Let me know how it goes.

Thanks,
Drazen

March 25, 2025 at 5:25 pm #16859267

mikeR-33

Hi Drazen,

Upon re-running the translation process it appears that several (but not all) of the ACF fields were automatically translated and are available in the advanced editor as well. It's possible a similar thing happened on our first attempt but with far fewer fields getting translated. Is there something we should do to ensure that all ACF text fields are picked up for translation?

Thanks,
=Niraj

March 26, 2025 at 7:03 am #16860652

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

It could be the first time a translation job was from previous settings, and not when you set ACF Settings to translate them.

You can send a page for translation from WPMl > Translation management and that will assure new translation job is created.

Regards,
Drazen