-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Cannot find linked files #6698
Comments
Just an idea - could you link a file that is found in folder whose path does not contain spaces (in your example "My Local Documents" contains spaces)? I remember, that this caused some issues in the past, but I thought it had been fixed in the meantime. |
The problem persists for path+file names without spaces. Also in the now released 5.1 (portable): |
Hm. Have you changed some fie directory settings? Normally JabRef should store the files as relative links. |
I had the same problem, without changing a file directory setting. It was fixed just by adding the "main file directory" adress, in "Options" ; "Preferences" ; "File". Thank's for the help, @Siedlerchr . |
At some point I started using absolute file links in combination with leaving "main file directory" empty. This worked fine under 5.0, not under 5.1. I now re-introduced a "main file directory" and did a manual serach & replace in my bib files. As a side note, I found out that the absolute paths still work when using this format: (appratently earlier versions of JabRef inserted the double \ wheras the current version inserts single /). |
JabRef 5.1--2020-07-18--ee2c985
Windows 10 10.0 amd64
Java 14.0.2
The portable version.
Under the General tab, linked files are reported as 'cannot find' and attempting to open them has no effect.
In the GUI I see this:
![Untitled](https://user-images.githubusercontent.com/20792626/87862507-3bbd0a00-c951-11ea-9d0c-c43fb51b9f98.jpg)
The Bibtex file portion is
And the file 'c:\Users\hogemajh\AppData\Local\My Local Documents\JEROENX\artikelen\2020\Addanki_2020.pdf' exists on my PC.
It's like this for all linked files; this issue did not occur in previous releases.
The text was updated successfully, but these errors were encountered: