Zotero Upgrade Error
Hi,
I just upgraded to version 5.0 for Mac and got this error message
Error: Invalid field 'accessDate
_fieldCheck@chrome://zotero/content/xpcom/data/itemFields.js:426:13
Zotero.ItemFields</this.getLocalizedString@chrome://zotero/content/xpcom/data/itemFields.js:166:5
getLocalizedName@chrome://zotero/content/xpcom/data/searchConditions.js:654:14
Zotero.SearchConditions</this.init<@chrome://zotero/content/xpcom/data/searchConditions.js:578:23
From previous event:
ZoteroService@file:///Applications/Zotero.app/Contents/Resources/components/zotero-service.js:352:7
@chrome://zotero/content/include.js:4:14
It doesn´t seem to be the DB. Already checked if it was corrupted. Worked before perfectly.
Thanks in advance for any help
I just upgraded to version 5.0 for Mac and got this error message
Error: Invalid field 'accessDate
_fieldCheck@chrome://zotero/content/xpcom/data/itemFields.js:426:13
Zotero.ItemFields</this.getLocalizedString@chrome://zotero/content/xpcom/data/itemFields.js:166:5
getLocalizedName@chrome://zotero/content/xpcom/data/searchConditions.js:654:14
Zotero.SearchConditions</this.init<@chrome://zotero/content/xpcom/data/searchConditions.js:578:23
From previous event:
ZoteroService@file:///Applications/Zotero.app/Contents/Resources/components/zotero-service.js:352:7
@chrome://zotero/content/include.js:4:14
It doesn´t seem to be the DB. Already checked if it was corrupted. Worked before perfectly.
Thanks in advance for any help
If you'd like to do that, can you upload the affected DB to the DB Repair Tool and provide the Upload ID here? You can ignore the download link that the tool provides — this is just to allow us to run some tests on the database file.
Sorry, next time I´ll upload it. Now I know better.
Thanks for the fast response.
And once more, thanks for the interest.
We strongly recommend making sure Zotero stays up to date (which it should automatically, by default), both because of the regular improvements and bug fixes in new releases and also to avoid unexpected problems like this coming from very old versions (though we'll obviously try to avoid problems like this in the future).