WPML Advanced Custom Fields Multilingual

Version 5.2.0 — 21 October 2026

• New Translated pages carry the inLanguage property in the JSON-LD structured data that ACF outputs.
• New When an AI agent creates an ACF field group through ACF's abilities, it can now choose the group's translation mode.
• Improved With ACF Extended, bidirectional relationship fields now stay paired on translations after WPML copies, duplicates or translates them.
• Improved Taxonomy custom fields set to Copy are locked on term translations.
• Improved On the Custom Fields Translation settings, the underscore system field of a locked ACF field is now locked too.
• Improved When ACF Multilingual is active without Advanced Custom Fields, a notice now says so and offers to activate or install it.
• Improved The String Translation packages for field group labels are named after their field group, so it is clear what each one holds.
• Improved 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.
• Improved "Overwrite with duplicate" on a field group refreshes ACF's field cache, so it no longer causes PHP warnings.
• Fixed A row inserted into a Copy-mode flexible content field reaches translations that were edited in the WordPress editor.
• Fixed With one field group per language, a translation's admin editor shows its saved values, and saving there keeps them.
• Fixed Saving a translation of a post with repeater fields no longer causes a fatal error when its previous translation job cannot be read.
• Fixed ACF options values translated in String Translation appear on the site, and completed translation jobs no longer overwrite manual String Translation translations.
• Fixed ACF Select fields are copied correctly to translations of existing pages.
• Fixed Field groups loaded from acf-json send their translation preferences to WPML.
• Fixed Options-page values read after switching language return the switched language, not the language the request started in.
• Fixed Flexible content layouts keep their disabled state and custom name in translations.
• Fixed ACF bidirectional relationships are kept per language.
• Fixed Duplicating ACF Extended bidirectional posts no longer adds the translations to the original post's relationship.
• Fixed 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.
• Fixed Clone field subfields get the right translation preferences, and a Link field's target is no longer sent for translation.
• Fixed ACF blocks are supported with post-meta storage, inline block fields and field groups assigned to blocks.
• Fixed Changing an ACF field's translation preference also updates existing term translations, not only posts.
• Fixed On sites set up with WPML 5.0, ACF field groups open in the WordPress editor again instead of WPML's translation editor.
• Fixed Post types created in ACF while ACF Multilingual was deactivated get their labels registered for translation.
• Fixed The post editor no longer asks to translate a post manually when its field groups mix "Same content" and Expert modes.
• Fixed Upgrading from an ACF Multilingual version older than 2.2.0 no longer leaves an untranslated duplicate "Field Group Labels" package per field group.
• Fixed The field-group modes notice reads correctly in Spanish, Hebrew and other languages, without wrong plural wording around the field count.
• Fixed New layouts are copied in posts with Flexible Content fields.
• Fixed Saving a translated post in the WordPress editor no longer removes its system fields.
• Fixed A Taxonomy field connects the translated terms instead of creating new terms when you save in the WordPress editor.
• Fixed Pagination in repeater fields works on translations.
• Fixed The ACF Multilingual and WPML SEO descriptions translate on the Plugins screen.
• Fixed Built and released together with WPML 5.2.0, with the same shared library version.
• Fixed Read the release announcement for WPML 5.2 for the full story behind this version.

Earlier versions

• 5.1.0 (29 September 2026): 1 new, 21 improved, 12 fixed, 1 security
• 5.0.0 (13 September 2026): 2 new, 20 improved, 1 fixed, 1 security
• 2.2.4 (21 April 2026): 2 fixed