Translator Errors with Optical Society of America Sites

Reference ID: 1433815796

I use Zotero standalone (4.0.17) with a Chrome extension (Chrome on PC version 32.0.1700.107 m), and I receive translator errors when accessing publications from the Optical Society of America (OSA) - OpticsInfoBase.

[JavaScript Error: "Attempting to use a disconnected port object" {file: "extensions::messaging" line: 71}]

also...

[JavaScript Error: "Cannot read property 'length' of undefined" {file: chrome-extension://'long directory string'/zotero/translation/translate.js" line: 1776}]

More information
---------------------
The Zotero icon appears on the right side of the address bar, and when I hover over the icon it says "Save to Zotero (Optical Society of America via Zotero Standalone)".

I've also tried updating Zotero, Chrome, and the connector. Nothing has helped.

Some OSA journals work fine, but this ID# references a case where it does not. I'd say this happens 1 out of every 4 times I access a publication from the OSA OpticsInfoBase.

What do you think is going?
  • To speed this up, could you provide a URL where this fails?
  • Thanks for replying so quickly!

    Sure...
    http://www.opticsinfobase.org/abstract.cfm?URI=CLEO_Europe-2011-CA11_4
  • When you say that it doesn't work, do you see the Zotero pop-up at the bottom right of the page with an error message? Or is the pop-up empty and just says Saving to (that's what I'm seeing)? If it's empty, does the article actually save in Zotero Standalone (it does for me)?
  • I get the pop-up in the bottom right, and it says

    "Saving to My Library...
    An error occurred while saving this item. Check Known Translator Issues for more information."

    I do not have an entry created in Zotero Standalone.

    That's interesting that it works for you. What version of Java do you have? I only mention it since it lists JavaScript errors in the log.
  • Java is independent of JavaScript. We'll see what Dan finds in your error report.
  • jschaar provides the relevant errors above.
  • The first one is a frequently occurring error that should not impact translation (I'm not entirely sure why we're seeing it in general) and the second error should, in theory, never happen.

    @jschaar, could you provide a Debug ID from Zotero Standalone after triggering this error?
  • @aurimas - I'd guess it's somehow picking up a different frame? That had been a problem before, though in principle the translator should take care of that (but might not be in this case).
  • I turned off my academic proxy for accessing these journals and the translation worked just fine. The pop-up box that says "Saving..." was still showing after more than a minute, but the entry did appear correctly in Zotero Standalone.

    Besides turning on/off my proxy while accessing/translating these web sites into Zotero, respectively, is there something I can do to make this work as expected.

    Here is the proxy address.

    http://pac.stanford.edu/suproxy.pac

    Thanks!
  • For the proxy issue, it would probably help if you could produce the Debug ID from Zotero Standalone as per instructions above. Dan will have to take a look at that. In the mean time I'm looking into the hanging "Saving..." dialog issue.
  • (I get the hanging saving dialog for items saved via Standalone consistently)
  • Here is my Debug ID

    D1577199323
  • (3)(+0001356): Connector: Method savePage failed with status 500
    We need a Debug ID from Standalone itself, not the connector.
  • Here is the Debug ID from Standalone.

    D11977816
  • (4)(+0000005): Translate: Binding sandbox to http://www.opticsinfobase.org/abstract.cfm?URI=CLEO_Europe-2011-CA11_4

    (4)(+0000002): Translate: Parsing code for Optical Society of America

    (3)(+0000002): Translate: All translator detect calls and RPC calls complete

    (5)(+0000000): Translate: Running handler 0 for translators

    (4)(+0000000): Translate: Parsing code for Optical Society of America

    (3)(+0000002): Translate: Beginning translation with Optical Society of America

    (3)(+0000001): Translate: We report on a high small-signal gain in a 10 mm-long Yb:CaF2 crystal pumped by a fiber laser at 976 nm. This result significantly outperforms any CW-diode pumped scheme.

    (3)(+0000000): HTTP GET http://www.opticsinfobase.org/abstract.cfm?URI=CLEO_Europe-2011-CA11_4

    (5)(+0000000): CookieSandbox: Managing cookies for www.google-analytics.com

    (5)(+0000000): CookieSandbox: Cleared cookies to be sent to www.google-analytics.com

    (5)(+0000002): CookieSandbox: Managing cookies for www.opticsinfobase.org

    (5)(+0000000): CookieSandbox: Added cookies for request to www.opticsinfobase.org

    (5)(+0000006): CookieSandbox: Managing cookies for www.opticsinfobase.org

    (5)(+0000001): CookieSandbox: Added cookies for request to www.opticsinfobase.org

    (5)(+0000041): CookieSandbox: Managing cookies for www.opticsinfobase.org

    (5)(+0000017): CookieSandbox: Managing cookies for weblogin.stanford.edu

    (5)(+0000000): CookieSandbox: Cleared cookies to be sent to weblogin.stanford.edu

    (5)(+0000010): CookieSandbox: Managing cookies for weblogin.stanford.edu

    (5)(+0000000): CookieSandbox: Rejected cookies from weblogin.stanford.edu

    (5)(+0000008): CookieSandbox: Managing cookies for weblogin.stanford.edu

    (5)(+0000000): CookieSandbox: Cleared cookies to be sent to weblogin.stanford.edu

    (5)(+0000010): CookieSandbox: Managing cookies for weblogin.stanford.edu

    (5)(+0000000): CookieSandbox: Rejected cookies from weblogin.stanford.edu

    (2)(+0000005): Translate: Translation using Optical Society of America failed:
    fileName => C:\Users\[...]\AppData\Roaming\Zotero\Zotero\Profiles\[...]\zotero\translators\Optical Society of America.js
    lineNumber => 93
    columnNumber => 0
    string => TypeError: text.match(...) is null
    stack => scrape/<@C:\Users\[...]\AppData\Roaming\Zotero\Zotero\Profiles\[...]\zotero\translators\Optical Society of America.js:93

    url => http://www.opticsinfobase.org/abstract.cfm?URI=CLEO_Europe-2011-CA11_4
  • edited February 12, 2014
    @Dan,

    Do PAC based proxies depend on cookies? I.e. would this be fixed by https://github.com/zotero/zotero/pull/409 or is Zotero Standalone not picking up the proxy in general?
  • Do PAC based proxies depend on cookies?
    Generally speaking, no, but the proxy server specified in the PAC file can require cookies if it wants to, and that's the case for Stanford — we get a lot of reports of this. A request that needs to be proxied gets back a 302 to weblogin.stanford.edu if there's no cookie.
  • (5)(+0000017): CookieSandbox: Managing cookies for weblogin.stanford.edu

    (5)(+0000000): CookieSandbox: Cleared cookies to be sent to weblogin.stanford.edu
    So you're saying that the above should have sent a cookie to weblogin.stanford.edu? That cookie would not have gotten passed from Chrome (even if we didn't clear it), since the URL of the resource was not proxied, so... I'm not sure how we can address this. I don't think we want to send all cookies from Chrome to Standalone.

    Simon has mentioned that he is working on a solution where the connector acts itself as a proxy, so Standalone downloads everything through the browser. That should pretty much fix all of the cookie issues, including this one, I think. It's also probably not going to happen very soon.
  • It sounds like there is a solution. That is great news! But it won't be implemented in the near term. In the mean time, what do you suggest I do?

    Thanks!
  • use VPN instead of the proxy: https://itservices.stanford.edu/service/vpn
Sign In or Register to comment.