-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
Direct page links #90
Comments
I will take a look at this |
I spend some hours into this topic and tried to support both cases, even if they are mixed in one environment. Unfortunately there is one edge case which I can't manage. If you have a file (via relative file name) in one folder it will look like this
The problem is, files located in the root folder will look like the same so I can't decide if i need to link to the same folder or the root folder. The only option I see is to implement a setting (variable) to switch between relative and absolute file links. |
its implemented on the dev branch and will be included in the next release. There will be a new setting |
fixed / implemented in 1.5.8 |
there is a little bug in the 1.5.8, its already fixed in the dev version and will be in the next release |
Thanks! Sorry for me not checking my notifications for so long. I see this has already been implimented, so awesome! Had I not been tardy I would have responded as follows:
I would have it only look for such a file in the current local folder. If the user wants to reference something in the root they could just do a Just my 2 cents. :) Thanks for your work on this. |
Is there a way to, instead of relative paths to internal links, we can do an absolute path from root?
EX:
Instead of the following to navigate up and then back down the folder structure:
We could just do this and it would work from wherever this link existed in the site hierarchy:
The text was updated successfully, but these errors were encountered: