logseq / logseq/logseq

Publishing: Link to an aliased page should render page

Open
#5,280 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

can-be-reproduced props:alias publishing
Dominant language
Clojure
Stars
45k
Forks
2.8k
Avg merge
1d 22h
Merged PRs (30d)
105

Description

### What happened?

In the context of Page Publishing with only public pages generation, the page content is not displayed if called by its alias name.

### Reproduce the Bug

1. Create a page "BACK-PAGE"
2. Set it public, with an alias (ie: BP)
```
public:: true
alias:: BP
```
3. Create another page "FRONT-PAGE"
4. Type
```
Feel free to see my #back-page or my #bp
```
6. PUBLISH the graph
7. Check the graph output
=> Upon clicking on first link the page is seen. The second link is not showing anything - just like if the page wasn't public.
Link are differents:
url 1: file:///E:/Documents/testgraph/index.html#/page/back-page => my page
url 2: file:///E:/Documents/testgraph/index.html#/page/bp => nothing

### Expected Behavior

If a published page is called by its alias, it should be displayed

### Screenshots

_No response_

### Desktop Platform Information

Logseq 0.6.8

### Mobile Platform Information

_No response_

### Additional Context

_No response_

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 by reproducing the published graph with a public page that has an alias, then compare the generated links for the page name and alias. Trace the publishing and page-link handling used by the reproduced case. Done means both links render the same published page when opened in the graph output.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.