I'm running into the known issue described here:
https://wpml.org/errata/advanced-custom-fields-inability-to-translate-external-links-in-same-fields-across-languages-mode/
The ACF Link field type simply doesn't get picked up for translation when the field group is set to "Same fields across languages" mode. The workaround (switching to Expert mode and manually setting each field to "Translate") is not a realistic option for projects with a larger number of field groups.
What makes this especially frustrating: WPML heavily promotes AI automatic translation as a key feature – but a bug like this makes it completely unusable for sites relying on ACF Link fields. If core field types aren't translated, the whole automation breaks down.
This issue was first reported for ACFML 2.0.5, released May 3, 2023. That's over two years ago, and the status is still listed as "Open" with no fix in sight.
My questions:
1. Is there an actual fix planned, and if so, when?
2. Is there a less invasive workaround than manually switching every field group to Expert mode?
3. If not, why is this not treated as a blocker for the AI translation feature?
I'd appreciate a concrete response from the WPML team, not just a pointer back to the existing workaround.
