Home › Forums › Bug Reports › ACF Clone field in group not importing properly › Reply To: ACF Clone field in group not importing properly
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.
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!
ACF wouldn’t be so widely used in WordPress if it didn’t have some pretty amazing capabilities. In this article, we look at a few of the features we’ll discuss during “7 things you didn’t know you could do with ACF” at #WPEDecode later this month. https://t.co/5lnsTxp81j pic.twitter.com/Yf0ThPG1QG— Advanced Custom Fields (@wp_acf) March 16, 2023
© 2023 Advanced Custom Fields.