Make WordPress Core

Opened 8 years ago

Last modified 2 months ago

#6342 assigned defect (bug)

Rapidly spamming/deleting comments can break "infinite river" feature on comment moderation pages

Reported by: markjaquith Owned by:
Milestone: Awaiting Review Priority: low
Severity: minor Version: 2.5
Component: Comments Keywords: needs-patch
Focuses: administration Cc:


Comment moderation pages have an "infinite river" feature whereby when you remove one comment (spam/delete), it'll load a new one at the bottom. Unfortunately, it doesn't seem to catch up if you click more rapidly than about once every 2 or 3 seconds, and you'll "lose" comments. At the end, you may just have one comment that, when dealt with, will be replaced by only one comment. This may have to do with doubleclicking the "spam" link, or maybe clicking the "spam" link of the next comment before the river action has finished.

Change History (8)

#1 @mrmist
7 years ago

Does this bug still apply ?

#2 @markjaquith
6 years ago

  • Milestone changed from 2.9 to 3.0

Yes. This bug applies even more strongly now that there is keyboard-based moderation.

#3 @nacin
6 years ago

  • Keywords needs-patch added
  • Milestone changed from 3.0 to 3.1

#4 @nacin
5 years ago

  • Milestone changed from Awaiting Triage to Future Release

#5 @petervanderdoes
4 years ago

I believe the main problem of this bug has to do with your connection speed to the server.

When you click, the javascript hides the comment, the request (A) is send to the server.
You click another comment, the javascript hides the comment, the request (B) is send to the server.
But if you have a slow connection to the server, Request (A) might not have finished yet and is terminate. The server won't handle the actual spam/delete Request (A).
When you do this multiple times, the queue that has the overflow of comments is depleted and doesn't fill up because of the terminated requests.

#6 @helen
22 months ago

  • Component changed from Administration to Comments
  • Focuses administration added

#7 @wonderboymusic
3 months ago

  • Milestone changed from Future Release to 4.4
  • Owner changed from mdawaffe to wonderboymusic
  • Status changed from new to assigned

#8 @wonderboymusic
2 months ago

  • Milestone changed from 4.4 to Awaiting Review
  • Owner wonderboymusic deleted
  • Priority changed from normal to low
  • Severity changed from normal to minor

Turns out I have no desire to work on this - I'd rather wait until we overhaul the whole thing.

Note: See TracTickets for help on using tickets.