Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Kuba Mikita

    (@kubitomakita)

    It’s server, or rather a WordPress configuration related. Seems when an Object cache is available (because you installed a caching plugin or your host provider alters the caching mechanisms), WordPress stores the cron in the cache, which is way faster.

    But it’s not the default WordPress behavior, though. See here, it uses just get_option() and update_option() functions.

    Thread Starter herihehe

    (@herihehe)

    Can it be solved by simply setting define(‘WP_CACHE’,false); from my end?

    Plugin Author Kuba Mikita

    (@kubitomakita)

    Worth trying! But it might have consequences, like decreased overall performance.

    It’s hard to predict how it will behave with the caching system you’re using.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Events not stored in wp_options’ is closed to new replies.