Reply To: Strange sync bug

• dylanfisher

• January 8, 2015 at 6:00 pm

I’ve made this mistake a few times. If you check your acf-json directory into version control and make field edits locally, when you deploy to production the fields will show up correctly and all is good.

However, if in the future you sync your local database with the db from production the ACF json fields will no longer exist in the database.

This makes sense but isn’t immediately obvious when the local acf-json still shows the fields as appearing when you edit posts, but not when you edit the custom fields.

I couldn’t get ACF’s default sync (http://www.advancedcustomfields.com/blog/acf-pro-v5-1-5-update/) or the FreshFlesh acf-sync plugin to work with a manual json sync, but this plugin did seem to work, though I haven’t thoroughly checked to make sure all the data is intact. https://wordpress.org/plugins/acf-pro-sync/