{"id":4641,"date":"2022-05-20T16:03:54","date_gmt":"2022-05-20T13:03:54","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=4641"},"modified":"2025-11-27T13:36:43","modified_gmt":"2025-11-27T11:36:43","slug":"how-to-replace-wordpress-cron-with-a-real-cron-job","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/how-to-replace-wordpress-cron-with-a-real-cron-job\/","title":{"rendered":"Replace WP-Cron with Real Cron Job"},"content":{"rendered":"\n

You don’t necessarily need to be a technical wizard to build a website, but this doesn’t mean there is no learning curve ahead of you. If you use a <\/span>CMS like WordPress<\/b><\/a>, you’ll probably get to grips with the <\/span>app’s basic functions<\/b> fairly quickly. However, if you want to develop a successful project, you’ll need to have a better understanding of how it all works.<\/span><\/p>\n\n\n\n

Among other things, this means figuring out <\/span>what cron jobs do<\/b> and setting them up correctly. Let’s see if we can help.<\/span><\/b><\/p>\n\n\n\n

What is a Cron Job?<\/b><\/b><\/h2>\n\n\n\n

Although most of them remain hidden, your computer performs tasks all the time. There are many examples. Your email client regularly <\/span>connects to the mail server <\/b>to check for messages, your operating system goes online to ensure it displays the correct time, etc.<\/span><\/p>\n\n\n\n

If you use Windows, all these processes are controlled by the <\/span>Task Scheduler<\/b>. If you run a Unix-based OS like Linux or macOS, they are taken care of by <\/span>cron<\/b>.<\/span><\/p>\n\n\n\n

Cron is <\/span>a command-line utility<\/b> that runs commands and scripts <\/span>at fixed times or preset periods<\/b>. In addition to app-specific jobs, it’s responsible for <\/span>automating many of the tasks related to the optimal performance of the operating system<\/b>.<\/span><\/p>\n\n\n\n

Cron jobs run periodically, and the schedule is kept in <\/span>a crontab file or cron table<\/b>. Every user on the machine can have their own cron table, and the system-wide crontab is usually located in either <\/span>\/etc <\/span><\/i>or <\/span>\/etc\/cron.d\/<\/span><\/i>.<\/span><\/p>\n\n\n\n

Crontabs can be edited with a text editor, and each line in them represents a separate cron job. The syntax looks like this:<\/span><\/p>\n\n\n\n

* * * * * [command or path to script]<\/i><\/b><\/p>\n\n\n\n

The asterisks can have different values, determining <\/span>when the cron job is to be executed<\/b>. The five asterisks represent <\/span>the minute, hour, day of the month, month, and day of the week<\/b>, respectively. After that, you have the shell command or application to be executed.<\/span><\/p>\n\n\n\n

For example, if we want the shell to output “hello world” every day at five minutes past midnight, we’ll have:<\/span><\/p>\n\n\n\n

5 0 * * * echo hello world<\/i><\/b><\/p>\n\n\n\n

If we want to have the same output at five past midnight on every fifteenth day of the month, we’ll have:<\/span><\/p>\n\n\n\n

5 0 15 * * echo hello world<\/i><\/b><\/p>\n\n\n\n

If we want it to happen every year on the fifteenth of April at five past midnight, we’ll have:<\/span><\/p>\n\n\n\n

5 0 15 4 * echo hello world<\/i><\/b><\/p>\n\n\n\n

Cron jobs on a web server are just as important. Often, they’re created manually by site owners who need to automate tasks related to their projects’ performance.<\/span><\/p>\n\n\n\n

But how does WordPress handle them?<\/span><\/b><\/p>\n\n\n\n

WordPress and Cron Jobs<\/b><\/b><\/h2>\n\n\n\n

The smooth operation of a WordPress project relies on <\/span>automated tasks<\/b>. For example, if you want to keep your<\/span> CMS, themes, and plugins up-to-date<\/b>, WordPress must periodically check for new versions. Scheduling posts is also a widely used feature that relies on automation. However, by default, <\/span>WordPress doesn’t use cron jobs<\/b> for several reasons.<\/span><\/p>\n\n\n\n

For one, although it’s rare, WordPress can run on Windows, in which case, any attempts to use cron would be unsuccessful. And even if we look at Linux only, we’ll see that the<\/span> cron configurations vary wildly from server to server.<\/b><\/p>\n\n\n\n

That’s why WordPress instead relies on the <\/span>wp-cron.php<\/b> file to schedule and automate tasks. Although it has the word “cron” in its name, the concept is different.<\/span><\/p>\n\n\n\n

Instead of keeping track of time and running commands according to a pre-selected schedule, wp-cron.php is <\/span>loaded every time a user visits the website<\/b>. If any tasks can be executed, wp-cron carries on with them automatically. Theoretically, it seems like a viable alternative, but in reality, it has a few inherent problems.<\/span><\/p>\n\n\n\n

For one, the execution of tasks may not be as reliable as you’d wish. The wp-cron.php file is <\/span>only loaded when there’s an active HTTP request to the site<\/b>, so if there’s no traffic, it may fail to work as expected.<\/span><\/p>\n\n\n\n

Furthermore, wp-cron.php is yet another file that the server needs to load every time a visitor access your site. This <\/span>increases the load and consumes bandwidth<\/b>.<\/span><\/p>\n\n\n\n

It’s not uncommon for hackers to target the cron file either, and it could cause<\/span> conflicts with some caching plugins<\/b>.<\/span><\/p>\n\n\n\n

Linux’s cron system<\/b> is definitely more reliable, and it can help you improve the performance and reliability of your WordPress website. Before you can use it to automate your tasks, however, it’s a good idea to disable wp-cron.php.<\/span><\/b><\/p>\n\n\n\n

Disabling wp-cron.php<\/b><\/b><\/h2>\n\n\n\n

A simple modification of the wp-config.php file can disable the default WordPress automated task behavior. You can use an <\/span>FTP client<\/b><\/a>, <\/span>SSH, or your <\/b>web hosting control panel’s<\/b><\/a> File Manager <\/b>to access wp-config.php in your site’s document root.<\/span><\/p>\n\n\n\n

As we’re talking about the primary <\/span>WordPress configuration file<\/b>, it might not be a good idea to create <\/span>a backup copy of it first<\/b>, just in case.<\/span><\/p>\n\n\n\n

Open the file and add the following above the line that says “<\/span>\/* That’s all, stop editing! Happy publishing. *\/<\/span><\/i>“:<\/span><\/p>\n\n\n\n

define(‘DISABLE_WP_CRON’, true);<\/i><\/b><\/p>\n\n\n\n

Make sure you save the changes and <\/span>re-upload the file if you’re using FTP.<\/b><\/p>\n\n\n\n

Creating a Regular Cron Job<\/b><\/h2>\n\n\n\n

Disabling wp-cron may help you optimize your website’s performance and resource usage, but it will also <\/span>disable the automated jobs<\/b> that the PHP file takes care of by default. For them, you’ll need regular Linux cron jobs.<\/span><\/p>\n\n\n\n

There are a couple of ways of setting up a cron job. If you prefer the command line, you can use the <\/span>crontab -e <\/i><\/b>command and save a new cron using the syntax we discussed a couple of sections ago. However, an easier option would be to use the utility in your web hosting control panel.<\/span><\/p>\n\n\n\n

All <\/span>popular management platforms<\/b> have a graphical interface for setting up cron jobs. They may differ slightly in terms of design, but they should all offer the options you see in the screenshot below.<\/span><\/p>\n\n\n

\n
\"Replace<\/figure>\n<\/div>\n\n\n

This is what SPanel users see when they open the <\/span>Cron Jobs <\/b>tool on the home page of the User Interface. You can determine when a cron job should be executed by entering values in the <\/span>Minutes<\/b>, <\/span>Hours<\/b>, <\/span>Date<\/b>, <\/span>Month<\/b>, and <\/span>Weekday<\/b> fields, or you can use the <\/span>Common Settings <\/b>in the drop-down menus.<\/span><\/p>\n\n\n

\n
\"Replace<\/figure>\n<\/div>\n\n\n

The <\/span>Cron command <\/b>field determines what the cron job is going to do. You can enter a regular command or do what most developers prefer and put <\/span>several tasks into a single script<\/b>.<\/span><\/p>\n\n\n\n

This does require diving deeper into the world of programming, but the internet is overflowing with resources, and you can also borrow ready-made scripts that take care of various site maintenance tasks. For example, with just three <\/span>WP-CLI<\/b><\/a> commands and four lines of code, you can have <\/span>WordPress automatically check for and install new versions of the core, plugins, and themes.<\/b><\/p>\n\n\n\n

This is what the script should look like:<\/b><\/p>\n\n\n

\n
\"Replace<\/figure>\n<\/div>\n\n\n


Bear in mind that this is a <\/span>very simple script<\/b>. A bit more research will show you that you can easily broaden the range of tasks you do with a single file and a cron job. When you’re ready with the script, enter its path into the <\/span>Cron command <\/b>field to set it up to work with a cron job.<\/span><\/p>\n\n\n

\n
\"Replace<\/figure>\n<\/div>","protected":false},"excerpt":{"rendered":"

You don’t necessarily need to be a technical wizard to build a website, but this doesn’t mean there is no learning curve ahead of you. If you use a CMS like WordPress, you’ll probably get to grips with the app’s basic functions fairly quickly. However, if you want to develop a successful project, you’ll need […]<\/p>\n","protected":false},"author":3,"featured_media":5547,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_robots_primary_cat":"none","_seopress_titles_title":"Replace WP-Cron with Real Cron Job | ScalaHosting KB","_seopress_titles_desc":"","_seopress_robots_index":"","_seopress_analysis_target_kw":"","footnotes":""},"categories":[34],"tags":[],"class_list":["post-4641","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-hosting"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/4641","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/comments?post=4641"}],"version-history":[{"count":8,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/4641\/revisions"}],"predecessor-version":[{"id":5856,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/4641\/revisions\/5856"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/media\/5547"}],"wp:attachment":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/media?parent=4641"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/categories?post=4641"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/tags?post=4641"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}