Make WordPress Core

Opened 4 years ago

Last modified 4 years ago

#49055 new enhancement

Standardise Plugin Notices With a Fly-Out Right-Hand Menu

Reported by: crdunst's profile crdunst Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Administration Keywords: close
Focuses: ui Cc:


Following on from my previous ticket, I have another suggestion, borne out of frustration.

Background: I'm primarily a developer, but with a background in UI design. I've been building with WP for 8 years, and work with client sites day-to-day when they're loaded with plugins, rather than 'vanilla' installs.

I'd like to suggest standardising plugin notices.

There's such a varying approach to plugin notices. In addition to the top 'header area', being misused for adverts:

  • Some plugin authors post notices under the 'upgrade' link in the plugin list (Woo is bad for this)
  • Some launch a notice in the header area after upgrading their plugin, and loading a page, with a 'What's new' etc.
  • Random adverts displaying occasionally 'do you like our plugin?'
  • I've started seeing notices pop-up on the front end. An analytics plugin, notifying you if you're signed in that you're not tracked.

Plugin authors all think their notices are useful, but they're not if you update 15 plugins doing the same thing, all in different ways, often at inconvenient times, within the global template. The plugins own pages are fair-game though.

My suggestion for standardisation would be a right-hand fly-out menu for plugin notices. Perhaps an icon top right could indicate new notices are available - click the icon to fly-out the right-hand menu.

Within the right-hand menu, plugins can place a notice of their choice - whether informative, up-selling or whatever. End-users could then dismiss an individual notice, or mute a plugin entirely.

Change History (2)

#1 @knutsp
4 years ago

  • Component changed from Menus to Administration
  • Focuses accessibility removed
  • Keywords close added
  • Version 5.3.2 deleted
Note: See TracTickets for help on using tickets.