Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Selecting the 'Rendered entity' display style when creating a view that's not based on a search index causes a crash:
> InvalidArgumentException: View test resources listing view mode is not based on Search API but tries to use its row plugin. in Drupal\search_api\Plugin\views\row\SearchApiRow->init() (line 122 of modules/search_api/src/Plugin/views/row/SearchApiRow.php).
Similarly, selecting it on an existing view causes the modal dialog to do nothing, presumably because of the same crash.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | 2718045-11--views_row_style_available_for_non_search_views.patch | 1020 bytes | drunken monkey |
| |||
Comments
Comment #2
drunken monkeyThat's very curious. Normally, this option shouldn't appear except for Search API views, and I also cannot reproduce this. Have you tried clearing the cache?
Comment #3
joachim CreditAttribution: joachim commentedThe option appears in the initial wizard to create a new view.
Comment #4
drunken monkeyCan't reproduce it there, either. For me, those options change according to the base table I pick, and are the same as later when editing the view.
Did you try with the latest version of Views? Or do you maybe have Javascript turned off? (Would be a Views bug, then, though.)
Comment #5
kevinwal CreditAttribution: kevinwal at KWALL commentedCan confirm: Created new view. Set to rendered entity and modal provides a 500 - is not based on Search API but tries to use its row plugin.
Comment #6
ayalon CreditAttribution: ayalon commentedWe have the same issue here. Did not find a solution yet except using Display Suite and selecting the viewmode in the display suite Views Plugin.
Comment #7
joachim CreditAttribution: joachim commented> We have the same issue here. Did not find a solution yet except using Display Suite and selecting the viewmode in the display suite Views Plugin.
You don't have the same issue then. The issue here is that the 'Rendered entity' display style *should not* show in the list, because it's only compatible with a view based on a Search API index.
Comment #8
damontgomery CreditAttribution: damontgomery commentedI just saw this issue as well. To select a view mode for a Taxonomy based view, I select "Taxonomy Term" as the Row style. The "Rendered Entity" was an option that produced the error noted above. I thought that's what I should pick since I wanted to select a view mode for the terms. For our case, I can just choose the right option and move along.
If other people encounter this bug, you probably are looking for the other row styles that let you pick a view mode.
Comment #9
Nigel CunninghamI'm seeking to make a view of paragraph content. The bug occurs in my case because Views::fetchPluginNames('row', 'normal', [ 'paragraphs_item_field_data' ]) matches the search_view plugin. Plugin['display_types'] is not set and plugin['base'] is not set so it gets added to the list of plugins that are returned.
Comment #10
BrightBoldThis still exists in Drupal 8.7.1. I created a view of Media (image type) and got this error after choosing rendered entity as the display format. Per other comments here, changing the display format eliminates the error.
It would definitely be good if invalid plugins weren't offered up. But great that there was an easy workaround.
Comment #11
drunken monkeyVery strange. This should actually already be taken care of by our
search_api_views_plugins_row_alter()hook implementation, which just adds our own base tables as possible bases for the row plugin.Or, hm, do you maybe just not have any search index set up (yet), so this comes out as an empty array and gets ignored by Views? Hadn’t thought of that. If that’s the cause, the attached patch should help – please test!
Or do you have a new search index and didn’t clear cache since then? Then just try clearing cache – maybe that’s the problem. (This should already be taken care of, too, I think, but can’t hurt to try.)
Comment #12
joelpittetThat does the trick, thank you @drunken monkey
Comment #14
drunken monkeyExcellent, thanks a lot for your feedback!
Committed.
Comment #15
hsponner CreditAttribution: hsponner at Freely Agency commented@drunken monkey, thanks. Works for me, too.
Comment #17
pfrenssenIt looks like this solution is not correct. It is now impossible to install modules that depend on Search API and have exported Views config that use our Views caching plugins. The following error is thrown when installing the module:
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "search_api_tag" plugin does not exist. Valid plugin IDs for Drupal\views\Plugin\ViewsPluginManager are: time, tag, noneEdit: there was already an issue for this: #3071591: Search_api plugin not exists after updating 8.1.13 to 8.1.14.
I have proposed a patch there that solves the problem.