This is introduced when go to search/content?search_api_fulltext=foo
Drupal 8.1.3
php 7.0.8
Enabled modules: search_api, search_api_db,search_api_db_defaults
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 2760953-8--fix_processor_configurable_property_extraction.patch | 1.77 KB | drunken monkey |
Comments
Comment #2
drunken monkeyI can't reproduce this. Can you try again with the latest dev version? (Please re-install the modules after updating.)
And you're not using any other related modules, like Facets?
Comment #3
edysmpHi @drunken monkey thanks for review.
I reinstalled all and continue much of this:
Steps to reproduce:
- Install Drupal 8.1.3
- drush dl search_api --select (selected dev version)
- drush dl search_api_db --select (selected dev version)
- install search_api, search_api_db, search_api_db_defaults
- drupal create:nodes (created 25 nodes , page and articles with Drupal Console)
- review Index status (25/25 indexed)
- go to /search/content
- search something... apply
- show Notice ^ and below the result
Thanks
Comment #4
frankcarey commentedI'm getting the same thing on a fresh install with drupal 8.1.5, search_api_solr 8.x-1.0-alpha5 and search_api alpha16.
Putting this through the debugger and I see that on line 181 of modules/contrib/search_api/src/Plugin/search_api/processor/RenderedItem.php
For some reason, the entity:node Item seems to have a "0" keyed empty field..
That empty field has no configuration (it's an empty array), hence no $configuration["roles"]
Comment #5
frankcarey commentedI decided to check on the "General" field that was added by search_api_solr_defaults' search index, and figured maybe setting the roles there would fix it, but when I go to save the index field, I get another error..
Which I think is from this issue: #2758583: Comparison of recursive processor arrays can lead to fatal error
Comment #6
frankcarey commentedI think the new default index provided by search_api_solr_defaults may be to blame? The default view doesn't provide configuration for all fields.. is that ok?
Comment #7
frankcarey commentedActually, this only seems to happen for the Highlight Processor..
as a workaround locally, I'm just setting the role config if it doesn't exist :
Comment #8
drunken monkeyThe
search_api_dbproject has no D8 version, that's now included in the Search API project (again). So this step isn't necessary.But, anyways, thanks a lot for providing such detailed steps for reproducing the problem! With this, I was finally able to reproduce the problem. I also got a fatal error when doing it, so fixing two issues with one stroke here!
Please test!
@ frankcarey: Please do not post entire index configurations in a comment. That makes it unnecessarily hard to scroll through the whole issue. Use an attachment instead.
Comment #9
edysmp@drunken monkey Yeah, fixed two issues with one stroke.
Thanks.
Comment #11
drunken monkeyGreat to hear, thanks a lot for testing!
Committed.