Changes between Initial Version and Version 1 of Ticket #6506, comment 8
- Timestamp:
- 06/15/2015 07:14:08 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #6506, comment 8
initial v1 5 5 The current capability check only ever happens if a non-capable member manually attempts to visit `/members/themself/messages/notices/` which is already not hooked into `bp_screens` if the member does not have the `bp_moderate` capability. 6 6 7 This means that if a developer is incorrectly using `bp_has_message_threads()` like you're stating, this bit of code only actually help protect them from themselves when a non-capable member visits `/notices` having core-hacked `BP_Messages_Component::setup_nav()` to remove the capability check in `setup_nav()`.7 This means that if a developer is incorrectly using `bp_has_message_threads()` like you're stating, this bit of code only actually helps protect them from themselves when a logged-in non-capable member visits `themself/messages/notices` having core-hacked `BP_Messages_Component::setup_nav()` to remove the capability check.