The following are not guaranteed plans and are subject to change.

I am getting close to finishing an update to the Compo.sr reported content addon. This update will  stop the use of the reported posts forum as it is not very convenient, especially since it doesn't allow direct communication with the reporter for, say, status updates and requests for more info.

Instead, it will streamline the process of content reporting by using support tickets instead. When someone reports a content on Composr, it will automatically create a support ticket between the user and staff for easy report management, communication, and staff assigning to reports.

In addition, the reported content addon is planned to replace the cns_reported_posts addon, making reported content the one and only reporting addon for all forms of content, including forums, forum topics, and forum posts,

The reported content addon will also feature something new in the update. When a user makes a report, the reported content module will make use of content_meta_aware hooks and make a copy of the content being reported inside the support ticket (AFTER the user has already submitted the form, opposed to putting the HTML inside the report box and making it easy for manipulation. Also tidies things up because the report form will be empty instead of filled with a bunch of stuff, making the user have to scroll to the bottom to add comments.). This is useful for several reasons:

• Maybe the user later changes the content and then staff have to intelligently find the problematic revision version
• Maybe you don't even have revisions enabled
• Maybe the content later gets deleted forever before you can get to it.

This will not, however, copy content such as actual download files, pictures, videos, etc. if the reported content was those items. Instead, the support ticket will show the download/image/video reported and link to it. If requested, I could try to make reported content copy such files as automatic attachments to a report.

The reported content addon will also automatically update a few templates so that report links can be displayed in the staff actions block at the bottom of content. It will also update Conversr if installed to make the report buttons use reported content addon opposed to cns_reported_posts addon, and will ask you to remove that addon prior to installing/updating.

Reported content will also use an overlay window opposed to going to another page.

Screenshots of this in action…

A demonstration of the first post in a support ticket created by the reported content addon when I reported a specific post in a forum topic:



Screenshot of reporting form (email address (when needed) and ticket category still to be added to the form. Also, not all of the text you see at the top will not be included by default. That's specific to my website's needs.)



Thoughts and feedback highly welcome

Report content module submitted for review. In addition to the above functionality, it will also allow for ticket category selection, anonymous reporting (logged in users), and reporting multiple times (in the event you reported once and then there's new development… will result in your additional reports being added as additional posts in the open support ticket instead of new support tickets getting created [if you have Conversr / cns forum installed… otherwise it will make new support tickets])

This sounds great.

Does this addon take permissions? ie you say it allows for anonymous reporting but can that be configured off if a user wants (i am just thinking it may attract abuse)

Duck said

This sounds great.

Does this addon take permissions? ie you say it allows for anonymous reporting but can that be configured off if a user wants (i am just thinking it may attract abuse)

From “Post #424”, 4th Apr 2016

The only permissions it takes at this time is the "can report" permission, which can be turned off for guests should you feel the vulnerability of abuse by guests. I'm not sure if it will work for this addon specifically though. I'll look into possibly adding another permission for anonymous reporting, as well as check on the current "can report" permission.

Maybe 'based off of a report against' should simply be 'for'. My contribution, unexciting as it is, short and sweet is hard to beat

KingBast said

Maybe 'based off of a report against' should simply be 'for'. My contribution, unexciting as it is, short and sweet is hard to beat

From “Post #501”, 14th Apr 2016

Saying 'for' makes it unclear that it was a report. So maybe I could say 'for report'.

Yeah, even better

For those of you who have been engaged on this thread, Chris is in the process of re-working the tickets system. The new tickets system will take over messaging, content reporting, and post reporting (aka. those three functionalities will no longer be separate but will instead utilize the tickets system; it is more stream-lined). cns_reported_posts will be deprecated when this happens since it'll be unified with content reporting.

There is no planned release for this. I just wanted to let you know of the progress. ^^