zotero-mdnotes
zotero-mdnotes copied to clipboard
Can't automatically use citekey as mdnotes' title with the latest version of BetterBibTex
Describe the bug Can't create mdnotes using citekey as mdnotes' title. Only can create mdnotes when don't use citekey as title. This bug happened when BetterBibTex was updated to the latest version. The citekey seems alright in the paper's info, so it may be the calling procedure that go wrong.
To Reproduce Steps to reproduce the behavior:
- Go to "Tools ->Mdnotes preferences", turn on the option"Use the item's citekey as title"
- Right click the paper.
- Go to "Mdnotes->Create Mdnotes file"
- Nothing will happen as there should be a file-saving window
Expected behavior I would really appreciate it if this issue related to BetterBibTex recent update could be solved soon.
Screenshots
It should show a window like this but it wasn't.
Desktop (please complete the following information):
- OS: [Windows 10]
- Zotero version: [v6.0.27]
- Mdnotes version: [v0.2.3]
- Zotfile version: [v5.1.2]
- BetterBibtex version: [v6.7.132]
I had the same problem yesterday.
同样的问题,还重装了mdnotes,点击创建相同的Mdnotes文件没有响应
Hey there, I ran into the same issue this morning. It was caused by a recent update to BetterBibTex that made some naming changes. I've submitted a pull request (#225) that fixes the issue.
This is not a problem with mdnotes, it is caused by the BetterBibtex update on October 24th. I fixed the problem by rolling back the version of BetterBibtex.
I solved it, I rolled better-bibtex's version back to the old one.I choseI chose thehttps://github.com/retorquere/zotero-better-bibtex/releases/tag/v6.7.77
I have also encountered this problem.
I solved it, I rolled better-bibtex's version back to the old one.I choseI chose thehttps://github.com/retorquere/zotero-better-bibtex/releases/tag/v6.7.77
Please don't suggest this as a general solution. MdNotes will have to update.
This is not a problem with mdnotes, it is caused by the BetterBibtex update on October 24th.
Rather, BBT has changed, and MdNotes will have to follow.
And a fix for this has been available since late October last year: #225