Description
“Which plugin just broke my site?” — answered automatically.
Existing tools show you that an error occurred. Conflict Detective tells you which plugin caused it by correlating the plugin change timeline with the error log — and gives you a confidence score.
Features
Dashboard
Live overview of your WordPress/PHP version, active plugins, active theme, memory limit, debug mode, recent changes, and latest errors — all on one screen.
Error Log Viewer
Reads debug.log and the server PHP error log automatically. Each entry is attributed to the plugin that owns the file where the error occurred. Filter by Fatal / Warning / Notice / Deprecated.
Change History
Full audit trail of every plugin activation, deactivation, update, and deletion — with exact timestamps and version diffs (e.g. 8.3.0 8.4.0).
Health Scan
On-demand scan that detects:
- Duplicate plugin functionality (multiple SEO, caching, security, or backup plugins)
- Known incompatibilities between specific plugin pairs
- Outdated plugins (not updated in more than 2 years)
- Missing theme files or a missing parent theme
- PHP version, memory limit, and
max_execution_timemisconfigurations - Pending WordPress core updates
Conflict Scanner
Automatically correlates plugin update timestamps with error spikes and reports a suspect plugin with a confidence percentage. Detected conflicts are stored in the database and can be marked as resolved with one click.
Safe Testing Mode
Disable any plugin for your own admin session while visitors remain completely unaffected. Cookie-isolated — the live site is never touched.
Conflict Wizard
Step-by-step guided diagnosis. Choose your symptom (white screen, login problem, WooCommerce issue, slow site, broken admin, front-end error, or other) and the wizard automatically analyses recent changes and errors to produce a tailored action plan.
Installation
- Upload the
conflict-detectivefolder to the/wp-content/plugins/directory. - Activate the plugin through the Plugins menu in WordPress.
- Navigate to Conflict Detective in the WordPress admin sidebar.
No configuration is required. All scanning is done on demand inside the admin area — zero front-end overhead.
FAQ
-
Does this plugin slow down my site?
-
No. All analysis runs on demand inside the WordPress admin. There is zero front-end overhead.
-
What log files does it read?
-
wp-content/debug.log and the server PHP
error_logpath returned byini_get('error_log'). -
Do I need to configure anything?
-
No. Optionally, enable
WP_DEBUGandWP_DEBUG_LOGinwp-config.phpto populate the error log. -
Does Safe Testing Mode affect my visitors?
-
Never. Safe Testing Mode uses a session cookie that is only present for your admin session. Visitors always see the live site.
-
What happens if I install the plugin via FTP?
-
The plugin detects missing database tables on every request and recreates them automatically — no activation hook required.
-
Is this plugin compatible with Multisite?
-
The plugin monitors the current site only. It is not a network-wide tool in this version.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Tahhan Conflict Detective” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Tahhan Conflict Detective” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
2.1.4
- Fixed critical bug: Safe_Mode::init() and Database::maybe_upgrade() were registered inside Plugin::init() on plugins_loaded priority 5, meaning they were never called (priority 1 and 0 already fired). Both are now wired up directly at file load time, outside the Plugin class.
- Safe Mode tab fully redesigned: inactive state shows a card with instructions and a Start button; active state shows an amber banner with plugin count and a Stop button above the plugin toggle list.
- JavaScript Safe Mode toggle now uses delegated event binding ($(document).on) so it works regardless of DOM load order, and reloads the page on success to reflect the new state.
- Added safeModeLoading and safeModeStop localised strings for button feedback during AJAX calls.
- Added CSS for .pcd-safe-mode-banner, .pcd-btn-stop, .pcd-safe-mode-steps, and .pcd-safe-mode-count.
2.1.3
- Added Safe Mode tab UI (render_safe_mode placeholder).
2.1.1
- Security: plugin slug from AJAX request now validated against the installed plugins list before being stored in user meta
- All JavaScript UI strings are now translatable via wp_localize_script — no hardcoded English in JS
- Replaced last remaining emoji with a Dashicon in the Conflict Wizard
- Fixed menu position conflict with WordPress core Plugins menu (changed from 65 to 65.1)
- Added languages/ directory to match the Domain Path declaration in the plugin header
- Fixed navigation instructions in documentation (plugin is a top-level menu, not under Tools)
- LICENSE updated to full GPL-2.0-or-later text including the “or any later version” clause
2.0.0
- Added Conflict Scanner with confidence percentage
- Added Safe Testing Mode (admin-only plugin toggle, visitors unaffected)
- Added Conflict Wizard with 7 symptom categories and automatic analysis
- New database table for storing scanner results
1.0.0
- Initial release — Dashboard, Error Log Viewer, Plugin Change History, Health Scan