Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zotero Citations: could not connect to Zotero. Are you sure it is running? #14

Closed
Hocnonsense opened this issue Aug 31, 2020 · 8 comments

Comments

@Hocnonsense
Copy link

Hi... I also got this error in #2 :
image

I downloaded the latest Zotero beta (version 5.0.90-beta.3+e9473caa1), but it didn't work.
What should I do to make it run?

Thanks!

@Hocnonsense
Copy link
Author

(By the way, I think it is more convenient to cite something like [author, year](https://doi.org/...). After all, It can work WITHOUT any requirement!)

@danieltomasz
Copy link

I am still getting this error, both on latest Zotero and Zotero beta :(

@SorenKF
Copy link

SorenKF commented Dec 17, 2020

I am still getting this error, both on latest Zotero and Zotero beta :(

Hey there!

Are you sure you have the BetterBibtex add-on ([https://retorque.re/zotero-better-bibtex/]) installed? :)

@Hocnonsense
Copy link
Author

I'm sorry but this issue was opened by mistake. After I opened Zotera, I can add zotero links by vscode key binding.

However, I rarely use it now because now I find coping the Citation key directly from Zotero is easier for me

If you DO think there is an issue, you can open another issue, and describe your demands preciously?

@igravious
Copy link

igravious commented Jun 27, 2021

eh? yeah. i had installed the extension onto a remote machine. did not know vscode could do that.

i am using

"remote.extensionKind": {
    "mblode.zotero": [ "ui" ]
}

to get this extension to run locally. seems to be working fine.

@eascarrunz
Copy link

I am having this problem with WSL2. Does anyone have a fix?

@nasiegel88
Copy link

nasiegel88 commented Mar 24, 2023

Same, I'm wondering if this is WSL2-specific.

@Viibrant
Copy link

Same, I'm wondering if this is WSL2-specific.

It may well be, I'm experiencing the same issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants