It seems i was able to identify the source of this issue for (at least) my situation. This pertains to multisite installations running ACF PRO 5.7.4. The bug lies in the fact that the update procedure erroneously checks the last blog in the multisite for update and license information, instead of the primary blog. The bug can be circumvented by either:
1) Activate ACF PRO and enter the license key on the last blog of the multisite, then run the updater.
2) Manually download and install ACF PRO 5.7.5 or newer from advancedcustomfields.com.
Any multisites running ACF PRO 5.7.4 may suffer from this issue, and will not be able to upgrade to newer versions without taking any of the two steps above. There should generally be no need to re-install WordPress or edit the database for this process.
Just for clarity’s sake… There may be an issue on multisite, but that seems to be a separate issue from what many of the rest of us are experiencing. At least in my case, there are about a half dozen single site installations that are unable to upgrade to 5.7.7 from 5.7.6.
On all the sites where I’ve had this issue the following always works
1) deactivate the ACF key
2) do into the db and delete the options _site_transient_update_plugins, _transient_acf_plugin_updates, _transient_timeout_acf_plugin_updates
3) reactivate my acf key
Actually, 1 & 3 have only been required once.
You could also try reinstalling WP as step 2.5, but if you try this I would do it then.
You must be logged in to reply to this topic.
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!