# Ability to hide previous revisions (after enabling the option in admin)

**URL:** <https://meta.discourse.org/t/ability-to-hide-previous-revisions-after-enabling-the-option-in-admin/29939>\
**Category:** Feature\
**Created:** [2015年六月12日 16:09 UTC](https://meta.discourse.org/t/ability-to-hide-previous-revisions-after-enabling-the-option-in-admin/29939 "2015-06-12T16:09:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**Post date:** [2015年六月12日 16:09 UTC](https://meta.discourse.org/t/ability-to-hide-previous-revisions-after-enabling-the-option-in-admin/29939/1 "2015-06-12T16:09:39Z")

</div>

I’ve just pulled the trigger on this option in admin,

> `edit history visible to public`  
> Allow everyone to see previous versions of an edited post. When disabled, only staff members can view.

However, the existing post revisions are still there over an hour later. Will this go back and prevent existing changes from being seen, or does it only effect future posts?

Thanks!

EDIT - Removed reference to @mcwumbly 's feature which deletes certain edits. That appeared to work within moments/refresh.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2015年六月12日 22:16 UTC](https://meta.discourse.org/t/ability-to-hide-previous-revisions-after-enabling-the-option-in-admin/29939/4 "2015-06-12T22:16:14Z")

</div>

This is a default on option. Did you have it off for some reason?

---

<div class="post-metadata">

**Author:** ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**Post date:** [2015年六月12日 22:43 UTC](https://meta.discourse.org/t/ability-to-hide-previous-revisions-after-enabling-the-option-in-admin/29939/5 "2015-06-12T22:43:15Z")

</div>

I turned it off today, and non-moderator/staff could still see revisions an hour later.

So, I’m asking to see what the expected behavior is, for edits which happened when that was still on.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2015年六月12日 22:44 UTC](https://meta.discourse.org/t/ability-to-hide-previous-revisions-after-enabling-the-option-in-admin/29939/6 "2015-06-12T22:44:48Z")

</div>

I think you might need to dump state and reboot the docker container for this change to take effect, e.g. it is held in memory persistently by Redis or the like.

There are a handful of settings like this in the app.

---

<div class="post-metadata">

**Author:** ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**Post date:** [2015年六月12日 23:07 UTC](https://meta.discourse.org/t/ability-to-hide-previous-revisions-after-enabling-the-option-in-admin/29939/7 "2015-06-12T23:07:37Z")

</div>

ok cool. I think I’ve hit that before on other settings.. would be great to have a “reboot required” next to those.

How should we handle that on hosted discourse?

---

<div class="post-metadata">

**Author:** ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)\
**Post date:** [2025年十二月4日 11:36 UTC](https://meta.discourse.org/t/ability-to-hide-previous-revisions-after-enabling-the-option-in-admin/29939/8 "2025-12-04T11:36:00Z")

</div>