Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Aliases shown in All Pages

Open
  • Is something wrong?
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
clojure
Domain
frontend

Research direction

Start in the All pages view and reproduce the issue with a page containing aliases, then compare its displayed entries and backlink counts with the DB version mentioned in the report. Trace the All pages and backlink behavior until the relevant entry point is identified; done means only pages appear and the main page reflects backlinks from the page and its aliases.

Written by the indexing model from the issue text.

Description

Search first
  • I searched and no similar issues were found
What Happened?

It should only show pages.

Reproduce the Bug
  1. Create a page, e.g. "Test Page"
  2. Add aliases, e,g.: alias:: Test Alias, Test Alias 2, Test Alias 3
  3. Now the aliases are shown in All pages. Also notices how they are shown to have 1 backlinks, while the page has 0.
  4. Now link to the page and aliases, e.g.:
- [[Test Page]]
- [[Test Alias]]
- [[Test Alias 2]]
- [[Test Alias 3]]
- [[Test Alias 3]]
- [[Test Alias 3]]
  1. Now "Test Alias 3" has 4 backlinks while "Test Page" has 1. This way of counting is not logical and makes it impossible to see which topic really is important in the graph. The main page should add up all backlinks for the page and any backlink! This seem to work in DB version.
Expected Behavior

All pages should only show pages, nothing else.

Screenshots

After Step 3.:

Image

After Step 4.:

Image
Desktop or Mobile Platform Information

NixOS 25.11.10134.26ef669cffa9
Logseq Desktop (AppImage) 1.0.0 (Current Revision: 680b371)

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!)
Dominant language
Clojure
Stars
316
Forks
56
No merged PRs in 30d

Getting set up

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.

More from logseq/og

All issues in logseq/og

Similar issues

More Clojure issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.