"sep is undefined"
I recently upgraded to 2.1.2.r8871 following the Firefox update.
When I attempting to make a Zotero change in my MS Word document,I get the error, "Your document must be permanently upgraded to work with Zotero 2.1 or later. It is recommended that you make a backup before proceeding...." After backing up, when I attempt to make that document upgrade, I get the message,
"Zotero experienced an error updating your document
sep is undefined"
Help! I just defended my dissertation and I need to make some changes before depositing it.
When I attempting to make a Zotero change in my MS Word document,I get the error, "Your document must be permanently upgraded to work with Zotero 2.1 or later. It is recommended that you make a backup before proceeding...." After backing up, when I attempt to make that document upgrade, I get the message,
"Zotero experienced an error updating your document
sep is undefined"
Help! I just defended my dissertation and I need to make some changes before depositing it.
I don't know exactly what content would trigger an error, and I haven't tested to reproduce the behavior, but the bug is clear in the code, and I'll include the fix in the next release of the processor, which will find its way into the next release of Zotero (which will be 2.1.4).
I await 2.1.6.
I added some tracing code to the processor for the 2.1.6 upgrade that should help us identify the root cause of the problem. If you produce a Debug ID that includes a refresh or other operation that triggers the error and post the Debug ID back here, the developers will be able to look at the debug report, and we may be able to get to the bottom of this one.
We can make this more robust by normalizing all quote marks to straight-quotes before running the parser, but for the moment let us know how changing the item manually to that form does for you. If it does fix the problem, we'll be pretty certain we can squash this bug permanently.
Straight quotes in the database should render as curly quotes in the citations and the bibliography, so no worries there.
Actually, I had to change straight quotes in database entries to curly quotes for them to appear as such in the final document.
The converter at least gives the "sep is undefined" error. If a "parsing issue" combination of characters remains in the database and an attempt is made to add a citation with that combination, the add/edit window just stops operating for that and any subsequent citation add/edit operations to that or any other citations and there is no error message. (I happen to know what is causing the problem and made the appropriate "parsing issue" corrections.) MS Word needs to be fully shut down and restarted to continue working.
The unrelated error, and this is new since the move to 2.1.x, may be peculiar to the "Chicago Manual of Style (Full note with Bibliography)" style which I use. A subsequent entry of a database item that ends in a quotation mark that is not the last of a multiple-entry citation does not terminate with proper punctuation.
Here's an example of what occurred in the past, focusing on the punctuation concluding the "Grady" citation. (I do not claim that what occurred in the past was correct punctuation, but it sufficed for footnotes.):
Grady, “The Seminary of Tomorrow, 1970”; “A Commentary on Seminary Priesthood Enrollment Statistics for 1984,” 3-4.
Here's an example of what is now occurring:
Grady, “The Seminary of Tomorrow, 1970.”; “A Commentary on Seminary Priesthood Enrollment Statistics for 1984,” 3-4.
If the situation is to be corrected, here's an example of what I believe to be the proper result:
Grady, “The Seminary of Tomorrow, 1970;” “A Commentary on Seminary Priesthood Enrollment Statistics for 1984,” 3-4.
Thank you all for applying your skills and donating your time to this worthy endeavor.