search

sawhney17 / logseq-citation-manager

73 stars 12 forks source link

Citation manager does not work anymore with logseq 0.8.1 #33

Closed menelic closed 1 year ago

menelic commented 1 year ago

@sawhney17 hinted that it has to do with logseq switching to new electron...hopefully there is a quick fix to keep this key plugin working with current logseq versions

carljoseph commented 1 year ago

Same for me. v0.8.2 just prints out "inserting..."

sawhney17 commented 1 year ago

Waiting for the next update to have a key api that would allow me to refactor the plug-in. On 24 Aug 2022 at 9:33 AM +0400, carljoseph @.***>, wrote:

Same for me. v0.8.2 just prints out "inserting..." — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

Feivele commented 1 year ago

Alternative solutions meanwhile? Revert to previous version or just wait?

sawhney17 commented 1 year ago

Are any of you on macOS?

menelic commented 1 year ago

No, I am on Linux, Ubuntu 22.04 LTS

carljoseph commented 1 year ago

I'm on macOS

AlexZeitler commented 1 year ago

I'm on macOS

Feivele commented 1 year ago

macOS

sawhney17 commented 1 year ago

Just pushed a new version. 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.

carljoseph commented 1 year ago

Latest version on macOS still has the same problem. It displays the sources in the pop-up but when selecting one it just puts "inserting..." in the text. Same happens regardless of which citation option you select.

sawhney17 commented 1 year ago

Are you sure you've configured a template? On 30 Aug 2022 at 3:20 AM +0400, carljoseph @.***>, wrote:

Latest version on macOS still has the same problem. It displays the sources in the pop-up but when selecting one it just puts "inserting..." in the text. Same happens regardless of which citation option you select. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: @.***>

sawhney17 commented 1 year ago

Yeah, revert for now is the workaround On 25 Aug 2022 at 1:50 PM +0400, Feivele @.***>, wrote:

Alternative solutions meanwhile? Revert to previous version or just wait? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>