Skip to content
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

Links to files in subdirectories broken in Markdown files #1358

Closed
flaix opened this issue Nov 9, 2020 · 1 comment
Closed

Links to files in subdirectories broken in Markdown files #1358

flaix opened this issue Nov 9, 2020 · 1 comment

Comments

@flaix
Copy link
Member

flaix commented Nov 9, 2020

In a Markdown document a link to another document in a subfolder will not work. The path to the subfolder is not properly escaped in the link.

Readme.md:

This is [a link](sub/file.md) to a document in a sub folder.

Will not properly link to file sub/file.md.

@flaix flaix added Priority-Medium 🐱 Defect Status-Verified A bug could be reproduced. Status-Fixed and removed Priority-Medium Status-Verified A bug could be reproduced. labels Nov 9, 2020
@flaix flaix added this to the 1.9.2 milestone Nov 16, 2020
flaix added a commit to flaix/gitblit that referenced this issue Nov 16, 2020
Add a link parser also for `ExpLinks` because we need to escape paths
to files in subfolders.
This closes gitblit-org#1358
@flaix flaix closed this as completed in b23269a Nov 16, 2020
@TomaszSzt
Copy link
Contributor

Needs to be re-opened. The fix have broken absolute explicit links in MD files.

TomaszSzt added a commit to TomaszSzt/gitblit that referenced this issue Nov 17, 2021
flaix pushed a commit that referenced this issue Nov 18, 2021
* This commit fixes what was broken in commit
b23269a
due to #1358 issue
flaix added a commit that referenced this issue Dec 6, 2021
As with explicit links, also for reference links in markdown documents
which point to repository-relative files the links are broken. They do
not take the path to the repository into account.
This fix is related to commit b23269 which fixed issue #1358
for explicit links.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants