Closed (fixed)
Project:
Views Bulk Operations (VBO)
Version:
6.x-1.x-dev
Component:
Core
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
10 Sep 2009 at 18:35 UTC
Updated:
6 Apr 2010 at 07:00 UTC
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
Comment #1
infojunkieThanks for your report. Please try the latest dev release (12 hours from now) and let me know if it fixes the problem.
Comment #2
Phanatic commentedIncidentally, 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.
Comment #3
infojunkieYes, the fix for this error has been added to the latest dev, after 1.8.
Comment #5
itsnotme commentedUnfortunately, 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.
Comment #6
infojunkie@itsnotme: this warning message is not critical for the proper functioning of the module after upgrade. Did you encounter further problems?
Comment #7
itsnotme commentedI 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 :)
Comment #8
infojunkieI fixed this notice in the latest dev. If you can, please wait for 12 hours before updating and let me know how it goes.
Comment #9
itsnotme commentedOh, 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 :)