Closed alhom closed 8 months ago
Hello there @alhom,
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. :smiley:
How to Share Your Debug Log:
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.
For other issues, follow these simple steps:
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".
No debug log id, as there isn't anything to debug or tag a log ID to.
You could have selected the items in your library and have generated a debug log as per the instructions in the issue template and as repeated by the issue but. I'm so incredibly tired of people arguing this point with me. In the time you typed that sentence, you could have generated a debug log.
After updating my laptop, I noticed I did not migrate Better BibTeX config. Now I have the issue of having ~2MB of an exported library with citation keys produced by apparent legacy formula of the form of
_ _year, and fresh Better BibTex has a new formula for these.
If that's the extent of the problem you could have selected the items in your library, right-clicked them, and refresh your citation keys after changing the formula.
Can I import old citation keys en-masse from the old Better BibTeX export, onto the Zotero database that was re-acquired from the Zotero cloud, without citation keys? How could I find the legacy citation key formulas for previous version to reproduce/approximate the old scheme?
I will get you a build that will do it, will take about 15 minutes.
:robot: this is your friendly neighborhood build bot announcing test build 6.7.140.2733.5479 ("fixes #2729")
Install in Zotero by downloading test build 6.7.140.2733.5479, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".
The procedure will be as follows:
On the old PC:
On the new PC:
Closing for inactivity
Debug log ID
N/A
What happened?
Re: the discussion here. https://github.com/retorquere/zotero-better-bibtex/discussions/2729 No debug log id, as there isn't anything to debug or tag a log ID to.
Hello,
After updating my laptop, I noticed I did not migrate Better BibTeX config. Now I have the issue of having ~2MB of an exported library with citation keys produced by apparent legacy formula of the form of__year, and fresh Better BibTex has a new formula for these.
My questions are then: