# Upgrading Discourse before upgrading plugins causes problems

**URL:** https://meta.discourse.org/t/upgrading-discourse-before-upgrading-plugins-causes-problems/61781
**Category:** Feature
**Created:** [April 28, 2017, 2:42pm UTC](https://meta.discourse.org/t/upgrading-discourse-before-upgrading-plugins-causes-problems/61781 "2017-04-28T14:42:25Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [April 29, 2017, 2:26pm UTC](https://meta.discourse.org/t/upgrading-discourse-before-upgrading-plugins-causes-problems/61781/9 "2017-04-29T14:26:10Z")

</div>

If only there was a way to simply eliminate that choice 😬

> [@Discourse Docker Manager: Upgrade All](https://meta.discourse.org/t/discourse-docker-manager-upgrade-all/33808):
>
> The Docker Manager is great for keeping everything up-to-date, but it’s awfully slow when you have more than one thing that needs upgrading, not to mention that you need to restart the web server once for each plugin. I’d like to propose a new button called Upgrade All that would go through and upgrade everything in one quick run, similar to what a ./launcher bootstrap app does. Advantages Disadvantages Less user intera…

---

_[View the full topic](https://meta.discourse.org/t/upgrading-discourse-before-upgrading-plugins-causes-problems/61781)._
