I have been trying out the new ‘Nested Replies’ feature in version 2026.6.0-latest - but found that replies to unrelated threads are appearing as ‘nested’ responses to user posts, and much of any given thread can simply disappear, to great confusion all round.
I wonder if this might be something to do with this nesting feature not correctly handling messages received via the pre-existing reply by email function?
Most of my users reply by email - and those replies are being directed to the correct threads when nesting is turned off - but as soon as nested replies is activated, the replies are seemingly shuffled to random other threads.
As soon as the feature is deactivated again, sanity returns.
We use the in reply to post number to determine where to put a post in nested mode. What I believe is happening is that users are replying via email to specific posts and they’re being nested in a way that doesn’t make them immediately visible. Does that sound correct?
Or are you saying posts are going to the wrong topic entirely? Any screenshots or further specifics would be helpful.
Thanks for using the feature and providing feedback!
Hi @markvanlan When I tried enabling it again, I was not able to replicate my experience with replies from other topics completely appearing in nested view, though am pretty sure that is what I was seeing.
However, I can confirm that many or most replies belonging to any given thread still disappear when nested view is active. I will try attaching nested vs non nested screenshots of same example topic below
Even worse, this time when I deactivated nested view again, every topic I had just tested was then returning ‘error 404’ (until I exited the forum web page and reopened it)
So, it seems like browser caching may be involved at some level.
Now nested threads have the correct number of posts - or at least the samples I have checked do.
The update process initially broke my site, apparently due to an old database import template reference in app.yml that was invoking mySQL12 - deleting that line and trying again resolved it.
- "templates/import/mysql-dep.template.yml"
Not sure why this happened, because Discourse has been successfully updated many times over many years with that line in place.
I wonder if something in a change added since the official full 2026.6.0-latest release (which update did not have any issues) has added some sort of new sensitivity?
