This little patch creates 2 actions. These are basically a copy of the submit function in the comment moderation form in an actions format. This is very useful for Views Bulk Operations compatibility and in use in a comment moderation view.

I don't agree with marking this as a dupe. This is a small, useful feature that can be used in Views Bulk Operations and elsewhere. Making it dependant on a confirm form issue is needlessly blocking it. It has already blocked for months. If the admins disagree, feel free to set this back to dupe.

Instead of a drupal_set_message(), a watchdog() would be more consistent with core. See the action below from core. The drupal_set_message calls would look upgly after deleting a hundred spams using views bulk operations.

I'll make the above change if the committers think this patch can proceed.

I agree this is a great idea to add. I agree holding it back based on a relatively unrelated issue is unfortunate.

Ultimately this means that mollom.com will get less information about spam comments. I'm building a view to delete a few hundred spam comments on g.d.o and now instead of reporting them to mollom I will simply delete them. That is valuable information that mollom.com loses out on.

Is there anything that can be done to hurry this along to a conclusion? I could test the patch if that helps (although - 2009? - is this going to work with the current dev release?).

I'm not sure how much longer I can use Mollom if I can't integrate it into Views Bulk Actions and Rules. Viewing individual comments and reporting them is just too time-consuming, so, like greggles, I often find my only option is to delete them and deny mollom.com the spam information.

So, the first two are basically just people who need support and are confused by the module. The next 3 are tied for most important meaning that this issue is tied for the most followed open issue in the mollom queue.

1. Enabled aggregate mode on the actions. This takes advantage of the *_multiple() functions, thus making the operation more optimal.
2. Removed the drupal_set_message(). Not needed as VBO already provides information about the results of the operation.

In light of the recent Spamming of Groups, and they Groups users VBO and actions to allow deleting of a users content. Right NOW it is only deleting the content and not notifying mollom that this is being deleted because of SPAM. This is not helping Mollom get rid of our spam. Adding this will help Mollom combat out current spam issue.

Feature requests shouldn't be marked Critical, according to the policy on Priority levels of issues. So I hope it's OK for me to drop it back to Major.

I doubt that upping the Priority would speed anything up anyway. Though I wish there was something that would speed progress up as it's nearly four years since indytechcook opened the issue by posting a patch :(

A lot of this history predates me so thank you for commenting on this and bringing it up on my radar. I'm going to take a look at the latest patch (will need a re-roll, etc.) and do some testing. It may take me a few days but we'll get this rolling again ;-)

We could certainly extend this to nodes pretty easily I would think using a similar approach. Probably can't get to it today but will be able to in the next day or two at most (unless you want to refactor it in before then, of course).

@greggles: Would you be able to help with testing (and perhaps a test class)?

Adding nodes is a bit more of an effort. The comment integration in place already provides delete callback handlers. Node deletion is limited to integrating with the node delete form. I'm a bit wary of just adding it in here, even with callbacks in place without lots of security checks....

I think what would be best is only having unpublish actions for nodes and comments. That is more within Mollom's area of responsibility.

So this is RTBC practically and I'm planning on rolling out a new release over the weekend that will probably include it. Any feedback from folks who think this will or won't meet their needs, please let me know so that it can be taken into account (or better yet - add on to the patch).