No activity with Zotero

When attempting to sync a file from EBSCO Linksource to Zotero, there is no activity. The syncing dialog box does not appear. When right clicking the icon for the desired page to save to Zotero and selecting Zotero Connector, the following is shown:

Report ID: 392655471

[JavaScript Error: "getTranslators: detection is already running" {file: "chrome-extension://ekhagklcjbdpajgpjgmbionohlpdbjgc/zotero/translation/translate.js" line: 1023}]
  • Can you provide the full URL, as you see it in the URL bar? Also, please provide a Debug ID from the connector starting with loading/refreshing the page and including clicking the URL bar icon.
  • This is the URL:
    http://linksource.ebsco.com.elib.uah.edu/FullText.aspx?linkout=http%3a%2f%2fejournals.ebsco.com%2fDirect.asp%3fAccessToken%3d95JI4IM8X9XX9IUUJ9EMXQXPXIXQ8IIXM4%26Show%3dObject%26ErrorURL%3dhttp%253A%252F%252Flinksource%252Eebsco%252Ecom%252Ferror%252Easpx

    I believe i did this correctly.
    ID: D1497982904
  • I just tried again from my home internet vs being at school, and it worked. I don't know that has anything to do with it.
  • aurimas:
    (3)(+0000000): Connector_Browser: URL changed for tab

    (3)(+0000855): Translators: Looking for translators for https://login.elib.[...].edu/login?url=http://linksource.ebsco.com/FullText.aspx?linkout=http://ejournals.ebsco.com/Direct.asp?
    AccessToken%3d[...]%26Show%3dObject%26ErrorURL%3dhttp%253A%252F%252Flinksource
    %252Eebsco%252Ecom%252Ferror%252Easpx

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

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

    (4)(+0000013): Translate: Binding sandbox to https://login.elib.[...].edu/login?url=http://linksource.ebsco.com/FullText.aspx?
    linkout=http%3a%2f%2fejournals.ebsco.com%2fDirect.asp%3fAccessToken
    %3d[...]%26Show%3dObject%26ErrorURL%3dhttp%253A%252F%252Flinksource%252E
    ebsco%252Ecom%252Ferror%252Easpx

    (4)(+0000003): Translate: Parsing code for Library Catalog (InnoPAC)

    (4)(+0000004): Translate: Parsing code for unAPI

    (4)(+0000007): Translate: Parsing code for COinS

    (4)(+0000003): Translate: Parsing code for DOI

    (4)(+0000003): Translate: Parsing code for Embedded Metadata

    (3)(+0000004): Translate: Embedded Metadata: found 1 meta tags.

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

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

    (3)(+0008322): Connector_Browser: URL changed for tab

    (3)(+0003204): Translators: Looking for translators for http://linksource.ebsco.com.elib.[...].edu/error.aspx?aspxerrorpath=/FullText.aspx

    (4)(+0000011): Translate: Binding sandbox to http://linksource.ebsco.com.elib.[...].edu/error.aspx?aspxerrorpath=/FullText.aspx

    (4)(+0000004): Translate: Parsing code for Library Catalog (InnoPAC)

    (4)(+0000003): Translate: Parsing code for unAPI

    (4)(+0000004): Translate: Parsing code for COinS

    (4)(+0000004): Translate: Parsing code for DOI

    (4)(+0000004): Translate: Parsing code for Embedded Metadata

    (3)(+0000004): Translate: Embedded Metadata: found 0 meta tags.

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

    (5)(+0000003): Translate: Running handler 0 for translators
  • So there's no sign of the URL button being clicked? Can you see version numbers in the Error report from the first post?
  • Nothing else.
    "connector => true, version => 4.0.26, platform => Win32, locale => en-US, appVersion => 5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.89 Safari/537.36, appName => Chrome"
  • @j3nnlamar, under chrome://extensions do you have any other extensions installed? If so, try disabling them, refreshing the page, and see if the issue is resolved.

    I'm not really sure how being on different networks would make a difference given the debug log above.

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.