Make WordPress Core

Opened 6 years ago

Last modified 4 months ago

#15101 new enhancement

Update Message Reduces User Orientation reg. WordPress Version

Reported by: hakre Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 2.5
Component: Upgrade/Install Keywords: has-patch
Focuses: Cc:


This is a usability issue many customers are telling me: When there is a WordPress update message, the current version is not prominent any longer.

Normally the current version is displayed in the admin's footer. If there is a (very promintent "on top") update message, this version information get's hidden in footer as well.

The only place where a user can find the current version is in some dashboard widget. That location is hard to find. And that location is hard to describe on the phone, e.g. in support.

I suggest to restore the current version display in the footer, because a footer is very easy to find and to describe by phone.

Additionally the update message on top should display the current version number as well. Something Like There is a new version available, you're currently running (should be 65%-70% of the width in english text of a 1024 width screen (970 or so viewport size) to allow this to be translated w/o consuming too much of the screen real estate).

Attachments (4)

15101.diff (1.7 KB) - added by dd32 3 years ago.
15101.2.diff (562 bytes) - added by circlecube 3 years ago.
Adding current WP version to update string.
31046.diff (1.3 KB) - added by dd32 20 months ago.
version-421-update-to-422.png (11.8 KB) - added by dd32 20 months ago.

Download all attachments as: .zip

Change History (22)

#1 @hakre
6 years ago

  • Component changed from General to Upgrade/Install
  • Version set to 3.1

#2 @scribu
6 years ago

I agree with showing the current verision in the footer.

#3 @scribu
6 years ago


#4 @dd32
6 years ago

  • Milestone changed from Awaiting Review to Future Release

It does seem a little weird, and is probably something that should be implemented whilst reworking some of the strings and UX of the upgrade pages.

3 years ago

#5 @dd32
3 years ago

  • Keywords has-patch added

This still seems like something we should do.

Attached a rough patch, any thoughts on the exact strings? I tried to keep HTML out of it, but it's pretty ugly..

#6 @SergeyBiryukov
3 years ago

  • Version changed from 3.1 to 2.5

Introduced in [7237].

3 years ago

Adding current WP version to update string.

#7 @circlecube
3 years ago

I'd agree. I am missing this feature every single time I update any install. I need to know how big the update is before I hit the button.

How about mirroring the language used for the plugins: You have x.x.x. installed. Short and sweet, see 15101.2.diff

#8 follow-up: @SergeyBiryukov
3 years ago

I think the long-term plan is to de-emphasize version numbers in favor of background updates:

#9 @MadtownLems
21 months ago

The long-term plan to de-emphasize version numbers in favor of background updates is well and good, but that doesn't mean there isn't a very valid desire from many of us to have easy access to this information in the footer. That being said, I do completely understand the intent behind NOT showing them.

What if you only show the current version number if Automatic Upgrades are disabled? I think this shows the information to people who need it most, and hides it from those who it doesn't matter as much for.

#10 @circlecube
21 months ago

I agree. I think it's worth pointing out that we have two users to consider here. The power users who are primarily the ones updating sites, and the masses who rarely run their update, the actual crowd who these background updates are for (I dare say). We can either ignore the power users who want to know this in favor of the masses who likely don't know or even care what version they are running. Or we can display a statistic which will be helpful to the power users who are seeing this update page more often than others and display information that is just as easily ignored to the masses.

Running an update is something that will likely not be happening on a site with automatic background updates anyways, so that's almost a moot point. If the background update runs, then the whole point is that the user doesn't have to go to the update screen... so they wouldn't see it anyways. But those who do see the screen during an update will find it helpful, rather than having to jump back to the dashboard page which still (rather prominently) displays the current version number (I'd say in a place where it's of much less use than the page where you can essentially change the version you're running.

#11 @dd32
20 months ago

#31046 was marked as a duplicate.

20 months ago

#12 @aymanalzarrad
19 months ago

Any updates on this?

#13 @daxelrod
18 months ago

#32211 was marked as a duplicate.

#14 @SergeyBiryukov
17 months ago

#33512 was marked as a duplicate.

#15 @Vayu
15 months ago

  • Type changed from defect (bug) to enhancement

I really would like to have this information too.

#16 in reply to: ↑ 8 @SergeyBiryukov
12 months ago

Replying to SergeyBiryukov:

I think the long-term plan is to de-emphasize version numbers in favor of background updates

Related: #35554

#17 @netweb
8 months ago

#36871 was marked as a duplicate.

#18 @markshep
4 months ago

Has the version number really not been displayed on the upgrade screen for six years? I guess there's not much chance of this getting fixed if it's been that long :-(.

Displaying this information would be really useful for anyone who either wants to or needs to manually upgrade WordPress. I'm in the situation where I'm forced to manually upgrade the various WordPress sites I run because the automatic updates don't work for me. When I go to the upgrade page for a site I'd really like to know what the currently running version of WordPress is so I know how far behind that particular site is.

I really don't understand the rationale for hiding this information. Those who don't need to know can just ignore it, but those of us who do want to know would find it very useful.

Note: See TracTickets for help on using tickets.