View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002928 | Composr | cns_forum | public | 2016-11-17 04:25 | 2016-11-17 20:17 |
| Reporter | Patrick Schmalstig | Assigned To | Chris Graham | ||
| Severity | @40@ | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0002928: Refine the validation tool functionality for forums, topics, and posts | ||||
| Description | The validation tool for forums, topics, and posts is inconsistent with the validation functionality of the rest of Composr CMS. For non-forum areas, non-validation means the content will not get listed, syndicated, and so on until the content has been validated (except to those with permission to see non-validated content). However, for forums, even topics/posts/etc marked for staff validation get syndicated and listed in blocks etc. before they're even approved. I think this is a big moderation loophole because what if, for example, someone submits something against the rules (especially in the title)? People can still see the title etc. in blocks and in the activity feed prior to staff approval. So it becomes a big problem. Users also get the assumption that since it's listed, it must be open for access. But it's not (unless they have permission to see non-validated content, of course); they get the warning about not having permission. | ||||
| Tags | No tags attached. | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| related to | 0002886 | closed | Chris Graham | Option for users to mark new content for moderator approval |
|
|
I think you've found a wider oversight here. |
|
|
What do you mean specifically Chris? |
|
|
Ok, I was mistaken. I thought blocks weren't considering validation privilege and caching separately. But they cache separately by group which achieves this. However, this issue 2 separate issues: 1) A bug, topic validation should be considered by the blocks. Fixed now. 2) Behaviour that the core design of the activity feed doesn't include (the activity is the submission of the content, so it is just listed verbatim) - it's not an activity-after-moderation system. This is the case for any content type, not just topics. I'll create a separate issue for this - I do think it would be best corrected, but it's not at all trivial because activities are log entries and therefore we'd need to do some juggling to write those out only when validation has happened, or make them check validated status when displaying, or copy and maintain a validation flag into that table. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-11-17 04:25 | Patrick Schmalstig | New Issue | |
| 2016-11-17 04:28 | Patrick Schmalstig | Relationship added | related to 0002886 |
| 2016-11-17 04:29 | Patrick Schmalstig | Summary | Refine the verification tool functionality for forums, topics, and posts => Refine the validation tool functionality for forums, topics, and posts |
| 2016-11-17 04:29 | Patrick Schmalstig | Description Updated | View Revisions |
| 2016-11-17 12:45 | Chris Graham | Note Added: 0004551 | |
| 2016-11-17 17:10 | Patrick Schmalstig | Note Added: 0004552 | |
| 2016-11-17 20:17 | Chris Graham | Note Added: 0004555 | |
| 2016-11-17 20:17 | Chris Graham | Status | non-assigned => resolved |
| 2016-11-17 20:17 | Chris Graham | Resolution | open => fixed |
| 2016-11-17 20:17 | Chris Graham | Assigned To | => Chris Graham |
