Algolia search response not displaying #8970
-
|
Hi all, new here :) sourcecode: https://github.com/mikehaart/wicbwwiki I'm using Docusaurus for a hobby project. I'm hosted on Netlify so I've installed the integration but when I use the search function on my site the response doesn't display in the UI. Looks like the request fires correctly and the response sends the right index information but getting nothing on the page. Not sure what to look into, suggestions welcome! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
|
Hey You are using optional options that you probably shouldn't here: algolia: {
// The application ID provided by Algolia
appId: 'DGMONGHJKH',
// Public API key: it is safe to commit it
apiKey: '211080b0a4c2c33dc0a2d0e25ac0c0f6',
indexName: 'netlify_2b25d0d1-0404-4bf1-a96d-fe292ed9901b_main_all',
// Optional: see doc section below
contextualSearch: false,
// Optional: Specify domains where the navigation should occur through window.location instead on history.push. Useful when our Algolia config crawls multiple documentation sites and we want to navigate with window.location.href to them.
externalUrlRegex: 'external\\.com|domain\\.com',
// Optional: Replace parts of the item URLs from Algolia. Useful when using the same search index for multiple deployments using a different baseUrl. You can use regexp or string in the `from` param. For example: localhost:3000 vs myCompany.com/docs
replaceSearchResultPathname: {
from: '/docs/', // or as RegExp: /\/docs\//
to: '/',
},
// Optional: Algolia search parameters
searchParameters: {},
// Optional: path for search page that enabled by default (`false` to disable it)
searchPagePath: 'search',
//... other Algolia params
}Not sure what is happening but I'd recommend to use a more minimal config to get started: algolia: {
appId: 'DGMONGHJKH',
apiKey: '211080b0a4c2c33dc0a2d0e25ac0c0f6',
indexName: 'netlify_2b25d0d1-0404-4bf1-a96d-fe292ed9901b_main_all',
}Your index name looks weird to me, are you sure it's the Algolia index name? Also note that you must ensure that the Algolia crawler did run (by default once every 24h but you can trigger it manually). The Algolia dashboard can tell if your index contains records or not, so make sure to double-check that your index is not empty. |
Beta Was this translation helpful? Give feedback.
-
|
Note for self: Netlify deploy links: https://app.netlify.com/sites/wicbwwiki/deploys Not sure what is happening here. @shortcuts any idea? Did you run the crawler again since the last deployment? Are you sure you are using a valid Docusaurus crawler config? |
Beta Was this translation helpful? Give feedback.
-
|
Please give me the exact search query you are currently using because right now all queries I try return 0 hits. For example, no hits (even in network devtools) using this query: I believe it could be fixed by reindexing, now that contextualSearch has been turned on again. But before running the crawler make sure you use the recommended crawler config: https://docsearch.algolia.com/docs/templates/#docusaurus-v2-template If you decide to change this config, it's your responsibility to make it work |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your help! I reran the crawler to make a fresh index and seem to be betting an error now when I search anything. The search term I've been using is "sm". I'm getting hits from that search but also getting an error now. I cant seem to find the config options for Algolia crawler anywhere - maybe due to it being created via Netlify integration 🤷 Could it be a formatting issue with my crawler? |
Beta Was this translation helpful? Give feedback.
-
|
I have no idea what is going on 😅 @shortcuts could it be related to the "skip to content" change you did recently? It looks like the search hits do not have a hierarchy for this site, and it's causing problems, and there's a weird mention of "skip to content" in search hits
Yes agree the crawler config is not easy to find in Algolia UI 😅 Go there: https://crawler.algolia.com/admin |
Beta Was this translation helpful? Give feedback.
-
|
Had another look for the crawler config at https://crawler.algolia.com/admin but theres no such option. I found a thread in the algolia community forums with the same issue https://discourse.algolia.com/t/docusaurus-v2-netlify-index-without-results/17662 Seems the poster of that thread also cant find the config. I've made a post there to see if I can get some guidance on accessing it. |
Beta Was this translation helpful? Give feedback.
-
|
It seems that when you use the Netlify plugin to integrate with Agolia search you are unable to access the crawler config. This presents a problem for Docusaurus since it expects the index to be presented in a certain way. As far as I can see the solution at the moment is just to simply avoid using that plugin. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @mikehaart @slorber, sorry I was in vacation :) Indeed, the Netlify x Algolia Crawler integration doesn't natively support DocSearch, and there's no way for you to update the Crawler configuration to make it work properly. A potential workaround would be to use If your project is open-source, just apply there https://docsearch.algolia.com/apply and you'll get a fully working and configurable crawler in no time! :D |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the follow up :) Do you know of any examples of the |
Beta Was this translation helpful? Give feedback.
It seems that when you use the Netlify plugin to integrate with Agolia search you are unable to access the crawler config. This presents a problem for Docusaurus since it expects the index to be presented in a certain way. As far as I can see the solution at the moment is just to simply avoid using that plugin.