Warning: array_flip(): Can only flip STRING and INTEGER values! in EntityAPIController->load() (line 203 of /var/www/sites/all/modules/entity/includes/entity.controller.inc).
Warning: array_flip(): Can only flip STRING and INTEGER values! in EntityAPIController->cacheGet() (line 297 of /var/www/sites/all/modules/entity/includes/entity.controller.inc).
Haven't debugged why this occurs, but it is reproducible by adding a facets block display to a view with a Search: Search Terms argument, and then saving the view.
/Robin
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | Advanced Search - Resources | NAILSMA.jpg | 18.77 KB | davidseth |
| #4 | search_api_views.display_facet_block-debug.patch | 1.5 KB | drunken monkey |
| #3 | search_api_facet_block_debug.txt | 313.21 KB | davidseth |
| #1 | entity.tmp_debug.patch | 780 bytes | drunken monkey |
Comments
Comment #1
drunken monkeySorry, but I can't reproduce this. For me, this works like expected. (I assume you meant the "Search: Fulltext search" argument?)
It would be nice if you could help me find the bug by first applying the attached patch, then triggering the bug and sending me the message output (which will hopefully be there).
In general, the sources of such warnings (I've seen them quite often already) are wrong calls to
entity_load()or its derivatives (in this case, most probablysearch_api_index_load()).Comment #2
davidseth commentedI get the same error as the original poster. Here is the debug output attached.
Comment #3
davidseth commentedsorry, file now actually attached.
Comment #4
drunken monkeyOK, thank you!
I can see now that this can be caused by someone adding the "Facets block" display to a view with a wrong base table – i.e., one not representing a Search API index. Then, the plugin will (of course) fail in loading the corresponding search index, causing the mentioned warning. This should in any case be fixed to throw an exception with a more meaningful error message.
However, I assume that you are using a correct base table, for a search index? If so, please apply the attached patch to the Search API and post the resulting message when triggering the error. It should now throw an exception, but underneath that display an info message prefixed with "DEBUG".
By the way, just saw I forgot to mention that the previous patch should be applied to the Entity API module, not to the Search API. Sorry for that!
Comment #5
davidseth commentedOkay, applied the patch at #4.
You are right, I had applied this to a base table of search_index. Sorry, my fault. I will switch it to use my Node index that I created.
Okay, after I have done this, it indeed works (kinda). I get the facets, but instead of the term names, I get the term ID. Attached is a screen shot.
Thanks.
Comment #6
drunken monkeyThis is an entirely different problem, that should go into a new issue. Please mention there, which field you use for the facets, and other circumstances that might influence this.
This issue is fixed, I now committed the above patch minus the debug lines, so wrong useage will now result in a more meaningful error message.