No issues with fields jumping out–it seems to work as desired. In my “simple” test I had cloned fields with and without the “seamless” selected and the “seamless” did not work before. Both work for me with this local-json approach — encouraging.
Yeah, I saw some stuff on the “disable syncing” and while I don’t think I will need it for this project, I can see how useful it would be for an environment where there are multiple people playing with this stuff.
Keep well
Hi @curious-toad
I posted a question on facebook acf group about this issue and got an interesting suggestion. It was to use the Local JSON feature (https://www.advancedcustomfields.com/resources/local-json/) – I didn’t know about it at all. What you do is create an acf-json file in your theme folder (there are hooks to change the location). Acf looks for the folder when a field group is updated/saved and puts a json copy of the group in the file. This means that the changes to acf field groups can now be migrated to other sites using normal file change procedures rather than database stuff. If that file present on your “destination” site, Acf will show that there are changed/new field groups available for “sync” and if you click sync on each group that needs a sync, you’re done. I tried this on the test environment I set up and it works well.
I wanted to check with you if you have tried this approach and if you still see issues if you have tried it? I am hesitant to change my workflows in case this has more problems. I plan on testing this on my “real” expanded setup when I get a chance and will let you know what I find.
Cheers
Yeah, I am not using flywheel, but what is now https://localwp.com/. It does not include the “advanced” tab that flywheel hosting provides. I can’t see any options in it that addresses caching.
I am running my tests on a mac using local by flywheel.
Some of my results after your previous input:
I created a simple setup with a field group with a couple of text fields (test group). Then two more field groups: “group that includes (seamless)” and “group that includes (not seamless)” with one text field followed by a flexible content field that contains one clone field which contains “test group”. These two groups that include have seamless and block settings on the clone field. When I export all the field groups and then import them on a different wordpress instance, I find that the “seamless” one does not work while the “block” one does work. I am attaching the json file.
I think this points to the “seamless” or not issue. If you want to, maybe trying it in the environment you said was working for you will give more understanding.
Cheers
That will be awesome. Thanks a lot
I just build a small sample group that includes a clone group and it worked. Maybe its only an issue with clone subfields inside flexible content fields??
Thanks very much for the detailed descriptions. I will work through them. So far I’ve gotten where I needed to by re entering everything and that’s quite a chore. I am intrigued by the seamless/block thing. Going to give that a shot.
Cheers
Hi there,
Did you figure this out> I have a similar situation. On import of field groups with clone fields the “contents” of the clone replaces the clone field.
Thanks
.