#5792 - Add privilege and access restrictions as punitive action
-
By PDStig
- Added
- 1 view
| Identifier | #5792 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Add privilege and access restrictions as punitive action |
| Status | Open |
| Tags |
Roadmap: Sponsorship (custom) |
| Handling member | Deleted |
| Version | 11 alpha4 |
| Addon | cns_warnings |
| Description | Add a cns_warnings hook allowing to define multiple privilege and/or access restrictions as part of a punitive action. This will be complicated to implement on a UI standpoint, but here's my idea (with some JavaScript involved): * The UI field itself is a textarea where you put in XML. * Above the field are JavaScript-controlled inputs. * The first line has a searchable dropdown of privileges which can be restricted, plus a date field for "until", and an "Add" button. * The second line has inputs to define access restrictions on zones, categories, and/or pages... plus an "until" date field and an "Add" button. * When an Add button is clicked, JavaScript will populate a new XML entity for the chosen options in the primary UI field and then clear out the inputs (so another one can be added). On actualisation, the XML is parsed accordingly, records added into the appropriate tables, and a punitive_action record also added referencing the relevant privilege / access record. We will also need to add "the_value" to all the member access tables so we can define a negative (denied) access record (like we do for privileges). And this takes priority if a similar record has a positive (granted) assertion. |
| Steps to reproduce | |
| Additional information | This will allow site administrators to add even more fine-grained control over how they moderate problematic users by restricting specific privileges or areas of the site which they've caused problems. It also allows us to say we now (sort-of) have a UI for these non-UI / rarely used tables. |
| 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
I wouldn't advise spending so much effort on making Composr do more and more, I think our effort should really on be making it more acceptable to a wider audience.
I'm going to switch this to Sponsorship. It is likely something I'll need personally for a v11 site WIP which I'll develop myself and maybe offer as a non-bundled addon.