Hi
Getting this error on after drush site install from existing configs

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "search_api" plugin does not exist. Valid plugin IDs for Drupal\views\Plugin\ViewsPluginManager are: entity_reference_revisions, entity:node, node_rss, data_field, data_entity, entity:user, entity_reference, rss_fields, opml_fields, fields, entity:block_content, entity:nent_tracking_script, entity:feeds_subscription, entity:feeds_feed, entity:encrypted_field_value, entity:file, entity:media, entity:monitoring_sensor_result, entity:redirect, entity:search_api_task, entity:taxonomy_term, entity:donation, entity:webform_submission, entity:menu_link_content, entity:paragraph in /var/www/site/web/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php on line 53 #0 /var/www/site/web/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryCachedTrait.php(25): Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition(Array, 'search_api', true)

Another possible error appearing during installation of a module / install profile / distribution is

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "search_api_tag" plugin does not exist. Valid plugin IDs for Drupal\views\Plugin\ViewsPluginManager are: time, tag, none

CommentFileSizeAuthor
#9 3071591-9.patch1.53 KBpfrenssen
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mudassar774 created an issue. See original summary.

mudassar774’s picture

Issue summary: View changes
DamienMcKenna’s picture

This happens to me when the install runs on Pantheon (and possibly Lando), but not on Vagrant. Maybe a caching problem somewhere?

DamienMcKenna’s picture

I tried reverting to 1.13 and this problem disappeared from the build system.

pfrenssen’s picture

I researched this.

In #2718045: Selecting the 'Rendered entity' display style when creating a view causes a crash a change was introduced that will unset the Views plugins from Search API if there are no search indexes defined yet. The reason for this is that these plugins only work with Search API based views and should be limited to the base tables for the Search API indexes. In case the user did not yet create any search indexes these plugins would be erroneously enabled for _all_ Views, leading to fatal errors. So a solution was proposed that delete the Search API plugins from the plugin list as long as there are no search indexes.

However this now makes it impossible to install a module / profile / distribution that includes Search API and contains config for a View that uses one of our plugins.

pfrenssen’s picture

Issue summary: View changes
pfrenssen’s picture

Issue summary: View changes
pfrenssen’s picture

Component: General code » Views integration
Status: Active » Needs review
Related issues: +#2718045: Selecting the 'Rendered entity' display style when creating a view causes a crash
FileSize
1.53 KB

Here is a proposed patch. Instead of removing the plugins, let's limit them to a non-existing dummy table for as long as the user does not have any search indexes.

idimopoulos’s picture

The patch seems to serve it's purpose. I am leaving this to the rest that also faced the issue though. It is RTBC from me.

drunken monkey’s picture

Thanks for reporting and analyzing this issue, everyone, and thanks for the patch, pfrenssen!
It looks very good to me already, but I agreee with idimopoulos: it would be great if mudassar774 or Damien could also confirm it works for them, before committing.

mudassar774’s picture

Hi

I can confirm patch #9 works just fine -:)

Thanks

acbramley’s picture

#9 fixed it for me, cheers!

pfrenssen’s picture

Status: Needs review » Reviewed & tested by the community

Setting to RTBC since the patch has been confirmed to work by @mudassar774 and @acbramley :)

drunken monkey’s picture

Status: Reviewed & tested by the community » Fixed

Alright, thanks for testing and reporting back, everyone!
Committed.
Thanks again!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.