Home › Forums › Bug Reports › Database corruption after re-importing updated fieldgroup › Reply To: Database corruption after re-importing updated fieldgroup
I received this reply from [email protected]:
It is against standard practise to import a field group bearing the same name to a site holding a similar field group without deleting the original. This will normally cause duplication issues or possibly break configured fields. The best practise is to make use of the local JSON feature that identifies changes to a field group and synchronize the changes. Please take a look at the following resource page for more info on this: https://www.advancedcustomfields.com/resources/local-json/
I hope this info helps.
I hope it’s fine to simply remove the errant fieldgroup, make a new home page (or recover it from backup) and try again. I hope the entire db isn’t corrupt as a result of this.
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!
© 2023 Advanced Custom Fields.