从 API 删除草稿帖子 - 收到 not_found 错误

zogstrip · 2026 年4 月 22 日 10:32

你试过在查询参数中也传递用户名吗？（即在 URL 末尾添加 ?username=<用户名>）

看来我们在没有提供 username 查询参数时，允许 API 回退到 Api-Username 用户名的方式不够一致。

这个问题应该已在以下提交中修复：

github.com/discourse/discourse

FIX: Drafts/reviewables API returned 404 when acting on own resource (#39449)

main ← fetch-target-user-helper

opened 10:29AM - 22 Apr 26 UTC

ZogStriP

+204 -166

Admin callers using the API to `DELETE /drafts/:id.json` or `DELETE /review/:id.…json` received a `not_found` error when the `username` param was omitted, even though the resource existed and was owned by the API user (`Api-Username`). The destroy actions always called `fetch_user_from_params` on the API path, which raises `Discourse::NotFound` when neither `username` nor `external_id` is provided — forcing callers to redundantly pass `username=<self>` to delete their own resources. Extract the target-user resolution into a shared `fetch_target_user` helper in `ApplicationController` that mirrors the pattern already used by `topics#set_notifications`: for API requests, an admin can target another user via `username`/`external_id`; otherwise the action operates on `current_user`. This also aligns API capabilities with the UI — non-admin API callers can now manage their own drafts/reviewables, matching what they can already do via the web. Migrated call sites: - `DraftsController#destroy` and `#bulk_destroy` - `ReviewablesController#destroy` - `TopicsController#set_notifications` (now uses the helper instead of its inline version) https://meta.discourse.org/t/401220

话题		回复	浏览量
Discourse Drafts api Not working Development rest-api	3	461	2024 年2 月 20 日
Delete draft, user made a draft poll with a million options Support	12	757	2019 年4 月 29 日
API - Delete isn't working Support	1	77	2024 年10 月 3 日
Delete users via API Development	2	971	2019 年1 月 15 日
Delete Post from a Topic Using discourse API Support	6	4441	2018 年10 月 22 日

从 API 删除草稿帖子 - 收到 not_found 错误

相关话题