-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
sphinx JS search is somehow broken / configuration changed in 7.2, please tell me where "undefined" is coming from #11686
Comments
a good search on alembic shows this
the broken one shows this:
now to find where that comes from |
I think the culprit commit may be 8e730ae (see #11608 (comment)). The comment also says:
Since the basic themes seem unaffected, your custom theme might contain the issue? |
yes it's that commit, as well as a957d6f , and ultimately DOCUMENTATION_OPTIONS is no longer a block inside the layout file. our layout still has this form and I think this is the problem:
i think this is the problem, will close this momentarily |
this has been long supplied by a separate js file, the issue just was not visible until more state was added to this file that was used. References: sphinx-doc/sphinx#11686
thanks that was the issue |
Describe the bug
SQLAlchemy uses a custom theme and sphinx 7.2 seems to have changed something somewhere, I can't find where, but my search results are coming out with all the file extensions as "undefined", note link in the browser toolbar:
I apologize for not tracking this down, which if I dont hear from folks here I'll have to do and also revert sphinx on my site which will take me all day. If I can just get a clue what changed in searchindex.js that suddenly it doesnt know the file extensions (obviously it works fine in my other sites that use built-in themes) that would be super helpful, thanks!
How to Reproduce
go to https://docs.sqlalchemy.org/en/20/
search for any term, like "relationship"
links all stuffed with "undefined"
Environment Information
Sphinx extensions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: