I'm implementing a custom _action_info() and I get this exception

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /xxxx/batch?id=2649&op=do StatusText: OK ResponseText: ( ! ) Fatal error: Unsupported operand types in ...\sites\all\modules\views_bulk_operations\plugins\operation_types\action.class.php on line 243 Call Stack #TimeMemoryFunctionLocation 12.5368150376{main}( )..\index.php:0 24.326327433096menu_execute_active_handler( ???, ??? )..\index.php:26 34.331227896160call_user_func_array ( ???, ??? )..\menu.inc:517 44.331227896288system_batch_page( )..\menu.inc:517 54.331427896344_batch_page( )..\system.admin.inc:2379 64.331427896864_batch_do( )..\batch.inc:80 74.331427896984_batch_process( )..\batch.inc:161 84.338228008224call_user_func_array ( ???, ??? )..\batch.inc:284 94.338228008328views_bulk_operations_active_queue_process( ???, ???, ???, ??? )..\batch.inc:284 104.342828016384views_bulk_operations_queue_item_process( ???, ??? )..\views_bulk_operations.module:974 114.368428399608ViewsBulkOperationsAction->execute( ???, ??? )..\views_bulk_operations.module:1065

in code I see the issue occur at the method public function execute($data, array $context) {
and in the line :
$context += $this->formOptions;

CommentFileSizeAuthor
#7 2431131-7.patch748 bytesjoelpittet

Comments

solide-echt’s picture

solide-echt commented

I just crossed your post looking at the same issue. In my config this happened because my hook_action_info() contained 'vbo_configurable' => TRUE' as per the example on https://www.drupal.org/node/2052067. After changing that to FALSE the error disappeared.
Your mileage may vary offcourse.

RavindraSingh’s picture

RavindraSingh commented
Assigned: Unassigned » RavindraSingh
RavindraSingh’s picture

RavindraSingh commented
Assigned: RavindraSingh » Unassigned
Lostboy22’s picture

Lostboy22 commented
Version: 7.x-3.2 » 7.x-3.3
Priority: Major » Critical

Still not fixed.

Does not call hook_action_form() with any possible combination of settings described in the development guide.

Filling my inbox with fail reports from cron.

cron results:
Fatal error: Unsupported operand types in /home/xxxx/public_html/sites/all/modules/views_bulk_operations/plugins/operation_types/action.class.php on line 243

manual action error log:
https://xxxx/special-change?type=article&order=created&sort=desc

Notice: Undefined index: workflow_sid in workflow_vbo_given_state_action_submit() (line 242 of /home/xxxx/public_html/sites/all/modules/workflow/workflow_vbo/actions/given.action.inc).

manual action results:
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?id=372&op=do StatusText: OK ResponseText: Fatal error: Unsupported operand types in /home/xxxx/public_html/sites/all/modules/views_bulk_operations/plugins/operation_types/action.class.php on line 243

kostask’s picture

kostask commented

I experienced the same issue. I solved it by returning something on the submit callback of the configuration form of the VBO action. ex:

function ACTION_NAME_submit($form, &$form_state) {
  return array(
    'form_values' => $form_state['values'],
  );
}
jeremyr’s picture

jeremyr commented

In case anyone else runs into this: Comment #5 worked for me and comment #1 didn't seem to make difference.

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Version: 7.x-3.3 » 7.x-3.x-dev
Status: Active » Needs review
StatusFileSize
new 2431131-7.patch748 bytes

This patch should resolve the issue, let me know.

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Status: Needs review » Fixed

I've committed this as it's critical and low hanging fruit for the new release.

  • joelpittet committed 11db302 on 7.x-3.x 
    Issue #2431131 by joelpittet, vijithaepa: Fatal error: Unsupported...

Status: Fixed » Closed (fixed)

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