# Deprecation warnings are causing an exception

**URL:** <https://meta.discourse.org/t/deprecation-warnings-are-causing-an-exception/245583>\
**Category:** Bug\
**Created:** [November 14, 2022, 10:18pm UTC](https://meta.discourse.org/t/deprecation-warnings-are-causing-an-exception/245583 "2022-11-14T22:18:12Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [November 14, 2022, 10:35pm UTC](https://meta.discourse.org/t/deprecation-warnings-are-causing-an-exception/245583/6 "2022-11-14T22:35:39Z")

</div>

We reverted the change via [this commit](https://github.com/discourse/discourse/commit/338901d335228944d5d1fb3675195be93ee8a1ef). Thanks @hithere for identifying the precise issue!

As an immediate workaround, [Safe Mode](https://meta.discourse.org/t/53504?silent=true) should allow you to access the affected forums. That will temporarily disable any themes/plugins which are triggering the deprecation notices.

We’ll get this fix rolled out to our hosting ASAP - very likely within the next hour.

---

_[View the full topic](https://meta.discourse.org/t/deprecation-warnings-are-causing-an-exception/245583)._