Does we need to declare define(‘ACF_EARLY_ACCESS’, ‘5’) in all installs to make ACF/ ACF PRO work with all latest versions/ updates?
I’m certainly not the authority of such a thing but this sounds like a feature for when Advanced Custom Fields 5 first hit the shelves – that’s what it seems like from the blog post. If you’ve been getting regular updates – ACF is a few versions into 5 and it’s definitely stable enough so it’s probably unnecessary to have it at this point.
The define statement causes ACF to look for and get updates from the ACF server instead of the WP repo. Once you start using it you need to keep it until the free version of ACF 5 is released to the WP repo.
