Hi Elliot,
Looks like this solution has stopped working. Is there a new way to do this?
thanks,
Scott
Any way to move the functionality for this in the to-do list from “Future” and into the next iteration?
The threads in the “Future” list:
Add constant for auto export – …http://support.advancedcustomfields.com/discussion/5453/add-support-for-auto-exporting-fields
Load and save to PHP – …http://support.advancedcustomfields.com/discussion/5495/exported-php-settings-override-database-based-settings
(and of course this thread)
I would personally prefer it to be a per-fields-set option rather than a global option. But will take what I can get!
If it helps – you could even make this another paid-for add-on as it’s certainly often going to be corporate/large-scale level users who need a feature like this. What’s another $25 to the cost of doing business?
thanks,
Scott
Hi Elliot,
I’d like to second this request. It would allow me to continue working on the auto-export plugin I mentioned here:
http://old.support.advancedcustomfields.com/discussion/5495/exported-php-settings-override-database-based-settings
I’d say that rather than use a global override that it would work better as a checkbox inside of an ACF field group which would allow that one field group to choose to either use the database or the php version.
Regardless, this would be an excellent feature for large-scale sites with multiple environments.
thanks,
Scott
Absolutely perfect solution. I had no desire to update core, just didn’t know how to explain the solution I needed :-).
As always, thanks a million Elliot!
-Scott
