An action may define its own access callback, e.g.: in CancelUserAction, it checks that the current user account has access to delete user entities.
Before executing Actions, the ActionProcessor checks the access callback.
Currently, if access is denied (forbidden) then Views Bulk Operations simply displays Access denied.
When returning an "Access Forbidden" (or Neutral) result, it is possible to specify a reason. This reason may help the user to understand why access was forbidden for them. For example, the core File entity can only be updated or deleted by the file owner.
It would be helpful to expose the reason to the person operating Views Bulk Operations, if the reason exists.
Modify the Access denied message to Access denied: @reason if the reason exists and is not empty.
None.
None.
None.
Fixed
4.1
Core
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.