The WordPress admin is full of noise
You log in to publish a post. Before you see your editor, you're hit with: a plugin update notice, a "try our pro version" banner, a dismissed-last-week "review us" popup that came back, two security warnings from plugins you forgot you had, and a "database optimization needed" message from a plugin you haven't touched in a year.
WordPress lets plugins inject notices at will. Most have a dismiss button. Many don't. Some re-appear after updates. There's no central place to see or manage them all.
What most people do instead
A better way: one command, per-notice control
Open the TrueCommander navigator. Type admin notices. Every notice captured from the current admin page appears as a card. Dismiss one permanently. Snooze another for a day. Ignore the two you want visible.
Shown in advanced mode, where commands start with tp. In easy mode you type the same command without the tp prefix.
Dismissed notices stay dismissed. Per-user preference stored in user meta. Snoozed notices re-appear automatically after the snooze period expires. A plugin update that would normally re-inject a dismissed notice can't, the hash of the notice content stays dismissed forever.
How it works
The command hooks into admin_notices at priorities -9999 (start buffer) and 9999 (end buffer) on every admin page load. Output is captured, parsed into individual notice blocks, and each gets a content hash. Dismissed/snoozed hashes are stripped from the output before WordPress renders the admin header, the notices literally never appear.
| Action | Description |
|---|---|
admin notices | Show captured notices for the current admin page (the default, with no flags) |
admin notices -dismiss=HASH | Permanently dismiss a notice by its content hash |
admin notices -snooze=HASH -hours=24 | Hide for N hours (default 24), then it reappears automatically |
admin notices -clear | Reset all dismissed and snoozed state (useful for testing) |
| Scope | Per-user. Each admin manages their own dismissals. |
| Can be used in |
Real example
You manage three client WordPress sites. Each has 15-20 plugins, each with its own flavor of admin noise. On Monday morning, logging into the first site, five notices greet you. Three are informational upsells you'll never act on. One is a "review us" request. One is a legitimate security warning.
You open the navigator and run admin notices. The three upsells get dismissed. The review request gets snoozed so it is gone for now. The security warning stays visible. Tomorrow, Wednesday, next month, none of those dismissed notices return.
You move on to the second client. Same command. Different plugins, different noise. Four minutes total across three sites, and your admin is clean.
Goes further with TrueCommander
tp help lists every command, and admin notices clears the dashboard clutter without hiding the warnings that matter.Frequently asked questions
tp admin notices to list the notices captured from the current admin page, then dismiss or snooze the ones you do not want, individually, instead of clicking X on each one every session.admin notices -dismiss=HASH to hide it permanently, or admin notices -snooze=HASH -hours=24 to hide it for a number of hours (24 by default) before it returns.admin notices -clear to reset all of it. Bind the command to a shortcut to open the manager whenever the admin feels noisy.