Upgrade Storage1062830147
unable to select a reference:
[JavaScript Error: "Error: Invalid field 'citekey" for base field" {file: "chrome://zotero/content/xpcom/data/itemFields.js" line: 283}]
getFieldIDFromTypeAndBase@chrome://zotero/content/xpcom/data/itemFields.js:283:13
Zotero.Item.prototype.getField@chrome://zotero/content/xpcom/data/item.js:247:19
Zotero.ItemTreeRow.prototype.getField@chrome://zotero/content/xpcom/itemTreeView.js:3490:10
Zotero.ItemTreeView.prototype.getCellText@chrome://zotero/content/xpcom/itemTreeView.js:1076:15
version => 5.0.79, platform => Linux x86_64, oscpu => Linux x86_64, locale => fr-FR, appName => Zotero, appVersion => 5.0.79, extensions => Zutilo Outil pour Zotero (3.3.0, extension), Zotero DOI Manager (1.3.9, extension), ZotFile (5.0.14, extension), Better BibTex for Zotero (5.1.166, extension), LyZ (4.1.1, extension), Zotero LibreOffice Integration (5.0.20.SA.5.0.79, extension), Shockwave Flash (32.0.0.270, plugin), ZoteroQuickLook (1.3.3, extension, disabled)
[JavaScript Error: "Error: Invalid field 'citekey" for base field" {file: "chrome://zotero/content/xpcom/data/itemFields.js" line: 283}]
getFieldIDFromTypeAndBase@chrome://zotero/content/xpcom/data/itemFields.js:283:13
Zotero.Item.prototype.getField@chrome://zotero/content/xpcom/data/item.js:247:19
Zotero.ItemTreeRow.prototype.getField@chrome://zotero/content/xpcom/itemTreeView.js:3490:10
Zotero.ItemTreeView.prototype.getCellText@chrome://zotero/content/xpcom/itemTreeView.js:1076:15
version => 5.0.79, platform => Linux x86_64, oscpu => Linux x86_64, locale => fr-FR, appName => Zotero, appVersion => 5.0.79, extensions => Zutilo Outil pour Zotero (3.3.0, extension), Zotero DOI Manager (1.3.9, extension), ZotFile (5.0.14, extension), Better BibTex for Zotero (5.1.166, extension), LyZ (4.1.1, extension), Zotero LibreOffice Integration (5.0.20.SA.5.0.79, extension), Shockwave Flash (32.0.0.270, plugin), ZoteroQuickLook (1.3.3, extension, disabled)
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
I updated BBT.
It is fixed now.