-
-
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
Changing entry type does not work when biblatex source is shown #5905
Comments
This should be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out this version. |
@tobiasdiez I have tested it. It seems there is still some issue left. Apparently, the first time the entry type gets changed, it does not get changed. (Subsequent changes seem to work.) Problem case:
Observation: The entry type will not change in the biblatex source and will not be updated in the main entry table and the library is indicated as "modified" (*). Verification: a.) Save library with CTRL+S. Observation: Previous (old) entry type is shown. If after step 6. the entry type gets changed at least another time (so at least twice) then it works. (Despite the fact, that the main table never gets updated.) This behavor can also be reproduced with another (untouched!) entry in the main table. |
This is really strange. Why is just the first one failing? I'm reopening this Issue. |
Does closing/reopening the entry editor help? |
Closing/reopening the entry editor does not help. |
I tried to triangulate the problem a bit. |
* Fix: setting BibEntry to "changed" state before setting a new entry type fixes #5905 * Update changelog
Thanks to @dawidm this issue is now fixed |
I am using the latest JabRef 5 master build:
Java 13.0.2
on Ubuntu 16.04
Steps to reproduce the behavior:
Observation: Commonly, the entry type will not change in the biblatex source and will not be updated in the main entry table.
I think in seldom cases the biblatex source has been updated as expected, but I could not reproduce this intended behavor anymore.
The text was updated successfully, but these errors were encountered: