by Service2Client LLC 0 (0 reviews)

Error Sniffing Pug – Tells you what broke

Name: Error Sniffing Pug – Tells you what broke
Author: Service2Client LLC

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,155 among WordPress.org plugins with 100+ active installations, is #1,120 of 5,310 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.8 (Current: 7.1.4)

v0.5.0 Current Version v0.5.0

Updated 2 months ago Last Update on 03 Sep, 2026

Refreshed 1 week ago Last Refreshed on

#1,120 of 5,310 in Utilities & Tools Top 25% by installs

View on WordPress.org

Rank

#13,155

— No change

Active Installs

100+

-48.5%

KW Avg Position

48.3

0.5 worse

Downloads

514

+6 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 200

Total Progress 88%

100+ 200+

481

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 12 more installs to reach 200+

Rank Changes

Current #13,155

Change

Best #

Upgrade to Pro

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

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

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%

0 (0%)

Security History

Source: WPVulnerability

No known vulnerabilities on record for Error Sniffing Pug. Checked 2 months ago.

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 0.5.0
Last Updated: Sep 03, 2026
Requires WP: 5.2+
Tested Up To: 7.0.8
PHP Version: 7.0 or higher
Author: Service2Client LLC

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

crash debugging error-handler fatal error troubleshooting

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,015

Elementor Website Builder – more than just a page builder

10M+ installs

Contact Form 7

10M+ installs

All-in-One WP Migration and Backup

5M+ installs

#10

UpdraftPlus: WP Backup & Migration Plugin

4M+ installs

#14

WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager

View all Utilities-and-tools plugins

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 error is captured; the next time you open wp-admin, Pug shows a dismissible notice linking to the report. Nothing is ever shown to your visitors.