-
-
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
Trouble importing after upgrading to Jabref 3.0 #479
Comments
Hi, Either from the terminal or from the error console (Help -> Show error console). Thanks! |
user.language=en |
Thanks, for this information - but we need the complete call hierarchy which led to the "NullPointerException" you mentioned before (this is called stacktrace) to investigate the issue. You should find this in the Error console. |
Hi Matthias, Thanks for the quick response. I tried to check the help --> show error console in jabref. Its showing a blank "output" tab. Its the same with "exceptions". I have attached a screenshot. Also please find attached the log file generated during installation. Since I couldn't attach a file name with .log extension, i changed it to .txt Thanks a lot for your help |
Oh, look at the exceptions tab instead. The output tab should really be removed as we try to get rid of all printouts there and rely on logging and exceptions. |
Hi, First of all, many thanks for all the great work you put into the new version! Looks awful and has some nice new features! Working on OpenSuse 13.1 I can confirm the above problem. Actually, I cannot import any files like *.bib or *.ris using Crtl-I. I get the error message "No entries found. Please make sure you are using the correct import filter." No output in the error console. To be sure, I did import exactly the same files with Jabref 2.11 a minute ago. Actually, when I remember correctly, in pre-2.11 versions one did not even have to select the proper file type (RIS, BIBTEX etc) which became necessary at least with 2.11. Thanks!! |
@tobiasdiez Could it be that we changed the behavior @pukk Why aren't you opening BibTeX files with the normal File-Open-Functionality? 😇 |
I want to include a reference into an existing database. Actually, using File-open with the same *.bib file works but opens a new database. That's not what "Import into current database" is supposed to do, isn't it? In addition, in my standard workflow I do use a one-line script called from within Firefox. The one-line script reads java -jar ~/bin/JabRef.jar --importToOpen $(readlink -f $1) This worked flawlessly with Jabref 2.11 but not with 3.0. Nothing happens when calling this using Jabref 3.0. Maybe the two problems are connected. |
as PUKK pointed out everything was fine until i upgraded to 3.0. |
@pukk @mazeratti Please double check that you have "Listen for remote operation on port: 6050" enabled. (Preferences/Advanced). Regarding "asap", @mazeratti did you check our backing page? |
@koppor Yes, "Listen for remote operation on port: 6050" was enabled in my tests. Is there any debugging option or similar, so that I can help nailing down the problem? |
In "Help/Error Console". What is said in the tab "Output" and "Exceptions"? Maybe restart JabRef to have the output cleaned. Further, what is the output of the script calling On my quick experiments (on Windows 8.1), the import dialog was hidden somewhere behind. I could get it working when JabRef was shown next to the browser window. |
The "Output" indeed shows (I overlooked before that I need to close and reopen the error console to get an update): And yes, I might have been wrong and not seen the hidden import dialog (which was up front in 2.11). So indeed the BibTeX import seems to work as originally reported by @mazeratti (sorry for the confusion on my side). Still RIS (and probably other formats) have a problem. Thanks for the quick feedback!! |
Could you please try the following: Open the import dialog, chooser your file and (this is important!) also select the importer from the drop-down below (titled "Files of type"). After this the format should be recognized. @Developers: // net.sf.jabref.importer.ImportFormats
FileFilter ff = fc.getFileFilter();
ImportFormat format = null;
if (ff instanceof ImportFileFilter) {
format = ((ImportFileFilter) ff).getImportFormat();
} |
For my tests I use, for example, inputs from the American Chemical Society. Here an example so that you maybe can better reproduce my issue Now using "File ->Import into Current Database" I cannot import neither the BIB nor the RIS files from the above link. As stated in my original post, I get the error message Using --importToOpen the error console statements are given in my previous post and only the BIB |
@koppor Yes “listen for remote operation on port 6050” is enabled @tobiasdiez I tried importing a .ris file by selecting RIS filter but I am receiving the error message “No entries found. Please make sure you are using the correct import filter” and as previously mentioned no messages in help -> error console -> output or exceptions |
While you look at fixing the import issues which did work before in 2.11, there are enhancements which would be nice to have (and were not there in 2.11):
Thanks for considering these issues and again thanks for all your effort and time!!! |
Hi, Is there a way to download 2.10 dmg file ? Till the new version is released I would like to work with 2.10. I have also noticed that V 3.0, does not remember the last folder opened. For ex. if I want to import the downloaded .ris or .bib file each time I have to show the path to the downloaded folder. The default is the folder where my jabref database is stored. For the previous versions this was not the case. |
The Mac Zip file for 2.10 is still available at sourceforge here: http://sourceforge.net/projects/jabref/files/jabref/2.10/JabRef-2.10-OSX.zip/download Sorry, I still had not found the time to investigate the importing issue - hopefully in the next few days... |
Thanks for the info Matthias. I had already tried that link. jabref file downloads but when I try to install it I am getting the error message that the file is damaged. Is there any other source from where I could download it ? I tried a couple of them, but almost all of them points to the newer version jabref V 3.0. |
@mazeratti Could you please check our Mac OS X FAQ? Does it help? Possibly 2.11 beta 3 might also still run on Mac OS X: https://sourceforge.net/projects/jabref/files/jabref/2.11%20beta%203/. It should be fine to use. Only the "special fields" functionality is broken there. |
@koppor Thanks a lot!!. that worked. JabRef-2.11b3-OSX.zip did not work but JabRef-2.11b3-OSX-Java6.zip worked.Import function works without any problem now 😊 Jabref 2.10 worked after disabling the firewall. Normally when the firewall blocks, the message says you cannot open it from an unidentified developer but when you right click and open, it works. That wasn't the case here, so I thought it had something to do with the file itself. Sorry for not checking up the FAQ, I was not aware that the firewall caused it. Once again thanks for the help you all extended. Hope the bug in V 3.0 will be fixed in the next update. Between, I also did not know that I can support jabref by ordering books from amazon via the link provided. Is there a more detailed info about the same ? If i click the link, it opens up a few selected books. Is the supported limited to those books only ? or can I order a book of my choice via the link. |
@mazeratti You can order anything you like. The important thing only is to start from the link. I'll update the text accordingly the next days. |
I think, this is solved via boceckts@b773a12. I don't know, why it worked earlier. The |
Yes, #531 fixes the issue of "importing not functioning". Thanks!! BTW, I would still be happy if my above enhancement suggestions would be considered :-) |
@koppor Thanks for the fix 😊 It works now |
Hi,
After the upgrade, I can only import .bib files. no other formats e.g. .ris, works. I am using jabref on OS X El Capitan (10.11.1). I got this error while installing:
an error occurred java.lang.nullpointerexception
The text was updated successfully, but these errors were encountered: