Chrome connector cannot save articles from SAGE journals to server

timfisken
Using the Chrome connector, I find I can save articles from SAGE journals fine if Zotero Standalone is running, but I cannot save articles to the Zotero server when Zotero Standalone is not running. The first time I attempted to save an article from Chrome with Zotero Standalone not running, a window popped up asking me to log in to Zotero, which I duly did, but the article was not added to my library. Subsequent attempts to save an article from Chrome without Zotero Standalone running produced no response at all.

Other journals seem to work whether or not Zotero Standalone is running.

I'm using Chrome 24.0.1312.57 on Linux (Ubuntu 12.10) with Zotero Connector 3.0.8.1 and Zotero Standalone 3.0.11.1.

I've enabled logging in the Chrome Connector extension, and submitted Debug Report D342260021. When producing this report, I did the following:

1. Started Zotero Standalone
2. Loaded http://ptx.sagepub.com/content/41/1/160.full.pdf+html?rss=1
3. Clicked "Save to Zotero (Hotwire 2.0)" icon in Chrome address bar.
4. (Received no feedback in Chrome, but item appeared correctly in Zotero Standalone)
5. Closed Zotero Standalone
6. Loaded http://ptx.sagepub.com/content/41/1/160.full.pdf+html?rss=1
7. Clicked "Save to Zotero (Hotwire 2.0)" icon in Chrome address bar.
8. (Received no feedback in Chrome, item not added to Library on Zotero server).
  • adamsmith
    Confirmed same behavior using the bookmarklet.

    (You should update Zotero to 3.0.13 btw, though it won't make a difference here).
  • aurimas
    edited February 14, 2013
    (3)(+0000002): HTTP POST {} to http://127.0.0.1:23119/connector/getSelectedCollection
    For Zotero server, the response is
    (3)(+0000972): Connector: Method getSelectedCollection failed with status 0
    For Zotero Standalone
    (3)(+0000001): Connector: Method getSelectedCollection failed with status 404

    I don't see anything in zotero-server.js about getSelectedCollection and I'm not sure why the connector even cares about the selected collection.

    Edit: Had the server and standalone flipped
  • aurimas
    The issue above is unrelated to the OP's actual problem.

    SAGE uses framesets in place of a document body element, so there is no place for the notification messages to appear (they are normally overlaid on top of the top-most body element and cannot be overlaid on top of a frameset). Maybe Simon has some ideas on how to fix this.
Sign In or Register to comment.