Hi John, I really would appreciate a tool integrated into ACF which would import the PHP it generates. Sometimes the workflow makes changes to the PHP necessary and more convenient and we need to reflect the changes back into the GUI.
Since the PHP is one big file containing actual function calls to acf_add_local_field_group the reverse process would be easier if the PHP export was changed in a way so that including that export won’t be such a hassle due to the function calls.
Asked differently: How can we assure a versioned workflow with both GUI tool and PHP export if we don’t get changes to the PHP easily back into the GUI tool (which happens to live on a different machine, btw.) I’ve tried that with JSON but the synching was confusing somehow and also doing strange things when switching between branches which I can‘t line out precisely right now.
The reason we use the PHP is that I develop locally and the actual website is used by many editors and admin which should not fiddle with the field groups. So the ACF GUI on live is empty but changes made to the code on different developer machines should be able to integrated back into the dedicated building environments GUI.
