Thanks to everyone who posted here so we could narrow down the issue. While modifying the database directly does fix the problem, that presents a significant amount of risk and also would be incredibly time consuming if you’re managing a lot of websites.
Does anyone know if the ACF team is working on rolling out an official fix for this?
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users