View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005279 | Composr | cns_warnings | public | 2023-02-11 04:43 | 2023-02-11 19:39 |
| Reporter | Patrick Schmalstig | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0005279: Add future submission ban to punitive actions | ||||
| Description | Staff have the ability to ban a member's ability to submit content in the future via investigate user. I think this would be a useful punitive action tick when warning a member. Make sure this also adds proper text when "Include punitive actions in message" is ticked. | ||||
| Tags | No tags attached. | ||||
| Time estimation (hours) | 0.5 | ||||
| Sponsorship open | |||||
|
|
For clarity, Patrick is talking about inserting a record into the "usersubmitban_member" table, which is the forum-agnostic way of banning member submissions. The has_submit_permission function checks this in addition to regular group privileges. (There is no way to ban submissions from particular IPs, we used to but it was changed to a complete IP ban system because trying to have anything fine-grained on the IP level is pointless given how easy it is to change IPs) For Conversr (i.e. if we aren't being forum-agnostic), typically preventing a member from making member submissions might normally be achieved by putting someone on probation instead. It makes sense to allow everything from the punish form though. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-02-11 04:43 | Patrick Schmalstig | New Issue | |
| 2023-02-11 19:39 | Chris Graham | Note Added: 0007903 |
