WordPress.org

Make WordPress Core

Opened 7 years ago

Closed 6 years ago

#3870 closed enhancement (invalid)

Better way of removing spam

Reported by: markjaquith Owned by:
Milestone: Priority: low
Severity: normal Version: 2.1
Component: Administration Keywords: spam ajax moderation wp-admin
Focuses: Cc:

Description

We have several wp-admin comment views, but none that is ideal for despamming.

Rundown of the current methods:

  • going backwards through your approved comments, marking spam as you find it
  • searching through bulk moderation on known spam keywords you've seen turn up

The second method is great for huge attacks. The first method has issues.

  • you don't know which comments are new, so as you page backwards chronologically, there isn't a good stopping point
  • it is slow, waiting for the AJAX request and animation
  • #3829 : as you mark comments as spam, new ones don't fill the page, so when you move to the next page, you skip over them.

Here is my idea:

  • new view: Despam
  • forward chronological view (oldest first)
  • compact display, for easy scrolling
  • radio buttons: Approve, Delete, Spam
  • "Process »" button at bottom
  • WordPress option that stores the timestamp of the most-recent comment on the page, every time the "Process" button is pressed

As you can tell, it's the last one that really sells it. That is what we use to determine the oldest comment shown when a user views the "Despam" page.

This would allow for a nice workflow:

  1. See: "Unprocessed comments (106)"
  2. Click
  3. Scroll through 50 comments on a page, with one click to mark as spam or delete (and no AJAX wait)
  4. Click "Process" when at the bottom of the page
  5. You get the next most recent page of comments, and will never again see the previous page

This would be very much like the Mass Edit Mode, except that you'd have radio buttons for spam/delete choices, it would be chronological (instead of reverse chronological), and it'd remember which comments you've processed and which you haven't, by storing that timestamp.

So what do you think? Good core addition, or should I write it as a plugin?

Change History (6)

comment:1 markjaquith7 years ago

  • Keywords spam ajax moderation wp-admin added
  • Type changed from defect to enhancement

comment:2 Viper007Bond7 years ago

So somewhat like SK2's tabs?

comment:3 markjaquith7 years ago

Yeah, SK2 had something similar from what I remember (I haven't used it in a while).

comment:4 foolswisdom7 years ago

  • Milestone changed from 2.2 to 2.3

comment:5 foolswisdom7 years ago

  • Milestone changed from 2.3 to 2.5 (future)

comment:6 pishmishy6 years ago

  • Milestone 2.6 deleted
  • Resolution set to invalid
  • Status changed from new to closed

I'm going to close as invalid for now as the interface has changed greatly between the last report and now. If you still have concerns please could you run through the current interface and let us know how you think it could be improved.

Note: See TracTickets for help on using tickets.