View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003278 | Composr | cns_warnings | public | 2017-05-07 07:44 | 2020-03-02 18:38 |
| Reporter | Adam Edington | Assigned To | Patrick Schmalstig | ||
| Severity | Minor-bug | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0003278: Make warnings UI intuitive for the member being warned | ||||
| Description | The display of warnings on the profile could be more informative (with regard to length of silence from forum or thread and duration of ban). The main issue is that the reason for the warning links to the post that the user was warned for, rather than to the explanation which should provide the link to the offending content. | ||||
| Tags | Roadmap: v11 | ||||
| Time estimation (hours) | 4 | ||||
| Sponsorship open | |||||
|
|
Also noticed I got emails about the warnings but the inbox didn't change state to indicate that, maybe because I warned myself. |
|
|
If you send a notification to yourself I think it would auto mark read. "The main issue is that the reason for the warning links to the post the user was warned for rather than the explanation providing a link to the offending content." This sentence doesn't make sense to me. Aren't "reason"/"explanation" and "post"/"offending content" synonyms? |
|
|
The reason appears under the warning tab, the email shows the post and doesn't show the warning, infraction details. |
|
|
For this, would you want me to do similar to how I did it when I used to run my former website? I refactored the warning module and made hooks for each type of punitive action. Each hook had a function for applying the action, reversing the action, the form field to use on the warning form, and what text to use on the warnings tab and in the sent private message. |
|
|
Sounds good :)! The main thing is for it to be user-friendly for everyone involved. I think others than me are likely best positioned to determine what that means. I would add though that it does need to be clear what text is only for staff to see and what is for the warned member to see. I would also say it needs to not become any harder to warn a member. |
|
|
Noted. Functionally from a UI perspective, it will work and look the same (aside from adding on this issue of warning messages including text explaining the punitive actions taken). Only difference is instead of everything hard-coded in the module, each type of punitive action and its text will be a hook. This also allows for extending the warnings module easily in the future for other types of punitive actions based on what modules are installed if desired. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-05-07 07:44 | Adam Edington | New Issue | |
| 2017-05-07 07:54 | Adam Edington | Note Added: 0005086 | |
| 2017-05-07 12:51 | Chris Graham | Time estimation (hours) | => 4 |
| 2017-05-07 12:51 | Chris Graham | Summary | Warning issues => Make warnings UI for intuitive for the members being warned |
| 2017-05-07 12:51 | Chris Graham | Description Updated | View Revisions |
| 2017-05-07 12:52 | Chris Graham | Note Added: 0005087 | |
| 2017-05-07 14:12 | Adam Edington | Note Added: 0005088 | |
| 2019-06-27 17:57 | Chris Graham | Tag Attached: Roadmap: v11 | |
| 2019-07-12 21:21 | Chris Graham | Assigned To | => Patrick Schmalstig |
| 2019-07-12 21:21 | Chris Graham | Status | non-assigned => assigned |
| 2019-12-24 18:20 | Patrick Schmalstig | Note Added: 0006255 | |
| 2019-12-24 18:50 | Chris Graham | Note Added: 0006259 | |
| 2019-12-24 18:56 | Patrick Schmalstig | Note Added: 0006260 | |
| 2019-12-24 18:59 | Patrick Schmalstig | Note Edited: 0006260 | View Revisions |
| 2020-01-23 17:35 | Adam Edington | Summary | Make warnings UI for intuitive for the members being warned => Make warnings UI intuitive for the member being warned |
| 2020-01-23 17:35 | Adam Edington | Description Updated | View Revisions |
| 2020-03-02 18:38 | Patrick Schmalstig | Status | assigned => resolved |
| 2020-03-02 18:38 | Patrick Schmalstig | Resolution | open => fixed |
