[Waiting for user feedback] WPML + ACF Blocks + Options Page — fields not detected for translation

I have uploaded my theme to your sandbox, installed ACF Pro, imported all ACF field groups, and added my ACF Blocks to the homepage.

Now I am trying to translate the original Hebrew page into English.
When I click the “+” icon to create the translation, the WPML Translation Editor opens — but I only see one field: the page title. None of my ACF fields appear.

In WPML → Settings → Custom Fields Translation, WPML also does not detect any of my ACF fields. It only shows a few standard post-type fields.
Fields from options pages and ACF Block field groups do not appear at all. This is most likely the root of the issue.

Next problem: I have an ACF Options Page called Theme General Settings.
I filled in the fields there, and all fields are set to:

Multilingual Setup: Expert

Translation Preference: Copy

These are global settings that should not differ per language.
However, when I switch to another language, the fields are empty. WPML expects a separate set of values per language instead of copying the original values.

These issues are critical for the project.
We chose WPML specifically for better control and the ability to use automatic translation, but right now WPML does not detect any ACF Block fields — so automatic translation is impossible.

Please help clarify:

Why WPML does not detect ACF Blocks and ACF Options Page fields in Custom Fields Translation.

Why ACF fields do not appear in the Translation Editor.

Why ACF Options Page fields set to “Copy” are not copied across languages.

Thank you — looking forward to your guidance.

Hi Kor, thank you for your reply.

We will double-check the “Sticky Panel” ACF field group as you suggested.
After removing the block, we also noticed that the Page Translation mode started showing the translatable fields correctly.

However, during testing we created a new field inside an existing ACF field group, filled it with content on the original language, but WPML did not detect this new field inside the Page Translation interface.
Is there any process we need to run (a refresh, rescan, or re-index), or is this a known issue with WPML not detecting newly added ACF fields?

Another thing that concerns us is that in WPML → Settings → Custom Fields Translation, we do not see any ACF field groups related to blocks or option pages.
On our older projects these fields appear there normally, so this behaviour seems unusual.

Finally, we still haven’t received clarification on how WPML is meant to work with global ACF option page fields that should NOT be translated.
Fields such as social links, contact email, phone number, etc. must use the same value across all languages.
At the moment WPML expects each language to store its own copy of these fields, and the “Copy” setting does not seem to work for us.

Could you please advise on the correct setup or expected behaviour for non-translatable global option fields?

Thank you.

I can reproduce this on any block.
For example, I add a new test field to an existing ACF group such as Block – Hero, then open the homepage in Hebrew, fill in the value and save.
When I click to edit the English translation, the Translate Page screen shows the same old fields as before — the newly added field does not appear, and WPML does not detect it at all.

I no longer have access to your sandbox – it now requires authorization, so I can’t verify anything there on my side anymore.

Regarding the issue: I was not able to reproduce the error shown in your screenshot either on your sandbox (when it was still accessible), nor on our staging, nor locally. Please check your server logs on the sandbox to see what exactly is failing on your side — the error seems unrelated to our implementation.

The original problem was clearly described:
When I add a new field to an existing ACF field group, WPML does not detect this new field inside the translation editor. It looks like WPML needs to “refresh” its internal ACF field registry or re-scan the field group, because until something triggers that refresh, the new field simply does not appear.

Please check why WPML doesn’t rescan updated ACF field groups automatically and how to force this refresh properly.

It seems that the StickyPanel block issue on your environment is likely caused by your firewall blocking the JSON file upload or save operation inside the ACF field. Most likely, the JSON file is being flagged as unsafe, which prevents ACF from storing it correctly.

Regarding the issue with newly added ACF fields not appearing in WPML translation:

As shown in the screenshots, the problem is easy to reproduce.
I simply add a new field to an existing ACF field group, fill in its value on the page in the original language, then click the translation icon to open the English translation.
However, WPML does not display this newly added field in the translation editor—it only shows the older fields that existed before.