Skip to content

Conversation

@stevector
Copy link
Contributor

I did some co-working today with @stovak and @jazzsequence trying to work out #181. We found that some requests from Drupal to Solr included the name of the core in the path of the request and some did not. (We did this by toggling debug property here: https://github.com/pantheon-systems/search_api_pantheon/blob/8.x/src/Services/PantheonGuzzle.php#L63)

Those that did not were 404s, those that did were 200s. So here's a hacky re-insertion of the core name that at least gets rid of the error in #181.

Screenshot 2024-07-18 at 9 48 59 PM

Someone with a better understanding of Solr than me could do more to explain. If I kept going, I'd stop comparing search_api_pantheon on a Pantheon multidev to search_api_pantheon on DDev and instead do a DDev to DDev comparison. I bet DDev works fine with regular search_api_solr.

@kristin-wiseman
Copy link

@stevector Thank you so much for this! I copied your changes into my local version of the module, and my local Solr is no longer reporting errors and can even index content. I also wanted to mention that DDEV with both Solr add-on versions (Solr 8 ddev-drupal-solr and cloud Solr ddev-solr) works with regular search_api_solr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants