Security and quality patch. Upgrade recommended for all users on 2.1.0.<\/p>","2.0.0":"
Major feature release: Conflict Scanner, Safe Testing Mode, and Conflict Wizard.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3572689,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3572689,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3574302,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3574302,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["2.5.0","2.5.1","2.5.2","2.5.3","2.6.0","2.6.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3572694,"resolution":"1","location":"assets","locale":"","width":1280,"height":800},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3572694,"resolution":"2","location":"assets","locale":"","width":1280,"height":800},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3572694,"resolution":"3","location":"assets","locale":"","width":1280,"height":800},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3572694,"resolution":"4","location":"assets","locale":"","width":1280,"height":800},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3572694,"resolution":"5","location":"assets","locale":"","width":1280,"height":800},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3572694,"resolution":"6","location":"assets","locale":"","width":1280,"height":800},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3572694,"resolution":"7","location":"assets","locale":"","width":1280,"height":800}},"screenshots":{"1":"Dashboard \u2014 live system overview: active plugins, stat cards, recent changes and the likely conflict culprit widget.","2":"Conflict Scanner \u2014 detected conflicts ranked by confidence score with one-click \"Mark Resolved\".","3":"Safe Testing Mode \u2014 amber active banner shows disabled-plugin count; toggle any plugin on\/off for your session only.","4":"Conflict Wizard \u2014 step-by-step diagnosis selects your symptom and produces a tailored action plan.","5":"Error Log Viewer \u2014 PHP errors parsed from debug.log and server error_log, attributed to the owning plugin with type filters.","6":"Change History \u2014 full audit trail of every plugin activation, deactivation, update, installation and deletion with timestamps.","7":"Health Scan \u2014 on-demand scan for duplicate functionality, outdated plugins, incompatibilities and server configuration issues."}},"plugin_section":[],"plugin_tags":[191246,94,93,1508,2391],"plugin_category":[59],"plugin_contributors":[266135],"plugin_business_model":[],"class_list":["post-322338","plugin","type-plugin","status-publish","hentry","plugin_tags-conflict","plugin_tags-debug","plugin_tags-errors","plugin_tags-health","plugin_tags-plugins","plugin_category-utilities-and-tools","plugin_contributors-mustafatahhan","plugin_committers-mustafatahhan"],"banners":{"banner":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/banner-772x250.png?rev=3574302","banner_2x":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/banner-1544x500.png?rev=3574302","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/icon-128x128.png?rev=3572689","icon_2x":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/icon-256x256.png?rev=3572689","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/screenshot-1.png?rev=3572694","caption":"Dashboard \u2014 live system overview: active plugins, stat cards, recent changes and the likely conflict culprit widget."},{"src":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/screenshot-2.png?rev=3572694","caption":"Conflict Scanner \u2014 detected conflicts ranked by confidence score with one-click \"Mark Resolved\"."},{"src":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/screenshot-3.png?rev=3572694","caption":"Safe Testing Mode \u2014 amber active banner shows disabled-plugin count; toggle any plugin on\/off for your session only."},{"src":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/screenshot-4.png?rev=3572694","caption":"Conflict Wizard \u2014 step-by-step diagnosis selects your symptom and produces a tailored action plan."},{"src":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/screenshot-5.png?rev=3572694","caption":"Error Log Viewer \u2014 PHP errors parsed from debug.log and server error_log, attributed to the owning plugin with type filters."},{"src":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/screenshot-6.png?rev=3572694","caption":"Change History \u2014 full audit trail of every plugin activation, deactivation, update, installation and deletion with timestamps."},{"src":"https:\/\/ps.w.org\/tahhan-conflict-detective\/assets\/screenshot-7.png?rev=3572694","caption":"Health Scan \u2014 on-demand scan for duplicate functionality, outdated plugins, incompatibilities and server configuration issues."}],"raw_content":"\n
\"Which plugin just broke my site?\"<\/strong> \u2014 answered automatically.<\/p>\n\n Existing tools show you that<\/em> an error occurred. Conflict Detective tells you which plugin caused it<\/em> by correlating the plugin change timeline with the error log \u2014 and gives you a confidence score.<\/p>\n\n Dashboard<\/strong>\nLive overview of your WordPress\/PHP version, active plugins, active theme, memory limit, debug mode, recent changes, and latest errors \u2014 all on one screen.<\/p>\n\n Error Log Viewer<\/strong>\nReads Change History<\/strong>\nFull audit trail of every plugin activation, deactivation, update, and deletion \u2014 with exact timestamps and version diffs (e.g. Health Scan<\/strong>\nOn-demand scan that detects:<\/p>\n\n Conflict Scanner<\/strong>\nAutomatically 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.<\/p>\n\n Safe Testing Mode<\/strong>\nDisable any plugin for your own admin session while visitors remain completely unaffected. Cookie-isolated \u2014 the live site is never touched.<\/p>\n\n Conflict Wizard<\/strong>\nStep-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.<\/p>\n\n Performance Monitor<\/strong> (new in 2.6.0)<\/em>\nTracks 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.<\/p>\n\n Cron Monitor<\/strong> (new in 2.6.0)<\/em>\nLists 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 \u2014 validated against the live WP-Cron schedule before execution.<\/p>\n\n AJAX \/ REST Monitor<\/strong> (new in 2.6.0)<\/em>\nAutomatically 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.<\/p>\n\n Plugin Interaction Map<\/strong> (new in 2.6.0)<\/em>\nVisualises 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.<\/p>\n\n\n No configuration is required. All scanning is done on demand inside the admin area \u2014 zero front-end overhead.<\/p>\n\n\n No. All analysis runs on demand inside the WordPress admin. There is zero front-end overhead.<\/p><\/dd>\n wp-content\/debug.log and the server PHP No. Optionally, enable Never. Safe Testing Mode uses a session cookie that is only present for your admin session. Visitors always see the live site.<\/p><\/dd>\n The plugin detects missing database tables on every request and recreates them automatically \u2014 no activation hook required.<\/p><\/dd>\n The plugin monitors the current site only. It is not a network-wide tool in this version.<\/p><\/dd>\n Performance Monitor hooks into WordPress's 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.<\/p><\/dd>\n Yes. Go to Conflict Detective \u2192 Cron Monitor<\/strong> 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.<\/p><\/dd>\n 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 Features<\/h4>\n\n
debug.log<\/code> 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.<\/p>\n\n8.3.0 \u2192 8.4.0<\/code>).<\/p>\n\n\n
max_execution_time<\/code> misconfigurations<\/li>\n\n
tahhan-conflict-detective<\/code> folder to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n\n
Does this plugin slow down my site?<\/h3><\/dt>\n
What log files does it read?<\/h3><\/dt>\n
error_log<\/code> path returned by ini_get('error_log')<\/code>.<\/p><\/dd>\nDo I need to configure anything?<\/h3><\/dt>\n
WP_DEBUG<\/code> and WP_DEBUG_LOG<\/code> in wp-config.php<\/code> to populate the error log.<\/p><\/dd>\nDoes Safe Testing Mode affect my visitors?<\/h3><\/dt>\n
What happens if I install the plugin via FTP?<\/h3><\/dt>\n
Is this plugin compatible with Multisite?<\/h3><\/dt>\n
How does the Performance Monitor work?<\/h3><\/dt>\n
plugin_loaded<\/code> 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 \u2014 treat them as estimates rather than precise benchmarks.<\/p><\/dd>\nDoes the AJAX \/ REST Monitor log every request?<\/h3><\/dt>\n
Can I manually trigger a WordPress Cron event?<\/h3><\/dt>\n
What is the Plugin Interaction Map?<\/h3><\/dt>\n
Requires Plugins<\/code> header introduced in WordPress 6.5 to show explicit declared dependencies.<\/p><\/dd>\n\n<\/dl>\n\n\n2.6.1<\/h4>\n\n
\n
2.6.0<\/h4>\n\n
\n
$_SERVER<\/code> directly (was using non-standard $GLOBALS['_SERVER']<\/code>).<\/li>\nget_entries()<\/code> now selects only required columns instead of SELECT *<\/code>.<\/li>\n{prefix}cd_ajax_log<\/code> table (schema version 3).<\/li>\n<\/ul>\n\n2.5.1<\/h4>\n\n
\n
tahcd_prev_version_*<\/code> options (was using the stale pcd_prev_version_<\/code> prefix, leaving orphaned rows in wp_options).<\/li>\nconflict-detective\/conflict-detective.php<\/code>).<\/li>\n2.5.0<\/h4>\n\n
\n
tahcd_<\/code> \/ TAHCD_<\/code> to satisfy WordPress.org uniqueness requirements (constants, AJAX actions, nonce, user meta, cookie, option keys, script handle, JS data object).<\/li>\n<\/ul>\n\n2.4.0<\/h4>\n\n
\n
tahhan-conflict-detective<\/code>) for WordPress.org compliance. Namespace changed to TahhanConflictDetective<\/code>. Text domain changed to tahhan-conflict-detective<\/code>.<\/li>\nWP_Filesystem::put_contents()<\/code> instead of file_put_contents()<\/code>.<\/li>\n<\/ul>\n\n2.3.1<\/h4>\n\n
\n
maybe_filter_active_plugins()<\/code> called get_option('active_plugins')<\/code> which re-triggered the same filter, causing a stack overflow. Fixed by reading directly from $wpdb<\/code>.<\/li>\n<\/ul>\n\n2.3.0<\/h4>\n\n
\n
2.2.0<\/h4>\n\n
\n
Safe_Mode::init()<\/code> and Database::maybe_upgrade()<\/code> moved to file-load time.<\/li>\n<\/ul>\n\n2.1.4<\/h4>\n\n
\n
2.1.3<\/h4>\n\n
\n
2.1.1<\/h4>\n\n
\n
2.0.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n