Conversation
supportHi, you shouldn’t mark every non-cron requests with DOING_CRON constant as it causes issue with an other plugin which check if this constant is set or not. I think the following code should be removed: // for all other cases disable wp-cron.php and spawn_cron() by telling the system it’s already running if ( !defined( ‘DOING_CRON’ ) ) define( ‘DOING_CRON’, true );
After a quick search – I found something which might be helpful to the creators of WP-Cron Control for solving their conflict issues with other plugins checking the DOING_CRON constant. Try replacing your disable wp-cron.php code with this: // disable WP_CRON if ( ! defined('DISABLE_WP_CRON') ) { define( ‘DISABLE_WP_CRON’, true ); } Reference: https://github.com/WordPress/WordPress/blob/master/wp-includes/cron.php#L350 This reply was modified 9 years ago by Kevin Vess .
It’s already in their code as I remember.
After a quick search – I found something which might be helpful to the creators of WP-Cron Control for solving their conflict issues with other plugins checking the DOING_CRON constant. Try replacing your disable wp-cron.php code with this: // disable WP_CRON if ( ! defined('DISABLE_WP_CRON') ) { define( ‘DISABLE_WP_CRON’, true ); } Reference: https://github.com/WordPress/WordPress/blob/master/wp-includes/cron.php#L350 This reply was modified 9 years ago by Kevin Vess .
It’s already in their code as I remember.