# Replied post doesnt display as such

**URL:** <https://meta.discourse.org/t/replied-post-doesnt-display-as-such/214841>\
**Category:** Support\
**Created:** [January 14, 2022, 10:14am UTC](https://meta.discourse.org/t/replied-post-doesnt-display-as-such/214841 "2022-01-14T10:14:35Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Thomas\_Bushell](https://avatars.discourse-cdn.com/v4/letter/t/45deac/32.png) [@Thomas\_Bushell](https://meta.discourse.org/u/Thomas_Bushell)\
**Post date:** [June 5, 2023, 11:43pm UTC](https://meta.discourse.org/t/replied-post-doesnt-display-as-such/214841/9 "2023-06-05T23:43:25Z")

</div>

> [@JammyDodger](#):
>
> I think it does occasionally catch people out. 🙂 If you check out the Related Topics feature at the bottom of the topic you’ll see a few other examples over the years:

Yeah, I did see those topics. Obviously, we are not the only people who did not expect this behaviour. Probably many more who haven’t filed “bug” reports like I did. Though I glad to see that this has been addressed with a config option…maybe the Justin devs don’t know about it.

I was worried that all hell might break loose if this were turned on. As a former dev, I’ve certainly seen situations where changing some seemingly innocuous setting causes a complete rebuilding of the message database, massive increases in storage requirements, and similar carnage.

I was reassured in my other thread that this would not happen. Was that your experience as well?

---

_[View the full topic](https://meta.discourse.org/t/replied-post-doesnt-display-as-such/214841)._
