NaveenCodes Site Diagnostics vs WP Debugging

💛 This plugin is dedicated to my mother. Every update carries her blessings. NaveenCodes Site Diagnostics is a developer-focused diagnostics plugin for WordPress administrators. It helps you isolate plugin conflicts, inspect debug.log, estimate plugin load impact, review dependency problems, monitor cron events, create environment snapshots, and troubleshoot errors with a local rules engine. Core features Plugin conflict detection from debug.log parsing Hook conflict discovery based on registered callback signatures Admin-only Safe Mode that does not change the public frontend Error log analyzer for fatal errors, warnings, notices, and deprecated messages Compatibility checker for PHP, WordPress, and installed plugin updates Performance scanner with estimated plugin load time in milliseconds Plugin size analyzer Debug snapshot export in JSON and CSV Dependency checker for required plugins Memory usage analyzer with per-plugin estimates Smart warning system Scheduled health report emails (weekly or monthly) with score, conflicts, log size, and cron status Local AI Debug Helper with rule-based cause and fix suggestions Debug timeline for plugin actions and captured fatal errors File change detector with SHA-256 baselines Cron job monitor Website health score Database Health Checker with table overhead, autoloaded options bloat, and transient/postmeta cleanup candidates Security Nonce verification on all AJAX actions Capability checks with manage_options Sanitization with WordPress helper functions Escaped output in admin views No external APIs No third-party libraries Notes Scans run on demand and cache their reports with transients Safe Mode only applies to wp-admin and admin-ajax requests that carry the Safe Mode cookie The plugin never disables itself inside Safe Mode

This plugin sets the following debug constants in wp-config.php on plugin activation and removes them on plugin deactivation. Any errors will result in a PHP Exception being thrown. Debug constants per Debugging in WordPress. Default settings: define( 'WP_DEBUG_LOG', true ); define( 'SCRIPT_DEBUG', true ); define( 'SAVEQUERIES', true ); @ini_set( ‘display_errors’, 1 ); is set when the plugin is active. WP_DEBUG is set to true when the plugin is first run, thereafter it can be turned off in the Settings. The Settings page allows the user to set the following. define( 'WP_DEBUG', true ); // Default on initial plugin installation. define( 'WP_DEBUG_DISPLAY', false ); // Default when not declared is true. define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true ); // WordPress 5.2 WSOD Override. When the plugin is deactivated best efforts are made to re-add pre-existing constants to their former state. When the plugin is activated the default settings and any saved settings are restored. This plugin uses the wp-cli/wp-config-transformer command for writing constants to wp-config.php. Debug Quick Look from Andrew Norcross is included with this plugin to assist in reading the debug.log file. If you already have this plugin installed you should delete it when WP Debugging is not active. Query Monitor and Debug Bar plugins are optional dependencies to aid in debugging and troubleshooting. The notice for installation will recur 45 days after being dismissed. If you have a non-standard location for your wp-config.php file you can use the filter wp_debugging_config_path to return the file path for your installation. The filter wp_debugging_add_constants allows the user to add constants to wp-config.php. The filter returns an array where the key is the name of the constant and the value is an array of data containing the value as a string and a boolean to indicate whether or not the value should be passed without quotes. $my_constants = [ 'my_test_constant' => [ 'value' => 'abc123', 'raw' => false, ], 'another_test_constant' => [ 'value' => 'true' ], ]; The value option contains the constant’s value as a string. The raw option means that instead of placing the value inside the config as a string it will become unquoted. The default is true. Set as false for non-boolean values. Example: add_filter( 'wp_debugging_add_constants', function( $added_constants ) { $my_constants = [ 'my_test_constant' => [ 'value' => '124xyz', 'raw' => false, ], 'another_test_constant' => [ 'value' => 'true' ], ]; return array_merge( $added_constants, $my_constants ); }, 10, 1 ); This will create the following constants. define( 'MY_TEST_CONSTANT', '124xyz' ); define( 'ANOTHER_TEST_CONSTANT', true ); Development PRs are welcome against the develop branch on GitHub.