Please integrate with override node options module

It is not strictly true that VBO requires "administer nodes" permission. Perhaps the action you're trying to grant your users does require that permission, and VBO merely enforces that request. Which action are you trying to expose? Note that users do need the permission "edit own blog content" to edit their own nodes.

I too am running into this same problem... I can't seem to get the "unpublish" to work for "authenticated users" who have access to only their information...

I've tried both the node_mass_update and node_unpublish_action, neither of which work. I can edit the node all by itself and unpublish the node without a problem, but vbo won't unpublish it. The site is a classified website so on the view page for the user, I have a "live" column which basically shows if the node is published/live (yes) or unpublished (no).

Now get this... I can manually edit a node, unpublish it, it shows up as unpublished in the view, then I apply a "publish" VBO to the unpublished nodes and it WILL publish them. Delete VBO works fine too.

So, I have: Delete, Publish & Unpublish as VBO options for the users.

Next question is probably whether the permissions are enabled and yes the VBO permission for unpublish is enabled.

@philsward: How does VBO refuse to unpublish? Does it say "Skipped ACTION on NODE because of insufficient permissions"? Does the log report anything? And just to make sure I understand properly, are the publish and delete actions working properly for the same user, on the same nodes?

To be honest, I am not seeing any error's on the unpublish. I skimmed through the watchdog logs but didn't see anything really out of place and it doesn't give any type of error when the actual action is performed.

This is what I do receive if I turn on the "Show proccess results" option or whatever it is in the view:

The update has been performed.
1 rows processed in about 130 ms:
Performed aggregate Unpublish on node 13.

For the delete and publish permissions, yes, they are both working just fine for the same user which makes it kind of a weird issue... I did check for the admin account and it works fine (as expected) so no troubleshooting help there...

I double checked just now to make sure that "Authenticated User" had the permission: execute Unpublish (node_mass_update) which it does, but didn't make a difference.

As of right now, I have the "unpublish" permission turned off to disable it from my users, but if you want me to turn it on so you can create an account and test it, let me know.

You wouldn't happen to have a rule or trigger that automatically publishes content?

Go ahead and create a test account for me. It might be necessary to make it admin though...

I don't have a rule that automatically publishes content, but I do have one that automatically unpublishes content, 3 months after it is published...

Closed unless I hear back from OP.

This is valid issue - if Drupal site uses Override Node Options module and leave out, say, "Publish" permission that would be great if VBO supported this as Drupal core lacks both good administration panel (that's where VBO comes in) and granular permission for basic operations like publish and unpublish.

I have a site where I do not let content managers to publish the content, only create and edit own. VBO lets users to publish the content through bulk operations, never taking into account override_node_options permissions.

Whilst not strictly related to integration with Override Node Options it turns out to be relatively easy to remove the need for the "administer nodes" permission for bulk operation in a custom module thus...

function MYMODULE_views_bulk_operations_object_info_alter(&$object_info) {
  unset($object_info['node']['access']);
}

Alternatively you could do something like...

function MYMODULE_views_bulk_operations_object_info_alter(&$object_info) {
  $object_info['node']['access'] = 'MYMODULE_node_access';
}

...and then include a modified node_access() in your module

I haven't checked but I think hook_views_bulk_operations_object_info_alter was introduced in 6.x-1.10 so you will need to update, if you haven't already.

In this case, it makes more sense for Override Node Options to integrate with VBO (by using the solution in #10)