Before all else, thank you for taking the time for submitting an issue, and I’m sorry that I’ve probably interrupted your flow.
Your report matters to me. I love hearing my software helps you, and it pains me to know that things aren’t working for you.
If you have any questions on the use of the plugin, please do not hesitate to file a GitHub issue to ask for help.
If you’re reporting a bug in the plugin, please take a moment to glance through the Support Request Guidelines below; it will make sure I get your problem fixed as quick as possible. The guidelines are very detailed, perhaps to the point of being off-putting, but please do not fret; these guidelines simply express my ideal bug submission. I of course prefer very clearly documented issue reports over fuzzy ones, but I prefer fuzzy ones over missed ones.
You can report problems with BBT by opening a new issue on github. Unfortunately, my time is extremely limited for a number of very great reasons (you shall have to trust me on this). Because of this, I cannot accept bug reports or support requests on anything but the latest version. By the time I get to your issue, the latest version might have bumped up already, and you will have to upgrade (you might have auto-upgraded already however) and re-verify that your issue still exists. Apologies for the inconvenience, but such are the breaks.
Send Better BibTeX debug reportfrom the
Helpmenu. Post the resulting ID (displayed in red) in a github issue.
Send Better BibTeX debug report
That in itself will in many cases give me what I need. Don’t forget to copy the generated ID to paste it into the github issue; you cannot call it up later (although you can just do it again).
For the fastest fix:
If Zotero stalls after installing BBT, it is often a one-time thing as the cache fills.