WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 3 years ago

#36787 closed feature request (wontfix)

A button to upgrade latest point release when automatic updates fail.

Reported by: rhyswynne Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.4.2
Component: Upgrade/Install Keywords: close
Focuses: Cc:

Description

Hi There,

I've a couple of legacy client sites that cause a break in jQuery which we all know about. As such we've kept these installations on the 4.4.x branch for now. With the release of 4.5.2, 4.4.3 also saw a release.

For whatever reason, the automatic update didn't happen straight away, so we're having to update the sites via FTP to the 4.4.3 branch.

It would be great, as well as the "Upgrade to 4.5.2" button in the Upgrade Page, there would be a "Upgrade to 4.4.3" somewhere, maybe a lot smaller and in a secondary style?

Change History (3)

#1 @swissspidy
4 years ago

  • Component changed from General to Upgrade/Install

For whatever reason, the automatic update didn't happen straight away, so we're having to update the sites via FTP to the 4.4.3 branch.

Automatic updates are rolled out over multiple hours to reduce server load on the dotorg infrastructure.

It would be great, as well as the "Upgrade to 4.5.2" button in the Upgrade Page, there would be a "Upgrade to 4.4.3" somewhere, maybe a lot smaller and in a secondary style?

There are already 4 buttons to update your WordPress installation:

https://cldup.com/OXQhilPdT1.png

Adding another two buttons there would result in a UI that is even more cluttered. That's why we strive to remove most of these buttons in the Shiny Updates feature plugin.

Also, I think we all want people to be on the latest and greatest WordPress version. Giving them an option to choose between 4.4.3 and 4.5.2 doesn't support that.

#2 @dd32
4 years ago

  • Keywords close added

There are already 4 buttons to update your WordPress installation:

FWIW That's only when running a development version, if you're running a stable release it would have only offered the option to update.

Also, I think we all want people to be on the latest and greatest WordPress version. Giving them an option to choose between 4.4.3 and 4.5.2 doesn't support that.

I would also agree with this and wouldn't support adding an option to update to a point release on an older branch.

Developers who understand what they're doing can achieve this using CLI tools, GIT/SVN externals, or using the ZIP directly.

#3 @swissspidy
3 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.