Error: Requested URL or resource not found

zogstrip · May 12, 2026, 1:29pm

I was able to reproduce locally but it’s somewhat trickier than I anticipated. I have a fix in progress though

github.com/discourse/discourse

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

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

merged 07:07PM - 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

Topic		Replies	Views
出错了：找不到请求的 url 或资源。 Bug	2	23	May 12, 2026
Random 404 errors when editing posts Bug	13	949	April 7, 2021
Reply to post link shows address bar URL instead of link to replied to post Feature	5	2651	January 21, 2016
Can't quote reply to post Bug	3	1438	October 23, 2015
Reply on Original Topic - undefined Bug	12	998	April 6, 2020

Error: Requested URL or resource not found

Related topics