by
Daniel Chase
1 (0 reviews)
Faultline – Error Log Assistant
See which plugin caused each PHP error, open the exact line of code, get alerted to fatal errors, and keep routine notices out of debug.log.
Faultline ranks #66,091 among WordPress.org plugins with 1+ active installations, is #3,668 of 5,310 in the Utilities & Tools category, a 1/5 rating from 0 reviews, and was last updated Oct 18, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.5
Current Version v1.5
Updated 2 weeks ago
Last Update on 18 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
#3,668 of 5,310 in Utilities & Tools
Actively maintained
Rank
#66,091
—
No change
Active Installs
1+
—
No change
KW Avg Position
90
—
No change
Downloads
516
+114 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
53,154
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
#66,091
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.5
- Last Updated
- Oct 18, 2026
- Requires WP
- 5.8+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- Daniel Chase
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
Elementor Website Builder – more than just a page builder
10M+ installs
#1
Contact Form 7
10M+ installs
#3
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
3M+ installs
#19
Hostinger Tools
3M+ installs
#20
WordPress Importer
2M+ installs
#23
WPS Hide Login
2M+ installs
#27
Frequently Asked Questions
Common questions about Faultline – Error Log Assistant
Activate Faultline and go to Tools > Faultline. If logging is off, Setup turns it on for you. The Log tab then shows every entry with its severity, the plugin or theme that caused it, and a link to the source code.
Each entry on the Log tab has a "Caused by" label naming the plugin or theme, with a link to that plugin's WordPress.org support forum. "Draft forum post" writes a support request with the error and your site details filled in.
Use Setup: it is one click. Three settings have to be right together (WP_DEBUG, WP_DEBUG_LOG and WP_DEBUG_DISPLAY), or either nothing is logged or errors are shown to your visitors. Faultline sets all three in wp-config.php for you, with a backup first. If your host does not allow that, it gives you the lines to paste in.
Under Settings, tick the types to suppress: notices, deprecation warnings, coding-standard suggestions and, if you choose, warnings. Suppressed messages are never written, so there is nothing to clean up.
Faultline keeps it small in four ways: suppressed messages are never written, repeated entries are trimmed to the first and newest 10 copies each day, old entries are removed after 30 days (14 for notices and deprecations), and the file is capped at 50 MB. All four can be changed under Settings.
It may be. debug.log usually sits in a folder your web server serves, and it contains server paths and stack traces. Faultline requests your log over the web the way a stranger would and tells you whether it could be read. Setup runs this check at the end, and you can repeat it on the Status tab. If the log can be read, a warning shows on every admin screen until it is fixed. There are two fixes: move the log to a private file name that bots cannot guess (one click, works on any server, keeps every entry), or add a blocking rule for Apache, LiteSpeed, nginx or IIS. On nginx only your host can usually add the rule, so Faultline writes the message to send them.
No. Setup looks for the PHP error logs your site was writing before, such as the error_log files hosting control panels create, and offers to copy their recent entries into the new log. The original files are only read, never edited, moved or deleted. Automatic cleanup also waits until you finish or skip Setup.
It can. Faultline shows every log entry with its severity, the plugin or theme that caused it and the source code, alerts you to fatal errors, and keeps routine notices out of debug.log.
Faultline is built for acting on errors, not only reading them. It names the plugin or theme behind each error, opens the line of code that failed, drafts a support request, and links to AI help with private details removed. It can also stop routine notices and deprecation warnings being written in the first place. All of this is free.
No. Faultline only ever keeps messages out of the log. It never changes PHP's error reporting level and never turns on WP_DEBUG_DISPLAY, the setting that prints errors on screen. Setup sets WP_DEBUG_DISPLAY to false.
