#105 - Remove concept of a forum moderator
| Identifier | #105 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Remove concept of a forum moderator |
| Status | Open |
| Tags |
Risk: Large database change (custom) |
| Handling member | Deleted |
| Addon | core_permission_management |
| Description | Conversr has a concept of the forum moderator group, activated via presence of the permission edit_midrange_content and applied by the cns_may_moderate_forum function. Use of this permission in this way is a proxy to our original way of handling moderation, which worked via an access-levels system (which got removed in v4 in favour of a more uniform Composr-wide system of overridable specific permissions).
Ideally we should not pass all moderation control through a single permission. Instead we should implement a few of them: perform_markup_validation_by_default [true for staff] perform_keyword_check [true for staff] move [true for staff] set_topic_open_state [true for staff] set_topic_pin_state [true for staff] set_topic_cascade_state \true for staff] set_own_topic_open_state [true for staff] set_own_topic_pin_state [true for staff] set_own_topic_cascade_state [true for staff] unset_topic_open_state [true for staff] unset_topic_pin_state [true for staff] unset_topic_cascade_state [true for staff] unset_own_topic_open_state [true for staff] unset_own_topic_pin_state [true for staff] unset_own_topic_cascade_state [true for staff] post_in_closed_topic [true for staff] attach_poll_to_any_topic [true for staff] emphasise_post [true for staff] |
| Steps to reproduce | |
| Related to | #1791 - Split up assume_any_member/member_maintenance privileges |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
There have been no comments yet