Transferring a site to a new server using the following deployment process which works on both dev -> staging and dev -> live.
Git pull -> composer install -> drush cim
On the new server though, this causes a site failure:
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "media_type" entity type does not exist.
errorlog:
#0 /var/www/html/web/modules/contrib/search_api/search_api.views.inc(760): Drupal\Core\Entity\EntityTypeManager->getDefinition()
#1 /var/www/html/web/modules/contrib/search_api/search_api.views.inc(826): _search_api_views_entity_type_table()
#2 /var/www/html/web/modules/contrib/search_api/search_api.views.inc(724): _search_api_views_add_handlers_for_properties()
#3 /var/www/html/web/modules/contrib/search_api/search_api.views.inc(106): _search_api_views_datasource_table()
#4 /var/www/html/web/core/modules/views/src/ViewsData.php(228): search_api_views_data()Initially uninstalled search_api / search_api_autocomplete /search_api_solr
This got the site back up and running. applied drush cim and eventually found that uninstalling search_api_autocomplete got the site back up:
drush pm-uninstall search_api_autocomplete
New server uses same version of solr and solr core name. Tried using both the solr core config from the old server, then once I got the site running, exported the config from the new server, both with the same results when search_api_autocomplete was reinstalled. [solr restarted on each config update]
I have no idea why The datasource with ID 'entity:media' is active on the new server - I have taken a look though the solr config on the live server and as far as I can see there is no media index, just content and paragraphs. There does not seem to be any references to media entities in the search view or the solr config. I am at a loss as to where this is coming from? Any suggestions would be very gratefully received!
Active
1.8
General code
On the new server though, this causes a site failure:
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "media_type" entity type does not exist.
If that’s the error message you get, then why is there a different one in the issue title? Those are two completely different things.
the title is the dblog entry title, the content is the dblog content.