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

cite as you write broken in zotero 7 betas 70 and 72 #2835

Closed
jpjoines opened this issue Apr 10, 2024 · 3 comments
Closed

cite as you write broken in zotero 7 betas 70 and 72 #2835

jpjoines opened this issue Apr 10, 2024 · 3 comments

Comments

@jpjoines
Copy link

Debug log ID

D113395719

What happened?

I am using CAYW with Vim as documented at https://retorque.re/zotero-better-bibtex/citing/cayw, and have been doing so for year. It still worked fine in Zotero 7.0.0-beta.68+c31a40c74, but is broken in both 7.0.0-beta.70+d654daae2 and 7.0.0-beta.72+128a540af.

Instead of launching the citation chooser dialog, calling the Vim function inserts the text "No endpoint found" into the document.

Zotero debug output shows:

(5)(+0020474): GET /better-bibtex/cayw?format=cite&brackets=1 HTTP/1.1 Host: 127.0.0.1:23119 User-Agent: curl/7.81.0 Accept: /

(5)(+0000001): HTTP/1.0 404 Not Found X-Zotero-Version: 7.0.0-beta.72+128a540af X-Zotero-Connector-API-Version: 2 Content-Type: text/plain No endpoint found

(3)(+0059944): HTTP POST "1712771543937 addons.xpi WARN …" (3775 chars) to https://repo.zotero.org/repo/report?debug=1

(3)(+0000013): POST body gzipped from 3775 to 1466; 61% savings

(3)(+0005352): HTTP POST https://repo.zotero.org/repo/report?debug=1 succeeded with 200

I'm not sure if I should report this here or to Zotero. Zotero seems to think it should be reported here, https://forums.zotero.org/discussion/comment/460448/#Comment_460448.

Copy link

Hello there @jpjoines,

Hope you're doing well! @retorquere is here to help you get the most out of your experience with Better BibTeX. To make sure he can assist you effectively, he kindly asks for your cooperation in providing a debug log – it's like giving him the key to understanding and solving the puzzle!

Getting your debug log is a breeze and will save us both time in getting your problem resolved or the new feature you'd like implemented. Trust me, it's way quicker than discussing why it's important. 😃

How to Share Your Debug Log:

  1. If the issue involves specific references, citekey generation, or exports, just right-click on the relevant item(s) and choose "Better BibTeX -> Submit Better BibTeX debug log" from the menu.

  2. For other issues, follow these simple steps:

    • Restart Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled).
    • Reproduce the problem.
    • Select "Send Better BibTeX debug report..." from the help menu.

Once you hit that submit button, you'll get a special red debug ID. Just share that with @retorquere in this issue thread. If the question is regarding an export, don't forget to include what you see exported and what you expected.

By sharing your debug log, you're giving @retorquere a clearer picture of your setup and the items causing the issue. It's like a superhero cape for him – he can swoop in and tackle the problem much faster.

We totally get that your time is valuable, and we appreciate your effort in helping @retorquere help you. You might be surprised at how much this simple step speeds up the whole process.

Thanks a bunch!

PS: If the Debug Log menu does not appear, or it does not send the debug log

A fallback option is available under "Help" > "Send debug log to file.io".

@jpjoines
Copy link
Author

Neither "Help > Send Better BibTeX debug report...", nor "Help > Send debug log to file.io" is available in Zotero 7 beta 72.

@retorquere
Copy link
Owner

#2829

Repository owner locked and limited conversation to collaborators Apr 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants