Description
Every time something breaks on your WordPress site, Conflict Radar helps you answer one question fast: what changed right before it broke?
It quietly records every plugin, theme, and core update, reads your PHP error log into a readable table, and gives you a simple health score — so a white screen or a broken checkout becomes a five-minute diagnosis instead of an afternoon of guesswork.
Built for agencies, WooCommerce store owners, and freelance developers who maintain sites they can’t afford to have break silently.
Free features
- Update tracking — Automatically logs every plugin, theme, and WordPress core update: what changed, from which version to which, who triggered it, and whether it was manual or automatic.
- PHP error log reader — Parses your debug log into a clean, sortable table. See fatal errors, warnings, and notices without FTP access or digging through raw files.
- Site health score — A simple 0–100 score based on recent errors and updates, so you get an at-a-glance pulse on your site’s stability.
- Dashboard widget — A compact summary right on your WordPress dashboard: health score, recent updates, and error counts.
Pro features
Conflict Radar Pro adds the capability that turns raw logs into answers:
- Error/update correlation — After every update, Conflict Radar watches for new errors and automatically flags the update that likely caused them (“3 new errors appeared 8 minutes after Plugin X updated”).
- Email alerts — Get notified the moment a fatal error or a correlated conflict appears, plus an optional weekly health digest.
- Extended history and reporting — Longer retention and scheduled reports.
Privacy
Conflict Radar stores all data locally in your own WordPress database. It does not send your update history, error logs, or site data to any external server.
Screenshots
Installation
- Upload the
conflict-radarfolder to/wp-content/plugins/, or install directly through the WordPress Plugins screen. - Activate the plugin through the Plugins screen in WordPress.
- Visit Conflict Radar in your admin menu to see your update history, error log, and health score.
For error log monitoring, make sure WP_DEBUG and WP_DEBUG_LOG are enabled in your wp-config.php. Conflict Radar will show a notice if logging is disabled.
FAQ
-
Does Conflict Radar slow down my site?
-
No. It reads your error log in the background on a schedule and records updates only when they happen. There is no front-end overhead for your visitors.
-
Do I need WP_DEBUG enabled?
-
For the error log reader, yes — Conflict Radar reads WordPress’s standard debug log. If logging is disabled, the plugin will tell you how to enable it. Update tracking and the health score work regardless.
-
Does it send my data anywhere?
-
No. All update history and error data stays in your own database. Nothing is transmitted to an external service.
-
What’s the difference between free and Pro?
-
Free records and shows you what happened — updates, errors, and a health score. Pro correlates errors to the updates that caused them, sends email alerts, and adds extended history and reporting.
-
Does it work on WordPress Multisite?
-
The free version runs on individual sites. Multisite network features are part of Pro.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Conflict Radar” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Conflict Radar” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.0
- Initial release.
- Plugin, theme, and core update tracking.
- PHP error log reader with deduplication.
- Site health score and dashboard widget.