mkdocs-pdf-export-plugin: Links in combined PDFs are still broken

ANy news ? I used the use_directory_urls to false, but the error is always here for subdirectory link…

Sorry to drop this, was away for a couple of weeks!

This workaround fixes one problem – I no longer get pointed at local files – but it looks like there was another issue hiding behind that one.

Now that the local file links are fixed (or worked around), some links work, but some links just render as styled text that doesn’t go anywhere.

• Links in pages at the root docs/ level, to other pages at the same level, work as expected 🎉.
• Links in pages at the root docs/ level with anchors, like [link](file.md#heading), or with only anchors, like [link](#heading), do not work.
• Links in pages under subfolders (for example, docs/folder/file.md) seem to never work no matter what.

I’ve expanded my test project to show these individual cases. If I can add test cases that would be helpful for you, I’m happy to build it out further. Also if this looks like a totally different issue to you, we can close this off and start a new one.

Revised test project: pdf-link-test-project.zip

Rendered PDF: test.pdf

Build output (not verbose this time because whoa): output.txt

Here’s the test project I’m using. I was curious if it was a Windows issue so opened the project on a Linux/Ubuntu desktop but am seeing the same behavior; PDFs are created successfully but links are pointing to local files instead of locations within the PDF. I also get errors for each head tag in the project, as above (this one is slightly different than my original report because I re-created everything from scratch).

ERROR: No anchor #/.:pdf-export-test-project for internal URI reference
ERROR: No anchor #/.:pdf-export-test-project for internal URI reference
ERROR: No anchor #/.:pdf-export-test-project for internal URI reference
ERROR: No anchor #/.:pdf-export-test-project for internal URI reference
ERROR: No anchor #/.:subheading for internal URI reference

Other details that may be useful:

• Weasyprint: 45
• mkdocs-pdf-export-plugin: 0.5.3
• mkdocs: 1.0.4
• mkdocs-material: 4.0.1 (also tested with 3.2.0)
• Linux/Ubuntu 18.04 (also tested with Windows 10)
• Python 3.6.7

Project: test.zip

Generated PDF: combined.pdf

Verbose build output (or most of it anyway, it filled up my buffer so we’re missing the beginning) console-output.txt

Thanks again for looking into it!

@CaptainQuirk sorry, forgot to watch my notifications. I cobbled together a solution for this (actually completely rebuilt the path generator) and it works for our team, but I wasn’t able to submit a PR here and then forgot about it.

I’ve forked this project and updated it with my code, you’re welcome to use it (the fork is not registered with pypi so you can’t use pip to install it, you’ll need to install it manually or copy the plugin files over this install.

https://github.com/erilot/mkdocs-pdf-export-plugin

@zhaoterryy I would be happy to submit this as a PR here but i think you have to allow that.

I found the issue. For the time being, use_directory_urls must be set to false. https://www.mkdocs.org/user-guide/configuration/#use_directory_urls

Need to write a separate href builder for directory urls.

Is there any work planned for supporting directory urls? Please let me know how we can help on getting this awesome feature in 😃

Not only broken, but unclickable.

I’m also experiencing the same with the latest version 0.5.5. Is there any setting we have to put in place to make this work?

I found the issue. For the time being, use_directory_urls must be set to false. https://www.mkdocs.org/user-guide/configuration/#use_directory_urls

Need to write a separate href builder for directory urls.

On my part, trying out the 0.5.3 version didn’t solve my problem in #42.

I still get No anchor #cp/show/:charge-de-communication for internal URI reference for the markdown construct En tant que [Chargé de communication](../glossaire.md#charge-de-communication)

👍 for the appreciation of the whole project