Search API 1.33 breaks Search API Solr Datasources and installations with custom field types that use fallback types

The issue is caused by 🐛 Not all fields that have a target_type setting are entity references Fixed .
That patch tries to avoid a Drupal\Component\Plugin\Exception\PluginNotFoundException.

But the new $definition->getClass() that has been added before the critical section could lead to a Drupal\Component\Plugin\Exception\PluginNotFoundException itself!

drunken monkey → made their first commit to this issue’s fork.

Created an MR with your patch and some minor style changes. (Testing of patches is not working anymore, we now need to use MRs – a bit funny, I know.) Would be great to get some quick feedback on whether this still worked for you, then I’ll merge and create release 1.34 – hopefully without any critical bugs this time.

And then we’ll either keep this open or create a follow-up to develop a proper fix.

As discussed on Slack this seems to not be a bug in this module after all, but one in the Solr module that was simply uncovered by the recent change in this one. I created a follow-up issue 🐛 Invalid type "text" specified in SolrFieldDefinition data defintions Active in the Solr module but will still create a new release of this module with the workaround in the MR to keep more people from being affected.

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