[MLZ] "blob.alldecor is undefined" error

I get the following error after the MLZ update of this morning. This is from a document that was updating perfectly as late as last night.
Zotero experienced an error updating your document. blob.alldecor is undefined.
Does it have anything to do with the latest MLZ update?
  • It's not impossible that something in the update triggered the error, but as far as I can tell, nothing in the citation processor has changed since early December of last year.

    In any case, we'll want to track down the cause. I'll need some more information to work from. Does this happen with all styles, or only with a particular style? If it only happens with a particular style, does the style pass validation? If it happens with multiple styles, please go through the steps for debugging broken documents. The steps should either clear up the issue, or leave you with reference (or smaller subset of references) that trigger the error. Once you have that, I can take a look.
  • Does this happen with all styles, or only with a particular style?
    ==> It happens with only one document. I can't tell if the same document will work with another style, because I can't switch style due to the error. In any case, other documents with the same style refresh without an error.

    If it only happens with a particular style, does the style pass validation?
    ==> It fails the validation due to the space in the prefix=" (", which was discussed in another thread. Other than that, it passes the validation.

    I went through the troubleshooting on https://www.zotero.org/support/word_processor_plugin_troubleshooting#debugging_broken_documents, and fixed the document. Here is how I did it: I deleted one pageful of the document from the beginning sequentially until the document no longer triggered the error. Assuming that the last deleted page contained the error, I undid the deletion (by pressing Ctrl+Z) for closer examination. But at this point the document no longer triggers the error, although that same document prior to the deletion & undeletion triggered the error. It is as if a mere deletion & undeletion, which does not change any content of the document, fixed the problem. Mysterious.
  • That's odd, but it's good to know your document is back with us. If it bites again, we'll take another look.
  • Yes, it came back to bite again and, through elimination, I found the problematic reference. How do you want me to pass it along to you? Via email?
  • That would be great. With the style and the reference as Bibliontology RDF, I can take a look and see what's up with this one.
  • This has now been fixed in the latest update. My apologies for the misstep -- there was a bug in the MLZ function that prepares data for submission to the CSL processor.
Sign In or Register to comment.