XF 1.0 Managing Reported Content

Well, you wouldn't have seen it because it's only exposed to moderators. :)

Moderator actions are invoked using the moderator bar that is at the top of every page. In this post, I'll be focusing on how moderators handle reported content.

Handling a report is a little more formalized than you might be used to. Reports are now tracked with a status, so that it's clear what has happened and, if you leave a comment, why.

report-moderator-bar.webp


This bar makes it easy to see when you have tasks outstanding, but doesn't get in the way of reading the forum.

Inside the reported items section, you are presented with a list of outstanding (open or assigned) reports:

report-overview.webp


This does not just have to show a list of reported posts. It will show any type of comment, including profile posts or those added by add-ons. (Add-ons simply need to implement the basic reporting functionality and write some code to interact with this system.)

You can also use the button in the upper right to view recently closed reports.

Diving into the report listed, we see:

report-view.webp


This shows us the content that was reported and any comments that may have been made. If a piece of content is reported multiple times, only one report will be created but all the comments will be listed here. Each moderator that can manage the report has the option of making a comment as well. This is important when the type of action that needs to be taken isn't 100% clear. Note that users that report content can't see this page or any of the comments that are made; they are for internal use only.

To modify the report's status, you must first claim the report. This is mostly important if you have two or more people who might handle the report. Once one person claims the report, the other can see that it's being handled. After claiming the report, the view switches slightly:

report-assigned.webp


Now, using the "go to content" button (which opens in a new window), you can manage the content directly. After you have taken your course of action, you'd come back to the report view and change the status. After submitting, you're taken back to the report list view to move on to the next thing.

After a report has been closed, it can be re-opened if needed:

report-reopen-comments.webp


A moderator's comment will automatically re-open it. Another user reporting the content will cause it to be re-opened; however, all of the comments will still be available to help you decide whether an action is really necessary.

Added September 22nd:
Floris has put together a video showing how the system works. Thanks, Floris!
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
Hi Peggy,
Can you explain why?
Grover I can see where you're coming from, and honestly, I liked the report opening a thread as well.
This is just very streamlined and clean-cut. We haven't really had to discuss anything. It's mostly been Lawrence and I handling reports, and they've been fairly simple, so far.

Now, I will concede that it would be nice to integrate an option, that the person who takes the report can choose to open a thread for discussion if need be. But if it's just a clear cut case of needing to close a thread, or something else very cut & dry, then why a thread? Just take it, do it, and close it.
 
How hard would it be to code something where you get a box to pop-up at the top of the forum list for moderators/admins, that shows you which reports were recently opened or replied to, as an add-on?

This box wouldn't show up all the time, only if there's an unread message/comment.
 
Grover I can see where you're coming from, and honestly, I liked the report opening a thread as well.
This is just very streamlined and clean-cut. We haven't really had to discuss anything. It's mostly been Lawrence and I handling reports, and they've been fairly simple, so far.

Now, I will concede that it would be nice to integrate an option, that the person who takes the report can choose to open a thread for discussion if need be. But if it's just a clear cut case of needing to close a thread, or something else very cut & dry, then why a thread? Just take it, do it, and close it.

Maybe the report center could be extended to give an option to create a thread for that specific report?
 
IMO,

There is no reason Admins can not create a forum for moderators to discuss certain reported items. Of all the reported items you receive, how many warrant discussions beyond what the comments section provides. Problem members (those whose posts are reported regularly for flaming, for example), IMO would have their own thread created in the mod forum for mods to discuss, keep, and ref, but if someone's posts gets reported as spam (ie: selling shoes), why bother wasting a thread on them?

In our case, ALL reported items are discussed. Hence the need for inclusion into "What's New". A separate report center does nothing more than create an additional item that staff members need to "remember" to check. IPB currently does this and it's a pain in the ass.
 
In our case, ALL reported items are discussed. Hence the need for inclusion into "What's New". A separate report center does nothing more than create an additional item that staff members need to "remember" to check. IPB currently does this and it's a pain in the ass.
http://xenforo.com/community/find-new/threads

That would just be integrating more things that the moderators won't need. If they see a reported item in the bar they will check it.
 
In our case, ALL reported items are discussed. Hence the need for inclusion into "What's New". A separate report center does nothing more than create an additional item that staff members need to "remember" to check. IPB currently does this and it's a pain in the ass.
We don't have to 'remember' to check anything, with the report bar at the top of the page. Hard to overlook a red number.
 
You'd be surprised how often that top bar gets overlooked. We've been using IPB for 2 months now, and it's VERY easy to overlook items at the top of the forum. I don't think I have a single staff member that likes this system.
 
We don't have to 'remember' to check anything, with the report bar at the top of the page. Hard to overlook a red number.

very true, :)

And to add: when there is nothing left outstanding you do not notice the bar, but as soon as a report comes in, the red number catches your eye. You really can not miss anything. :)
 
Suggestion, which would hopefully satisfy most concerned:
  1. In addition to how it works now, have an admin option to create a thread for each ticket, and
  2. have the url to that thread in the ticket
  3. have the url to the ticket in the first post of the discussion thread
For simple things the created threads could be ignored, but they cause no harm

For the complicated things there could be a discussion in the thread, with the 'cliff notes' in the ticket.

edit: if there were an non-moderator advisory group set up, they could view and comment on all reported posts.

.
 
Perhaps, as a middle ground, make an optional "public" link for each ticket, where mod can send the said link to specific parties for commenting?

IE:
/reports/this-is-some-problem-post.123/public.deadbeef/
/reports/this-is-another-problem-post.234/public.1badf00d/

The "public" link have unique keys generated by system automatically (only upon request by staff), and is usable by any user group with permission to view public reports. When someone with appropriate permission uses the public link, they can only see and comment on the report. Because user permission system is used, user information are recognized, comments made can also be traced to specific users.
 
You'd be surprised how often that top bar gets overlooked. We've been using IPB for 2 months now, and it's VERY easy to overlook items at the top of the forum. I don't think I have a single staff member that likes this system.
That's because IPB is full of unneeded things up there that can get conjested. When the design is simple and clean, it's hard to miss a red number in a notice bubble :D
 
That's because IPB is full of unneeded things up there that can get conjested. When the design is simple and clean, it's hard to miss a red number in a notice bubble :D
Blame the style designer in such cases. Just because the default style is nice and clean, doesn't mean some crazy "designer" isn't going to come by and butcher it ;)
 
Most of the staff, myself included, uses "What's New" type link as our primary link to view new threads. As I tend to place that link where it does the most good for our users (right side of forum), any red number at the top is going to get overlooked. This is why it's imperative that new comments be included in the "What's New".

As I stated earlier, this type of system with its limitations is a pain and one that would immediately preclude me from using the software. It has TOO many limitations, and isn't flexible enough without me having to go in and modify core files. I was using vB from 2002 until recently, and now I'm having to modify core files with IPB. I'm getting tired of it, and shouldn't have to make those kinds of modifications for something like this.
 
Alerts have the same issue that would exist with the report center. If you don't select an alternative means of being notified (email, pop up, etc.), it's easily overlooked.
 
Most of the staff, myself included, uses "What's New" type link as our primary link to view new threads. As I tend to place that link where it does the most good for our users (right side of forum), any red number at the top is going to get overlooked. This is why it's imperative that new comments be included in the "What's New".

As I stated earlier, this type of system with its limitations is a pain and one that would immediately preclude me from using the software. It has TOO many limitations, and isn't flexible enough without me having to go in and modify core files. I was using vB from 2002 until recently, and now I'm having to modify core files with IPB. I'm getting tired of it, and shouldn't have to make those kinds of modifications for something like this.
But the What's new only works as good as you say it is because it has things people wants to see. New Topics. If we start filling it up wtih unwanted things like avatar changes and user signature changes for example then it will become obsolete like other things we bloat.
 
Suggestion, which would hopefully satisfy most concerned:
  1. In addition to how it works now, have an admin option to create a thread for each ticket, and
  2. have the url to that thread in the ticket
  3. have the url to the ticket in the first post of the discussion thread
For simple things the created threads could be ignored, but they cause no harm
For the complicated things there could be a discussion in the thread, with the 'cliff notes' in the ticket.

edit: if there were an non-moderator advisory group set up, they could view and comment on all reported posts.

.

Or.. A choice to have reported posts go to a staff forum and bypass the report center altogether. For those that like the report center, the option is there. For those of us that hate the report center, we can use vB's version of reported posts and have them go directly to a designated forum. By having them go to the forum, they're treated as posts/threads, they're searchable, and they show up in the recent post listings.

Seriously. The way IPB has implemented reported posts stinks. It's treated as a separate function from the forum software which I think detracts from the overall usefulness. And it's serious enough in my book that would preclude me from even considering using it.
 
But the What's new only works as good as you say it is because it has things people wants to see. New Topics. If we start filling it up wtih unwanted things like avatar changes and user signature changes for example then it will become obsolete like other things we bloat.

Huh?! Where did I state anything of the sort? A reported post results in a new thread. Therefore, it should appear when you select "What's New". A new reply to that report also results in a new post, which also should show up with "What's New". What you've alluded to in your post has absolutely nothing to do with my complaint on how the system will work.
 
Top Bottom