Error Sniffing Pug – Tells you what broke
by Service2Client LLC 0 (0 reviews)

Error Sniffing Pug – Tells you what broke

Turns a WordPress fatal error into a plain-language diagnosis, names the plugin at fault, emails you the reason, and prepares a bug report.

Error Sniffing Pug ranks #13,353 among WordPress.org plugins with 100+ active installations, is #1,111 of 4,938 in the Utilities & Tools category, and was last updated Sep 3, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.4 (Current: 7.1)
v0.5.0 Current Version v0.5.0
Updated 1 week ago Last Update on 03 Sep, 2026
Refreshed 12 hours ago Last Refreshed on
#1,111 of 4,938 in Utilities & Tools Top 25% by installs Downloads -36.4% this week Actively maintained
View on WordPress.org
Rank
#13,353
+31 this week
Active Installs
100+
-193%
KW Avg Position
75.3
No change
Downloads
326
+2 today
Support Resolved
0%
No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 200

Total Progress 46%
100+ 200+
6,050
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 54 more installs to reach 200+

Rank Changes

13,299 13,416 13,533 13,649 13,766 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026
6,433 21,427 36,421 51,415 66,409 01-09-2026 02-09-2026 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026
Current #13,353
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 20 30 40 50 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026
0 100 01-09-2026 02-09-2026 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0
0 reviews
Overall 0%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Security History

Source: WPVulnerability

No known vulnerabilities on record for Error Sniffing Pug. Checked 1 week ago.

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress site owners and administrators who want to quickly understand why their site crashed with a fatal error. It catches fatal errors as they happen, identifies the plugin, theme, or must-use plugin responsible, explains the cause in plain language, and prepares a privacy-safe bug report you can submit yourself.

  • Plain-language error diagnosis
  • Identifies plugin at fault
  • Crash-notification emails
  • Privacy-safe bug report generation
  • After-crash admin notice
  • Plugin conflict scanner
  • Uses WordPress fatal-error-handler drop-in
  • Checks plugin on WordPress.org API

Frequently Asked Questions

Common questions about Error Sniffing Pug – Tells you what broke

No. Pug does its work on the admin side and on the error path only. On a normal page load it does almost nothing; the diagnosis, help links, and reports are all generated when you open a crash report, not on every request.
fatal-error-handler.php is Pug's capture drop-in, installed on activation. It is a standard WordPress drop-in location — the only path from which core will load a custom fatal handler. Pug installs, updates, and removes it for you, and will never overwrite one that belongs to another plugin.
Only one fatal-error-handler.php can exist. If another plugin got there first, Pug will not overwrite it, and Pug's capture will not run. Pug tells you this in the admin so you can decide which one to keep.
Pug supports PHP 7.0 and newer. On PHP older than 7.0 it deactivates its own code quietly rather than causing errors.
No. Diagnosis is done locally. The bug report for a plugin author is copy-and-paste — you send it, Pug doesn't. The notification email goes only to the address you configure, through your own site's mail.
Two ways, both private to you: point Pug at a notification email and it writes to you shortly after a fatal is captured, and the next time you open wp-admin Pug shows a dismissible notice linking to the report. Nothing is ever shown to your visitors.

Sign In / Register

You need to sign in or register to use this feature.