Sync Error

When I tried to sync, "Conflict Resolution" window appeared. So I clicked the "Next" button to proceed. However, in the 10th item, the window disappeared, and sync process was stopped.
Error message was "getFileName() can only be called on attachment items in Zotero.Item.getFilename()", and Repot ID is 835957066. The Debug ID is D1416345621.
Please help!
  • I have the same problem
    Report ID 1385941326
  • I am having the same problem.

    Report ID: 47678644
    Debug ID: D728269177
  • edited January 15, 2010
    I'm still having this problem. This same problem is also posted to a forum here. The conflict resolution screen comes up related to attached files that have been moved or deleted, but I have tried deleting those entries entirely and re-uploading the troublesome parts of my library and get the exact same conflict resolution screen.

    Any help would be greatly appreciated as a group is trying to collaborate with a shared library.

    Report ID: 1628591081
    Debug ID: D536805937
  • I had a similar problem (http://forums.zotero.org/discussion/10479/sync-fails-after-deleting-local-files-added-a-quickdirty-fix) and I found something that may work for you as well.

    Most likely, the error is due to a change of type (e.g., from attachment to note) that the wizard does not detect. If you can access and change zotero/chrome/content/zotero/bindings/merge.xml
    you can try to change

    if (this._leftpane.ref == 'deleted' && this.type == 'item') {

    into

    if (this._leftpane.ref == 'deleted') {

    But keep in mind that you do it at your own risk, I have a very limited knowledge of Zotero code. Hopefully we will get some feedback on this.
  • Hi, I'm having the same problem. I reported it: report ID is 788093718.

    I also sent a debug log, D1384252709, although I see now that debug logs are generally done at the request of a zotero developer, so sorry for that.

    I do hope there is a fix for this problem.
  • These conflict resolution errors are fixed in Zotero 2.0rc3.
  • Thanks! All fixed.
Sign In or Register to comment.