JSTOR inconsistencies
We're experiencing an inconsistency at our institution that I can't figure out so far, related to JSTOR. Each machine has the same OS (WinXP) and the same Firefox (4.0.1) and the current Zotero.
On some of the machines, when "Automatically attach associated PDFs" is checked that's exactly what happens for JSTOR articles. On other machines, for the exact same articles even, the PDF is not downloaded and attached--and this is after the user manually opens a PDF and accepts the JSTOR terms of service for the session. There is no error message, of course--just no PDF. The metadata is fine.
On the machines that won't download JSTOR articles, it is still possible to get PDF attachments from other databases, such as Project MUSE, so there seems to be something specific going on with JSTOR. Any ideas? Could it have something to do with preferences set by the users elsewhere in Firefox?
Thanks!
slg
On some of the machines, when "Automatically attach associated PDFs" is checked that's exactly what happens for JSTOR articles. On other machines, for the exact same articles even, the PDF is not downloaded and attached--and this is after the user manually opens a PDF and accepts the JSTOR terms of service for the session. There is no error message, of course--just no PDF. The metadata is fine.
On the machines that won't download JSTOR articles, it is still possible to get PDF attachments from other databases, such as Project MUSE, so there seems to be something specific going on with JSTOR. Any ideas? Could it have something to do with preferences set by the users elsewhere in Firefox?
Thanks!
slg
The Debug ID is D1758098412.
The Debug ID is D1212934957.
Thanks!
But this made me realize that the one where auto download does work has had Firefox/Zotero installed for a long time, going back to some point in the past where JSTOR functionality required the explicit addition of a cookie "allow" exception. The exception was still present.
So I went over to a machine where the auto download was not working, added the explicit "allow" cookies from www.jstor.org, and voila!
Is this some weird problem due to the way Firefox is locked down at our institution? The way JSTOR is served?
Thanks for your help!
slg