[Resolved] ACFML2 Causing issues with some cloned fields

here's the code:

<?php
$max_per_row = get_sub_field("max_buttons_per_row");
$max_per_row_tab = get_sub_field("max_buttons_per_row_tablet");
$max_per_row_mob = get_sub_field("max_buttons_per_row_mobile");
$align = get_sub_field("button_alignment");
$row_width = ( get_sub_field("row_width") == "full-width") ? 12 : 6 ;
?>

<?php if( have_rows( 'button_group_repeater' ) ): ?>
<div class="inner-content grid-x align-center">
<div class="large-<?php echo $row_width; ?> cell">
<div class="grid-x grid-margin-x small-up-<?php echo $max_per_row_mobile; ?> medium-up-<?php echo $max_per_row_tab; ?> large-up-<?php echo $max_per_row; ?> <?php echo $align; ?>" data-equalizer >

<?php while( have_rows('button_group_repeater') ): the_row(); ?>

<div class="cell ">

<?php get_template_part( 'parts/content-blocks/content-types/content-type', 'button' ); ?>

</div>

<?php endwhile; ?>

</div>
</div>
</div>

<?php endif; ?>

Ok this is interesting.

I changed those 3 fields:
Content Type: Button Group — To Clone
Block: Button Group — To Clone
Global Content Blocks
from
GROUP back to SEAMLESS

var_dump($repeater);
returned:
bool(false)

Then I disabled "Advanced Custom Fields Multilingual" plugin
and
var_dump($repeater);
returned:
array of button information.

The plugin is definitely part of the issue here. I've left the var_dump() on the homepage under the her image. you'll see it's returning bool(false). I reverted your settings back to "Group" and enabled your plugin. You can turn it off and change the setting back to "Seamless" to see it recognize the repeater values.

hidden link

I think we're at the point where we are ready do move away from WPML and use a different solution. This breaking change in the plugin has been a massive waste of resources and expensive.

Can you provide instructions to uninstall and remove all WPML data.

Thank you.

We decided that there are too many buttons throughout the site to have to go around and rebuild this. While we appreciate you may've found a way to resolve this, renaming the button_group field is not a great solution for us. This appears to be a major breaking change. We have opted to move away from WPML.

Thanks for your time.