Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

No way to delete a wiki (recipe) or bag from admin UI/API

Abierto
#138 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
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, typescript

Línea de trabajo

Start by comparing the registered admin routes with the reported /admin/recipe_delete and /admin/bag_delete paths, then inspect the admin-react code and its serverRequest.recipe_delete call. Check how the admin-vanilla interface and recommended Docker image are produced. Done means admins can delete recipes and bags through a supported UI or documented API, with a clear upgrade path for the image.

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

Descripción

Problem

In the current release there appears to be no supported way to delete an existing wiki (recipe) or bag once it has been created:

  1. Admin UI: The recipe edit dialog does not expose a "Delete recipe" / "Delete bag" button. The form only allows editing metadata, bags and plugins.
  2. Admin API: The documented route POST /admin/recipe_delete (and /admin/bag_delete) returns NO_ROUTE_MATCHED / INVALID_REQUEST_PATH on a live instance. Only /admin/load and /admin/save/:tab appear to be registered.

Impact

  • Old sample wikis (mws-docs, docs, dev-docs, tour) and their bags stay visible in /admin forever.
  • Users must resort to manual SQL/Prisma operations against the MWS database, which is risky due to FK constraints (recipe_bags, recipe_acl, tiddlers, tiddler_events, etc.).

Environment

  • MWS version: deployed from the currently recommended Docker image path (no official GHCR release yet).
  • The running image appears to use the admin-vanilla admin interface, while the admin-react code in this repo does contain a Delete Recipe button calling serverRequest.recipe_delete.

Request

  1. Please make sure the delete routes (/admin/recipe_delete, /admin/bag_delete) are registered and callable by admins.
  2. Expose a delete button in the admin UI (or at least document the API).
  3. Publish an official GHCR image and a documented upgrade path, so deployments can move to a version that supports deletion without rebuilding the image locally.

Thanks!

Lenguaje dominante
TypeScript
Estrellas
60
Forks
16
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

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 TiddlyWiki/MultiWikiServer

Todos los issues de TiddlyWiki/MultiWikiServer

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.