Our team is having a problem syncing ACF fields with git. It goes like this:
1. User A creates new ACF fields in his local environment and then syncs them up from his local branch to master branch. In WP backend of the staging site on the master branch the ACF tools show that new fields have been discovered and user A syncs them to the DB.
2. User B branches of master to his new feature branch and for some reason the sync button doesn’t appear on his local WP installation. (we noticed that this happens when the feature branch of user B is created right after the master branch was appended by user A) User B checks the json file and sees new ACFs that are located there. If user B increases the number in the “modified” field of the JSON file – the sync button will appear. But if user B will move forward without syncing the JSON file and create new ACFs, he will silently overwrite the entire file without any conflicts from git.
Due to this behavior we were constantly overwriting each others work, until we tested our the sync process. We’re using lates version of ACF 5.9.1 and the latest version of WP 5.5.2
Does anyone have any idea how this can be fixed?
Viewing 1 post (of 1 total)
You must be logged in to reply to this topic.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users