Thanks John for the detailed response!
Method #1 is pretty much what I was anticipating would need to be done and is manageable.
The biggest thing I was wondering is if there’s a way to read the actual values back from the database and populate ACF with them in the admin interface when the user visits the options page next time?
Exactly like save_post but on the other end of the edit process.
If we have the normal settings pages disabled I don’t anticipate that there’d be a situation in which the two got out of sync, but in the event that a plugin or some other piece of the system would update the value of the options I’d prefer, for completeness, to make sure that new value is represented again in the ACF options page when opened.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!