retorquere / zotero-better-bibtex

Make Zotero effective for us LaTeX holdouts
https://retorque.re/zotero-better-bibtex/
MIT License
5.3k stars 284 forks source link

Since update to v 6.7.245 plugin is not starting anymore in Zotero 7.0.8 #3033

Open KonstantinHirsch opened 2 hours ago

KonstantinHirsch commented 2 hours ago

Debug log ID

7K7R7PQA-fio-IfERxOWN19bJ

What happened?

After the update to version v 6.7.245 the plugin is not starting anymore.

Zotero version: 7.0.8 OS: Linux (Fedora)

github-actions[bot] commented 2 hours ago

Hello @KonstantinHirsch,

@retorquere is ready to assist you with Better BibTeX. In order to do so efficiently, a debug log is generally required. The information it containst is key to him understanding, replicating, and resolving your issue. If you have shared a D<number> log, those go to the Zotero team, @retorquere cannot access those.

Here’s how you can share your debug log:

  1. If your issue involves specific references, citekey generation, or exports, right-click on the relevant item(s) and select "Better BibTeX -> Submit Better BibTeX debug log" from the menu.
  2. For issues where items do not play a role, follow these steps:
    • Restart Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled).
    • Reproduce the problem.
    • Choose "Send Better BibTeX debug report..." from the help menu.

After these steps, you will receive debug ID displayed in red. Please share this ID with @retorquere in this issue thread. If your query is about an export, include both the actually exported result and your expected/desired outcome.

Sharing your debug log gives @retorquere a view of your Better BibTeX configuration and the elements contributing to the issue. This helps him address your concerns more efficiently.

Thank you.

PS: If the Debug Log menu is not available, or if it fails to send the debug log, you can use the option under “Help” > “Send debug log to file.io”.

KonstantinHirsch commented 2 hours ago

can be closed, it is now working again for some miracle reason.

github-actions[bot] commented 2 hours ago

Thanks for the feedback! Just so you know, GitHub doesn't let me control who can close issues, and @retorquere likes to leave bug reports and enhancements open as a nudge to merge them into the next release.