search

sawhney17 / logseq-citation-manager

73 stars 12 forks source link

No existing db could be found #37

Closed zerone01y closed 1 year ago

zerone01y commented 1 year ago

I've been using the plugin for some time and it worked ok. But recently it seems unable to find the database, even if I reindex the citation db. I did not change any of the settings during the period. Please help, thanks!

sawhney17 commented 1 year ago

A few versions back broke something so you You will have to reconfigure the .bib export. It now has to be located in .logseq/storage/logseq-citation-manager and in settings, you just give the filename with extension(like starred-items.bib), no need for the file path. On 8 Sep 2022 at 6:32 AM +0400, lingyiy @.***>, wrote:

I've been using the plugin for some time and it worked ok. But recently it seems unable to find the database, even if I reindex the citation db. I did not change any of the settings during the period. Please help, thanks! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

zerone01y commented 1 year ago

Thanks!! Yes, I realized it is due to the new updates. A humble suggestion, could you please include these breaking updates in the readme file? This is because people like me may just update the plugins in batch from logseq, without knowing what is actually changed. It would be easier to read about the changes on the description page in logseq.

github-actions[bot] commented 1 year ago

:tada: This issue has been resolved in version 2.0.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

sawhney17 commented 1 year ago

Excellent idea. I just pushed an update with some fixes for inline insertion. I’ve also updated the readme On 8 Sep 2022 at 8:00 AM +0400, lingyiy @.***>, wrote:

Thanks!! Yes, I realized it is due to the new updates. A humble suggestion, could you please include these breaking updates in the readme file? This is because people like me may just update the plugins in batch from logseq, without knowing what is actually changed. It would be easier to read about the changes on the description page in logseq. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>