Every plugin gets to shout at the top of wp-admin, and they all do: licence reminders, review requests, setup wizards, update nags. The existing answer is to hide them, and that creates a worse problem: a genuinely critical warning disappears along with the sales pitch.<\/p>\n\n
Notice Triage does not hide anything. It ranks. It captures every admin notice, works out which plugin or theme emitted it (by reflecting on the hook callback, not by guessing from the text), sorts it into a severity bucket and shows one summary bar: \"6 notices \u2014 2 need action, 3 informational, 1 license\". Critical notices stay inline by default, exactly where they were, unmodified. The log then tells you which plugin has shown you the same nag 400 times. Setup banners and onboarding bars that are not standard notice markup are collapsed as well; scripts and hidden templates pass through untouched. Nothing is deleted, nothing is rewritten; the panel simply moves the noise out of the way and labels each notice with its source.<\/p>\n\n
Severity comes from the notice's declared type, then its CSS classes, then a list of keywords that can only raise a notice (security, failed, database error\u2026). The keyword and marketing lists are visible and editable in Settings and filterable in code.<\/p>\n\n
Tools \u2192 Notice Log lists every distinct notice this admin has seen: the plugin behind it, its bucket, when it first and last appeared and how often it has interrupted you (counted at most once every five minutes per notice, so the log costs nothing on busy sites). The same count shows next to each notice in the panel. From there you can mute a notice for everyone, snooze it for 7 or 30 days, or pin it inline or collapsed regardless of its bucket. Each notice in the panel also has a per-user Snooze link (7 days), and administrators get a Mute link right there. Counters and dates are normalised before logging, so \"3 items need attention\" and \"4 items need attention\" are one entry.<\/p>\n\n
This plugin intercepts other plugins' output, so the recovery paths come first:<\/p>\n\n
define( 'NOTICE_TRIAGE_DISABLE', true );<\/code> in wp-config.php switches capture off entirely.<\/li>\n- Append
?notice_triage_off=1<\/code> to any admin URL to bypass capture for that one page load \u2014 no FTP needed.<\/li>\n- Capture never runs during AJAX, REST, cron, the Customizer, iframes, or on the update and install screens, and never before the admin screen is known.<\/li>\n
- A per-plugin \"always inline\" rule and a screen exclusion list exempt anything whose own scripts rely on inline notices.<\/li>\n
- A notice callback that throws is caught and logged instead of taking down wp-admin.<\/li>\n<\/ul>\n\n
Captured markup is re-emitted byte-for-byte, including ids, classes, data attributes and inline scripts, so each plugin's own dismiss buttons and AJAX handlers keep working.<\/p>\n\n
Compatibility<\/h4>\n\n
Checked on WordPress 7.1 with each plugin's current release, on a clean site. \"Dismiss\" means the plugin's own dismiss control was clicked inside the collapsed panel and the notice stayed dismissed after a reload.<\/p>\n\n
\n- Yoast SEO<\/strong> \u2014 captured, attributed, \"blocking robots\" is Critical (inline), first-run configuration notice is Informational. No dismiss control on its notices.<\/li>\n
- Rank Math SEO<\/strong> \u2014 captured and attributed; \"only one SEO plugin\" is Critical and stays inline, its own dismiss works.<\/li>\n
- Elementor<\/strong> \u2014 captured and attributed; promotional notices land in Informational, its own dismiss control (
e-notice__dismiss<\/code>) works inside the panel and persists.<\/li>\n- WooCommerce<\/strong> \u2014 no admin_notices output on a fresh store (its notes live in the WooCommerce Admin app). The panel renders on WooCommerce screens without conflict.<\/li>\n
- Jetpack<\/strong> \u2014 its connection banners are injected by JavaScript, not printed as admin notices, so they are neither captured nor affected.<\/li>\n
- Wordfence<\/strong> \u2014 captured and attributed (\"Needs action\"); its dismiss button works inside the panel and persists. Its onboarding banner is not a notice and passes through untouched.<\/li>\n
- WPForms<\/strong> \u2014 removes every admin notice on its own screens itself; elsewhere nothing to capture on a fresh install.<\/li>\n
- Contact Form 7<\/strong> \u2014 emits no notices on a fresh install; no conflict.<\/li>\n
- UpdraftPlus<\/strong> \u2014 welcome notice captured on its settings screen as Informational.<\/li>\n<\/ul>\n\n
No plugin needed the shipped \"always inline\" list, which is therefore empty in this release.<\/p>\n\n
Known limitation<\/h4>\n\n
A plugin whose JavaScript binds to a position-dependent selector, or binds before the panel exists in the page, may lose its dismiss button when its notice is collapsed. Set that plugin to \"Always inline\" in Settings \u2192 Notice Triage \u2192 Per-plugin rules.<\/p>\n\n
Privacy<\/h4>\n\n
Notice Triage stores the plain-text excerpt, source and counts of each notice in a table on your site. It makes no outbound requests and sends nothing anywhere.<\/p>\n\n\n
\n- Upload the
notice-triage<\/code> folder to \/wp-content\/plugins\/<\/code>, or install it from the Plugins screen.<\/li>\n- Activate it.<\/li>\n
- Open any admin screen: non-critical notices are now in a single collapsed panel. Tools \u2192 Notice Log shows what has been seen; Settings \u2192 Notice Triage holds the rules.<\/li>\n<\/ol>\n\n\n
\nHow is this different from the notice-hiding plugins?<\/h3><\/dt>\nThree things. Attribution: every notice is labelled with the plugin or theme whose callback printed it, resolved from the code, so you know who is shouting. Ranking: notices are sorted into Critical, Needs action, Informational and Marketing & license, with a guard rail that never demotes an error notice, so critical warnings cannot vanish into a \"hidden\" pile. The log: each distinct notice is counted, so you can see which plugin has interrupted you hundreds of times and act on that plugin rather than on one banner.<\/p><\/dd>\n
Does it hide anything?<\/h3><\/dt>\nNot on its own. Every notice is either inline or inside the panel. The only way a notice disappears is a mute or snooze you set yourself, and the panel still counts them. If you collapse the Critical bucket, the panel forces itself open whenever a critical notice is present.<\/p><\/dd>\n