Engineering Village translator broken since Zotero 2.1.1 update (Firefox 4)

Engineering Village is a powerful web-based information service that I and many of my colleagues use to search for academic articles. I have been using it with Zotero (v1.0 and v2.0) for some time without any problems. Yesterday (3/23/11), I updated Zotero to v2.1.1 and updated Firefox to v4.0. All of the sudden, the translator for Engineering Village no longer worked. None of the troubleshooting suggestions provided here: http://www.zotero.org/support/troubleshooting_translator_issues have fixed the problem.

Note: the translator seems to still be working just fine on other sites -- just stopped working on Engineering Village. Any help appreciated.

ADDITIONAL INFORMATION
Error Code (reported to developers): 1573195103

Steps to reproduce:
1) Update Zotero to v2.1.1 and Firefox to v4.0

2) Search for a citation in Engineering Village and open the Detailed view. One example below:
http://www.engineeringvillage2.org.libproxy.mit.edu/controller/servlet/Controller?SEARCHID=1db985212edf90a0e21470prod3data1&CID=quickSearchDetailedFormat&DOCINDEX=9&database=7&format=quickSearchDetailedFormat

3) Try to save citation information to Zotero using translator (fails)
  • And you've tried updating translators? There was an issue with RIS, which this translator uses, but that issue has been since resolved.
  • edited March 24, 2011
    Yes. I've updated the translators. When that didn't work, I reset the translators and re-updated to no avail.

    Could this be a problem on the FF 4.0 side or induced by some change in Zotero from v2.0 to v2.1.1? All cookies are allowed and I don't believe there are any problems from the proxy. I also don't suspect that anything happened on the Engineering Village side since it was working a few hours before I updated FF and Zotero.
  • Note that I can't test this personally, since I don't have access to Engineering Village.
  • Do you have a computer with Firefox 3.6 and Zotero 2.0 handy that you could check with?

    Also, please post the error from the error report here-- the full report can be accessed by core developers only. Maybe we can troubleshoot this one in the dark.
  • edited March 24, 2011
    Yes -- I'll test on another computer shortly. In the meantime, here is the error report:

    [JavaScript Error: "no element found" {file: "http://www.jstor.org/rx?uid=767955754338294&st=1301000676532&pn=http://www.jstor.org/pss/4145096&ets=BodyTagTiming:13,load:724" line: 1}]
  • haven't looked at the translator code, but it appears to get into an infinite recursion.


    (3)(+0000000): Translate: tag: 'L2'; data: 'http://dx.doi.org/10.1109/CA.1995.393549'

    (3)(+0000001): Translate: Saving item

    (5)(+0000000): Translate: running handler 0 for itemDone

    (3)(+0000000): Translate: Saving item

    (5)(+0000000): Translate: running handler 0 for itemDone

    ... (+ quite a few more)


    (2)(+0000005): Translate: Translation using Engineering Village failed:
    message => too much recursion
    fileName => chrome://zotero/content/xpcom/translation/translate.js
    lineNumber => 78
    stack => ([object Object],[object Proxy])@chrome://zotero/content/xpcom/translation/translate.js:78
    ([object Proxy])@chrome://zotero/content/xpcom/translation/browser_firefox.js:112

    ... (+many more again)
  • Ok. Just tested it on another (Windows) computer running FF 3.6 and Zotero 2.0.3. The translator is working perfectly there -- no problems with translator with that setup.
  • I'm wondering whether Zotero v2.1 changed the way proxies are handled from v2.0. I don't believe v2.0 ever gave the popup notification when it was redirecting an inquiry through a proxy, but since the update, it does:
    "Zotero automatically redirected your request to www.engineeringvillage2.org through the proxy at www.engineeringvillage2.org.libproxy.mit.edu"

    I've tried running the translator with proxy redirection enabled and disabled both, but neither works. A red herring probably, but it's the most visible change I've seen apart from the translator simply not working.
  • If it's infinite recursion, then this is the bug that hit the RIS translator as well.

    Please go to http://github.com/ajlyon/zotero-bits/raw/master/Engineering Village.js and save the file to the translators directory of your Zotero data directory (http://www.zotero.org/support/zotero_data).

    It should start working again. If this works for you, please post here so that I can submit this change to be pushed to all users.
  • The proxying notification is because people were getting confused by Zotero's silent proxying-- the actual proxying behavior has not changed.
  • Ok. I overwrote the Engineering Village.js that was in my translators directory with the one you provided and tried again. While no error window pops up, links do not appear to be saving to the directory. Instead, the Zotero notification popup is blank and nothing gets added to the library. I restarted Firefox to no avail -- do I need to re-initialize the translators after switching out the .js?
  • Missed a piece. Try downloading from there again.
  • That worked. Thanks!
  • Glad to hear. This will no longer be necessary in 2.1.2, so do "Reset Translators" in the Zotero preferences when that release comes out.
  • Will do. Thanks again for the quick help.
  • edited November 6, 2012
    Zotero 3.0.8 is having trouble with Engineering Village again.

    Here's the log (Report ID: 1464229926)
    [JavaScript Error: "temp.match(/\?EISESSION=[^&]+/) is null" {file: "/Users/sterling/Documents/Background Literature/Zotero Data/translators/Engineering Village.js" line: 65}]

    Is this a problem with proxies?
  • Should be fixed now.
    Your copy of Zotero will auto-update within 24hs or you can update immediately from the General tab of the Zotero preferences.
    Any problems, please let us know.

    We can't auto-test Engineering Village like most other translators because of session IDs, so we rely on reports like yours to keep it working, thanks!
  • Working now. Thanks guys.

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.