# 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:** 7

<div class="post-metadata">

**Author:** ![neounix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neounix/32/215617_2.png) [@neounix](https://meta.discourse.org/u/neounix)\
**Post date:** [April 17, 2020, 2:35am UTC](https://meta.discourse.org/t/adding-server-side-plugin-disabling-to-safe-mode/148299/7 "2020-04-17T02:35:33Z")

</div>

> [@angus](#):
>
> Adding a automatic disabling of plugins would make it a slightly better solution, reducing the number of instances in which a full restart / config change is required, and better reflecting how non-technical site admins see it.

Yes, if possible someday, it would be very good to have a single “disable all plugins” boolean in the admin settings, which works without any container rebuilding. However, not being a Discourse developer (having only a year of `node.js`, `vuejs` app development), my instincts tell me this is not an easy change and would be a very big change to the architecture.

Our legacy LAMP forum had this feature and we cannot count the times we used this boolean to quickly trap an error as related to plugins. However, the software architecture is so different, it’s not even useful to compare.

I’m personally confident the Discourse Team will come up with something. Lot’s of users are addicted to plugins and there will be more dragons over time.

Thanks for looking into this.

---

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