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_time misconfigurations
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.

Performance Monitor (new in 2.6.0)
Tracks the estimated load time, memory delta, and database query count for every active plugin during the current page load. Results are color-coded as Fast / Slow / Heavy and refreshed on demand.

Cron Monitor (new in 2.6.0)
Lists all scheduled WordPress Cron events with their next run time and interval. Overdue events are highlighted in red. Each event can be triggered manually via a “Run Now” button — validated against the live WP-Cron schedule before execution.

AJAX / REST Monitor (new in 2.6.0)
Automatically logs slow AJAX and REST API calls (those taking more than 500 ms) to a dedicated database table. Filter by All / AJAX / REST / Slow to quickly identify bottleneck endpoints.

Plugin Interaction Map (new in 2.6.0)
Visualises your plugins grouped into known ecosystem clusters (WooCommerce, Elementor, Yoast SEO, Jetpack, ACF, Gravity Forms, and more). Highlights declared plugin dependencies and shows active/inactive state at a glance. Plugins that don’t belong to a known ecosystem are listed separately as Standalone Plugins.

Screenshots

Dashboard — live system overview: active plugins, stat cards, recent changes and the likely conflict culprit widget.

Conflict Scanner — detected conflicts ranked by confidence score with one-click "Mark Resolved". — Dashboard — live system overview: active plugins, stat cards, recent changes and the likely conflict culprit widget.

Installation

Upload the tahhan-conflict-detective folder 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_log path returned by ini_get('error_log').
Do I need to configure anything?: No. Optionally, enable WP_DEBUG and WP_DEBUG_LOG in wp-config.php to 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.
How does the Performance Monitor work?: Performance Monitor hooks into WordPress’s plugin_loaded action, which fires once for every plugin that loads. It records a snapshot of the PHP execution time, memory usage, and database query count immediately before and after each plugin loads, then computes the delta. The results are stored in a 5-minute transient and can be refreshed on demand. Because measurements happen at request time, values vary between requests — treat them as estimates rather than precise benchmarks.
Does the AJAX / REST Monitor log every request?: No. Only requests that take longer than 500 ms are written to the database. The log is automatically trimmed to the most recent 500 entries.
Can I manually trigger a WordPress Cron event?: Yes. Go to Conflict Detective Cron Monitor and click the “Run Now” button next to any event. The plugin validates the hook name against the live WP-Cron schedule before execution so arbitrary code cannot be triggered via this interface.
What is the Plugin Interaction Map?: The Interaction Map groups your installed plugins into known ecosystem clusters (WooCommerce, Elementor, Yoast SEO, Jetpack, ACF, Gravity Forms, Contact Form 7, WPML, LearnDash, Divi, WP Rocket, and more). Plugins within the same ecosystem are more likely to interact and potentially conflict with each other. The map also reads the Requires Plugins header introduced in WordPress 6.5 to show explicit declared dependencies.

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.

Mustafa tahhan

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.6.1

Updated: Tested up to WordPress 7.0.

2.6.0

New: Performance Monitor tab — tracks per-plugin load time, memory delta, and DB query count during page load; color-coded Fast / Slow / Heavy badges; Refresh Data button.
New: Cron Monitor tab — lists all scheduled WP-Cron events with next run time and overdue detection; “Run Now” button per event; overdue count summary badge at top.
New: AJAX / REST Monitor tab — logs slow AJAX and REST API calls (>500 ms) to a dedicated DB table; filter bar for All / AJAX / REST / Slow views.
New: Plugin Interaction Map tab — visualises plugin dependency clusters (WooCommerce, Elementor, Yoast, Jetpack, ACF, etc.) and standalone plugins with active/inactive state.
Security: cron “Run Now” AJAX handler now validates the hook against the live WP-Cron schedule before execution.
Security: AJAX monitor REST timing now reads from $_SERVER directly (was using non-standard $GLOBALS['_SERVER']).
Security: AJAX log get_entries() now selects only required columns instead of SELECT *.
DB: new {prefix}cd_ajax_log table (schema version 3).

2.5.1

Fixed: uninstall routine now correctly deletes tahcd_prev_version_* options (was using the stale pcd_prev_version_ prefix, leaving orphaned rows in wp_options).
Fixed: Safe Mode plugin list no longer shows Conflict Detective itself (self-exclusion filter used the old slug conflict-detective/conflict-detective.php).
Docs: readme.txt changelog updated with entries for v2.2.0 through v2.5.0.

2.5.0

All plugin-specific prefixes standardised to tahcd_ / TAHCD_ to satisfy WordPress.org uniqueness requirements (constants, AJAX actions, nonce, user meta, cookie, option keys, script handle, JS data object).

2.4.0

Plugin renamed to Tahhan Conflict Detective (slug: tahhan-conflict-detective) for WordPress.org compliance. Namespace changed to TahhanConflictDetective. Text domain changed to tahhan-conflict-detective.
Debug log clear handler now uses WP_Filesystem::put_contents() instead of file_put_contents().

2.3.1

Fixed critical infinite recursion crash: maybe_filter_active_plugins() called get_option('active_plugins') which re-triggered the same filter, causing a stack overflow. Fixed by reading directly from $wpdb.

2.3.0

CI action SHA pinning for security hardening. Code cleanup in class-dashboard.php and class-error-log.php.

2.2.0

Safe Mode tab fully functional: Start/Stop button now triggers AJAX and reloads on success.
Architecture fix: Safe_Mode::init() and Database::maybe_upgrade() moved to file-load time.

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

Description

Features

Screenshots

Installation

FAQ

Does this plugin slow down my site?

What log files does it read?

Do I need to configure anything?

Does Safe Testing Mode affect my visitors?

What happens if I install the plugin via FTP?

Is this plugin compatible with Multisite?

How does the Performance Monitor work?

Does the AJAX / REST Monitor log every request?

Can I manually trigger a WordPress Cron event?

What is the Plugin Interaction Map?