Almost five years later and John’s still helping people. Way to go!
Yep, seems to be working great right now! And even is automatically syncing, not sure how that’s happening.
So I used the code you provided in both the parent and child themes and then I’ve been making tweaks to the parent theme fields in the site with the parent theme, and then the child theme fields in one that has the child theme installed. Not exactly sure how it all works, but seems to be!
Thanks John!
Looks like it might have worked! Can’t delete them, just sync them, I think. The one thing that might be tough is not having automatic syncing though. As we develop new features with the sites, we’ll just have to release them manually in each one? Might be helpful to have more of an eye on it, but do you know if there are any plans for automatic syncing at some point?
Interesting! So it can work, that’s awesome.
Just to make sure then, right now I have one site that’s using the child theme and I’ve been building all of the custom fields on that one. So what I would do is start a new site with parent theme activated, import the parent theme fields there, sync it with JSON, then delete the parent theme fields on the child theme site so that they only show up from the JSON?
As always, thanks so much John!
That was it! Had to update ACF first. Thanks John!
Super helpful.
I’ll have to look into the individual fields then, sounds like the best option!
Thanks again, John. Your epic avatar suits you.
John, thanks so much for taking the time to write all that out. Here’s some follow-up:
1. That’s all really helpful information that I’ll copy down. But for this case, the goal is to have multiple places of editing the same value. So that if you were to save changes in one spot of the backend, it would display that change in the other spot in the backend. Whichever gets saved will just show up in the other. So you said “the field keys will be different and this can cause problems if the data in the fields is different” — can you expand on that?
2. Awesome, that’s exactly what I needed
3. I’ll look more into the Local JSON resource, thanks! But is there not a way to load a field group to an acf_form by its name or some other identifier other than ID? Right now I’m using the JSON to spread the custom fields themselves across the sites using that theme but when I created a new multisite site, the IDs were all different.
Again, thanks for your help!
Just found the admin_head action, so cross off #2!
Yeah definitely over my head. I think the simplest solution will be to just make a radio button field and drop like 5 or so options in there—when they select an image it drops the text into the page itself.
Thanks for taking the time, John!
Beau
Thanks John!
Yeah that came to mind. So I’d want to then somehow make folders within the media uploader of the preloaded options.
What if those photos were all in the theme folder itself? Is there a way to automatically grab any images in that folder and make them selectable?
If not, I might just keep it at a smaller number of options and do radio buttons with images.
acf-export-2....zip