-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
added file link has absolute instead of relative path #4241
Comments
Duplicate of #4201 Thank you for reporting this issue. We think, that is already fixed in our development version and consequently the change will be included in the next release. We would like to ask you to use a development build from https://builds.jabref.org/master and report back if it works for you. Please remember to make a backup of your library before trying-out this version. |
Thanks for the very quick response! I tested the latest master and the issue does not seem to be solved. Version: I can provide further info if needed. |
I found the issue. The file only gets relativized if you hit the browse button. |
Thank you for reporting this issue. We think, that is already fixed in our development version and consequently the change will be included in the next release. We would like to ask you to use a development build from https://builds.jabref.org/master and report back if it works for you. Please remember to make a backup of your library before trying-out this version. |
I just tested the latest master and development snapshop. The file attachment is still not working. I've tried adding via General -> "+" and via right clicking on the enry. Win 7, 64bit |
@dropbearII what exactly is not working for you? |
JabRef version 4.3.1 on Windows 10
Jabref generates an absolute path to file if the relative path would "climb" the directory tree
Steps to reproduce:
0. assume you have a file "C:\foo\file.pdf"
Note that JabRef (at least on Windows) still handles correctly relative paths which include ".." (or start with "\") as long as you type them yourselves.
The text was updated successfully, but these errors were encountered: