Zotero Integration Error: a.sortkeys is undefined
Hi,
Anyone else getting this? Cannot find it in discussions on the Forum. Restarting Firefox (16.0.2) each time it occurs solves it for a while, but I don't know what causes it. Using Word 2010 plug-in on Windows 7, Zotero 3.0.8.
Error appears as:
<Zotero Integration Error.
Zotero experienced an error updating your document.
TypeError: a.sortkeys [or b.sortkeys] is undefined.>
Any thoughts?
Anyone else getting this? Cannot find it in discussions on the Forum. Restarting Firefox (16.0.2) each time it occurs solves it for a while, but I don't know what causes it. Using Word 2010 plug-in on Windows 7, Zotero 3.0.8.
Error appears as:
<Zotero Integration Error.
Zotero experienced an error updating your document.
TypeError: a.sortkeys [or b.sortkeys] is undefined.>
Any thoughts?
Does this occur in a new document?
If it doesn't, post again and answer my two question above "are you able to change the citations style (for testing purposes)?
Does this occur in a new document? "
Yes, I can change the style inside Word by clicking Zotero set Doc Prefs. When I Zotero Refresh the document I get the error sometimes.
Sounds like we have a processor bug that needs clearing up. To track down the exact cause, I'll need to reproduce the error at this end. I've tried a few combinations of input that I thought might possibly trigger something, but no errors so far. If you can work out what combination of input or what changes to a document cause the error, I'll take a closer look.
Sometimes, I'm just editing the document for some time and then when I hit refresh I get the 'a.sortkeys' error. Have to quit again both apps and restart for it to go aways. Possibly this is related to having more than one item from the same author and for the same year. You would get Harvard citations like (xxx, 1999a) and (xxx, 1999b)...
Do this help?
After you have a copy of the document, make another copy, and split it into two halves, saving each half as a separate file. Check to see if either half still triggers the error. Repeat the process until you find the minimal document content that triggers the error. Then start removing citations until the error goes away.
It's a troublesome process, but if you have time for it, it will lead us to the exact conditions that trigger the error. We don't have many reports of this, so the information you provide will be very helpful.
http://gsl-nagoya-u.net/http/pub/zotero-processor.xpi
The plugin swaps the revised processor into Zotero. With the plugin installed, documents that were previously affected by the 'a.sortkeys is undefined' error should work correctly.
Looking forward to hearing how it goes.