To verify if you have the same cause of this problem as me:
- go to the ‘edit page’ screen
- open your browser’s developer console
- in the HTML of the page, search for ‘_acf_nonce’
If it’s not present, you can try to following stop gap fix, which seems to have worked for me:
Edit wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-post.php and in the function save_post($post_id, $post) comment out the following three lines:
if( !acf_verify_nonce('post') ) {
return $post_id;
}
Warning: I’m not entirely sure what function nonce plays in ACF, or whether it’s lack is part of a larger bug. Use this workaround at your own risk.
Hello,
I’ve encountered this issue this week with the following setup:
– WordPress: 4.9.8
– Gutenberg (as a plugin): 3.9.0
– ACF: 5.8.5
I investigated a bit, comparing it to my local installation where I did not update ACF from 5.7.7 to 5.8.5.
What I was able to find is that the problem revolves around the function ‘acf_verify_nonce()’, which on 5.8.5 returns false and stops the saving pipeline. What’s more, the hidden input field ‘_acf_nonce’ is not rendered on the page on which I’m editing the ACF fields.
I see that between versions 5.7.7 and 5.8.5 there are changes in how this works in the plugin – for example, rendering of the field ‘_acf_nonce’ moved from ‘includes/forms/form-gutenberg.php’ to ‘includes/admin/admin-tools.php’ and ‘pro/admin/views/html-settings-updates.php’ That makes me think it’s quite possible it’s a bug in ACF that’s causing this.
Thanks,
Jan
