Hi @Elliot Condon,
This looks promising!
Am I correct that the JSON file is always in version control on the dev file, and thereby would be deployed to staging / production environment. On those environments ACF would read the JSON file and see that it has updated fields and show me the ability to sync. Is this correct? 🙂
Thanks for your reply,
Jeroen.
Hmm, that looks indeed like the same problem.
But using the field id is also not a great solution because they are also different in every environment. If they would be the same across every environment (dev, staging, production), because the field was editable for example, that would be less annoying. Right now I have a file where I define all constants based on the environment to map the field key. But I actually hate doing that 🙁
So, the text above hasn’t actually anything to do with the issue, but I think it explains why I don’t want to use the field id in get_field, for every field. So I hope it is possible to fix it in another way. It is particularly strange that it works after you update the post. So the relationship of the fields is still saved somewhere.
