Jabref: Changes in Source Tab are not saved correctly without switching to another tab

[Doc73]

JabRef version 4.0-beta2 on Debian 9 Stretch AMD64

Steps to reproduce:

1. Add a book entry
2. Add title, author etc. and save
3. Add subtitle and save
4. Switch to another entry
5. Return to the previous entry --> subtitle disappeared!!!!

It is very annoying and happens also with other fields.

[koppor]

Which java version? Did you try our latest build? You can also try snap install jabref --edge --devmode. - snapd should be available at Debian testing.

[matthiasgeiger]

Hi @Doc73,
I cannot reproduce the problem on my machine with your description neither using the 4.0-beta2 nor using the most recent dev builds...

Can you please check whether this problem is also present in the dev builds available from https://builds.jabref.org/master ?

[Doc73]

Dear all,
I use latest openjdk-jre version available in Debian Stable repositories, i. e. 8u141-b15-1~deb9u1, with openjfx v. 8u111-b14-1.

I can reproduce it sistematically with beta2. Try this way:

1. Add a book with author, title, date, key
2. Search the item with a field common to other items, in order to have other items in table with the one just added.
3. In biblatex source editor, add ex. gr. titleaddon
4. In the table, switch with arrows to another item
5. Return to previous item

Later I'll try dev builds.

EDIT
From other tests, it seems that the issue happens whenever I add an entry in source editor.

[Doc73]

I can confirm that the real issue is that every changes made directly into the source editor are not saved, even if you press the CTRL+S keys. :-(

[matthiasgeiger]

Thanks for the clarification.

I can now reproduce the problem in 4.0-beta2 and master: Changes in the source tab are not stored when switching to another entry.
However, if you switch to another tab first before selecting another entry this problem does not happen. This might be a workaround for you.

Potentially related to #2946 resp. 03861a35028f162bf0034a143648641ca93aee7c - @tobiasdiez can you check whether this is easily solvable?

//Edit: Also related https://github.com/JabRef/jabref/issues/3063

Best regards,
Matthias

[Doc73]

@matthiasgeiger
Yes, I noticed this workaround.
BTW, thank you very much!

[lenhard]

@Doc73 @matthiasgeiger I think I have fixed this. Can you please try out http://builds.jabref.org/fix-sourcetab-update/ and see if it works for you?

[Doc73]

@lenhard
Many thanks! It seems working!

[wujastyk]

Problem: in editor, bibtex source tab not updating.

Steps:

1. add article
2. go to optional fields, add DOI
3. fetch DOI data and accept "replace"
4. Fields all okay in Required tab
5. All fields blank in Bibtex source tab.

JabRef 4.0-dev--snapshot--2017-08-11--master--18fffc6b9
Linux 4.8.0-58-generic amd64
Java 1.8.0_144

[matthiasgeiger]

@wujastyk This should also be fixed by the change of @lenhard I just merged into the master branch.

Please try the newest version from https://builds.jabref.org/master. Thanks!

[wujastyk]

JabRef 4.0-dev--snapshot--2017-08-13--master--ce5038dd3
Linux 4.8.0-58-generic amd64
Java 1.8.0_144

Problem persists. Exactly as previously described. :-(

On 13 August 2017 at 21:06, Matthias Geiger [e-mail]
wrote:

@wujastyk https://github.com/wujastyk This should also be fixed by the
change of @lenhard https://github.com/lenhard I just merged into the
master branch.

Please try the newest version from https://builds.jabref.org/master.
Thanks!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JabRef/jabref/issues/3086#issuecomment-322060782, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAuhhtdhgSxqttsuN7WI-PgDkQhq6cJUks5sX0k8gaJpZM4OwY5r
.

[lenhard]

@wujastyk I've tried with the same JabRef version, but on Win7, but I cannot reproduce your problem. Can you give a DOI? I do the following:

1. add article
2. go to General fields tab, add DOI https://doi.org/10.1016/j.future.2017.01.006
3. Click get BibTeX data from DOI
4. Click replace
5. All fields properly populated in the required tab and and in the BibTeX source tab

[wujastyk]

I do the same, but I enter the doi in the Optional Fields tab

Sent from Android phone

On 14 Aug 2017 9:46 am, "Jörg Lenhard" [e-mail] wrote:

@wujastyk https://github.com/wujastyk I've tried with the same JabRef
version, but on Win7, but I cannot reproduce your problem. Can you give a
DOI? I do the following:

1. add article
2. go to General fields tab, add DOI https://doi.org/10.1016/j.
   future.2017.01.006
3. Click get BibTeX data from DOI
4. Click replace
5. All fields properly populated in the required tab and and in the
   BibTeX source tab

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JabRef/jabref/issues/3086#issuecomment-322121835, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAuhhixF8ZohtNoHz8qqOjpzX65px0QTks5sX_tegaJpZM4OwY5r
.

[koppor]

@wujastyk Did you customize your entry types somehow? (http://help.jabref.org/en/CustomEntryTypes)

[matthiasgeiger]

I was able to reproduce the problem and I opened #3103 for this bug.

[wujastyk]

Yes.

Now offline for the rest of tge day, flying Vienna-Edmonton.

Sent from Android phone

On 14 Aug 2017 10:49 am, "Oliver Kopp" [e-mail] wrote:

@wujastyk https://github.com/wujastyk Did you customize your entry
types somehow? (http://help.jabref.org/en/CustomEntryTypes)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JabRef/jabref/issues/3086#issuecomment-322133589, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAuhhhiIZyp5CmDObBvwXAmHOGsr0f_Qks5sYAongaJpZM4OwY5r
.

[matthiasgeiger]

Have a good flight!
Should now be fixed in recent master builds.

[wujastyk]

Yes, with

JabRef 4.0-dev--snapshot--2017-08-14--master--0b779cdc4
Linux 4.8.0-58-generic amd64
Java 1.8.0_144

this bug is fixed. Thanks!

Dominik

On 14 August 2017 at 20:49, Matthias Geiger [e-mail]
wrote:

Have a good flight!
Should now be fixed in recent master builds.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JabRef/jabref/issues/3086#issuecomment-322275957, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAuhhuRwGk4_1VNEUKqxrYF2gUfWzYjGks5sYJbUgaJpZM4OwY5r
.