ACS Publications (Could Not Save Item)

ajasja
Hello!

I couldn't save this link http://pubs.acs.org/cgi-bin/abstract.cgi/bichaw/2007/46/i08/abs/bi0616089.html

Best regards & thanks for Zotero
  • Tjowens
    I had no trouble with the article you linked to. Is anyone else having trouble with this article?
  • Acrymble
    no problem here
  • ajasja
    Hmm, strange.
    I'm still getting the error http://ajasja.ljubetic.googlepages.com/zotero_error.jpg

    I'm using Firefox 3.0 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1) on WinXP SP2 and Zotero version 1.0.7.

    The database integrity is OK and the translators are up to date.
    I did everything under the troubleshooting section except "Reset Translators and Styles", because I don’t know what styles it will reset (I have some custom citation styles, will it reset those as well?)
  • dstillman
    Resetting translators and styles would indeed wipe out your custom styles—you'd want to have copies saved elsewhere first.

    But please try disabling your other Firefox extensions to see if that fixes the problem, and, if that works, let us know which one is causing the problem.
  • ajasja
    I disabled all the extensions (wow Firefox is WAY faster without them =) but the problem remains. I did find a copy of the same article in my library. I think I got the copy form some other source (science direct?) but I'm not sure. Could that interfere with the saving?
    (I guess I could just delete it and see, but I wouldn't like to break my Zotero as I'm in the middle of writing my thesis :)
  • ajasja
    I did try to import some other article (not in my library) from the same journal http://pubs.acs.org/cgi-bin/abstract.cgi/bichaw/2007/46/i08/abs/bi602371n.html but I still get the can't save error.
  • dstillman
    Is "Accept third-party cookies" enabled in the Privacy pane of the Firefox prefs? (There's a bug in Firefox that can cause translator problems in Zotero when that pref is disabled, and a workaround we put into 1.0.7 wasn't sufficient. We'll have a real workaround in 1.0.8 (and/or Mozilla will fix the problem in Firefox 3.0.2).)
  • ajasja
    Yup, that fixes it. Thank you!

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.