[5.0 Beta] [NoScript] Firefox connector seems broken

nmjxv3
edited January 30, 2017
My Zotero 5.0 standalone updated this evening, and now the Firefox Zotero connector will not save anything, either to standalone Zotero or directly to the web (by closing Zotero standalone).

Nothing appears in the debug log of the connector aside from pings.

Sometimes I get the message 'Message `Prefs.getAsync` has no callback arg. It should use the returned promise' in the browser console.
  • adamsmith
    Have you tried will all other add-ons disabled? We've had several reports of conflicts with other, in particular privacy enhancing, add-ons.

    If this fails with no other add-ons active, how exactly do things fail? Nothing happens when you press? The Zotero pop-up comes up but with no item title listed? Same but with item title? Or you get an actual error?
  • dstillman
    What version? Make sure you have 4.999.8 or later.
  • nmjxv3
    edited January 26, 2017
    Ah, more poking reveals it was NoScript again. D'oh!

    Do you have any idea what Zotero is doing that's unusual here? I've never had it break other extensions before. As far as I can tell, Zotero only loads resources via resource:// and moz-extension:// URIs, which can't be blocked by NoScript.
  • adamsmith
    you still have 127.0.0.1 whitelisted, right?
  • nmjxv3
    edited January 26, 2017
    Yep, both https and http://127.0.0.1:23119 for good measure.

    EDIT: it's something to do with translators, I have a hunch. With NoScript on, the only translators I get on any page are the Web Page with/without Snapshot ones. With NoScript off, all the per-site ones show up.
  • adomasven
    edited January 26, 2017
    If you provide a Connector Debug ID for a page refresh with NoScript running we could take a look.
  • nmjxv3
    Well, this is odd: clicking the Submit to Zotero button gives the following error in the browser console (with NoScript either enabled or disabled): 'TypeError: Zotero.HTTP.request is not a function[Learn More] connector.js:294:11'

    I do have a report of some errors that appear when I start Zotero, but I think they're entirely unrelated: Report ID:927433958

    I get the following debug output (snipped to remove pings, etc.), but I don't suppose that it'll answer all your questions:

    (3)(+0001236): Translators: Looking for translators for http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.59.8232

    (3)(+0000033): HTTP POST {"translatorID":"fa396dd4-7d04-4f99-95e1-93d6f355441d"} to http://127.0.0.1:23119/connector/getTranslatorCode

    (3)(+0000073): Connector: Method getTranslatorCode succeeded

    (3)(+0000003): HTTP POST {"translatorID":"4fd6b89b-2316-2dc4-fd87-61a97dd941e8"} to http://127.0.0.1:23119/connector/getTranslatorCode

    (3)(+0000063): Connector: Method getTranslatorCode succeeded

    (3)(+0000001): HTTP POST {"translatorID":"e7e01cac-1e37-4da6-b078-a0e8343b0e98"} to http://127.0.0.1:23119/connector/getTranslatorCode

    (3)(+0000040): Connector: Method getTranslatorCode succeeded

    (3)(+0000001): HTTP POST {"translatorID":"05d07af9-105a-4572-99f6-a8e231c0daef"} to http://127.0.0.1:23119/connector/getTranslatorCode

    (3)(+0000024): Connector: Method getTranslatorCode succeeded

    (3)(+0000001): HTTP POST {"translatorID":"951c027d-74ac-47d4-a107-9c3069ab7b48"} to http://127.0.0.1:23119/connector/getTranslatorCode

    (3)(+0000065): Connector: Method getTranslatorCode succeeded

    (3)(+0000001): HTTP POST {"translatorID":"c159dcfe-8a53-4301-a499-30f6549c340d"} to http://127.0.0.1:23119/connector/getTranslatorCode

    (3)(+0000021): Connector: Method getTranslatorCode succeeded

    (3)(+0000001): 2 translators found. Injecting into [rootUrl, url]: http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.59.8232 , http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.59.8232

    (3)(+0000560): Message `Translators.getWebTranslatorsForLocation` has no callback arg. It should use the returned promise

    (3)(+0000003): Translators: Looking for translators for http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.59.8232
  • adomasven
    Thanks for this. Debug output submitting has now been fixed.

    Can't see anything obvious from the log. I will look into running the connector with NoScript at some point later, but this will not be very high priority I am afraid.
  • nmjxv3
    Cool. I'll update and see if I can figure out what's going on, maybe with some console logging to see what JS isn't getting run next time I have a moment.
Sign In or Register to comment.