Incorrect flyout links for Mkdocs

[marcelstoer]

http://nodemcu.rtfd.org/ is a MkDocs/GitHub based RTD project. I noticed recently that the links in the RTD footer (fly-out menu) are totally borked, all 404 there.

I maintain localized .md files in the same docs directory but I don't know if that's got anything to do with it. GitHub: https://github.com/marcelstoer/nodemcu-firmware/tree/dev-rtd/docs

• on http://nodemcu.readthedocs.org/en/dev-rtd/en/ (docs/en/index.md)
  • "Versions dev-rtd" points to http://nodemcu.readthedocs.org/en/dev-rtd/Home/, where does "Home" come from
  • "On GitHub View" points to https://github.com/marcelstoer/nodemcu-firmware/blob/dev-rtd/home/docs/checkouts/readthedocs.org/user_builds/nodemcu/checkouts/dev-rtd/docs/Home.md
• on http://nodemcu.readthedocs.org/en/dev-rtd/en/build/ (docs/en/build.md)
  • "Versions dev-rtd" points to http://nodemcu.readthedocs.org/en/dev-rtd/Building%20the%20firmware/ which is doubly wrong
  • "On GitHub View" points to https://github.com/marcelstoer/nodemcu-firmware/blob/dev-rtd/home/docs/checkouts/readthedocs.org/user_builds/nodemcu/checkouts/dev-rtd/docs/Building%20the%20firmware.md

I report it here (rather than e.g. with the RTD theme for MkDocs) because the content for that fly-out menu is provided by an RTD AJAX call to https://readthedocs.org//api/v2/footer_html/.

[agjohnson]

This sounds like a duplicate of #1480, which would be fixed with #1634, though we require a mkdocs release. Feel free to reopen if that does resolve these issues.

[marcelstoer]

This sounds like a duplicate of #1480

Indeed, thanks a lot. Surprizes me that my earlier GitHub issues search didn't find the dup.

[agjohnson]

Great. To be fair, the title of the original issue didn't describe the issue best -- I've updated it for future reference :)

[dnrce]

AFAICT #1480 only covers half of this. I reported #1917 regarding the GitHub URLs.

[marcelstoer]

True, thanks for reporting. That faulty GitHub link is even in the description of this issue 😦.

[agjohnson]

Indeed, I missed this scanning too quickly. Someone can address this issue at #1917