Obviously this update has created a LOT of unintended issues. The current fix of updating documentation and providing a notification that covers a small portion of the troublesome use-cases is not enough. We need a comprehensive fix or a rollback of this so-called security “enhancement”.
Appreciate the response – we are well aware of a fix. The fix on hundreds of sites becomes less straightforward.
The main concern is this should not have happened in the first place.
ACF Pro has been a solid part of our enterprise website implementation strategy for many years. I understand that issues happen, but this seems to be the first of its kind that has effected us so extensively. Changes that break or eliminate previous functionality need to be well publicized and documented.
We are seeing this issue as well.
We run quite a few large multi-sites and after using switch_to_blog() the get_field(‘something’, ‘options’) returns null.
This is a big issue for us.
We found a temp fix, but this seems like a breaking change that needs to be rolled back.
Joe
