#DRUPAL 8 CRON HOW TO#

Now that the task has been saved, it looks more like the examples we’ve seen on the help pages.

Day of the week: * (Every day of the week).

Day of the month: * (Every day of the month).

This is the minute of the hour, so entering a “5” here would execute five minutes after the hour, not every five minutes.) Since I want this to run every minute, I’m going to enter “*” for each parameter. Here we can start setting our parameters and give Plesk the command we’d like to execute. In order to schedule a new task via Plesk, we need to log in and find the “Scheduled Tasks” option. This page lists all of the available options for each parameter, so check that out for detailed information. Basically, there are five parameters for setting the frequency of which the command should be executed, followed immediately by the actual command to execute.

When you scroll down, there is a diagram that explains the crontab syntax. has some great information on configuring cron. This can be done a number of ways, and I’m going to show you how it is done via Plesk (because that’s what I use), but even if you’re using CPanel or another control panel, the process will still apply, and you can contact your hosting support team for instructions specific to your environment.īefore we actually set it up, let’s take a look at a documentation page. Now that we know the path to the lightweight cron, we can create a crontab that will automatically access this page on a schedule that we define. This means that at any time, you can go to “/scheduler/cron” and Scheduler will check for content that needs to be published and unpublished, without running Drupal’s system-wide cron. The path to Scheduler’s lightweight cron is “/scheduler/cron”. To have our cake, and eat it too (have Drupal’s cron run every three hours, and have Scheduler check for content to publish and unpublish every minute) we can utilize Scheduler’s lightweight cron and set that to a frequency that’s more appropriate for our site. Now, if you do have a lot of actions that get performed when cron runs, they may take more than a minute to complete, and then you run into issues where cron tries to run while it’s already running. If we want to have fine-grained control over when content is published and unpublished using Scheduler, we might want to have cron run as often as every minute. This means that your site may see a slight performance hit each time cron does run. Many modules hook into cron and perform a variety of actions on each cron run.

#DRUPAL 8 CRON HOW TO#

In this video we take a look at how to use Scheduler’s lightweight cron to publish and unpublish content on a more frequent basis, without affecting Drupal Core’s cron schedule.Īs we’ve seen in previous videos, Scheduler performs its publishing and unpublishing of content when cron runs.

Drupal 8 cron