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

Cannot import non-XML preferences, cannot import BibTeX key generator preferences #2021

Closed
jkulesza opened this issue Sep 20, 2016 · 13 comments · Fixed by #2094
Closed

Cannot import non-XML preferences, cannot import BibTeX key generator preferences #2021

jkulesza opened this issue Sep 20, 2016 · 13 comments · Fixed by #2094
Assignees
Labels
keygenerator status: waiting-for-feedback The submitter or other users need to provide more information about the issue

Comments

@jkulesza
Copy link

JabRef version 3.6 on Mac OSX 10.11.6

Steps to reproduce:

  1. Install JabRef 3.6 in a different location than JabRef 3.5.

The Preferences -> BibTeX key generator preferences appear lost.

  1. Import preferences -> browse to preferences location.
  2. Select file format: "All Files" and the format does NOT change (it remains XML file).

Renaming my preferences file from jabref.prefs to jabref.prefs.xml allows it to be selected/imported and I am told to restart JabRef for changes to take effect. When I restart, the BibTeX key generator preferences have not been changed.

@matthiasgeiger
Copy link
Member

I'll have a look.

@matthiasgeiger
Copy link
Member

The keypattern part should be fixed for version 3.6... (see #1704)

@jkulesza Are you using the "portable mode" of JabRef, i.e., your prefs are always saved in an XML file?

Normally JabRef 3.6 should automatically use (and convert) the preferences from earlier versions without manual import as the prefs are stored in a system file/registry.

@jkulesza
Copy link
Author

@matthiasgeiger, No, I'm not (knowingly) using JabRef in "portable mode." I originally installed it, imported my saved preferences (exported on another computer), and then they are loaded on each launch with no action on my part. Only after performing the upgrade did I have a problem.

From your comment, it seems like everything "should just work." However, I assure you that things are as I reported. What can I do to test / help you debug (I'll be in my office tomorrow to try whatever you suggest)?

@matthiasgeiger
Copy link
Member

Okay I was able to solve the problem regarding the automatic preference migration. This is now fixed in the current development builds.

However, this automatic conversion is only performed once (at the first startup of JabRef 3.6 or 3.7dev) - so it will not be executed for you @jkulesza

Please make a backup before any changes and if you have any trouble please upload the prefs file here or send it us privately to developers@jabref.org.

To reenable the automatic migration you'll have to remove a "node" in the preferences stored at ~/Library/Preferences/ - there should be a JabRef related file (sorry I don't have a Mac and I don't know how exactly the file is named). In this file you'll have to remove the \net\sf\jabref\bibtexkeypatterns entry (again I do not exactly know how this is stored at your Mac)

Note for windows users: Remove the node HKEY_CURRENT_USER\SOFTWARE\JavaSoft\Prefs\net\sf\jabref\bibtexkeypatterns using regedit to reenable the automatic migration

@matthiasgeiger
Copy link
Member

Ah... regarding your second problem: Changing the filefilter from *.xml to All files is working for me... Is this problem specific for the preferences import dialog or are all file dialogs affected? (e.g. "File" -> "import into current database")

@jkulesza
Copy link
Author

@matthiasgeiger Sorry for the slow reply; I've been away at a conference.

I've downloaded and installed:
JabRef 3.7dev--snapshot--2016-09-28--master--555944f
mac os x 10.11.6 x86_64
Java 1.8.0_102

Some remarks:

  1. For other users' reference, opening $HOME/Library/Preferences/net.sf.jabref.plist within Xcode and removing the entry cited (bibtexkeypatterns) allowed the preferences to be brought in. Thank you!
  2. Changing from *.xml to All Files appears to only be an issue within the preferences. When I try File -> Import into Current Database, I can change file types as expected. Are there other dialogs I can test against?
  3. Renaming my preferences file to ...xml and importing still does not work (though, with Point New Sorting/Export preferences #1, this is moot).

@jkulesza
Copy link
Author

It's worth noting that I can also not export my preferences in a format other than XML.

@matthiasgeiger
Copy link
Member

Well... The content of the preferences file is always XML-Code - so exporting it only as an XML file is sensible. However, import should be possible regardless of the file extension I think...

@Siedlerchr and @stefan-kolb: Can you investigate the file dialog problem? Should be caused by #1771, #1774 or #1737

@stefan-kolb
Copy link
Member

I cannot reproduce this behavior on the current master. Import and export is working as expected.

@stefan-kolb stefan-kolb added the status: waiting-for-feedback The submitter or other users need to provide more information about the issue label Sep 29, 2016
@matthiasgeiger
Copy link
Member

Mac specific problem?
@chochreiner Can you reproduce this one? 😉

@Siedlerchr
Copy link
Member

Regarding the file dialog, I am not sure, but I think that only XML is set as File Filter. Not sure if you can switch to All files.

@stefan-kolb
Copy link
Member

You can, I tested it.

@chochreiner
Copy link
Collaborator

I can reproduce this bug on MacOS 10.12 on the master

chochreiner added a commit to chochreiner/jabref that referenced this issue Sep 29, 2016
chochreiner added a commit to chochreiner/jabref that referenced this issue Sep 30, 2016
chochreiner added a commit to chochreiner/jabref that referenced this issue Oct 3, 2016
chochreiner added a commit to chochreiner/jabref that referenced this issue Oct 10, 2016
stefan-kolb pushed a commit that referenced this issue Oct 14, 2016
* fixed #2021
* Add a comment why the method is needed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keygenerator status: waiting-for-feedback The submitter or other users need to provide more information about the issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants