We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
js/open-in-new-tab.js
The plugin injects js/open-in-new-tab.js to the extra-javascript: section here
extra-javascript:
✅ This works fine locally: when using mkdocs serve where I can see the up-right arrow:
mkdocs serve
http://127.0.0.1:8000/
❌ However, this does not work, i.e. I cannot see the up-right arrow: when deployed to my own GitHub Pages with mkdocs gh-deploy --force
mkdocs gh-deploy --force
https://ericbouchut.com/trio-docs/
The /js/open-in-new-tab.js file cannot be loaded (Error 404) because it is in /trio-docs/js/open-in-new-tab.js.
/js/open-in-new-tab.js
/trio-docs/js/open-in-new-tab.js
The items in extra_javascript have changed since Mkdocs version 1.5. This could be a clue.
extra_javascript
I tried to fix things in the plugin code (PR is underway). The fix now works fine in both cases.
I need your guidance and a double pair of eyes.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Description of the Issue
The plugin injects
js/open-in-new-tab.js
to theextra-javascript:
section here✅ This works fine locally: when using
mkdocs serve
where I can see the up-right arrow:❌ However, this does not work, i.e. I cannot see the up-right arrow:
when deployed to my own GitHub Pages with
mkdocs gh-deploy --force
Cause
The
/js/open-in-new-tab.js
file cannot be loaded (Error 404) because it is in/trio-docs/js/open-in-new-tab.js
.The items in
extra_javascript
have changed since Mkdocs version 1.5. This could be a clue.Fix?
I tried to fix things in the plugin code (PR is underway).
The fix now works fine in both cases.
I need your guidance and a double pair of eyes.
The text was updated successfully, but these errors were encountered: