[ad_1]
The security log will only appear when access is blocked by this plugin. If something else prevents your access, you usually won’t get the log. For example, if your admin menu is correctly configured to allow access, but another plugin has its own custom access restrictions (separate from the admin menu), you can still be blocked, and you won’t see the security log.
In general, if the log is enabled but you don’t see it on the “access denied” page, that usually means that the problem is not in the admin menu configuration.
I was worried that might be the case. Thank you for your response.
Would it be possible to still see the reason that access was denied though?
This might be out of scope of the current thread topic, but most if not all of my issues have been associated with restricting access to Divi setting pages.
That would be convenient, but I can’t think of a reliable way to achieve that, not even with custom code. While it’s relatively straightforward to check if a user or role has the capability associated with a menu item, plugin/theme developers can also choose to implement arbitrarily complex access requirements, and there’s no unifying standard. You would need something that can read plugin source code and figure out what’s going on, which may require human-level AI.