# 1.4.3 Upgrade Oddity?

**URL:** <https://meta.discourse.org/t/1-4-3-upgrade-oddity/36095>\
**Category:** Product Support\
**Created:** [2015 年 11 月 27 日午後 5:56 UTC](https://meta.discourse.org/t/1-4-3-upgrade-oddity/36095 "2015-11-27T17:56:33Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![fearlessfrog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fearlessfrog/32/119653_2.png) [@fearlessfrog](https://meta.discourse.org/u/fearlessfrog)\
**Post date:** [2015 年 11 月 27 日午後 5:56 UTC](https://meta.discourse.org/t/1-4-3-upgrade-oddity/36095/1 "2015-11-27T17:56:33Z")

</div>

We’re on stable 1.4.2 and I saw in /Admin a notification that an upgrade was available.

On the web update page, the discourse\_manager was the only thing enabled to be upgraded, with other updates shown for other packages/plugins but their buttons not enabled.

I upgraded but after it finished when returning to the the /Admin page and going back to select further updates (to update Discourse main, plugins etc) I get the following:

 ![](https://global.discourse-cdn.com/meta/original/3X/f/0/f0f8d03479cd8daded38ead5604910355537ad3d.png)

It’s no problem for me to go in and do that via SSH, but I just wanted to ping incase this wasn’t normal for a stable small point release?

EDIT: I upgraded fine doing the above git pull etc, so really it’s just a question of if it needed to do this or not, i.e. not upgrade via the web admin?

---

_[View the full topic](https://meta.discourse.org/t/1-4-3-upgrade-oddity/36095)._