Thanks John that tip solved it for me!
In my case I’m placing the field groups on my production server with the json files and generating them from my local install. This way the client can’t edit them and I manage the fields through a git repo.
So to get around this problem I’m making a copy of the field group json on site 12 (theme 12) and giving it to site 2 (theme 2). And then I change “active” to 0, this way the field is not displaying on site 2 but it is registered, and that seems to be enough for ACF to load the field contents from site 12 again! The one thing I have to aware of now is that I need to keep these files in sync when changing f.e. a label, and re-apply the “active” 0 difference.
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!