Zotero-better-bibtex: Citekey � on Windows for references without citation key, on Mac normal citekeys like zotero-1234

[danieltomasz]

Please verify all of the below before submitting:

1. you have picked the right category for the issue in the previous screen.
2. You are on the latest release of Zotero
3. in the Zotero addons screen you can see that you have the latest release of BBT (https://github.com/retorquere/zotero-better-bibtex/releases/latest)
4. you are posting a single bug or feature request.
5. the issue has a subject that succinctly describes the problem or question.
6. you are available for follow-up questions and testing.
7. you have included an error-report ID here generated by reproducing the problem, selecting the problematic reference(s), right-clicking, and submitting an BBT error report from that popup menu, not from the Help menu.
8. you have included the actual output you got from exporting the items you sent in the debug log, not simplified fictional output or a description of the output, and a sample (not a description) of how you want it to look instead, again based on the actual items you selected in the previous step.

Picking the right issue category is really important. Each category (Export, General error, Import, Key generation, Question) has different instructions for gathering the data necessary required to resolve the issue you are experiencing

The error report is important; it gives me your current BBT settings and a copy of the problematic reference as a test case so I can best replicate your problem. Without it, I'm effectively blind.

Report ID:
6UQDDQXE-euc
Expected behavior:*
**Actual behavior:

Hi, I use Zotero between computers.
I use BetterBibtex plugin. I have my library on two computers
While on Mac for different non-paper entries I have citekeys like zotero-1234, the same entries on windows have non-defined citekeys (citekeys appear as �)
How I could solve that?

[label-gun[bot]]

It looks like you did not upload an debug report. The debug report is important; it gives @retorquere your current BBT settings and a copy of the problematic reference as a test case so he can best replicate your problem. Without it, @retorquere is effectively blind. Debug reports are useful for both bug analysis and enhancement requests; in the case of export enhancements, I need the copy of the references you have in mind.

This request is much more likely than not to apply to you, too, _even if you think it unlikely_, and even if it does not, there's no harm in sending a debug log that turns out to be unnecessary. @retorquere will more often than not just end up saying "please send a debug log first". Let's just skip over the unnecesary delay this entails. Sending a debug log is very easy:

1. If your issue relates to how BBT behaves around a specific reference(s), such as citekey generation or export, select at least one of the problematic reference(s), right-click it, and submit an BBT debug report from that popup menu. If the problem is with export, please do include a sample of what you see exported, and what you expected to see exported for these references.

2. If the issue does not relate to references and is of a more general nature, generate an debug report by restarting Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled), reproducing your problem, and selecting "Send Better BibTeX debug report..." from the help menu.

Once done, you will see a debug ID in red. Please post that debug id in the issue here.

Thank you!

[retorquere]

You've missed point 7.

[danieltomasz]

You've missed point 7.

Thanks, I just updated my initial post.

[blip-bloop]

:robot: this is your friendly neighborhood build bot announcing test build 5.2.53.6961 ("fallback needs a postfix")

Install in Zotero by downloading test build 5.2.53.6961, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

[retorquere]

6961 should fix the problem.

[danieltomasz]

I installed test build and it works!

[retorquere]

Thanks for the confirmation, I've scheduled a new release.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.