VBO fails when trying to load selected rules components that have been deleted from the system

I ran into the same problem and did the workaround suggested by @itserich at #1 which solved the problem. In doing so, I noticed the following change (removals) to my view, which suggests that there is a possible backward compatibility issue with the Rules component:

   $handler->display->display_options['fields']['views_bulk_operations']['hide_alter_empty'] = 0;
   $handler->display->display_options['fields']['views_bulk_operations']['vbo']['entity_load_capacity'] = '10';
   $handler->display->display_options['fields']['views_bulk_operations']['vbo']['operations'] = array(
-    'rules_component::rules_add_terms_to_node' => array(
-      'selected' => 0,
-      'use_queue' => 0,
-      'skip_confirmation' => 0,
-      'override_label' => 0,
-      'label' => '',
-    ),
-    'rules_component::rules_set_primary_category' => array(
-      'selected' => 0,
-      'use_queue' => 0,
-      'skip_confirmation' => 0,
-      'override_label' => 0,
-      'label' => '',
-    ),
     'action::node_assign_owner_action' => array(
       'selected' => 0,
       'use_queue' => 0,
@@ -261,13 +247,6 @@
       'override_label' => 0,
       'label' => '',
     ),
-    'rules_component::rules_del_terms_from_node' => array(
-      'selected' => 1,
-      'use_queue' => 0,
-      'skip_confirmation' => 0,
-      'override_label' => 0,
-      'label' => '',
-    ),
     'action::node_save_action' => array(
       'selected' => 0,
       'use_queue' => 0,

Reopening just in case we miss this potential backward compatibility issue.

I don't understand what the potential backward compatibility issue is? Is anything not working?

Its a weird case and I not sure where the error lies. Also the reproduceable steps are a bit vague as this was discovered by accident by another developer working with the same view while testing it. The steps are something like:

* Before upgrade to 3.0-rc1, there was a VBO view created that used rules components in 3.0-beta3
* After upgrade, edited the view to remove those components along with other changes to make way for the upgraded features of inbuilt actions of editing fields for content types.
* Re-exported view and saved into feature. Noticed that the rules components did not get removed in the export.
* View did not work (blank screened) with error:

Fatal error: Call to a member function parameterInfo() on a non-object in /sites/all/modules/views_bulk_operations/plugins/operation_types/rules_component.inc on line 50

* Deleted the Bulk operations field, re-added it and re-exported the view. This time it works.
* On the second import, the removal of rules components were noticed, as in #2

Like I said I'm not sure where the problem is, but did not want a bug to creep in if at all.

Okay, that helped, I understand the problem now.

If a component is still enabled in VBO, and gets deleted, VBO chokes and dies because it's trying to load a component that no longer exists.
Looks like you failed to save the view when you disabled the component in VBO (or there was a problem with features, wrong view - possibly overriden - being loaded, etc), hence running into this bug (it doesn't appear for components that have been disabled in VBO field settings prior to deletion).

Note that just disabling a component in VBO does not remove it from the export, it just flips its "selected" variable.

Committed a fix:
http://drupalcode.org/project/views_bulk_operations.git/commitdiff/138ac40

Thanks @bojanz.

Thanks @itserich, I was about to get worried :P

nico