Move Tools -> Upgrade to Dashboard -> Updates

[dd32]

As per dev meetup today.

See: ​https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2010-03-04&sort=asc#m86319

[dd32]

(In [13588]) Move Tools -> Upgrade to Dashboard -> Updates. As per dev meetup today. See #12517

[mdawaffe]

Clicking the "Dashboard" menu item now takes me to update-core.php.

[jane]

We probably need to make an Overview item for the actual dashboard screen.

[wpmuguru]

(In [13590]) UI upgrade -> update, see #12517

[hakre]

After commit, filename contains still the old wording: ms-upgrade-network.php

[dd32]

Clicking the "Dashboard" menu item now takes me to update-core.php.

Whoops.. All fixed now.

Should probably add a Bubble there counting sum(core, theme, pugin) updates.

[dd32]

Whoops.. All fixed now.

Err.. Ryan fixed that in [13589], Not sure why i didnt see the commit.. Eitherway, That reduces the conditionals called anyway.

[dd32]

(In [13593]) Add an update count bubble to the Updates menu. See #12517

[caesarsgrunt]

Replying to dd32:

Clicking the "Dashboard" menu item now takes me to update-core.php.

Whoops.. All fixed now.

It still does this in r13597...

[dd32]

It still does this in r13597...

What configuration are you running under? Multisite? Administrator? Other Account?

Should've been fixed by ryan in [13589]

[dd32]

(In [13603]) Do not count Development versions of WordPress as having a core-update available. See #12517

[dd32]

(In [13607]) GUU: Add Update breakdown to Title attribute of update bubble. See #12517

[caesarsgrunt]

Standard installation (not multisite - actually I haven't worked out how to install it as multisite yet). Administrator account (using name caesar, not admin). No other accounts set up.

[dd32]

Standard installation (not multisite - actually I haven't worked out how to install it as multisite yet). Administrator account (using name caesar, not admin). No other accounts set up.

Got the same setup here, I cant fault it.

Your wp-admin/menu.php file isnt out of date is it?

[caesarsgrunt]

Not sure what that file is, but I'll have a look and I'll install from scratch, and report back.

[caesarsgrunt]

Working fine now after reinstalling. Sorry for the false alarm...

[hakre]

Are URLs (that stuff that can be typed into your browser's address bar) considered part of the UI or not? If those are considered part, the file should reflect the new wording so that it can be requested as intended.

[dd32]

Are URLs (that stuff that can be typed into your browser's address bar) considered part of the UI or not?

They generally would be, however - Since this is a pre-existing file, and we already have a 'update.php' and 'upgrade.php', I think its best to leave this as-is.

Can anyone see anything that needs to be implemented here before this ticket is closed? Bugs can go into new tickets.

[nacin]

Actually..

We currently list updates for inactive plugins and themes. Those are included in the bubble. In testing themes and downloads, I've downloaded quite a few on a testbed, and now I'm getting a bubble of '5' even though I'm using Twenty Ten and have no plans to use those in the future.

I'm not so concerned about the bubble, but we do say "You are running version %s", which isn't exactly accurate for an inactive plugin or theme. The string should indicate "installed," and more so, it'd be nice for inactive vs. active to be indicated.

Aside from all that, I'm noticing the bubble is blue on hover, orange normally, and gray when you're on the Dashboard menu. Was the idea to eliminate the orange? It just seems kind of inconsistent.

[dd32]

Just because a theme or plugin is inactive, i dont see why they shouldn't recieve update notifications. Plugin-wise, some people may decide to disable a plugin until its updated, an update may include a fix for a problem they're having. For themes, I agree that most will never use the theme even though its installed, but take Multisite, or any other scenario where multiple installs use the same theme repo (Custom content dir's, custom wp-config.php's etc)... just because it isnt used on the current site, doesnt mean its not used elsewhere..

The bubble mimicks the comment bubble, and the plugin update bubble, all use the same colours. If anything, the Blue should go.. (and be replaced with the grey)

[jane]

@dd32: agreed. Use case for themes, though:
-user loves their theme.
-user sees new WP feature and wants to use it, but theme doesn't support it, so they deactivate and use a different theme, waiting for the original theme author to do an update to support the new WP feature.

I'd like to see updates on everything showing up, even if it's deactivated.

[nacin]

I'm agree with including inactive plugins and themes. I was actually just setting myself up for the string and the bubble color. So:

• Orange/blue/gray -- pick two. (Orange is leftover from 2.6. Is our goal to eliminate it?)

• "You are running" to something that's accurate. I'd kind of like to see an indicator of what is active versus inactive when looking through bulk upgrades. Or, we change the string for both active and inactive to something "You have version %s installed."

[johnonolan]

As far as I remember from the last UI meetings Jane is looking to get rid of the orange, however I think we do need a bright color there to indicate the call the action when active - I don't think blue is strong enough. Gray works for if it's inactive.

I think "You have version %s installed." works fine

[johnonolan]

Related: #13236

[nacin]

(In [14496]) Use a more generic string for GUU plugins and themes, as inactive items aren't 'running.' fixes #12517.