Warning: array_flip() Missing field item

Mh, as always i try to reproduce problems, so it's possible to fix them later.

Here is an export i tryed to play with, though i didn't got an error. What about providing an export for us? Maybe you text is missing one little detail here.

This kind of errors happens if $entity_load_multiple is called with wrong parameters.

I'm wondering whether you have something like realname module installed? By just using this view i don't get an error like that, even every comment is created by uid = 0 etc.

Here is a short guess: your comment/node_comment_statistics table contains entries for a uid "" but actually it should be "0" so if something is triggering user_load, for example realname the notice get's fired.

It would be somehow helpful if you create a backtrace from that. Therefore you can use something like this code in "includes/entity.inc"

if (!is_array($ids)) {
  dsm(views_trace());
}
...
$passed_ids = !empty($ids) ? array_flip($ids) : FALSE;

I hope this gives enough information to tell a bit more about this problem.

I am getting
Warning: array_flip(): Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->load() (line 175 / Warning: array_key_exists() expects parameter 2 to be array, null given in theme_image_formatter() (line 615

Solved with this patch, which throws a watchdog notice instead of trying to render the missing item.

Patch 8 is really helpful, we were bouncing around this array_flip issue for months internally wondering where or how to fix this. Lo and behold, patch 8 to the rescue. Now our drupal admins will no longer have to scratch their heads with annoying array_flip errors caused by content with missing fields. Instead of an annoying and confusing , almost meaningless array_flip message, patch 8 prevents an array_flip by stopping the rendering process for empty field items. Rather than array_flip, a helpful watchdog message is provided that provides information about a node or entity that has a field with an empty or missing item. So now our drupal admins can solve the issue themselves by fixing the content that was causing the issue.

Great job @dsutter , 5 years after this issue was openned, you came up with an elegant solution! Great idea.

After reviewing the patch a bit more, we might want to add some validation for the entity_type first before assuming a node id (nid) and then add support for fid and mlid , tid , etc. Views can display many types of content more than just nid.

I'll see if I can whip up something to make this great patch even better.

quick change so that all entity types are handled without notices. Not all entity types have nids

removed tab spacing , replaced with spaces
formatted for 80 columns as per code sniffer.

Update to patch #12 to deal with yet another watchdog warning (array_key_exists() expects parameter 2 to be array).

new patch comming

ok, Duncans' patch 13 is the way to go.
we need to check that the array_key_exists because isset when the array element value is null would return false (meaning the test would fail) but we want to know when it's empty and empty on a null returns true

so therefore , logic stays as-is.

The patch in #13 applied cleanly to the latest views 7.x-3.x-dev.