-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Fix links to other versions in mkdocs documentation footer #1634
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
Conversation
The problem was that we didn't had access to the correct page name (the relative path to the source file without the .md suffix). In order for this fix to work mkdocs needs to integrate mkdocs/mkdocs#721 and create a new release.
22dea40
to
76b3d93
Compare
@gregmuellegger - mkdocs/mkdocs#721 has been merged. Is there anything keeping this from being merged. |
mkdocs needs to make a release with this change in it. We could switch to using the development branch of mkdocs, but that feels like a bad solution. |
@ericholscher - I think waiting for the next release of mkdocs makes sense. I'll keep bugging @d0ugal. |
bug away, but I am not going to get to this until next month - getting married makes me super busy |
Congrats!
Hhmm, that would have been last month by now 😉 Would be really happy this issue (and all its dups) would see some progress. I documented a few more links to verify the PR against in my issue #1884. |
@gregmuellegger, is this unblocked by MkDocs 0.15.0? |
I would like to see this one fixed too! I see there's a new MkDocs release as of a couple of days ago. Maybe that new version helps? |
Merging this with the upgraded mkdocs release. |
Fix links to other versions in mkdocs documentation footer
The problem was that we didn't had access to the correct page name (the relative path to the source file without the .md suffix).
In order for this fix to work mkdocs needs to integrate mkdocs/mkdocs#721 and create a new release.
Blocked by mkdocs/mkdocs#721.
Fixes #1480.