search

ahonn / logseq-plugin-todo

A simple to-do list plugin for logseq
MIT License
157 stars 11 forks source link

Widget not showing anything #12

Closed Microeinstein closed 2 years ago

Microeinstein commented 2 years ago

Setup

Description Value
OS ~ Distro ArchLinux
Locale IT
App version v0.7.1
App install method custom repository (tried AppImage)
App theme light built-in
Plugin version v1.3.1
Plugin install method marketplace

Message

Hi, I just installed Logseq and your plugin as described, but I can't get the widget to show up the tasks from journal nor from other pages. Am I missing something?

Best regards

Attachments

screenshot

ahonn commented 2 years ago

Please enter the following query in logseq and see if it shows the tasks in the current page?

#+BEGIN_QUERY
{:title "Find tasks"
 :query [:find (pull ?b [*])
     :where
     [?b :block/marker ?marker]
     [(contains? #{"NOW" "LATER" "TODO"} ?marker)]
     [?b :block/page ?p]
     (or
       (and
        [?p :block/journal? true]
        [?p :block/journal-day ?d]
        (not [?b :block/scheduled])
        (not [?b :block/deadline])
        [(<= ?d :today)])
       (and
        (or
          [?b :block/scheduled ?d]
          [?b :block/deadline ?d])
        [(<= ?d :today)]))]}
#+END_QUERY
Microeinstein commented 2 years ago

Tested both in a custom page and the journal — the query correctly detects as specified (journal entries not shown in the screenshot — tested later); the widget remains empty.

screenshot

ahonn commented 2 years ago

It looks like something went wrong. Try opening the console tab in devtools (F12), then click to open the plugin widget and see if there is an error message in the console. Please take a screenshot of what the console shows.

Microeinstein commented 2 years ago

Ctrl+Shift+I worked for me; I don't see any errors, I made you a video (notice the brief freeze of developer tools)

Is it possible for some extensions to conflict with each other?

https://user-images.githubusercontent.com/16826381/172172886-3fc4db94-8be7-4d5b-845e-b7473683410e.mp4

arnefm commented 2 years ago

I'm having the exact same issue. Funny that I'm on Arch Linux too. I've installed Logseq using the logseq-desktop-git package from AUR, so it's completely up to date. The plugin was installed from the marketplace, it's the latest version right now.

webbj74 commented 2 years ago

I'm experiencing this on Manjaro Linux with KDE Plasma (I also installed Logseq via AUR logseq-desktop-git, and plugin from the Marketplace).

Edit to add:

webbj74 commented 2 years ago

Possible cause? The AUR package patches package.json to change the electron version from v15.x to v17.x (to fix a bug with electron & wayland).

See also: logseq/logseq#6032

webbj74 commented 2 years ago

Hmm - when running yarn dev-electron-app from macOS (following logseq's develop-logseq.md), I'm able to replicate this problem.

piyueh commented 2 years ago

I'm the maintainer of the AUR package logseq-desktop-git. Could anyone see if this plugin now works with logseq-desktop-git? It's working on my machine, but I don't really use this plugin, so maybe someone can do more and deeper tests.

The upstream has bumped the version of electron to v19 (and bumped the Logseq version to v0.8), so the only thing I did was to remove the patch for electron version.

haoadoreorange commented 2 years ago

I confirm that the plugin works with logseq-desktop-git, it seems the problem was indeed with the electron version.

arnefm commented 2 years ago

Yes, it works fine now after rebuilding Logseq. I'm now on version 0.8.1, package version 0.8.1.r21.653b72211-1. Not a plugin bug after all!

Microeinstein commented 1 year ago

Sorry for disappearing, I still wanted to say I confirm it's working for me too with Logseq 0.8.8 and mentioned repackaging :+1: immagine