PDFs will not save to Zotero from any browser
I use Zotero a lot to add citations and full-text articles. I access my library's databases via their proxy server. When I attempt to save a citation with a "pdf full text" link on the citation page, everything is fine.
In cases where the article is listed as "linked full text," so clicking on that opens the PDF alone in a new tab, still proxied, I get either a red X when I try to download it, or an error message (see below). I have tested this in several databases (ProQuest and ScienceDirect, for example) and I THINK it's only happening in EBSCO databases, if that helps. The PDF itself isn't in EBSCO, it's in some other place (like coming from Sage journals, but it's opening via EBSCO).
I tried uninstalling and reinstalling Zotero, uninstalling and reinstalling the connector in both Firefox and Chrome, and am getting the same result. Can you help?
sample page on which this occurs: https://journals-sagepub-com.libproxy.umassd.edu/doi/pdf/10.1177/1084822319850819
Translator says "Save to Zotero (PDF)
Either I get a red X or it says An error occurred while saving this item.
Debug error ID: D549823565
In cases where the article is listed as "linked full text," so clicking on that opens the PDF alone in a new tab, still proxied, I get either a red X when I try to download it, or an error message (see below). I have tested this in several databases (ProQuest and ScienceDirect, for example) and I THINK it's only happening in EBSCO databases, if that helps. The PDF itself isn't in EBSCO, it's in some other place (like coming from Sage journals, but it's opening via EBSCO).
I tried uninstalling and reinstalling Zotero, uninstalling and reinstalling the connector in both Firefox and Chrome, and am getting the same result. Can you help?
sample page on which this occurs: https://journals-sagepub-com.libproxy.umassd.edu/doi/pdf/10.1177/1084822319850819
Translator says "Save to Zotero (PDF)
Either I get a red X or it says An error occurred while saving this item.
Debug error ID: D549823565
You can see the test results here showing that it's broken ("Chain issues: incomplete").
So @nsouza2 should try again. If there's only one server, it should work now.