-
Notifications
You must be signed in to change notification settings - Fork 372
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
"cannot read property value of undefined" #1041
Comments
Hey Tim! I've fixed this issue in #1039 and will release the new version Monday! This is related to the indexing (as far as I've seen in previous occurences of this bug), with an |
Thanks! By the way, is there an ETA for the official release of the v3? Or is using |
Hey Tim, It's now fixed in the Yes, using the |
@shortcuts Thanks, it's no longer displaying errors. But I have irrelevant results returned now. Duplicate entries that redirect to pages that do not match my query (except in the sidebar) I don't think it is related to my markup, as I'm using the same theme on other websites. Would you want me to create a new issue for that? |
Hey @pixelastic, it seems that you config wasn't using the same template as the other websites, I've pushed an update here: algolia/docsearch-configs#4524 so let me know if it solves it! |
Description
Hello,
On this website, for most of the keywords no results are showing and I have the following error in the console:
Some other keywords seem to work fine.
Steps to reproduce
local
=> errors displayed in the consoleindexed
=> seems to work as expectedLive reproduction:
https://projects.pixelastic.com/reddinx/
Expected behavior
I have DocSearch enabled on a handful of other websites, using the same HTML theme (firost, norska, imoen) and everything is working correctly. This makes me wonder if this is an issue with the js library, or the indexed data/config?
Environment
PS: #trust #candor #care #grit #humility ❤️
The text was updated successfully, but these errors were encountered: