Hello,
Thanks for the feedback!
In fact, the latest ACF 6.3.2 update released yesterday evening includes quite some changes to the ajax verification logic, and I wasn’t aware of the update until it was released.
Recent reports shows this patch cause issues with the Clone Field with ACF Extended (you can’t select any Field to clone in the ACF Field Group UI), and the Form UI which cannot find Field Groups/Fields.
I’m currently working on a compatibility patch. In the meantime, you can either downgrade to the ACF 6.3.1.2 version to fix the issue. Or, if you want to stay on the latest version, as it includes security fixes, here are quickfixes you can add to your?functions.php?file:
// ACFE 0.9.0.5: Fix compatibility with clone on ACF 6.3.2
add_action('acf/init', 'my_acfe_fix_clone', 100);
function my_acfe_fix_clone(){
$instance = acf_get_instance('acfe_field_clone');
remove_action('wp_ajax_acf/fields/clone/query', array($instance, 'ajax_query'), 5);
}
// ACFE 0.9.0.5: Fix compatibility with fields on ACF 6.3.2
add_action('acf/input/admin_print_footer_scripts', 'my_acfe_fix_form_fields');
function my_acfe_fix_form_fields(){
?>
<script>
(function($){
if(typeof acf === 'undefined' || typeof acfe === 'undefined'){
return;
}
new acf.Model({
filters: {
'select2_ajax_data/action=acfe/form/map_field_groups_ajax': 'ajaxData',
'select2_ajax_data/action=acfe/form/map_field_ajax': 'ajaxData',
'select2_ajax_data/action=acf/fields/acfe_taxonomy_terms/query': 'ajaxData',
},
ajaxData: function(ajaxData, data, $el, field, select){
ajaxData.nonce = acf.get('nonce');
return ajaxData;
},
});
})(jQuery);
</script>
<?php
}
Please note there might be other ajax related issues until the full compatibility patch is up. I can’t list them all here at the moment.
Also as a side note, the security fixes added in latest ACF patch are really minor issues, but I can understand you would want to keep using the latest version.
Thanks!
Regards.
