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

Widget not showing anything #12

Closed
Microeinstein opened this issue Jun 2, 2022 · 12 comments
Closed

Widget not showing anything #12

Microeinstein opened this issue Jun 2, 2022 · 12 comments

Comments

@Microeinstein
Copy link

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
Copy link
Owner

ahonn commented Jun 6, 2022

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
Copy link
Author

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
Copy link
Owner

ahonn commented Jun 6, 2022

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
Copy link
Author

Microeinstein commented Jun 6, 2022

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?

screen-2022-06-06_15.41.28.mp4

@arnefm
Copy link

arnefm commented Jul 10, 2022

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
Copy link

webbj74 commented Jul 22, 2022

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:

  • Experienced this issue with TODO List v1.5.0 and Logseq v0.7.8 on Manjaro
  • DO NOT experience this issue with on macOS with above versions
  • I posted a comment to AUR referencing this issue.

@webbj74
Copy link

webbj74 commented Jul 25, 2022

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
Copy link

webbj74 commented Jul 25, 2022

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

@piyueh
Copy link

piyueh commented Aug 9, 2022

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
Copy link

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

@arnefm
Copy link

arnefm commented Aug 22, 2022

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!

@ahonn ahonn pinned this issue Sep 6, 2022
@ahonn ahonn closed this as completed Sep 20, 2022
@Microeinstein
Copy link
Author

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

@ahonn ahonn unpinned this issue Mar 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants