corrupted database! help!
I was creating a search (identifying items not in collections) and I got a message from zotero saying there has been an error please restart Firefox. I did. Now my database is gone! Since I restarted Firefox as per instructions, the backup is no good either. I do have a backup from yesterday but I put in hours and hours of work today updating and changing things and would hate to lose it all. I reported it from the Gear Menu. Help!
I think I will try re-installing zotero first. Any harm in that?
I think I will try re-installing zotero first. Any harm in that?
First, make a backup of your entire Zotero data directory, if you haven't yet.
Next, could you elaborate on "Now my database is gone"? What happens when you start Zotero?
I do have full back up from yesterday and also just made another one.
If you upload your database to the repair tool and e-mail support@zot....org the Upload ID, I'll fix the inconsistent row manually (and try to figure out where it came from—this might also just be a bug in the search infrastructure and not a problem in the database). Ignore the "repaired" database that the tool creates.
Yes, I can't get zotero to do anything... I am trying to manually delete the search, and that won't work either.
These shouldn't happen, obviously. I'll look into making sure any bugs that caused them no longer exist and also try to make Zotero handle such problems more gracefully so they don't require manual fixing.
Thanks.
Thanks for such a speedy response.
I've been thinking back on what I was doing before this happened and I think I had zotero open in two or three of my browser windows. I often do that because I have multiple pages open while browsing and I use zotero a lot. Never had a problem with that before, though.
One of the problems (row in the notes table that wasn't in the items table) might have been from an earlier database migration (1.0.0b4.r1 -> 1.0.0b4.r2, assuming you were using Zotero back in March).
The other was likely from deleting a collection referenced in the saved search. I thought we fixed that bug, but I guess it's back.