logseq / logseq/db-test

Queries that use 'current-page' input fail to load results in side-bar

Open
#1,049 0 comments 0 reactions 1 assignee View on GitHub

@megayu is already working on this.

Since Aug 17, 2026.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

I have a generic query that I use across pages to load items related to that page via the `current-page` input variable. The query is embedded with `/node-embed`

When opening the page in the main window everything looks great, but when opening in the side bar no results load.

https://github.com/user-attachments/assets/a2a3523b-91c3-4094-a151-8b07c373870b

### Reproduce the Bug

1. Create a query using `current-page` input
Example:

```
{:title "##Epics"
:query [:find (pull ?e [:block/title :logseq.property/status :logseq.property/priority])
:in $ ?ctx-title
:where
[?e :block/tags ?t]
[?t :block/title "Epic"]
[?prop :block/title "Project"]
[?prop :db/ident ?attr]
[?e ?attr ?p]
[?p :block/title ?ptitle]
[(clojure.string/lower-case ?ptitle) ?plc]
[(= ?plc ?ctx-title)]]
:inputs [:current-page]}
```

2. Create a *new* page and embed the query with /node-embed

3. Verify the query returns results as expected
4. Open the page in the side-bar
5. see that no results load in the side-bar render of the page

### Expected Behavior

I expect `current-page` to resolve consistently in both the main window and the side-bar.

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

Desktop nightly 20260728

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.