by Linkon Miyan
5 (2 reviews)
Fatal Plugin Auto Deactivator - Never let a plugin break your site
Automatically deactivates plugins that cause fatal errors to prevent site crashes and keep your WordPress site running smoothly.
Compatible with WP 7
v1.3.0
Current Version v1.3.0
Updated 3 weeks ago
Last Update on 24 Jun, 2026
Refreshed 11 hours ago
Last Refreshed on
Rank
#17,705
—
No change
Active Installs
80+
-7%
KW Avg Position
19.2
-18.8 better
Downloads
786
+4 today
Support Resolved
0%
—
No change
Rating
100%
Review 5 out of 5
5
(2 reviews)
Next Milestone 90
80+
90+
648
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 6 more installs to reach 90+
Rank Changes
Current
#17,705
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
5.0
2 reviews
Overall
100%
5
2
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 5 of 5| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| crash prevention | 1 | — | Tag | 2 days ago |
| fatal error | 5 | — | Tag | 2 days ago |
| plugin deactivation | 5 | — | Tag | 2 days ago |
| error handling | 12 | — | Tag | 2 days ago |
| site protection | 73 | — | Tag | 2 days ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.3.0
- Last Updated
- Jun 24, 2026
- Requires WP
- 5.3+
- Tested Up To
- 7
- PHP Version
- 7.0 or higher
- Author
- Linkon Miyan
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 2
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Fatal Plugin Auto Deactivator - Never let a plugin break your site
No, Fatal Plugin Auto Deactivator works automatically right after activation with no configuration required.
No, the plugin only activates its core functionality during the PHP shutdown phase and only takes action when a fatal error is detected.
The plugin catches fatal PHP errors, parse errors, and other critical errors that would normally crash your site.
Yes, an admin notice will be displayed in your WordPress dashboard showing which plugin was deactivated and the specific error that caused it.
Yes, you can reactivate the plugin through the normal WordPress plugins page. However, be aware that if the issue hasn't been fixed, the plugin will be deactivated again if it causes another fatal error.
Yes. Go to Tools → Fatal Plugin Log → Settings and add the plugin to the "Protected plugins" list. Protected plugins are never deactivated automatically — for example, you may prefer to keep a checkout or payments plugin running and fix it manually rather than have it switched off. The fatal error is still logged and an honest message is shown on the error page.
Yes. Enable "Log-only mode" under Tools → Fatal Plugin Log → Settings. The plugin will keep detecting and logging fatal errors and showing the custom error page, but it will never deactivate a plugin.
The Fatal Plugin Log page shows a status banner ("Protection active" or a warning), and if the protection drop-in is missing, was replaced by another plugin, or could not be installed (for example because wp-content is not writable), you'll see an admin notice and a Site Health test telling you, with a one-click "Reinstall protection" button.
The current version is designed for standard WordPress installations. Multisite support may be added in future updates.
The plugin compares the file path of the fatal error against the directories of your active plugins. When the error originates inside an active plugin's folder, that specific plugin is deactivated. Errors originating outside the plugins directory — such as in a theme, a must-use plugin, a drop-in, or WordPress core — are still logged and shown on the custom error page, but nothing is deactivated.