# Problem with post revisions after updating to 2.8.6 stable or 2.9.0.beta7

**URL:** <https://meta.discourse.org/t/problem-with-post-revisions-after-updating-to-2-8-6-stable-or-2-9-0-beta7/232885>\
**Category:** Bug\
**Created:** [July 14, 2022, 3:34pm UTC](https://meta.discourse.org/t/problem-with-post-revisions-after-updating-to-2-8-6-stable-or-2-9-0-beta7/232885 "2022-07-14T15:34:21Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [July 15, 2022, 11:13am UTC](https://meta.discourse.org/t/problem-with-post-revisions-after-updating-to-2-8-6-stable-or-2-9-0-beta7/232885/15 "2022-07-15T11:13:59Z")

</div>

Unfortunately I don’t think disabling the plugin will make any difference. The problematic data is already stored in the database, so it’s there to stay. I think we can safely add `Symbol` to the list of allowed classes. I’ll do that 👀

Edit: to be clear, this isn’t really the plugin’s fault. Previously, any data type was allowed to be stored in the PostRevision. The Rails security issue means we’ve had to suddenly change the behaviour and limit the allowed data types.

---

_[View the full topic](https://meta.discourse.org/t/problem-with-post-revisions-after-updating-to-2-8-6-stable-or-2-9-0-beta7/232885)._