Hello WPML Support,
ACF Support has reviewed the issue and confirmed that it is related to the translation layer handled by WPML rather than ACF itself.
We are experiencing a problem with ACF Repeater/Flexible Content blocks:
When a new ACF block is inserted in the default language, existing translations remain linked to the old block positions. As a result, translated content is assigned to the wrong blocks.
When an empty block is deleted in the default language, all translated content temporarily disappears from every translated language. The translations only reappear after recreating the same block in the default language.
This makes it impossible to safely add, remove, or reorder ACF blocks without affecting existing translations.
ACF Support advised us to contact WPML because the translation mapping is managed by WPML.
Could you please investigate:
Why the translation mapping depends on block position instead of a stable block identifier?
Whether this is a known issue with ACF Repeater/Flexible Content and WPML?
If there is a recommended workflow or a fix that allows adding/removing/reordering ACF blocks without losing or misaligning translations?
For reference, this is the response we received from ACF Support:
"Usually, ACF doesn't come with translations built in out of the box... if you encounter any issues with the plugin (in your case, WPML) you're using to translate the fields, I'd request that you reach out to the specific plugin support... our support is limited to the basic usage of the ACF plugin, and we don't offer any translation-related support."
Thank you.
ეს უკვე საკმარისად მკაფიოდ გადადის WPML-ის გუნდთან და თან უთითებს, რომ ACF-მა თავად გადმოგამისამართათ.
