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

Upgrade from 3.2 to 3.3: BibtexKeyGenerator preferences are lost #1257

Closed
jkulesza opened this issue Apr 20, 2016 · 6 comments
Closed

Upgrade from 3.2 to 3.3: BibtexKeyGenerator preferences are lost #1257

jkulesza opened this issue Apr 20, 2016 · 6 comments
Milestone

Comments

@jkulesza
Copy link

JabRef version 3.3 on OSX 10.11.4

Steps to reproduce:

  1. Install 3.3 on OSX, selecting to replace 3.2.
  2. After installation, launch Preferences, and note that there are differences (most notably in hand-specified BibTeX key generator formats.
  3. Attempt to reimport old preferences file. Choose preferences file, click OK. A dialog shows "You must restart JabRef for this to come into effect." Click OK. Click OK. ⌘-Q to Quit fully.
  4. Relaunch and note that preferences are not updated.
@matthiasgeiger
Copy link
Member

Manually changing the preferences and saving does work?

@jkulesza
Copy link
Author

Yes, manually updating a key generator entry, saving, quitting, and restarting preserves the change.

@matthiasgeiger matthiasgeiger added the bug Confirmed bugs or reports that are very likely to be bugs label Apr 20, 2016
@matthiasgeiger
Copy link
Member

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>

--> labelPattern vs. labelpattern (small vs. capital P)

Quick-Fix for users: Open the exported preferences in a text editor and replace the labelPattern with labelpattern, save the file and import again in JabRef 3.3.

@matthiasgeiger matthiasgeiger changed the title OSX Upgrade from 3.2 to 3.3 Loses Preference, Cannot Re-import Upgrade from 3.2 to 3.3: BibtexKeyGenerator preferences are lost Apr 21, 2016
@simonharrer
Copy link
Contributor

I think we should bring the JabRef preferences and the labelPattern preferences together, and on the way solve this issue as well.

@stefan-kolb stefan-kolb added this to the v3.4 milestone May 12, 2016
@stefan-kolb stefan-kolb modified the milestones: v3.5, v3.4 Jun 2, 2016
@stefan-kolb
Copy link
Member

Lots of old artifacts...

          <node name="labelPattern">
            <map/>
          </node>
          <node name="logic">
            <map/>
            <node name="labelPattern">
              <map/>
            </node>
            <node name="labelpattern">
              <map/>
            </node>
          </node>

@stefan-kolb stefan-kolb added status: wontfix Bugs or suggestions that we are not able to fix or don't have the resource to implement. and removed bug Confirmed bugs or reports that are very likely to be bugs labels Aug 9, 2016
@matthiasgeiger matthiasgeiger removed the status: wontfix Bugs or suggestions that we are not able to fix or don't have the resource to implement. label Aug 11, 2016
@matthiasgeiger
Copy link
Member

Starting from version 3.6 key pattern preferences will bemigrated upon first start of the new JabRef version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants