solidus

Screenshot 2023-02-13 at 10.35.58 AM.png

Is the search on the guides broken for anyone else?

Maybe the index needs to be rebuilt, I don’t seem to get any results no matter what I type

<@U0ENVE2G1> Good call! It looks like the search works on `Next` but not 3.3 or 3.2!!!

Here’s a possible solution: <https://discourse.algolia.com/t/algolia-searchbar-is-not-working-with-docusaurus-v2/14659|https://discourse.algolia.com/t/algolia-searchbar-is-not-working-with-docusaurus-v2/14659>

If I am reading this correctly, we need to add a `custom_settings` with the attributes for faceting here <https://github.com/solidusio/edgeguides/blob/main/docusaurus.config.js#L146> :thinking_face:

Screenshot 2023-02-13 at 12.01.27 PM.png

It looks like we have the meta fields configured for language, version and docusaurus_tag

I am a bit confused, because reading through the docs here, it seems like this should _just work_ <https://docusaurus.io/docs/search#contextual-search>

Screenshot 2023-02-13 at 12.21.49 PM.png

Screenshot 2023-02-13 at 12.20.35 PM.png

I’d be curious if we force a re-crawl if it would just work :thinking_face: Though I see that the requests we send to Algolia only include the tags, not the versions.
This is the search request on version 3.3 (no results) and the search on Next (returns results)

I sent a PR with the quickest fix suggested by the article posted by <@U0ENVE2G1>, the search should now be working with results always pointing to the current release

<@U03M5C5RX> can you confirm it works for you as well?

Hey <@U0DRAKB26>, the search now works on every version but the results always take you to the pages for version 3.3. I think this is better than before, while we figure out the long term fix. I might have some time this week to play around with it, but for some reason I am not getting cloudflare builds on draft PRs (see <https://github.com/solidusio/edgeguides/pull/96|here>). Having that would be helpful in debugging this

<@U03M5C5RX> agree,
alas cloudflare pages doesn’t support that :disappointed:
so for now we’ll need to test locally… but for the simple change I did the results were already popping up on the development server, so maybe that will be the case also for more complex configurations…

The alternative is pushing to branches on the original repo and create PRs from there, but long term we would still need a better solution

I can try to play around this on local and see if I can’t get something working