Make WordPress Core

#56932 closed feature request (wontfix)

Using color for disabled plugins

Reported by: zhelev81's profile zhelev81 Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Plugins Keywords:
Focuses: ui, css, administration Cc:

Description

Hello i suggest using a colored line for disabled plugins in “plugins”. This will make them more visible the the admin.

For example the active plugins are with blue so we can do the inactive with pink for example.

Attaching a screenshot

https://i.ibb.co/Jm5S2Rw/Screenshot-7.jpg

it will be nice to see this update … it will be useful for people that testing plugins all the time 🙂

Change History (5)

#1 @SergeyBiryukov
21 months ago

  • Component changed from General to Plugins
  • Focuses ui administration added

#2 @SergeyBiryukov
21 months ago

  • Summary changed from Using color for desabled plugins to Using color for disabled plugins

#3 @desrosj
21 months ago

  • Version 6.1 deleted

Version indicates the first version of WordPress affected by a problem. Since this is not new to 6.1, going to clear that field.

#4 @sabernhardt
21 months ago

  • Keywords 2nd-opinion close added

Thanks for the suggestion! However, I think styling like this would be better coming from a plugin than from WordPress Core.

The plugins list already has multiple indicators to show whether a plugin is active or not:

  1. Inactive plugins do not have any special border on the side, so the absence of the blue border should be more obvious than a color difference (especially for anyone who has difficulty perceiving color).
  2. The active plugin rows have a light blue background color instead of white.
  3. Active plugin names have a heavier font-weight.
  4. Inactive plugins have a red Delete link that is not available when the plugin is active.

In my testing sites, I may click the "Active" filter link below the heading to verify that only specific plugins are active. I usually have so many inactive plugins that I prefer not to look at every row to determine the difference.

#5 @desrosj
19 months ago

  • Keywords 2nd-opinion close removed
  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from assigned to closed

I agree with @sabernhardt above that this seems to be sufficiently handled already.

It's been several weeks and no further reasoning has been provided as to how this suggestion would be an improvement to the overall user experience. If there's a specific benefit to this change (such as an accessibility improvement), then this can always be reopened in the future.

Note: See TracTickets for help on using tickets.