Zotero Connector Chrome Not Saving Articles Properly

edited August 17, 2017

I installed Zotero standalone after using the Mozilla extension for many years. I have switched to using Chrome, but there is a problem because it can't recognize articles and only can save as webpage. I already checked the connection with standalone and it says it's connected in the settings. When I save articles they do go through. Even going to PubMed, the extension doesn't recognize the article. Can you help me fix this please?


  • Can you provide an example URL and a Debug ID from the connector for a page load that doesn't recognize an article?
  • edited August 17, 2017
    This is the website:


    [output removed — D.S.]
  • That's for saving — we'd want for loading the page.
  • edited August 17, 2017
    Here is the report for loading:

    [JavaScript Error: "Script injection timed out" {file: "chrome-extension://ekhagklcjbdpajgpjgmbionohlpdbjgc/background.js" line: 263}]

    [JavaScript Error: "Script injection timed out" {file: "chrome-extension://ekhagklcjbdpajgpjgmbionohlpdbjgc/background.js" line: 263}]

    connector => true, version => 5.0.17, platform => Win32, locale => en-US, userAgent => Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36, appName => Chrome Connector, zoteroAvailable => true


    (3)(+0008967): Connector_Browser: onActivated for http://jamanetwork.com.myaccess.[…]/journals/jamainternalmedicine/fullarticle/487011

    (3)(+0000998): Connector_Browser: onActivated for https://www.ncbi.nlm.nih.gov/pubmed/14693982

    (3)(+0003132): Connector_Browser: onDOMContentLoaded for https://www.ncbi.nlm.nih.gov/pubmed/14693982; https://www.ncbi.nlm.nih.gov/pubmed/14693982

    (3)(+0000011): Injecting translation scripts into 0 https://www.ncbi.nlm.nih.gov/pubmed/14693982

    (3)(+0000000): Injecting scripts into https://www.ncbi.nlm.nih.gov/pubmed/14693982 : node_modules.js, zotero_config.js, zotero.js, promise.js, http.js, proxy.js, cachedTypes.js, zotero/date.js, zotero/debug.js, zotero/openurl.js, zotero/xregexp/xregexp.js, zotero/xregexp/addons/build.js, zotero/xregexp/addons/matchrecursive.js, zotero/xregexp/addons/unicode/unicode-base.js, zotero/xregexp/addons/unicode/unicode-categories.js, zotero/xregexp/addons/unicode/unicode-zotero.js, zotero/rdf/init.js, zotero/rdf/uri.js, zotero/rdf/term.js, zotero/rdf/identity.js, zotero/rdf/match.js, zotero/rdf/rdfparser.js, zotero/translation/translate.js, zotero/translation/translator.js, translate_item.js, zotero/connectorTypeSchemaData.js, zotero/utilities.js, zotero/utilities_translate.js, utilities.js, inject/http.js, inject/progressWindow.js, inject/translate_inject.js, messages.js, messaging_inject.js, api.js, inject/inject.js

    (3)(+0000271): Translators: Looking for translators for https://www.ncbi.nlm.nih.gov/pubmed/14693982

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

    (3)(+0000000): No suitable translators found

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

    (5)(+0000003): Translate: Running handler 1 for translators

    (3)(+0001564): Connector_Browser: onActivated for chrome-extension://ekhagklcjbdpajgpjgmbionohlpdbjgc/preferences/preferences.html#advanced

    (3)(+0000000): HTTP POST

    (3)(+0000008): Connector: Method ping succeeded
  • This should be an easy fix, but since we're trying to track this down, if you open your Zotero data directory and go to the 'translators' folder, how many files are there? Is there a PubMed.js file?
  • I've checked that and there are 497 items in the translator file including PubMed.js
  • OK, if you right-click on the save icon, click Options to open the Zotero Connector preferences, go to the Advanced pane, and click Update Translators, and then reload the page, does that help?
  • Actually that solved the problem. Thanks!
  • OK, great. We'll try to figure out why this is happening.
  • Your tip helped but my problem now is that every time I start Chrome I have the same problem again that requires me to repeat the solution. Can you stop this from happening?
  • Could you go into Connector Preferences -> Advanced, tick "Enable at Startup" under Debug Output Logging, restart the browser, go to a site that doesn't work after restart and try saving, then go to Preferences -> Advanced, untick "Enable Logging" and Submit Debug Report, then post the Debug ID here.
  • Hello - here is my debug ID after doing that: d1920761169

    The site that doesn't work is the last link in the report (Lancet). After updating translators and refreshing, it works - but only for the current browsing session.
  • Anyone able to help on this issue?
  • Connector: Method getTranslators failed with status 0
    It shouldn't really matter, but do you have Zotero running when you restart Chrome?

    This shows the initial request for translators from Zotero at Chrome startup failing. That could happen if Zotero was closed, but also if another extension or security software or proxy settings were preventing the connector from connecting to Zotero.

    I believe translators should be cached between restarts, but it's possible that something is causing those to be cleared when you restart Chrome, and then the failed connection is causing them to not be refetched.
  • You're right, it only happens if I don't have Zotero already running before starting Chrome. Very strange.
Sign In or Register to comment.