Chrome Plugin - icon not showing up when logged into Pubmed via school library

After a recent update, I'm having issues with Chrome and the pubmed translator where the icon is not showing up if I'm logged in to Pubmed via my university library. The translator seems to be working in the background (see debug output below) but the icon doesn't show up. If I just visit Pubmed without logging in, the icon shows up fine. Any way to fix this?

Standalone version 4.0.9.1
Plugin version 4.0.8.2
Chrome version 28.0.1500.95 m

here are the lines from debug:
--------------------------------------------------

(3)(+0014532): Translators: Looking for translators for http://eresources.library.mssm.edu:2060/pubmed/9142025

(4)(+0000007): Translate: Binding sandbox to http://eresources.library.mssm.edu:2060/pubmed/9142025

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

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

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

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

(3)(+0000002): Translate: Embedded Metadata: found 21 meta tags.

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

(5)(+0000000): Translate: Running handler 0 for translators
-----------------------------------------------------
  • this won't work in the connectors - your library removes the entire pubmed URL, which Zotero needs to recognize this as a pubmed page. It _might_ work in Firefox (though not sure either).
    It's possible you may be able to log-in differently - e.g. on campus this shouldn't be necessary - but otherwise using plain pubmed is the only way this will work with Zotero.
  • But here's the thing: it worked until the latest update, further, you can see from the debug lines that it actually is reading and recognizing the metatags - it just needs to know to display the icon.

    Is there some way for me to edit the pubmed translator to make it work?
  • maybe your library changed something. I can guarantee you that this would never have worked. The debug just shows that Zotero is trying all four of its generic translators on the page and none of them with success - that's exactly what we'd expect to see.
  • Interesting; it definitely worked just a few weeks ago. Thanks.
  • as for changing the translator yourself:
    http://www.zotero.org/support/dev/translators/coding
    the only thing you'd need to do is to change the target regex - not hard at all, but not something we'd want to do for the general purpose version of the translator.
  • The PubMed translator isn't running at all. The embedded metadata translator is reading the meta tags, but unfortunately the meta tags are useless and don't identify the article, as you can see by looking at the page source. I would be very surprised if this ever worked outside of Firefox.

    You can change the translator target so that it matches, but you'd have to make sure you always have Zotero Standalone open before the first time you access a PubMed page in a Chrome session, and you'd also have to disable automatic translator updates or update the translator manually with every automatic update, so it's not really a viable solution. You could also try to convince your library to set their EZProxy to proxy by hostname mode.
  • (to clarify, what Simon and I say about changing the translator is the same suggestion, with some additional details from him).
Sign In or Register to comment.