add jQuery to get search working in guides #10456
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Sometime after 6.1, search stopped working in the guides.
Which issue(s) this PR closes:
Special notes for your reviewer:
I'm not sure why jQuery can't be found anymore. I found this solution here:
Suggestions on how to test this:
Test the doc preview generated by this pull request. For example, here's a search for "data": https://dataverse-guide--10456.org.readthedocs.build/en/10456/search.html?q=data&check_keywords=yes&area=default
Here is a tarball from
build html, built from this branch: build.tar.gzAnd here is an epub, also build from this branch: Dataverse.epub.tar.gz
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No.
Is there a release notes update needed for this change?:
No.
Additional documentation:
No.