Bug with ACF on save post

Could you please provide some more details? What type of fields? How exactly you save them? How to replicate it?

We just tried to install ACF add a text custom field and then publish a new post. That field was saved without any issues.

Definitely appears to be an issue here.

We’re using SNAP 4.1.1 and ACF Pro 5.6.7, with posts being published to Facebook. If we create and publish a new post, none of the ACF custom fields are stored; that appears to happen whether or not the post is being published to Facebook. The fields in question include standard text fields, so nothing special.

Curiously, the problem still occurs even if comment out these lines in SNAP:

add_action('edit_post', array($nxs_SNAP, 'NS_SNAP_SavePostMetaTags'));
    add_action('publish_post', array($nxs_SNAP, 'NS_SNAP_SavePostMetaTags'));
    add_action('save_post', array($nxs_SNAP, 'NS_SNAP_SavePostMetaTags'));

If I deactivate SNAP, however, ACF goes back to working correctly. So SNAP is definitely the culprit.

Any ideas, please?

I’ve done some further tracing through the code. The problem is in this function: nxs_removeAllWPQueryFilters which is called by nxs_snapPublishTo. Specifically, it’s with the removal of the posts_where filters which presumably ACF needs to be able to find its fields and save its data.

Can you look at that, please?