Lazy Cron

This core module provides hooks that are automatically executed at various intervals.

It is called 'lazy' because it's triggered by a pageview, so the interval is guaranteed to be at least the time requested (and maybe more) rather than exactly the time requested. The more pageviews your site gets, the closer it is. This is fine for most cases, but if you need it to be fully accurate I'll describe how you can make it not-lazy a little further down.

How to install

This is a core module included with ProcessWire 2.1+. Go to Admin > Modules and click "check for new modules". Then click the "install" button for the LazyCron module. LazyCron is now installed and ready to be used by other modules or via the API.

Hookable time intervals

These are the function names you can hook from LazyCron. The function names describe the time intervals they provide. If you think I'm missing any important time intervals, please let us know and we can add more.

  • every30Seconds
  • everyMinute
  • every2Minutes
  • every3Minutes
  • every4Minutes
  • every5Minutes
  • every10Minutes
  • every15Minutes
  • every30Minutes
  • every45Minutes
  • everyHour
  • every2Hours
  • every4Hours
  • every6Hours
  • every12Hours
  • everyDay
  • every2Days
  • every4Days
  • everyWeek
  • every2Weeks
  • every4Weeks

How to use Lazy Cron

This module is mainly of use inside the API and to other modules. You hook one of the named intervals mentioned in the list above, and the function you provide will be executed at approximately that time interval. Here's how you do it, both from a class (module) and outside of one:

Usage in a class/module

// initialize the hook in your AutoLoad module
public function init() {
    $this->addHook('LazyCron::every30Minutes', $this, 'myHook');
}
// the function you want executed every 30 minutes
public function myHook(HookEvent $e) {
    echo "30 Minutes have passed!";
}

Procedural usage (like in a template or elsewhere in the API):

// create your hook function
function myHook(HookEvent $e) {
    echo "30 Minutes have passed!";
}
// add a hook to your function:
wire()->addHook('LazyCron::every30Minutes', null, 'myHook');

Arguments provided to the hooks

If desired, you can retrieve the number of seconds that have actually elapsed since your hooked function was last called:

function myHook(HookEvent $e) {
    $seconds = $e->arguments[0];
    echo "30 Minutes have passed! (actual seconds were: $seconds)";
}

Note that in production usage, you probably wouldn't want to echo anything from these hooks because they are executed after the pageview was already delivered. So while you can directly echo output from these, it's probably not that useful (other than for demonstration purposes, like this).

How Lazy Cron works

When installed, LazyCron hooks into ProcessWire's ProcessPageView::finished() method. This ensures that the scheduled tasks are executed after the pageview has already been delivered rather than before or during it. This hopefully avoids any perceived slowdown if the scheduled tasks take time.

LazyCron provides a bunch of hooks that anything else can hook into. These functions are outlined in the section above titled "Hookable time intervals." These functions are called at the interval specified in their name. LazyCron simply uses ProcessWire's existing hook system. So when you hook into any one of these functions, your hook will also be executed at that same time interval.

LazyCron hooks are only executed during pageviews that are delivered by ProcessWire. They are not executed when using ProcessWire's API from other scripts.

How to make it not-lazy

In most cases, the way that LazyCron works out of the box is just fine. But if your need requires assurance that the module will always execute at exactly the interval you need (rather than possibly later), you need to setup a real cron job to trigger a pageview in your site. So if you needed accuracy to 1 minute, you'd setup a cron job to execute every one minute, and pull a page from the site. There are any number of ways you could pull a page from your site, but here is one using wget:

wget quiet no-cache -O - http://www.your-site.com > /dev/null

That command basically says to pull a page from the site, don't tell us anything, don't cache the request, and discard any output.

Twitter updates

  • This week we’ve got a few new and interesting core updates in progress, though none quite ready to release just yet. So rather than releasing version 3.0.154 today, I thought we'd instead take a brief look at what’s coming over the next few weeks… More
    3 April 2020
  • ProcessWire 3.0.153 (dev) focuses on comments field updates, significant refactoring/improvements to ProcessWire’s core Template class and PagesLoader class (which is used by the pages API variable), and we introduce a useful new pages API method— More
    20 March 2020
  • ProcessWire 3.0.152 core updates— This week we have some major improvements to our core date/time Inputfield, as well as a new ability to specify your own custom classes for Page objects— More
    6 March 2020

Latest news

  • ProcessWire Weekly #308
    In the 308th issue of ProcessWire Weekly we're going to take a look at some upcoming core and pro module updates, check out two all-new third party modules, and more. Read on!
    Weekly.pw / 4 April 2020
  • ProcessWire updates and additions in progress
    This week we’ve got a few new and interesting core updates in progress, though none quite ready to release just yet. So rather than releasing version 3.0.154 today, I thought we'd instead take a brief look at what’s coming over the next few weeks. This post covers all the details.
    Blog / 3 April 2020
  • Subscribe to weekly ProcessWire news

“We chose ProcessWire because of its excellent architecture, modular extensibility and the internal API. The CMS offers the necessary flexibility and performance for such a complex website like superbude.de. ProcessWire offers options that are only available for larger systems, such as Drupal, and allows a much slimmer development process.” —xport communication GmbH