@robjs yes “traditionally” it’s been robust… but Elliott sold the plugin this summer and I’m not really sure the new team can be trusted.
Apparently the somehow managed to ignore that people are using ACF to run mission critical settings : SEO, sitewide settings, plugin behavior settings, etc…
This change is really an example of “developer making what he thinks make sense (whereas I totally agree with @robwent comment on the dubious security issue it really created) without considering everything it can breaks”.
Personally if they screw up again, I’ll go somewhere else, despite having been a raving fan of Elliott’s plugin for years.
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!