I get this issue now and again and usually comes from conflicting naming convention on your fields or if you have some field groups registered in both json and in the DB that are sharing field keys for some reason (human error)
Welcome
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.
