Link to a local file creates a page with the name of the path

Questions & Help
1

Hi everyone, whenever I create a link to a local file, Logseq creates a page with the name of the path. For example, [link name](file://C:/file.pdf) will create a link that opens the PDF, but it will also create a page called “C:/file.pdf”. Is there a way to prevent that? Thanks

2

FWIW that doesn’t happen for me on 0.4.1

3

I just tried it and yes → Logseq search reported a page with the name of the path. (It didn’t create a physical page).

I assume this is a bug.

Re-Index does NOT get rid of this “page” in the search result :frowning:

4

I am using versions 0.4.4 and this doesn’t happen anymore. It seems to be fixed

5

I noticed that this problem is happening again with me on version 0.4.9. Can anyone else confirm that? Thanks

6

This still happens to me on MacOS with version 0.7.5. When I link to an external file, multiple pages get created, each separated by a slash. Re-indexing recreates deleted pages.

7

Hi @Sarah_C, there is this workaround that I found somewhere, that is to remove the double slash and write the link like this (file:C:/file.pdf). I don’t know why, but it is working for me so far.

1 Like
8

This syntax opens a local file without moving it:

`FILENAME

E.g.:

`[Textfile.odt](<file:///C:/Directory1/Directory2/Textfile .odt>)

where:

FILENAME = ” Textfile.odt”

DRIVELETTER = ”C:/”

PATH: ”Directory1/Directory2/”