#2928 - Refine the validation tool functionality for forums, topics, and posts
-
By PDStig
- Added
- 6 views
| Identifier | #2928 |
|---|---|
| Issue type | Trivial issue (does not break functionality) |
| Title | Refine the validation tool functionality for forums, topics, and posts |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | cns_forum |
| 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. |
| Steps to reproduce | |
| Related to | #2886 - Option for users to mark new content for moderator approval |
| 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
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.