# Adding server-side plugin disabling to safe mode

**URL:** <https://meta.discourse.org/t/adding-server-side-plugin-disabling-to-safe-mode/148299>\
**Category:** Development\
**Created:** [April 17, 2020, 12:04am UTC](https://meta.discourse.org/t/adding-server-side-plugin-disabling-to-safe-mode/148299 "2020-04-17T00:04:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)\
**Post date:** [April 17, 2020, 12:28am UTC](https://meta.discourse.org/t/adding-server-side-plugin-disabling-to-safe-mode/148299/3 "2020-04-17T00:28:01Z")

</div>

True.

I think the key point is that non-technical site admins look for a fix to get their site working when it’s broken. A “[Safe mode](https://meta.discourse.org/t/53504?silent=true)” is often perceived to do that (rightly or wrongly). Perhaps a way to do this would be to have additional admin safe-mode controls.

You could add a big button in the /admin/plugins route to automatically disable all plugins in the same way, however I wonder whether it would have the same effect. Perhaps it would.

I’m also drawn to this as it’s quite doable within the current Discourse plugin architecture.

---

_[View the full topic](https://meta.discourse.org/t/adding-server-side-plugin-disabling-to-safe-mode/148299)._