logseq / logseq/db-test

Unpublish fails with 404 and the page stays published

Open
#1,203 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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?

Clicking **Unpublish** next to a page's **Published URL** shows "Unpublish failed." The request `DELETE https://logseq.io/pages//` returns **404**.

The page is not unpublished: its short link (`https://logseq.io/p/…`) still serves the page, and the **Published URL** property stays on the page. There is no way to take the page down from the app.

This happens for both published pages in the graph, which were published in January 2026:

```
DELETE https://logseq.io/pages/e710ff0c-7809-4853-95d2-6f24ce14cdd8/184bd8ad-4d4e-4241-93c5-1344678d5a11 404 (Not Found)
DELETE https://logseq.io/pages/e710ff0c-7809-4853-95d2-6f24ce14cdd8/695affc3-8218-44de-9d28-85bb7517a5d1 404 (Not Found)
Error: Unpublish failed (publish.cljs:438)
```

### Reproduce the Bug

1. Open a page that was published to logseq.io (it has a **Published URL** property).
2. Click **Unpublish** next to the URL.
3. "Unpublish failed." appears, and the console shows a 404 for the DELETE request.
4. Open the page's published link. It still loads.

### Expected Behavior

The page is removed from logseq.io, its link stops serving it, and the **Published URL** property is cleared.

### Screenshots

### Browser, Desktop or Mobile Platform Information

macOS 26.6.2, Desktop app 2.0.1 — local build of `6bf8fe772f` (built 2026-09-16)

Contributor guide

No contributing guide indexed for this repository

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 at publish.cljs:438 and trace the Unpublish action and its DELETE request for the graph and page UUIDs. Reproduce the 404 in the app or browser console, then verify that a successful unpublish removes the published page, stops its short link from serving it, and clears the Published URL property.

Written by the indexing model from the issue text.

Assessment

Domain
api, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.