Syncing not working with MLZ [ItemID not set for object before attempting to load data]

bjoern_mueller
Hello,

syncing has not worked for a long time, now I changed to MLZ and it persists not working.

version => 4.0.26m501, platform => MacIntel, oscpu => Intel Mac OS X 10.8, locale => de-DE, appName => Firefox, appVersion => 35.0.1, extensions => Zotero Word for Mac Integration (3.5.7, extension), Zotero LibreOffice Integration (3.5.9, extension), RTF/ODF Scan for Zotero (1.0.22, extension), Zotero Auto Index Plugin (0.0.33, extension)

When attempting to sync, I first go through some syncing dialogues making me choose the correct version to keep, and then it stops with the error "ItemID not set for object before attempting to load data". The error report cannot be sent (error message: no valid answer from repository (in German)). It lists a whole bunch of JavaScript errors having to do with pdfs that are allegedly not indexed: for example like

[JavaScript Error: "Mandelli et al. - The construction of network identity a central pr.pdf was not indexed" {file: "chrome://zotero/content/xpcom/fulltext.js" line: 515}]

and then it lists the following:

No chrome package registered for chrome://dta-modules/content/support/filtermanager.js
No chrome package registered for chrome://dta-modules/content/support/filtermanager.js

What can I do?

Thank you very much.
B
  • adamsmith
    you're using MLZ Zotero. You need to mark that in the title of your thread (change it by editing your first post) so that MLZ's developer sees it. Always do that when reporting errors while using MLZ.

    First thing I'd try is if disabling auto-index helps, but after that, fbennett will have to take this.
  • bjoern_mueller
    ok, thanks. tried disabling auto-index to no avail. the syncing still does not work and the error mesage persists.
    fbennett, any ideas?
  • fbennett
    A question first: were you getting this error in sync failures before installing MLZ, or is it a new symptom?
  • fbennett
    Answering my own question here: the error is definitely an MLZ bug. Working on a fix for it.
  • fbennett
    The MLZ bug should be fixed now. If you still get a sync error after updating the client, post again and we'll look further.
  • bjoern_mueller
    Thanks! It works! Much appreciated!!
  • fbennett
    Thanks are due from this end, too, for your report. That bug has been lurking in MLZ forever - there was an old comment in the code about exactly this error, with a question mark over whether it had actually been resolved. MLZ multilingual fields now respond to that condition (an item removed or added during conflict resolution, I think) in exactly the same way as first-class Zotero fields.

    There should be no further problems from this one, but if you hit any other snags, just give a shout.

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.

Sign In or Register to comment.