Sometimes UUID is shown instead of title for links in blocks
@megayu is already working on this.
Since Jul 8, 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 noticed this in several places:
#### When editing a block in the journal.
I can't reproduce it with most pages. But with most linked tags.
Maybe this happens now with every new page, but not when linking existing ones?
#### When exporting a block.
Text:
> Ich hab [[Max]] getroffen und wir haben [[Tennis]] gespielt.
This seem now the default behavior since few versions.
```
{:logseq.db.sqlite.export/block
{:block/title
"Ich hab [[6a3d7146-b84e-4cc2-88d8-963be052e826]] getroffen und wir haben [[69c4140f-c5c9-4103-b443-4b6a7aa1bcd1]] gespielt.",
:build/tags #{:user.class/SocialLog-b3bUHRH5}},
:pages-and-blocks
[{:page
{:block/title "Max",
:block/uuid #uuid "6a3d7146-b84e-4cc2-88d8-963be052e826",
:build/keep-uuid? true}}
{:page
{:block/title "Tennis",
:block/uuid #uuid "69c4140f-c5c9-4103-b443-4b6a7aa1bcd1",
:build/keep-uuid? true}}],
:classes {:user.class/SocialLog-b3bUHRH5 {:block/title "SocialLog"}},
:logseq.db.sqlite.export/export-type :block}
```
#### When setting properties.
Demo: https://www.youtube.com/watch?v=YrHQTDwAZ4g
### Reproduce the Bug
1. Link to page. Then check if title is used or UUID.
2. Link to Tag
3. Select property that is a reference to a tagged page
### Expected Behavior
Always use human-readable title and not UUID. I think an end-user should not see UUIDs.
### Screenshots
_No response_
### Files
_No response_
### Browser, Desktop or Mobile Platform Information
NixOS 25.11.10684.8fd9daa3db09
Logseq-linux-x86_64-2.0.1-alpha+nightly.20260624
### 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.