Unplishing Properties URL and Backlink Access.

Chiusa
  • Qualcosa non va?
#1,514 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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!)
Lingua principale
Nessun dato sulla lingua
Stelle
29
Fork
2
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di logseq/db-test

Tutte le issue di logseq/db-test

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.