Changelog
Requires WPML 5.3.0.
What's New
- An ACF options-page text field set to Translate shows the default language's value on the front end until its translation exists.
Performance
- Saving a post with many fields is faster: field checks are worked out once per post.
- ACF Multilingual no longer loads its field annotations on the front end.
Fixes
- The field group's WPML setup panel names the Translation Dashboard section "ACF Field Groups", as the Dashboard does.
- ACF URL and Link fields that point to your own site keep their query string and #anchor in every case.
- A manual translation of an ACF Link or URL field is kept when the content is translated automatically again.
- ACF field labels show translated on the admin page that runs the ACF Multilingual 2.2 upgrade.
- Saving a post repairs ACF relationship and bidirectional fields that still point to original-language posts.
- Field groups translated the legacy way no longer trigger a false "same field name" warning, and the "Translatable" warning no longer links to the documentation.
- An edited ACF repeater row keeps its existing translation in a new Classic Translation Editor job.
- Editing an ACF repeater row in place no longer holds the row's Copy sub-fields back from translations.
- No fatal error on PHP 8.4 when the ACF Multilingual sub-field settings upgrade runs.
- Rows of nested ACF repeaters, and their new order, reach translations edited in the WordPress editor.
- An ACF options page saved in a secondary language keeps its values as entered, without added backslashes.
- Rows nested in an ACF repeater row that moved in the same save follow their row on translations.
- Rows removed or moved in an ACF repeater set to Copy reach translations edited in the WordPress editor.
- An ACF Link field on an options page translated in String Translation shows its translation on the site.
- Security hardening.
- Pages using Elementor Pro's ACF dynamic tags no longer stop with a fatal error on sites with per-language user fields.
- Admin pages no longer stop with a fatal error when a field registered in PHP writes its conditional logic as one rule.
- ACF fields set to Copy that use a widget, such as relationship lists, pickers and WYSIWYG, are locked on a translation.
- An ACF save no longer overwrites a custom field preference that wpml-config.xml locked.
- ACF repeater rows changed with update_field() keep their translations when the post is saved in the same request.
- A bidirectional field no longer breaks when another plugin stores post objects in it.
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 PluginsAdd New PluginCommercial. 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.
