[5.0 Beta] Bug: notes are replaced by others notes

Zotero version: 5.0-beta.200+182cf67


Steps to reproduce:

1) Cclick on a tag in the left pan.
2) In the middle pan, open a "top-level" note (a note without a parent item). Let's call it "Note1". The note doesn't open on the right pan. (This is a bug)
3) Without changing anything, open a "children" note in the middle pan (a note with a parent item). Let's call it "Note2". The note opens in the right pan (as expected)
4) Without changing anything, try to reopen Note1. The note that appears in the right pan is still Note2. (This is a bug)
5) Without changing anything, open another "children" note (Note3). Note3 appears in the right pan (as expected) BUT Note1 is replaced by Note2 (the content of the note and the tags are replaced, but the key in the table " items" from the Sqlite remains the same). This is a huge bug: I lost many important notes before I realized what happened.

  • First, we need a Report ID after reproducing this.
    In the middle pan, open a "top-level" note (a note without a parent item). Let's call it "Note1". The note doesn't open on the right pan. (This is a bug)
    I'm not sure what you mean by "open". If you mean "create", this works for me. It's best to say the exact UI elements and text you're clicking on screen.

    I can't reproduce anything like this, though.
  • edited 6 days ago
    While I still can't reproduce this, I've made a change in the latest beta that might prevent this or similar problems — it'll crash the app if it detects a problem during saving. If you can reproduce it before upgrading, a Report ID would still be helpful, though.
  • By "open", I meant clicking on an existing note displayed in the middle pan, expecting it to be displayed in the right pan so I can edit the existing content.


    I couldn't reproduce the bug today, though it happened yesterday on two different computers (same zotero version) connected to the same zotero account.

    If the bug comes back, I will try to gives you more details.

  • Actually it’s happening again and I think I found the bug. Actually there is two bugs. Forget whatever I say about the tag search, the bug isn’t linked to it.


    ***BUG 1: When an item is permanently deleted, the entries in the table itemRelations pointing to that items are not removed. ***

    Steps to reproduce:
    1) Create 5 notes (NoteA, NoteB, NoteC, NoteZ and NoteY) with some content in it.

    2) Relate NoteA, NoteB, NoteC

    2) Move NoteA to trash and delete it permanently.

    3) When NoteA is permanently deleted, the entries in the table itemRelations for
    NoteB and NoteC that point to NoteA aren’t removed. So NoteB and NoteC are still related to NoteA but NoteA doesn’t exist anymore. NoteB ad NoteC are thus corrupted

    4) Now click on NoteB, it won’t be displayed in the right pan. (Same thing with NoteC) This is where BUG2 starts.


    ***BUG 2: The corrupted items get replaced***

    Steps to reproduce:

    1) After doing the steps in BUG1, click on NoteB and it isn’t displayed on the right pan.

    2) Click on note NoteZ, NoteZ is displayed without any problem.

    3) Click on NoteB, the note displayed in the right pan is still NoteZ

    4) Click on NoteY, the note displayed in the right pan is NoteY but NoteB has just been replaced by NoteZ.


    That would be great if you could add a DB checker that would automatically remove all the entries in itemRelations that point to a non-existing items.


    My zotero version didn’t change, it’s still 5.0-beta.200+182cf67

    +++++
    Another bug:
    Also I notice that simply clicking on some notes (not all) modifies the "Date Modified" of the note : the date displayed for the note in the column "Date Modified" of the middle pan is set to the current date and time even though I didn’t change anything, I simply clicked on it. The content, tags and related items aren’t modified.
  • OK, thanks, I can reproduce Bug 1, and the updated beta I mentioned above (201) does indeed crash Zotero when this occurs, which prevents Bug 2.

    I'll fix this later today.
  • Fixed in 202, available in a few minutes. (Existing orphaned relations aren't removed, for complicated reasons, but a future repair step might clean them up, and they shouldn't cause problems in the meantime.)
  • Thanks a lot for your rapidity. The update 202 didn't come through.
  • Not sure what you mean by that. You can trigger the update manually — look for Check for Updates in the menus.
  • Yes, that's what I meant. My version is still 201 and when I click on "Check for updates", the pop up mentions that no update is available.
  • Vialo is right, no update available
  • Ah, sorry, the other platforms went through but not Windows. The Windows build is available now.
Sign In or Register to comment.