WP Debugging vs WP Crontrol

WP Crontrol enables you to take control of the scheduled cron events on your WordPress website or WooCommerce store. From the admin screens you can: View all scheduled cron events along with their arguments, schedule, callback functions, and when they are next due. Edit, delete, pause, resume, and immediately run cron events. Add new cron events. Bulk delete cron events. Add and remove custom cron schedules. Export and download cron event lists as a CSV file. WP Crontrol is aware of timezones, will alert you to events that have no actions or that have missed their schedule, and will show you a helpful warning message if it detects any problems with your cron system. Usage Go to the Tools → Cron Events menu to manage cron events. Go to the Settings → Cron Schedules menu to manage cron schedules. Documentation Extensive documentation on how to use WP Crontrol and how to get help for error messages that it shows is available on the WP Crontrol website. For site owners Owners of WordPress websites and WooCommerce stores use WP Crontrol to ensure that scheduled cron events run correctly and efficiently. By providing complete control over cron events, WP Crontrol helps you: Improve reliability: Address missed or failed cron events, ensuring your website or WooCommerce store continues to function as expected. Enhance security: Monitor and control cron events to ensure automatic update checks are performed as they should. Simplify management: Add, edit, delete, and pause cron events from a user-friendly interface, without needing to write any code. Gain insights: Export cron event data for analysis or reporting. Action Scheduler compatibility: Full support for the Action Scheduler system in WooCommerce, which is used to process recurring payments, subscriptions, and background orders. Clarity of times and timezones: All times are shown with a clear and accurate indication of which timezone applies. No more guesswork! For developers Developers use WP Crontrol to streamline and debug their WordPress development process: Enhanced debugging: Identify and troubleshoot issues with scheduled tasks, ensuring your scheduled events and their callbacks run as expected. Custom schedules: Create and manage custom cron schedules to fit the specific needs of your website, plugins, or themes, providing greater flexibility than just the core schedules. Efficient workflow: Add, edit, and delete cron events directly from the WordPress admin interface, saving time and reducing the need for manual coding. Insightful monitoring: Get insight into the performance and behavior of your scheduled tasks, allowing for optimization and better resource management. Accurate debugging: WP Crontrol goes to great lengths to ensure that running an event manually does so in a manner which exactly matches how WordPress core runs schdeuled events. This ensures that you can debug events accurately and with confidence. Other Plugins I maintain several other plugins for developers. Check them out: Query Monitor is the developer tools panel for WordPress. User Switching provides instant switching between user accounts in WordPress. Privacy Statement WP Crontrol is private by default and always will be. It does not send data to any third party, nor does it include any third party resources. WP Crontrol’s full privacy statement can be found here. Accessibility Statement WP Crontrol aims to be fully accessible to all of its users. WP Crontrol’s full accessibility statement can be found here.

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.