WPML Advanced Custom Fields Multilingual 2.1.4.2

Fixed an issue where copying a value between ACF fields in one post changed the values in the translated post into a JSON-like string.

Features

• You can now copy custom field values associated with media.
• Hardened the data checking for synchronizing custom fields translation preferences, which prevents from running the check when the field object doesn’t have a correct field ID.
• Added support for translation preferences for fields associated with taxonomy terms.
• Added the ability to translate and display more than one ACF block.
• Added support for field translation preferences on the ACF Options Pages.

Fixes

• Improved the logic that checks whether to display a warning about not saved field translation preferences.
• Fixed a fatal error when WPML is not active.
• Fixed relationship fields not copying to translation when there are more than one related items.

Features

• Code for field type resolving has been simplified which results in performance improvement.
• ACFML now automatically sets ACF system fields to “copy”, preventing fields from not displaying on the front-end.

Fixes

• Repeater fields translated with Translation Editor are now correctly displayed on the front-end.
• Flexible fields with spaces in names are now correctly duplicated to other languages.
• Displaying duplicated fields in the Classic Translation Editor is not happening anymore.
• Fixed the issue with Numeric values not being translatable with the Translation Editor.
• Gallery fields inside repeater fields are now correctly copied during post duplication.
• Translated field labels are now correctly displayed on the front-end.
• Translated oEmbed field is now correctly displayed on the front-end.

Compatibility

• Ability to choose different media inside the flexible field.
• When translating Field Groups as post types, native WordPress editor is set as default.