Home › Forums › ACF PRO › ACF JSON sync IDs different › Reply To: ACF JSON sync IDs different
Thank you, I understand the reasons behind it. But I’m wondering if maybe location options should be handled differently, maybe only using the JSON as a default unless a database value is present or something.
I guess right now I would have to create an options page, with a Post Object field that would allow a user to select a post/page, and then create a custom location filter that checks against that option value. That way the selected page could be different on development vs production.
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!
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 Privacy Policy. If you continue to use this site, you consent to our use of cookies.