エラー：リクエストされた URL またはリソースが見つかりません

zogstrip · 2026 年 5 月 12 日午後 1:29

ローカル環境で再現できましたが、予想よりも少し複雑でした。ただし、修正中です

github.com/discourse/discourse

FIX: Saving an edit on a reply can fail after expanding replies (#39919)

main ← fix-edit-reply-after-expanding-replies

opened 01:05PM - 12 May 26 UTC

ZogStriP

+53 -1

Editing a post that's a reply produced a "The requested URL or resource could no…t be found" dialog when the post had been viewed via its parent's expanded replies list. The dialog came from a `PUT /post_replies/:id` request that 404s; the URL should be `PUT /posts/:id`. `loadMoreReplies` calls `store.find("post-reply", …)` then `store.createRecord("post", reply)` on each result. The first stamps `__type = "post-reply"` (and `__munge`, `__state`) onto each model. The second re-hydrates the same `id` under `post` — and the topic stream's canonical post for that `id` is already in the store. `_hydrate`'s "update existing" path copies those internal fields onto the canonical record via `setProperties`, so a later `post.save()` builds its URL from the wrong `__type`. Fix: skip every `__`-prefixed key when diffing in `_hydrate`'s update path. Internal store/RestModel metadata stamped at hydration time has no business being carried across types. The `__` prefix is the existing convention for "internal", so future additions are protected by the same guard. https://meta.discourse.org/t/402747

トピック		返信	表示
出错了：找不到请求的 url 或资源。 Bug	2	23	2026 年 5 月 12 日
Random 404 errors when editing posts Bug	13	949	2021 年 4 月 7 日
Reply to post link shows address bar URL instead of link to replied to post Feature	5	2651	2016 年 1 月 21 日
Can't quote reply to post Bug	3	1438	2015 年 10 月 23 日
Reply on Original Topic - undefined Bug	12	998	2020 年 4 月 6 日

エラー：リクエストされた URL またはリソースが見つかりません

関連トピック