zotero-better-bibtex: Error while exporting collection to Zotero-RDF

Hello,

I’ve got errors trying to export some of my collections to Zotero RDF files while BBT is enabled.

Debug log ID:

  • YJMUWV36-euc
  • 6VTRNZ3N-euc (second collection)
  • G52R6DHP-euc (with cache disabled)

It seems that it only concerns elements with the connector’s timestamps (2013-07-11T07:00:00.000Z), as one of my collections without one is exported without error.

There are some errors given in the debug logs, which seem to imply it’s from Zotero or one of the files (?):

[JavaScript Error: "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIFile.initWithPath]" {file: "chrome://zotero/content/xpcom/file.js" line: 47}]
[JavaScript Error: "Error: Unexpected path value 'undefined'" {file: "chrome://zotero/content/xpcom/file.js" line: 56}]
[JavaScript Error: "value must be defined in Zotero.RDF.addStatement" {file: "chrome://zotero/content/xpcom/translate/src/translation/translate.js" line: 2995}]
[JavaScript Error: "value must be defined in Zotero.RDF.addStatement" {file: "chrome://zotero/content/xpcom/translate/src/translation/translate.js" line: 2995}]
[JavaScript Error: "XML Parsing Error: no root element found
Location: http://s3.eu-central-1.amazonaws.com/ping
Line Number 1, Column 1:" {file: "http://s3.eu-central-1.amazonaws.com/ping" line: 1}]
[JavaScript Error: "XML Parsing Error: no root element found
Location: http://s3.ap-southeast-1.amazonaws.com/ping
Line Number 1, Column 1:" {file: "http://s3.ap-southeast-1.amazonaws.com/ping" line: 1}]
[JavaScript Error: "value must be defined in Zotero.RDF.addStatement" {file: "chrome://zotero/content/xpcom/translate/src/translation/translate.js" line: 2995}]
[JavaScript Error: "value must be defined in Zotero.RDF.addStatement" {file: "chrome://zotero/content/xpcom/translate/src/translation/translate.js" line: 2995}]

Thank you for your attention

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 21 (10 by maintainers)

Commits related to this issue

Most upvoted comments

The change to two-part names wasn’t intended to be a solution, just a diagnosis. The new build is the solution. Thanks for reporting this, I’ll roll it out in a new release.