View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
105 | Composr | core_permission_management | public | 2010-04-06 15:15 | 2022-08-15 02:07 |
Reporter | Chris Graham | Assigned To | Guest | ||
Priority | normal | Severity | feature | ||
Status | new | Resolution | open | ||
Summary | 105: Remove concept of a forum moderator | ||||
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] | ||||
Tags | Risk: Large database change | ||||
Attach Tags | |||||
Time estimation (hours) | 10 | ||||
Sponsorship open | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2016-06-08 00:15 | Chris Graham | Tag Renamed | Large database change => Risk: Large database change |
2022-08-15 02:07 | Chris Graham | Relationship added | related to 1791 |