Conflict with Advanced Custom Fields Pro
-
Definitely appears to be a conflict between SNAP and Advanced Custom Fields, which causes ACF fields not to be saved when a post is published.
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 actually being published to Facebook. The fields in question include standard text fields, so nothing special.
If I deactivate SNAP, ACF goes back to working correctly. So SNAP is definitely the culprit.
From tracing through the code, it appears that 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.
Any ideas, please?
- The topic ‘Conflict with Advanced Custom Fields Pro’ is closed to new replies.