WPML

Advanced Custom Fields Multilingual 5.2.0

Released
October 21, 2026
Channel
Stable
Tested with WordPress
7.1
Product
Advanced Custom Fields Multilingual

Changelog

Translated pages carry their language in ACF's structured data, and 27 fixes.

What's new

  • Translated pages carry the inLanguage property in the JSON-LD structured data that ACF outputs.
  • When an AI agent creates an ACF field group through ACF's abilities, it can now choose the group's translation mode.
  • With ACF Extended, bidirectional relationship fields now stay paired on translations after WPML copies, duplicates or translates them.
  • Taxonomy custom fields set to Copy are locked on term translations.
  • On the Custom Fields Translation settings, the underscore system field of a locked ACF field is now locked too.
  • When ACF Multilingual is active without Advanced Custom Fields, a notice now says so and offers to activate or install it.
  • The String Translation packages for field group labels are named after their field group, so it is clear what each one holds.

Performance

  • ACF Link and URL fields that point to your own pages now keep their #anchor, query string and sub-path instead of being cut to the bare page address.
  • "Overwrite with duplicate" on a field group refreshes ACF's field cache, so it no longer causes PHP warnings.

Fixes

  • A row inserted into a Copy-mode flexible content field reaches translations that were edited in the WordPress editor.
  • With one field group per language, a translation's admin editor shows its saved values, and saving there keeps them.
  • Saving a translation of a post with repeater fields no longer causes a fatal error when its previous translation job cannot be read.
  • ACF options values translated in String Translation appear on the site, and completed translation jobs no longer overwrite manual String Translation translations.
  • ACF Select fields are copied correctly to translations of existing pages.
  • Field groups loaded from acf-json send their translation preferences to WPML.
  • Options-page values read after switching language return the switched language, not the language the request started in.
  • Flexible content layouts keep their disabled state and custom name in translations.
  • ACF bidirectional relationships are kept per language.
  • Duplicating ACF Extended bidirectional posts no longer adds the translations to the original post's relationship.
  • Row sync, Copy once and field-group setup also run on saves through REST, the front end, WP-CLI and ACF's own data store.
  • Clone field subfields get the right translation preferences, and a Link field's target is no longer sent for translation.
  • ACF blocks are supported with post-meta storage, inline block fields and field groups assigned to blocks.
  • Changing an ACF field's translation preference also updates existing term translations, not only posts.
  • On sites set up with WPML 5.0, ACF field groups open in the WordPress editor again instead of WPML's translation editor.
  • Post types created in ACF while ACF Multilingual was deactivated get their labels registered for translation.
  • The post editor no longer asks to translate a post manually when its field groups mix "Same content" and Expert modes.
  • Upgrading from an ACF Multilingual version older than 2.2.0 no longer leaves an untranslated duplicate "Field Group Labels" package per field group.
  • The field-group modes notice reads correctly in Spanish, Hebrew and other languages, without wrong plural wording around the field count.
  • New layouts are copied in posts with Flexible Content fields.
  • Saving a translated post in the WordPress editor no longer removes its system fields.
  • A Taxonomy field connects the translated terms instead of creating new terms when you save in the WordPress editor.
  • Pagination in repeater fields works on translations.
  • The ACF Multilingual and WPML SEO descriptions translate on the Plugins screen.
  • Built and released together with WPML 5.2.0, with the same shared library version.

Read the release announcement for WPML 5.2 for the full story behind this version.

Update or download

The update is available to all WPML clients with an active subscription — it appears on the Plugins page in your WordPress admin within 24 hours of release. You can also check for it right away under Plugins → Add New Plugin → Commercial. To download and install manually, go to Downloads in your wpml.org account (see the installation instructions) and remember to update all components together without mixing versions.

Need help or want to give feedback? Please use our technical support forum.

See all Advanced Custom Fields Multilingual versions