I’ve used this featured but I’m not 100% satisfied with this feature. It does help with binding field logic to a theme, but it does not help with version control and local development. This feature is a one way export. Once it has been exported and transfered to another enviroment, I can not easily change or extend these settings. Also, this method doesn’t work well with merging two different setups that has been developed separatly.
Maybe an alternative option to store all, or maybe just a fieldset’s, structure as a json document (like composer) in the active theme, instead of the database.
Viewing 1 post (of 1 total)
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users