Error in EBSCOhost translator

[dstillman]

I can reproduce this.

message => line.replace is not a function
fileName => 
lineNumber => 206
stack => doImport()@:206

name => TypeError
url => http://web.ebscohost.com/ehost/results?vid=15&hid=21&sid=202bb25d-9e45-48d9-ba5c-64e502672455%40sessionmgr2
extensions.zotero.cacheTranslatorData => true
extensions.zotero.automaticSnapshots => true

[stakats]

EBSCO's export functionality has completely changed, breaking our translator. On the plus side, any new translator will benefit from their simplified export architecture, which should require far fewer POST requests (probably just two).

[simon]

(In [937]) - closes #407, error in EBSCOhost translator

• closes #430, Amazon translator causing utilities.js to throw exception
• officially deprecated Zotero.Utilities.getNodeString() (use doc.evaluate and nodeValue or textContent instead, or access attributes directly; these options take the nearly the same amount of code, should be faster, and don't unnecessarily bloat our utilities)
• updated word integration to the latest version

[dstillman]

EBSCOhost is still throwing errors:

thrown exception => cannot translate: no location specified
url => http://web.ebscohost.com/ehost/results?vid=2&hid=19&sid=8c457bb8-0772-4595-8406-109508a53387%40sessionmgr3
extensions.zotero.cacheTranslatorData => true
extensions.zotero.downloadAssociatedFiles => false

[simon]

(In [1122]) references #407, error in EBSCOhost translator. while the issue has been fixed on our end, at the moment, EBSCO's export appears to be broken, returning an empty file instead of RIS output. there's a relatively easy workaround if they don't get it working in a day or two.
closes #517, ScienceDirect translator fails

[simon]

seems to work now