Zotero and Google Docs integration not working: MacOS/Safari?

DavidBrookshireConner

Recently, the Zotero menu in Google Docs stopped working correctly for me.
It still switches to Zotero when I select "add/edit citation" and pops up the red search window, but there's no text field.
It then prompts me to choose an account for Google, which I do, which leads to a zotero.org window that says the window should close, and if it doesn't, try posting in the forums for troubleshooting help. So here I am.
Same behavior in a new document or an old one that I used Zotero on before.
Current version of everything.

dstillman

Make sure you're running Zotero 7 and that the Zotero Connector has permission to access all sites.

DavidBrookshireConner

First thing I did was upgrade to the latest version of Zotero from the website yesterday. Then I checked to confirm that Zotero as a Safari extension is set to “Allow” for all web sites. Which it is. I then turned off other extensions that had access to all web pages (Ghostery and DuckDuckGo). Same behavior.

dstillman

What macOS/Safari version?

DavidBrookshireConner

MacOS Sonoma 14.6.1
Safari 17.6

adomasven

Did you try restarting your computer? If it does not help, completely remove Zotero from your computer, restart Safari, then reinstall Zotero. Does that fix it?

DavidBrookshireConner

Reinstalling Zotero did not help.

adomasven

If you go to Safari Preferences -> Websites, scroll to the bottom and select Zotero Connector, is there an entry for zotero.org? Is there a yellow triangle at the bottom with a warning about allowing the extension to run on every site?

DavidBrookshireConner

It is set to allow reading and editing on all websites, after re-installing.
Previously, it was set to specifically allow zotero.org and also all web sites.
Same behavior in both cases.
And yes big yellow warnings that this extension is allowed everywhere.

DavidBrookshireConner

Yes, if you edit websites, it has the yellow triangle warning to allow for all websites. It is also specifically set to allow edits on docs.google.com

adomasven

If you open the developer tools (Develop -> Show Web Inspector) and switch to the Console tab, do you see any error messages there? If so, could you post them here (or send them to support@zotero.org if they contain any sensitive information)?

DavidBrookshireConner

[Error] Blocked a frame with origin "https://clients6.google.com" from accessing a frame with origin "https://docs.google.com". Protocols, domains, and ports must match.
Global Code (inject.js:748)
[Error] Blocked a frame with origin "https://contacts.google.com" from accessing a frame with origin "https://docs.google.com". Protocols, domains, and ports must match.
Global Code (inject.js:748)
[Error] Refused to load https://contacts.google.com/_/scs/social-static/_/js/k=boq.SocialPeopleHovercardUi.en.GujzdezfUzI.es5.O/am=oGACaw/d=1/excm=_b,_tp,hovercardwidget/ed=1/dg=0/wt=2/ujg=1/rs=AGLTcCOHCSGsftrN7fYFDfd0zhGXR_JHng/m=_b,_tp because it does not appear in the script-src directive of the Content Security Policy.

adomasven

Sorry, I meant on the "Connector Authorization Complete" page that doesn't automatically close.

DavidBrookshireConner

No error messages on that page.
Now on MacOS Sequoia 15.0 if that makes a difference.

adomasven

Does it work with a different browser? If you create a new temporary macOS user account does it work there?

DavidBrookshireConner

I tried it on Chrome, and it worked correctly there. I'd strongly prefer to continue to use Safari of course.
I haven't tried making another user ID yet, because it would be some lifting to get all the access right.

adomasven

You should only make a macOS user for troubleshooting temporarily, to see if it's a system-wide problem or related to some configuration on your account.

thcscott

Hi,
Just wondering if this problem has been solved. I have tried the same thing, I made sure it is allowed to access all websites and also reinstalled Zotero but it didn't work.

adomasven

This isn't fundamentally a bug in Zotero, but an issue caused either by some bug in macOS or Safari, or occurs due to user configuration or other software interfering, which is why we recommend testing in a new user account, where user configuration would be reset to default.