Unplishing Properties URL and Backlink Access.

Closed
  • Is something wrong?
#1,514 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Domain
backend

Research direction

The report concerns a published node URL that remained accessible after the property was removed, using Logseq DB Desktop 2.0.2 on Linux and the online app. Start by checking how unpublishing and removing a published property are handled, then determine whether the URL is still served. Done means a reliable way to remove the publication and confirm that its URL is no longer accessible; the report provides no reproduction steps or code entry point.

Written by the indexing model from the issue text.

Description

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

First and foremost: this is my first time submitting any feedback on Logseq or on Github, second I am not a developer or even remotely knowledgeable about programing so please forgive any mistakes on my part. This is just to provide info, no a complaint of any kind.
I have been testing Logseq DB Desktop version 2.0.2 (the latest current one) on a Linux laptop. Since I enabled sync I regularly suffer data loss so I keep back-ups and recreate the graph to the latest copy under another name and delete the older graph. This carried-over published pages and one node URL that are all password protected. I have attempted to unpublished these pages but could not do so on the desktop edition (fail message each time) but was successful on the online app (at the suggestion of AI, I did not even know an online edition existed to be honest). The only thing that is outstanding was the node "property" URL that refused to be unpublished and held on for dear life until I did "add" under properties and then "delete" which finally removed it (a happy occurrence, not sure I could recreate it), but when the old link is tested on Brave Incognito the page is still present and accessible. It is password protected, and nothing on there is particularly sensitive, but I just wanted to identify that it remains active. If someone can offer a way to confirm that unpublished pages and nodes are truly gone, I would appreciate it.

Here is the still active URL for that node:
Published URL:: https://logseq.io/p/05fqGENCG8

Thank you very much for your assistance.
Cordially
Fabienne

Reproduce the Bug

could not tell you how to reproduce it.

Expected Behavior

No response

Screenshots
Image
Files

No response

Browser, Desktop or Mobile Platform Information

Logseq DB Desktop 2.0.2 for Linux and Online app https://app.logseq.com.

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
No language data
Stars
29
Forks
2
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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/db-test

All issues in logseq/db-test

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.