Invalid argument supplied for foreach() in _views_bulk_operations_get_field()

I am seeing this problem too. The cause is that $view->field is NULL for some views.

The view that is causing this for me has the following interesting properties:

• View type: Fields
• Only field in master display: taxonomy term list
• Output of field is rewritten

I suspect that $view->field must be an array for any view containing a VBO field in the master display, in which case wrapping the guts of the function in a check for is_array($view->field) should be an adequate fix. However, I don't know enough about views to know what should happen when there is a VBO field in an overridden display.

I have changed the category to Bug report because this is clearly a software problem.

It turns out that inn my case the cause of the empty $views->field was actually a missing handler. I had created a content pane display and then disabled Views content panes. Reenabling the module caused $views->field to become populated with an array once more.

I think a fix should generate a meaningful error message reporting the problematic view, especially since it will not usually be the VBO view at fault. The meaningful error message might not be able to be very specific, but at least it can report the name of the view that is at fault.

e.g. Configuration problem detected in view "faulty_view". Check for disabled modules and deleted fields.

Here is a patch to check for a non-array value of $view->field and issue a warning. This should allow Rules to correctly populate its list of available VBO fields.

Symptom: Warning: array_unique() expects parameter 1 to be array, null given in views_bulk_operations_modify_action() (line 69 of /www/d754/sites/all/modules/contrib/views_bulk_operations/actions/modify.action.inc).

For us, patch #4 prevents the above warning.

Patch in #4 continues to apply without difficulty to the 7.x-3.x-dev 2019-05-16