How can I bulk change commenting status of nodes?

There is currently no action that lets you change the commenting status. You can contribute it or mark this issue as a feature request.

Here's a recipe to achieve this:
* In Administer > Site configuration > Actions, create a new advanced action of type "Execute arbitrary PHP script".
* In the "PHP script" section, type:

$object->comment = COMMENT_NODE_READ_WRITE;
node_save($object);

* Save the new action under a descriptive name.
* In your VBO admin page, select the new action in the style settings.
* Save the updated VBO and navigate to its page.
* Select a few nodes and apply the new action to them.

Note that you can choose to disable comments (COMMENT_NODE_DISABLED), make them read-only (COMMENT_NODE_READ_ONLY) or read-write (COMMENT_NODE_READ_WRITE).

Hope this helps!

That was awesome. Thank you.

It's great that there's a recipe for this but I'm wondering if there's some reason it can't be included with VBO to begin with? This seems like a pretty common operation.

Thanks,

Michelle

I'd be grateful if someone could package this recipe as a configurable action, allowing to choose which commenting option to apply.

#2 works well, many thanks.

Thank you very much Mr. Karim Ratib
I will save many hours of work.

+1 for this feature.

Subscribe

This really should be included as a standard action in Drupal.

It's not nice to wade through bad code examples to eventually find the right one.

Hat tip to info Junkie for the working code example.

Sorry, wrong move :-)

Great, thank you very much. Saved me an evening of work...

#2 works well, but I'm still casting a vote for #6.

do you know if does not work with nodecomment???

for anyone interested, possible solution (via sql hacking):

http://drupal.org/node/164393#comment-4403834

I have just set this up using Views Bulk Operations and Rules.

For information on how to link VBO with Rules, there is an excellent video from Nodeone.se: http://dev.nodeone.se/en/blog/nodeone-talks-drupal-rules-vbo-revisited#c....

Basically, you set up a rule set (it's a Component, not a "normal" Rule) with the required action and then add a new View with a VBO field to enable the action to be performed.

It took me all of 5 minutes, the two tools really are very powerful indeed.

The rule action by the way is "Set a data value" and the target is the data item "[node-comments:comment]". The value of this data item gets set to either 0, 1 or 2 depending on whether you want no comments, comments, or read-only comments (in that order).

If you need any help, mail me. I'm a Drupal newbie (although I have a background in IT, PHP and databases) but I seem to have worked this out so far (I'm still stunned how far Drupal has come in the five years I have been away from it).

Changing back to 6.x-1.x since there's a patch that might be considered for that branch.

Thanks for the tip, edbradburn!

#2 looks like it will accomplish what I am trying to do but "Execute arbitrary PHP script" does not appear in the drop down menu at "Administer > Site configuration > Actions" in Drupal 7. Any ideas?
I have enabled PHP filter (which I assume is needed) and also checked permissions.

The VBO for D7 can do this out of the box with tomorrow's -dev, using the "Modify entity values" action.

The patch from #19 for 6.x-1.x works for me. However, it's missing comment blocks for all of the functions, and includes a commented out function. Needs coding standards work.

Actually it seems that the 1.x branch now doesn't list the available actions in a file, but detects them automatically, so the patch in #17 is the one to use for the 1.x branch.

Coding standards issues still apply.

Sorry, one more change. The action files are now located in the actions folder. So slight change to the patch. This one will apply cleanly to 1.x-dev and place the new action in the right location.

Committed to latest dev with slight changes.

Note to action authors: On the action form, don't forget to read the default values from the $context array. This is essential in two cases:
* If a validation error occurs on the form, values are not lost when the form is re-displayed.
* If the user saves your action with preset arguments (in the "Advanced actions" section of admin/settings/actions/manage), preset arguments are automatically used in the VBO (or anywhere that the saved action is used.)

Any interest for D7?

See #25. This is possible in D7 with the "Modify entity values" action (included since RC1).
I think that's enough (plus, Rules can be used as well, if the user just hates that action).

Hello,

I couldn't manage to use VBO to disable comments on some nodes, cam you help me more ?

Thanks.