I’ll give a look, thank you!
However, isn’t the actual behavior a little weird?
I mean, if the “mismatch” is really the cause here, why AFC make the choice of “empty” rather than simply loading the database value as fallback?
Perhaps I’m missing a technical point here, but for now, it makes much more sense to me.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users