Posted by garym@teledyn.com on October 13, 2004 at 6:07pm
Jump to:
| Project: | Drupal core |
| Version: | 4.5.0 |
| Component: | comment.module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
My MT-migrated drupal was live for only 13 hours before the first burst of spam comments adapted to the new POST form.
and this one was so stupid they were undefeatable: By not supplying the closing tag on their sex-drug URL, the comment is undeleteable -- the delete button forms the closing of their tag making the 'delete' take you to their site.
this underlines two features urgently needed:
- could we implement an immediate delete feature? I think there should be an option to delete immediately and in bulk from the 'comments' list without the intervening click of each and every one followed by are you sure? ... because I am sure I don't want sex-drug advertising on my blog. I was lucky this time -- in the past I've had spammers hit my site hundreds of times per hour, and to delete those with the current interface would be very tedious.
- Could we set a different default filter-bundle for blog items vs comments, such that we allow use of the A tag to authenticated users but deny this tag to anon (which will be comments, where permitted). The current filter seems to be a single set of allowed tags for all filtered HTML situations, but I think that may be too narrow.
Comments
#1
On Firefox on the Mac, you can Command-click on the delete button -- this opens the site in a new window, but also manages to activate the delete button.
For 1:
Yes, it's necessary. Rather than a quick delete, I think multi-delete is necessary -- remove the current "delete" column and replace it with a row of check boxes, then have a drop-down list to apply an action to all selected comments (publish, unpublish, delete).
On 2:
This is a separate feature request, and should be filed separately.
#2
#3
Dries, I'm not going to change this back to critical, but let's put it this way...
I have over 100 comment spams sitting in my approval queue on my personal website. I think this is a critical issue that the Drupal community *needs* to address before it becomes a huge issue like it has for MT (and the associated bad name).
We can't stop comment spam (in fact, the spam module only unpublishes comments by default...still leaving us with the need for multi-delete), but at least we can give users and website administrators good tools for dealing with it.
(and it's a feature request, not a bug: why can't it/shouldn't it be critical?)
#4
As noted elsewhere ;) I'm also beseiged by comment spam and would call this a 'critical' feature request.
As a side story, I dropped in at a friend's shop the other day, and he jokingly complained that I was now dominating his aggregator -- because I have to use SQL to delete the pile of spams that are pouring in and then clear the cache to effect them on the site, his (admittedly broken) aggregator software was led to believe my RSS was now invalid and needing to be downloaded and all items re-entered. I'm OK with using SQL to delete these comments (a better solution than porting back to MT) but I wouldn't recommend it for everyone.
#5
Jeremy has added a patch to comments.module to implement exactly this sort of batch-operation ability -- I think it belongs in the core.
You can find his patch in the optional/ dir in contrib's modules/spam
#6
Then it's solved.