Cannot enter an 'editor' field (better BibLaTeX)

[svann576]

Debug log ID

GTSMCP3J-refs-euc/6.7.250-6

What happened?

I cannot enter an 'editor' field, only an 'editors' field. When entering

tex.editors = Joe

it exports correctly, while entering

tex.editor = Joe

exports no editor. I came across this issue when I had book entry that only listed editors, no authors, and better biblatex had not exported any of them. This manual attempt at fixing things however did not help: it seems that my biblatex setup expects the 'editor' field, not 'editors'; if an entry only has the latter, it ignores them completely.

Another test is entering a post-script:

ex.add({ name: 'editors', value: 'test' });

this results in a 'test' field for every item, but

ex.add({ name: 'editor', value: 'test' });

outputs nothing.

[github-actions]

Hello @svann576,

@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”.

[retorquere]

D<number> debug logs go to the Zotero team, I cannot access those, and it lacks information I need. Please see point 1. above how to send a BBT debug log.

[svann576]

Edited, see above.

[retorquere]

you have editor in your skip fields.

[svann576]

I am so sorry, this is embarrassing. Sorry for wasting your time!

[github-actions]

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.

[retorquere]

No problem.

You can also add them in the extra field as

editor: Lastname || Firstname

and that will work for both BBT and Zotero itself