sissiB

Problem:
After updating to a version of ACFML greater than 2.0.5, you might find that on a secondary language page, many ACF fields (e.g., from an ACF options page) and unfilled fields in the backend are saved in the postmeta. This results in numerous empty fields and incorrect

get_field()

calls because the field is present with the post but has an empty array as a value. In the default language, these fields are not saved in the database.
Solution:
We recommend editing the file

\sitepress-multilingual-cms\classes\custom-field-translation\class-wpml-copy-once-custom-field.php

. On line 36, replace:

$custom_fields = get_post_meta( $post_id );

with:

$custom_fields = get_post_meta( $post_id );
$custom_fields_to_copy = array_intersect(array_keys((array) get_post_meta( $source_element_id )), $custom_fields_to_copy);

This change should resolve the issue. Additionally, ensure that each of your custom fields across different field groups has a unique Field Name to avoid translation and functionality issues. More details can be found in the WPML documentation.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, you can always contact our support at WPML support forum.