I just upgraded from 1.7 to 1.8 - leaving the module enabled

* warning: array_filter() [function.array-filter]: The first argument should be an array in /var/www/beta/sites/all/modules/views_bulk_operations/views_bulk_operations.install on line 47.
* warning: Invalid argument supplied for foreach() in /var/www/beta/sites/all/modules/views_bulk_operations/views_bulk_operations.install on line 47.

Comments

infojunkie’s picture

Version: 6.x-1.8 » 6.x-1.x-dev
Assigned: Unassigned » infojunkie

Thanks for your report. Please try the latest dev release (12 hours from now) and let me know if it fixes the problem.

Phanatic’s picture

Incidentally, I get the same thing, from 1.7 to 1.8. I had disabled the module before deleting it, reuploaded, enabled then updated:

* warning: array_filter() [function.array-filter]: The first argument should be an array in /home/content/m/u/p/mupra/html/sites/all/modules/views_bulk_operations/views_bulk_operations.install on line 47.
* warning: Invalid argument supplied for foreach() in /home/content/m/u/p/mupra/html/sites/all/modules/views_bulk_operations/views_bulk_operations.install on line 47.

infojunkie’s picture

Status: Active » Fixed

Yes, the fix for this error has been added to the latest dev, after 1.8.

Status: Fixed » Closed (fixed)

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

itsnotme’s picture

Component: Code » Core
Status: Closed (fixed) » Needs work

Unfortunately, I also get this error when I update from 1.7 to the current 1.9. (update 6000)

The full warning:

warning: array_filter() [function.array-filter]: The first argument should be an array in C:\xampp\htdocs\drupal-6.12\sites\all\modules\views_bulk_operations\views_bulk_operations.install on line 45.

Help would be appreciated, or at least the information whether this is somehow critical for the functioning of this module.

infojunkie’s picture

@itsnotme: this warning message is not critical for the proper functioning of the module after upgrade. Did you encounter further problems?

itsnotme’s picture

I didn't encounter further problems but the warning made me nervous enough not to update the module on my live server right away.

Thanks for the feedback! In this case, I'm going to update tomorrow :)

infojunkie’s picture

Status: Needs work » Fixed

I fixed this notice in the latest dev. If you can, please wait for 12 hours before updating and let me know how it goes.

itsnotme’s picture

Oh, I didn't see your last reply. I just updated my live system, had the warning but everything seems to be working okay. Thank you :)

Status: Fixed » Closed (fixed)

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