WPML Advanced Custom Fields Multilingual 2.1.4.2

Introduced the constant ACFML_EXCLUDE_FIELD_GROUP_STRINGS_IN_POST_JOBS.
Improved the field group multilingual mode rendering for right-to-left (RTL) languages.
Fixed a malformed translation file for French.
Fixed an issue with custom code when field choices are defined by another field.
Fixed the label display for required fields when it’s locked.
Fixed a fatal error in Options page when using taxonomy term as object in single select field.
Fixed a performance issue due to strings being repeatedly registered.
Fixed the display of repeater fields when translating via the native editor, and acf-field-group is set to Translatable using the Expert mode.

Fixed an issue with a custom field displayed twice in the native WordPress editor when the “acf-field-group” post type is made translatable (and field groups are translated).

Features​

• Introduced a new field group multilingual mode to automatically preset field preferences.
• Added a notice to ask the admin to set the translation mode for his existing field groups on plugin activation.
• Added support for the new field group translation modes in local JSON files.
• Added the option for disabling WPML’s Advanced Translation Editor for posts with groups that have different fields per language.
• Added an automatic switch that enables or disables the repeater field sync feature based on the selected field group mode.
• Added the possibility to translate field group labels and field choices using WPML String Translation.
• Added a feature that includes untranslated field group strings in the first post translation job.
• Added a feature that locks field preferences on the WPML Settings page if they’re controlled by the field group mode.
• Added a check that locks ACF’s “acf-field-group” custom post type when it’s “not translatable” (recommended) and is not unlocked.
• Added a recommendation to make the “acf-field-group” custom post type not translatable if it already is set as translatable and not all groups are translated.
• Added a feature that makes sure that fields set to “Copy” are now pre-filled when creating a new translation with the native WordPress editor.
• Fields set to “Copy” are now read-only when editing a post translation using the native WordPress editor.
• Added a new section for the repeater synchronisation checkbox in the field group settings.

Fixes​

• Once a custom field translation preference is changed, WPML will recalculate the translation status for all posts using this field.
• Fixed a bug related to synchronizing repeaters on the Options page when using checkboxes inside repeaters.
• Fixed a bug related to synchronizing repeaters on options pages.
• Fixed an issue with the Options pages when language code has more than two characters like “pt-br”, for example.
• Fixed a bug that occurred when saving options and having several admin tabs open in different languages.
• Fixed a bug that occurred when single value in a gallery caused data to be corrupted in the translated languages for which the value should be copied.
• Fixed a bug where fields would not render on the front-end for translated post if the original post does not have any fields.
• Fixed an offset warning and an error on the ACF options page when there was only one language.

Misc​

• Handled PHP 8.1 deprecation notices.
• Added interface translations for strings in German, Spanish, Italian, French, Dutch, Polish, Swedish, Japanese, Hebrew, Greek, Chinese, Portuguese.
• Changed the icon and tooltip text on the Field Group edit screen.
• Removed the tip to set the repeater field as “copy-once”.
• Improved the description of the auto-scanning feature for ACF JSON field groups.
• [Expert Mode] When a field’s custom preference is not set, it will be set as “Do not translate” by default.
• Fixed the ACF Multilingual activation to make sure it is not displayed if ACF is inactive.