I have a custom JS file that handles some user actions -- namely, changing a user's role. This has worked well for a couple of years, but with our necessary update to PHP 8, we now get this error when running either `update_user_meta()` or `wp_delete user()`, we're not sure which. It seems that the Access `save_user_options` hook gets run on one of these operations, and my guess is since we're not actually on a profile page, IS_PROFILE_PAGE is not defined, and in PHP 8, that now throws a fatal error.
I'm not going to dwell on the exact steps to reproduce this, as it's a clear weakness in the code that makes it vulnerable to triggering such an error (in the context of more recent PHP versions which are much less forgiving).
So I've escalated this directly to the developers, it's a very simple fix to check if the constant is defined first.
Although simple, we just released an Access update, and I'm not sure when the next one will be, so you might want to make such an edit in the plugin code yourself.
Thanks so much for the reply, and thanks for the heads up about the unknown date of the next release. I'll add a patch to check for the constant on our end for now, and will look forward to the next release!