VBO is a nice and mature module. It would be useful to deploy it on drupal.org to be able to create admin-only utility views. For example, a "all comments of a user, with possibility to bulk delete / unpublish comments" would be very useful for our spam-fighting troops.

Comments

Gerhard Killesreiter’s picture

Got some more use-cases?

Damien Tournoud’s picture

My primary target is the spam-fighting one. Even if we only deploy this one, I think installing the module worth it:

View: All posts / comments of a given user
Actions: unpublish / delete

I'm pretty sure the documentation team would be interested too.

merlinofchaos’s picture

Another use case that probably requires some work on project.module to be really doable (i.e, exposing project specific actions).

Perform mass administration of issues in a queue. For example, perform auto-updates of old issues to close or promote them to newer versions.

Michelle’s picture

Being able to filter by spammer name would be helpful. The core tools mean a lot of hunting thru the list and the possibility of accidentially clicking the wrong post.

Michelle

WorldFallz’s picture

Only somewhat tangentially related-- but it would be really useful to have the ip address of the user listed along with the post which should be pretty simple with vbo. I'm finding a lot of spam lately where the spammer is creating multiple accounts to spam the same link or repeatedly bump the same post. It's not fool proof, but would sure help to easily identify them.

The spammers seem to have new tools every day and we're still fighting with the same old technology. It feels a bit like trying to build a flood wall with a teaspoon. :-(

Gerhard Killesreiter’s picture

There seem to be several use cases, I suggest we install it on d6.d.o and some volunteers build some views which we can then put into code.

Damien Tournoud’s picture

Status: Active » Needs review

Ok, deployed on VBO, and created a "comments per user" View:

   http://d6.drupal.org/user/22211/comments

Dave Reid’s picture

That is sweet.

Michelle’s picture

Oh, wow, that looks awesome! Can we have one for nodes as well?

Thanks. :)

Michelle

Damien Tournoud’s picture

Here we are, both Nodes and Comments:

http://d6.drupal.org/user/22211/moderate

swentel’s picture

I like it, this makes spam moderation way more easier!

Damien Tournoud’s picture

It seems like the "Unpublish" and "Unpublish post" actions do not work went run in a Batch API...

Damien Tournoud’s picture

Damien Tournoud’s picture

Ok, both bugs are fixed now (one of them was already fixed). I opened a feature request against views that would allow us to display the IP address of the poster (for comments): #520632: comment.views.inc does not export comment.hostname.

Please test the two views on d6.drupal.org and report back the results.

WorldFallz’s picture

WOW-- this will save tons of time when one of those spam bots gets through and we have to delete/unpublish 3 pages of junk!!! And when IP is added it will help spot the imposters-- this is great! Thanks so much!

WorldFallz’s picture

One suggestion-- i think it would be helpful to have unpublished comments/nodes listed as well-- to better understrand a users history. A lot of unpublished nodes and/or comments is not a good sign. That should probably be an exposed filter or maybe just a sortable column.

WorldFallz’s picture

WorldFallz’s picture

nevermind, it actually wasn't that big a deal-- the posts were close enough together that they could be easily located and deleted via admin/content/node. The smarter spam bots space them out so you have to waste time paging around trying to find them all.

infojunkie’s picture

Subscribe

kiamlaluno’s picture

I tried to see the views created, but I have no luck. In both the cases, I just see the user profile page.

Am I doing anything wrong? I used my account, and I see the admin menu (which means I am seen as a site maintainer); still, I cannot see the created views.

Dave Reid’s picture

We have the admin comments view, but can we get one added for nodes?

kiamlaluno’s picture

Definitively, a similar tab for nodes would be very useful.

kiamlaluno’s picture

It doesn't seem the view Administer comments is built using VBO; to me it seems a normal view.
Am I wrong, and missing something?

Heine’s picture

@23, I also have a normal view. While a definite improvement over the Track page, I do long for a full VBO experience here after deleting yet again a few pages of UGG comments.

dww’s picture

Right, I built the "Administer comments" view as a normal view and was going to turn on VBO when killes objected saying he'd rather d.o admins use JS scripts for this sort of thing. I think that's a terrible position, and would be happy to see enough d.o admins band together to override this decision.

Michelle’s picture

I have no idea how to use a js script for that so +1 from me for VBO. Seriously, I don't think killes wants js newbs like me messing around with trying to automate drupal.org maintainers tasks. ;)

Michelle

kiamlaluno’s picture

Which should then be the JavaScript solution that works on all the browsers currently used by who is site maintainer? If the solution is to change the browser one usually uses, then that is not a solution, IMO.

I am happy with Administer solution, and I am happy dww provided that view, which is very useful; I anyway understand the view was supposed to be a temporary solution (which, I repeat, is a valid solution).

There are other views which could be created to help site maintainers; for all those views, VBO seems a valid help.

dww’s picture

Project: Drupal.org webmasters » Drupal.org infrastructure
Component: Other » Drupal.org module

Ping? I just had to manually clean out 4 pages of spam with the "administer-comments" view I made months ago when I found a spammer bumping posts in my tracker (#688968: Daily SPAM). Then, as I was composing this, I had to delete some more for #688984: daily spam report. Gerhard, can we PLEASE turn on VBO now? If not, I'm on strike regarding cleaning out spam... ;)

Michelle’s picture

Yes, please. I have to do this fairly often, too. I watch the global tracker a lot and so tend to catch a lot of the spam. While the new view is nice, having to click on 50 delete links and then go back to each tab it opens and confirm I want to delete the spam is tiresome.

Michelle

WorldFallz’s picture

Me three-- we should make dealing with spam easy for maintainers so they're not wasting precious time on garbage detail.

kiamlaluno’s picture

+1 from me too; removing spam is a perfect use case. Once VBO is installed, it can be used for other tasks as well, but it does help when the view Admin comments reports 4 pages (or more) of spam comments.

Gerhard Killesreiter’s picture

What's wrong with using bdragon's mallet script?

kiamlaluno’s picture

What's wrong with using bdragon's mallet script?

Is it something that can be run from Drupal.org?

dww’s picture

@killes: I'll summarize (since you haven't seem to have read the comments here that already motivate the reasons) ;)

1) Not everyone runs a browser that supports this.

2) It's a lot of extra steps to setup for d.o maintainers who want to help fight spam.

3) Having a (set of) controlled VBO view(s) for tasks like this makes it easier to make them consistent and debug any problems than having a fleet of admins using random versions of JS scripts floating around

4) There are potentially dozens of use-cases for VBO on d.o, for both admins and end-users. It's insane to propose that everyone should start installing a suite of d.o-specific JS hacks in their browser to actually use our site.

...

I could keep going, but then you'll say I'm too verbose and won't read it. ;

kiamlaluno’s picture

I am using Safari, and most of the JS hacks don't work on it; I cannot even use Dreditor.

Just as me, there are many other site maintainers who use Safari, and would help in removing spam. If site maintainers would be allowed to remove spam without to delete the comments one by one, or without to wait for somebody with shell access to the database to remove the comments, that would help.

As pointed out from dww, VBO would be helpful in many situations, and not just for spam removal or for site maintainers.

Michelle’s picture

I'm using Opera and I can't even upload to drupal.org. Plus, I wouldn't feel comfortable running a hack on something like deleting comments. I'd be too afraid of something going wrong and wiping out more than I meant to. VBO is simple checkboxes and I can double check that it's deleting exactly what I want to before I tell it to run.

Michelle

Gerhard Killesreiter’s picture

I find it strange that people who work on a free software project use proprietary browsers. :p

Anyway, could you maybe list some more use cases for vbo? I am wary of installing one-trick ponies.

dww’s picture

Initial list of VBO use cases:

A) cleaning up spam comments

B) cleaning up spam nodes

C) A tracker page with "mark all these read" checkboxes

D) Adding VBO to various issue views to let you do bulk updates (close all issues marked "postponed (maintainer needs more info)", move all 7.x core feature requests to 8.x, etc). Sky's the limit with the cool crap we could do here.

...

Again, I'm sure there are more, but I'm not going to bother writing them if you're not going to bother reading them. ;)

kiamlaluno’s picture

Talking of issue reports, it could use useful to assign a set of issues to a different project, as it would be useful now that has been created the issue queue for the Drupal redesign (and issues marked as such could be moved to the new issue queue).

I still think that being able to remove spam without to remove the single comment each by each would be a step further; I am aware of at least three cases where the spammer created so much spam comments that using the actual view to administer comments would have taken too much time (and in fact, I gave up after I saw how much comments were created).

Considering that VBO is not a module for just removing spam comments, or spam in general, and considering that Views is already installed, I would think that VBO could be installed as well. Once installed, we can think of many other uses for that; but until it is not installed is not worth to list all possible uses.

webchick’s picture

Even if comment/node spam mass-deletage is the only use case (and I don't actually think this is the case; dww and others have cited many others), I think this is worth doing. Why? Because it saves our volunteers time, and saving our volunteers time means they can do more with the time that they have.

Furthermore, the people with the permissions to delete other users' content are the people who are the most trusted, whose contributions over time have been the most valuable, and whose time we most definitely do not want to waste on things that could be easily automated by computers.

Gerhard Killesreiter’s picture

I've already given in. :p

But please somebody try this on scratch first.

webchick’s picture

To summarize: if rockstar contributors like Michelle and dww are spending 30-60 minutes per day (or per week or per month; doesn't matter) clicking delete, confirm, back, delete, confirm, back, delete, confirm, back instead of making Drupal more awesome, then we have a critical bug (and one that makes me die inside).

Edit: Oops. Cross-post! Thanks, Gerhard! :D

kiamlaluno’s picture

Component: Drupal.org module » Other

I guess scratch.drupal.org is not accessible from anybody.

dww’s picture

Assigned: Unassigned » dww
kiamlaluno’s picture

Thanks, dww; I can access that.

Rather than a button for each operation, I would use a select field; it would be easier to add more operations.

webchick’s picture

webchick’s picture

Er. Got cut off.

This is based on drawing parallels from the current admin/content/node and /tracker pages that core already provides. Hopefully provides some more consistency.

dww’s picture

Status: Needs review » Fixed

@kiamlaluno: There are only 2, maybe 3 operations we're ever going to have on this view, so it's silly to have to click twice for that.

I made a bunch of other improvements in the meanwhile (e.g. including the body of the comment so you can really be sure what you're deleting).

This is now committed to the default view in drupalorg.module (see #699696: Split default views into separate files in a "views" subdirectory), merged into d.o SVN, and deployed on d.o:

http://drupal.org/user/83/admin-comments

Future tweaks for this particular view should be a new issue in the drupalorg queue.

Future uses of VBO on d.o should be in other issues, too.

We've now considered installing VBO, decided it was a good idea, and did it, so *this* issue is now fixed. ;)

YAY!!!!

infojunkie’s picture

As the author and maintainer of VBO, I am very happy to see it used on d.o! Thanks to everyone who pushed for it.

As a non-admin, however, I can't access the admin-comments VBO. Would it be possible for me to get permission to access the VBO pages, at least on staging, to help with troubleshooting/tweaking?

dww’s picture

@infojunkie: thanks for the offer. At this point, it's just this one view, and it's running smoothly. The view is exported to code in the http://drupal.org/project/drupalorg project, so if you want to try it yourself on your own site, you can. If we run into any trouble or need help, I'll definitely ping you and can get you access to the views on a test site.

Thanks again for the incredibly useful module!

Cheers,
-Derek

webchick’s picture

Just wanted to report my extreme elation with this improvement! :) Tonight I caught an issue queue spammer with about 8-9 posts under his belt already. In the old days that would've taken me at least 10 minutes to click through (what with all the distractions that pop up while you're waiting for pages to load...). Instead it took about 10 seconds.

YAY!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.