by
Emtiaz Zahid
1 (0 reviews)
Faultwright – Error Monitor, Cron & Email Failure Alerts
Every PHP error, JavaScript error, failed cron job, failed email and failed update on one screen, explained in plain English, with what changed.
Faultwright ranks #62,511 among WordPress.org plugins with 1+ active installations, is #2,110 of 3,634 in the Communication category, a 1/5 rating from 0 reviews, and was last updated Oct 26, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.1.0
Current Version v1.1.0
Updated 1 week ago
Last Update on 26 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
#2,110 of 3,634 in Communication
Downloads +56.7% this week
Actively maintained
Rank
#62,511
—
No change
Active Installs
1+
—
No change
KW Avg Position
N/A
—
No change
Downloads
615
+75 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
49,574
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
Need 8 more installs to reach 10+
Rank Changes
Current
#62,511
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.1.0
- Last Updated
- Oct 26, 2026
- Requires WP
- 6.4+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- Emtiaz Zahid
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar 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
Contact Form 7
10M+ installs
#3
WP Mail SMTP by WPForms – SMTP for Reliable Email Delivery with Gmail, Outlook, Amazon SES, Brevo, Other SMTP & More
4M+ installs
#12
MC4WP: Mailchimp for WordPress
1M+ installs
#35
Hostinger Reach – AI-Powered Email Marketing for WordPress
1M+ installs
#41
Popup Builder & Popup Maker for WordPress – OptinMonster Email Marketing and Lead Generation
1M+ installs
#53
Flamingo
800K+ installs
#79
FluentSMTP – WP Mail SMTP Plugin with Amazon SES, SendGrid, Mailgun, Postmark, Cloudflare, toSend, Gmail and Any SMTP
700K+ installs
#87
Joinchat – Enhanced “click to chat”
700K+ installs
#89
Frequently Asked Questions
Common questions about Faultwright – Error Monitor, Cron & Email Failure Alerts
Yes. Faultwright never reads or changes PHP's error-reporting level, so it cannot tell whether a call was wrapped in @. Warnings are grouped and counted, so a silenced call that fails repeatedly shows up as one group. Notices and deprecations are off by default and can be enabled in Settings.
No. When nothing goes wrong, the PHP handler costs well under a millisecond and no database queries run on the front end. The JavaScript collector is 1.5 KB and only talks to the server when an error happens. Sampling lets you record a fraction of front-end visitors.
No. Faultwright captures errors directly. If WP_DEBUG_LOG is on, new lines in debug.log are imported as well and de-duplicated.
No. Nothing leaves your site unless you turn on "Explain with AI", with a provider connected under Settings → Connectors or your own API key, and use it on an issue. There is no telemetry.
A tiny file copied into wp-content/mu-plugins that loads Faultwright before every other plugin, so a fatal error raised while another plugin starts up is still captured. You can remove it from Settings → Capture at any time; uninstalling deletes it.
It explains them and points at the most likely culprit with the change history. Rolling a plugin back or contacting the author remains a manual step.
Error records store the visitor's role, never a user ID, email address or IP address. IP addresses are hashed (/24) for rate limiting only and expire after one minute. Query strings are stripped from recorded URLs by default. Failed-email records keep the subject line and, optionally, the recipient domain, never the full address. The change log records which logged-in user activated, updated or changed something, so you can see who did what. The plugin adds a suggested paragraph to Settings → Privacy → Policy Guide.
No. Faultwright has no server of its own and sends no usage statistics or telemetry. Errors are stored in your own database; the browser collector posts to your own site's REST API. The only outbound requests are the optional AI explanations described under "External services", off until you turn them on and connect a provider under Settings → Connectors or enter your own API key.
Yes, on WordPress 7.0 and later. Choose "WordPress AI (Settings → Connectors)" under Faultwright → Settings → Explanations (it is the default for new installs there), and requests go through WordPress's built-in AI Client to the provider you connected, with the key WordPress keeps. On older WordPress versions, or if you prefer, you can enter your own API key for OpenAI, Anthropic, Google Gemini or an OpenAI-compatible endpoint instead.
The admin app and the browser collector ship un-minified in assets/src/; the files in assets/build/ are produced from them with npm install && npm run build (the package.json is included). Nothing else is compiled or obfuscated.
