Make WordPress Core

Opened 5 years ago

Last modified 6 months ago

#45437 new enhancement

On plugin update screen, offer more information and options

Reported by: krogsgard's profile krogsgard Owned by:
Milestone: Future Release Priority: normal
Severity: minor Version:
Component: Upgrade/Install Keywords: shiny-updates needs-design
Focuses: administration Cc:

Description

On the plugin update screen, where all available updates to plugins show, there would be some really neat information to be able to see:

  • Is this plugin active on my website right now?
  • Delete this (or these) plugin(s) rather than update

There is currently not a lot of information on this screen, and some of that information could be useful, particularly in eliminating cruft or unnecessary and no longer used plugins.

I did a very rough sketch of what I mean, and some information / actions that could be useful. Now that we have synchronous same-screen plugin actionability this may even end up being able to be somewhat elegant.

https://www.dropbox.com/s/5un8qycsy017jov/plugin-updates.png

Attachments (1)

plugin-updates.png (174.3 KB) - added by krogsgard 5 years ago.
Image of very basic mockup

Download all attachments as: .zip

Change History (6)

@krogsgard
5 years ago

Image of very basic mockup

#1 @swissspidy
5 years ago

  • Keywords shiny-updates added

#2 @jorbin
5 years ago

  • Keywords needs-design added
  • Milestone changed from Awaiting Review to Future Release

I love the idea. Adding the needs-design keyword so that the design team can review this and potentially iterate on the mockup.

#3 @SergeyBiryukov
5 years ago

Would it be a good idea to always display active plugins first, i.e. in the list table on Plugins screen too? (Also suggested in #44696 and #45056.) Seems consistent with the Themes screen, where the active theme is displayed first.

This ticket was mentioned in Slack in #design by chaion07. View the logs.


6 months ago

#5 @richtabor
6 months ago

This came up in triage today. I'm not sure why this table is any different from the table used in Installed Plugins. If they were the same components, you'd have an existing/known UX pattern in place to depict activated plugins. If this moves forward, we should probably just do that.

Note: See TracTickets for help on using tickets.