Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin seems not to work with Logseq 0.10.2 #48

Closed
tangit86 opened this issue Dec 22, 2023 · 11 comments · Fixed by #50
Closed

Plugin seems not to work with Logseq 0.10.2 #48

tangit86 opened this issue Dec 22, 2023 · 11 comments · Fixed by #50
Labels

Comments

@tangit86
Copy link

tangit86 commented Dec 22, 2023

Just updated Logseq to v0.10.2 (Ubuntu - Logseq-linux-x64-0.10.2.appimage) and:

  • plugin fails to render menu items (buttons) and doesn't catch changes and/or impossible to commit/push
  • no errors in the console

Uninstalled, restarted Logseq, re-installed and still non functional.

Switched back to v.0.9.19 version of Logseq and it functions as expected again.

@andzejsp
Copy link

andzejsp commented Dec 22, 2023

0.10.2 not working, 0.10.1 works for me. Windows 10.

P.s. would be nice feature if you could add checkbox to plugin settings for when you press Ctrl + S to commit, that it either push or dont push to remote. Sometimes i dont want to push to remote, and just work locally but it always gives me error when i Ctrl + S that it has no remote to push to and its annoying.

Plugin works great, thank you!

@DawMatt
Copy link

DawMatt commented Dec 23, 2023

The Developer Tools console contains the following message when the plugin is enabled in 0.10.2:

index-c9525fa1.js:145 Uncaught (in promise) Error: Not existed method #git_execCommand
    at br.R (lsplugin.core.js:2:49378)
    at br.<anonymous> (lsplugin.core.js:2:93271)
    at a.emit (lsplugin.core.js:2:28521)
    at X.<anonymous> (lsplugin.core.js:2:88623)
    at lsplugin.core.js:2:53506
    at Array.forEach (<anonymous>)
    at X.listener (lsplugin.core.js:2:53491)
    at g (helpers.js:151:57)

It is also worth noting that the inbuilt Logseq auto-commit functionality doesn't seem to be working in 0.10.2. I rolled back to 0.10.1 and the Git functionality is working again.

This "Plugin API" enhancement may be a factor? logseq/logseq#10399

@ssilb4
Copy link

ssilb4 commented Dec 23, 2023

@DawMatt @andzejsp @tangit86 Thank you!!!! I am using logseq with git at first. but It doesn't work. It is because of 0.10.2. You save my 7 hours.

@kadd13
Copy link

kadd13 commented Dec 25, 2023

same . windows 11, logseq 10.2 . Last commit from the author of this plugin was 5 month ago. Maybe some alternatives, except 101 ?

@kadd13
Copy link

kadd13 commented Dec 25, 2023

same . windows 11, logseq 10.2 . Last commit from the author of this plugin was 5 month ago. Maybe some alternatives, except 101 ?

even 10.3 version. When i press ctrl+S - red bot brgins to blink, but nothing happens

@philipmorg
Copy link

When i press ctrl+S - red bot brgins to blink, but nothing happens

Same here; Logseq 0.10.3 on Windows 11

@Chanstien
Copy link

Same issue; Logseq 0.10.3; Win 10

@tibitTW
Copy link

tibitTW commented Dec 27, 2023

Same here; Logseq 0.10.3; macOS Sonoma 14.2.1(23C71)

@xyhp915
Copy link
Contributor

xyhp915 commented Dec 27, 2023

A quick patch PR for the latest Logseq release #50

Copy link

🎉 This issue has been resolved in version 1.5.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@andzejsp
Copy link

confirming, it works on 0.10.3 windows 10, thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants