Algolia search results PAGE not returning any results

[yoavniran]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Prerequisites

• I'm using the latest version of Docusaurus.
• I have tried the npm run clear or yarn clear command.
• I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
• I have tried creating a repro with https://new.docusaurus.io.
• I have read the console error message carefully (if applicable).

Description

I enabled algolia search on my site: https://react-uploady.netlify.app

The modal works fine and returns results for existing search terms.

For example:

However, when clicking the "see all results". The search page always shows NO results:

I noticed that when contextualSearch was enabled, I also got no results in the modal. When I set it to false the results started showing.

I think there are values being sent from the page that arent being sent from the modal.

This is the query data from the modal:

{"requests":[{"query":"provider","indexName":"react-uploady","params":"attributesToRetrieve: ["hierarchy.lvl0","hierarchy.lvl1","hierarchy.lvl2","hierarchy.lvl3","hierarchy.lvl4","hierarchy.lvl5","hierarchy.lvl6","content","type","url"]
attributesToSnippet: ["hierarchy.lvl1:10","hierarchy.lvl2:10","hierarchy.lvl3:10","hierarchy.lvl4:10","hierarchy.lvl5:10","hierarchy.lvl6:10","content:10"]
snippetEllipsisText: …
highlightPreTag: <mark>
highlightPostTag: </mark>
hitsPerPage: 20
facetFilters: []"}]}

While this is the query from the page:

{"requests":[{"indexName":"react-uploady","params":"hitsPerPage: 15
advancedSyntax: true
query: provider
page: 0
facets: ["language","docusaurus_tag"]
tagFilters: 
facetFilters: [["language:en"],["docusaurus_tag:default","docusaurus_tag:docs-default-current"]]"},{"indexName":"react-uploady","params":"hitsPerPage=1
advancedSyntax: true
query: provider
page: 0
attributesToRetrieve: []
attributesToHighlight: []
attributesToSnippet: []
tagFilters: 
analytics: false
clickAnalytics: false
facets: language
facetFilters: [["docusaurus_tag:default","docusaurus_tag:docs-default-current"]]"},{"indexName":"react-uploady","params":"hitsPerPage=1
advancedSyntax: true
query: provider
page: 0
attributesToRetrieve: []
attributesToHighlight: []
attributesToSnippet: []
tagFilters: 
analytics: false
clickAnalytics: false
facets: docusaurus_tag
facetFilters: [["language:en"]]"}]}

Steps to reproduce

1. open https://react-uploady.netlify.app
2. use search modal to search for ex: "sender"
3. see results
4. scroll to bottom and click "see all X results"
5. see page with no results

Expected behavior

Page should return all results

Actual behavior

no results are shown

Your environment

• Public source code: https://github.com/rpldy/react-uploady-docs
• Public site URL: https://react-uploady.netlify.app
• Docusaurus version used: 2.0.0-beta.15

Reproducible demo

https://react-uploady.netlify.app

Self-service

• I'd be willing to fix this bug myself.

[Josh-Cena]

Duplicate of #5084, right?

[Josh-Cena]

I noticed that when contextualSearch was enabled, I also got no results in the modal. When I set it to false the results started showing.

That sounds like a distinct issue from the search modal sending incorrect requests, while we are only aware of the latter.

[yoavniran]

thanks @Josh-Cena
Indeed duplicate (GH issue search sucks) and disheartening that its still open

1. Is there no solution then for the search page yet? Or is the last comment something I can follow?
2. Yes, the contextualSearch param does seem to break the search. Thats what made me think to look at the params being sent from the search page

[Josh-Cena]

/cc @lex111 We may need to revamp the search page, now that you are already working on #6692.

We'll keep it open because of that contextualSearch issue. cc @shortcuts as well, if we can get any input on your side.

Since I'm not familiar with Algolia at all, not much input on my side🤷‍♂️

Indeed duplicate (GH issue search sucks)

The in:title query is your friend, especially if you want to navigate around larger repositories like the TypeScript repo with 5000+ issues. #5084 is not very easy to find because it's not searchable through search page in:title, but it is through algolia request in:title, since you already realized it has something to do with the request shape.

[slorber]

you added the search only 2 hours ago

Have you triggered a new crawl since enabling the search?

[yoavniran]

@slorber Search works in the modal consistently. This also seems to be the same issue reported in #5084
Are you suggesting that for the same term working in modal, not working in page, can be related to crawling?

[slorber]

@slorber Search works in the modal consistently.

You said they do not show if you turn contextualSearch on.

Yes, you have to follow the doc and trigger a crawl or wait 24h. If contextual search doesn't work, then you have a deeper problem because the search page somehow always use contextual search (we'll change that)

[shortcuts]

Hey,

As @slorber said, the issue is that the search plugin was not enabled before crawling your website, which make contextualSearch unusable.

To solve your issue:

1. Keep your search plugin enabled
2. Enable contextualSearch
3. Start a new crawl from the crawler interface https://crawler.algolia.com/
4. Enjoy searching from both the modal and the search page :D

because the search page somehow always use contextual search (we'll change that)

It would indeed be nice to make it follow the config value

[Josh-Cena]

Okay! In that case, closing as duplicate of #5084. Hope we can get this fixed up soon...

[huynhicode]

I know this issue is closed as it is a duplicate of #5084, but I wanted to chime in here and say that I am also experiencing the same issues as outlined above.

The modal search will only return results if contextualSearch is set to false. The /search page does not return any results.

I have tried to debug this issue according to the suggestions from the Discord servers for Algolia DocSearch and Docusaurus, and so far nothing has worked for me.

I am hoping there is a fix soon, thank you. 🙏

@Josh-Cena @shortcuts