-
-
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
Upgrade from 3.2 to 3.3: BibtexKeyGenerator preferences are lost #1257
Comments
Manually changing the preferences and saving does work? |
Yes, manually updating a key generator entry, saving, quitting, and restarting preserves the change. |
I can confirm, this at least partially... The bug only affects the exported/imported "BibTeX key generator formats": Those settings are not loaded automatically and also import of exported 3.2 settings does not work. Other settings are imported correctly. This is caused by some changes in the casing of the stored information: In JabRef 3.2 the exported XML contains the following: <node name="labelPattern">
<map>
<entry key="article" value="[author][year]"/>
</map>
</node> In JabRef 3.3 this is slightly changed: <node name="labelpattern">
<map>
<entry key="article" value="[author][year]"/>
</map>
</node> --> Quick-Fix for users: Open the exported preferences in a text editor and replace the |
I think we should bring the JabRef preferences and the labelPattern preferences together, and on the way solve this issue as well. |
Lots of old artifacts... <node name="labelPattern">
<map/>
</node>
<node name="logic">
<map/>
<node name="labelPattern">
<map/>
</node>
<node name="labelpattern">
<map/>
</node>
</node> |
Starting from version 3.6 key pattern preferences will bemigrated upon first start of the new JabRef version. |
JabRef version 3.3 on OSX 10.11.4
Steps to reproduce:
The text was updated successfully, but these errors were encountered: