Warning: array_values() [function.array-values]: The argument should be an array in views_handler_filter_in_operator->op_simple()

I'm seeing the same two errors on a site I just started maintaining.

Warning: array_values() expects parameter 1 to be array, string given in views_handler_filter_in_operator->op_simple() (line 369 of /home/redacted/webapps/redacted/sites/all/modules/views/handlers/views_handler_filter_in_operator.inc).

Warning: Invalid argument supplied for foreach() in DatabaseCondition->compile() (line 1853 of /home/redacted/webapps/redacted/includes/database/query.inc).

Please check this patch

It didn't work for me. Still same warning message is popping up.

I have been getting below error for some pages -

Warning: Invalid argument supplied for foreach() in DatabaseCondition->compile() (line 1853 of /home/redacted/webapps/redacted/includes/database/query.inc).

I have resolved the bug, but it was not related 'Views' module, rather is was caused by my custom code.

Just sharing here, in case anybody might be benefited - I have used 'hook_views_query_alter' to alter the query of views block and passed array value to altered filter field value. But since that array value was empty for certain pages where block is displayed it showed the warning message.

To resolve the issue, I have checked if array has value with (!empty($variable)).

It appears that @rupesh_jagtap had an unrelated problem so this should be returned to "Needs review"

I agree with @chewie that we should check whether $this->value is an array, but suggest we should do that as well as (rather than instead of) checking that the array is not empty.

Note: While this patch fixes the warning, it's more probable than not that the real cause of this problem lies somewhere else.

You may want to get a backtrace with Printable Backtrace and post it here or even better debug why that illegal value got here in the first place.

I agree with @axel.rutz that this is just repressing an error that is caused by something else. We should find the real cause of the problem and fix that.

Lets keep this in the 7.x branch for now, since the most likely cause is a D7 handler doing something wrong. Unless we can trace this to something that is still around in D8, then lets move it up to D8 core queue.

If we want to fix the source(s) of the error I have found one when using an exposed "User: Name" filter and entering a filter value of a non-existent user.

This is the fix I used if anyone cares to roll a patch.

modules/user/views_handler_filter_user_name.inc

  function exposed_validate(&$form, &$form_state) {
    ...
+   $this->validated_exposed_input = array();
    if ($uids) {
      $this->validated_exposed_input = $uids;
    }
  }

Here's a trivial re-roll of the patch in #10 for 7.x-3.21.

Tested it here and MustangGB's patch on #15 really works well. I agree with #13 fixing the root cause. Good catch. So moving to RTBC. Thank you so much, everyone

Moved to the dev branch. Thank you so much, everyone. Have a great week