-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Algolia search broken after new release #3391
Labels
bug
An error in the Docusaurus core causing instability or issues with its execution
Comments
slorber
added
the
bug
An error in the Docusaurus core causing instability or issues with its execution
label
Sep 2, 2020
If you want to add several values for a specific meta tag, you will need to follow this template: <meta name="docsearch:version" content='["2.0.0-alpha.62","latest"]' /> Please note the use of single quote and double quote. The value of the |
slorber
added a commit
that referenced
this issue
Sep 2, 2020
…arch/Algolia, so that on new version publish, search still works even if new version is not already indexed (#3391)
Followed up on Discord. We need simple quote here. |
slorber
added a commit
that referenced
this issue
Sep 3, 2020
* We should create an alias for searching last version of docs on DocSearch/Algolia, so that on new version publish, search still works even if new version is not already indexed (#3391) * commit missing snapshot * update after algolia changes * put back facetFilters: [`version:${versions[0]}`] until latest facet is indexed
So, it seems it worked, search is not broken just after the alpha 63 release :) Next will be contextual search: #3396 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Bug Report
Everytime we publish a new Docusaurus release, the Algolia search fets broken for a while, until the new version is indexed.
@s-pace said:
@francoischalifour said a temporary solution would be to send an empty PR to https://github.com/algolia/docsearch-configs/blob/master/configs/docusaurus-2.json: as they merge it, it would trigger site reindexation
This problem is likely because we use a new facet due to the new release:
I think we should find a way to keep the facet filter constant so that search does not break.
Implementation idea: using "version aliases" (does not exist yet: #3285), so the latest version would always be at
/docs/latest
, and we could use a constant facet instead:So when we publish a new version, search will temporarily be a bit stale, but won't break.
In the meantime, @s-pace @francoischalifour do you know if it's possible to add the
"docsearch:version
header multiple times?If yes we could also do this on pages of the latest version:
The text was updated successfully, but these errors were encountered: