logseq / logseq/logseq

In-line page reference using `[[]]` does not show the name of page.

Open
#13,087 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
45k
Forks
2.8k
Avg merge
1d 22h
Merged PRs (30d)
105

Description

### Search first

- [ ] I searched and no similar issues were found

### What Happened?

I have written a few blocks in my Journal page, and upon using inline references for a few pages, one of them decided to disappear while typing. All linked references of that page has no interactable inline-references anymore.

### Reproduce the Bug

1. Reference a page in the journal,
2. Write some text - I had written about 1 parent and 3 child blocks worth of text.
3. Make 4 other inline references
4. On the 5th reference, the 1st reference had disappeared.
However, I was unable to reproduce this bug

### Expected Behavior

References should not disappear, and be click-able.

### Screenshots

https://github.com/user-attachments/assets/360db6df-db6a-4199-8735-8ee9baacaca6

### Desktop or Mobile Platform Information

MacOS 26.5.2
Logseq installed via homebrew.

### 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

Open the contributing guide

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.

Research direction

Start with inline page references in a Journal page and follow the reported sequence: create blocks, add references, write text, then add more references. Compare the screenshot and expected behavior while checking whether an earlier reference disappears or loses clickability; done means references remain visible and interactable. The report notes that the bug could not be reproduced, so confirming a reliable reproduction is the first step.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.