I'm getting this error when I delete a bunch of nodes using the Content system (/admin/content/node):

Fatal error: Call to a member function get_selected_operations() on a non-object in /var/www/html/sites/all/modules/views_bulk_operations/views_bulk_operations.module on line 1331

When I return to see the nodes list again, I can see that it started to delete few nodes (2 or 3), before it gets this error. Consequently, if I select a few nodes only, and reload 2 or 3 times when it reaches this page error, it "returns" to normal.

I'm using 1.x-dev and Views 2.10.

Thanks for attention.

Comments

infojunkie’s picture

Are you sure you mean "/admin/content/node" or "/admin/content/node2"? The first is the Drupal core content admin screen which has nothing to do with VBO.

Did you set up a rule or trigger to automatically delete nodes when some node is deleted?

Vuds’s picture

Yes, it was the core system from Drupal (/admin/content/node).

And yes, I have a Rule that use VBO to delete nodes that node-referenced these ones (detail: they are different content types) that I deleted manually via core system.

But thinking of it, if it doesn't have any nodes that node-referenced them, the VBO view is empty and it should pass by with success (and not with errors), right?

More info about my Rule and VBO View: If I delete a node from a content type X, the rule seeks using a VBO View (passing by the nid as a view argument) for nodes from content type Y, that have a CCK node reference field linking them to X, and delete them also.

Maybe deleting mass in the core Content system, it tries to pass by any important hook that this Rule uses and when executing it, it gaves me the error?

infojunkie’s picture

Did you make sure the node is still there when the rule is fired? It might be that the node has already been deleted so the View fails to validate the nid argument.

bojanz’s picture

Category: bug » support
Status: Active » Fixed

No activity for more than a year. Suggestion in #3 makes sense.

Status: Fixed » Closed (fixed)

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