TiddlyWiki / TiddlyWiki/MultiWikiServer

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

Open
#138 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
60
Forks
16
PR merge metrics
No merged PRs in 30d

Description

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!

Contributor guide

Open the contributing guide

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 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.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
api, backend, devops, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.