washingtonpost.com

Seems at least this article is not being seen by Zotero. I don't recall ever having had problems with washingtonpost.com content before.
  • bruce--it works for me--try updating your scrapers.
  • Weird. I did update the scrapers, as well as restart FF; still no go.
  • Works for me too. Bruce, could you start Firefox via the Terminal (/Applications/Firefox.app/Contents/MacOS/firefox) with the extensions.zotero.debug.log pref enabled via about:config and send support@zo.....org the output after loading that page? Thanks.
  • Looks like this was a problem in 1.0.0b4.r5 that Simon has since fixed in the dev branch. It's in the main code rather than the translator, so we can't fix it via the repo. Should be fixed with the next release.
  • Thanks.

    When do you expect the next update? Should I move to the dev xpi?

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