Unplishing Properties URL and Backlink Access.

Cerrado
  • ¿Algo no está bien?
#1,514 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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!)
Lenguaje dominante
Sin datos de lenguaje
Estrellas
29
Forks
2
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de logseq/db-test

Todos los issues de logseq/db-test

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.