Defining WP_CRON as running is, well, wrong.

  • Joost de Valk

    (@joostdevalk)


    11 years, 4 months ago

    In validate_cron_request, which apparently runs all the time, you do:

    if ( !defined( 'DOING_CRON' ) )
  define( 'DOING_CRON', true );

    This breaks quite a few things, including Genesis layout settings saving, as that’s checking for “DOING_CRON” and bails if it’s set to 1. I doubt setting that to true here is really needed?

    http://wordpress.org/extend/plugins/wp-cron-control/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Thorsten Ott

    (@tott)

    11 years, 4 months ago

    Hi Joost,
    I’m going to take a look, but it’s likely not going to happen before the weekend.

    Thorsten

    Tevya

    (@thefiddler)

    11 years, 1 month ago

    Any updates for this plugin? Several people reporting it broken on 3.4 and 3.5.

    Plus, does it work with Multisite? I mean will calling the unique string run it for every site on the network? Or how does that work?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Defining WP_CRON as running is, well, wrong.’ is closed to new replies.