Comments on: Run WordPress tasks from real cron job

By: Sam Kear

Sam Kear — Sun, 14 Aug 2011 03:42:23 +0000

Thanks for the detailed information! The WordPress developers should revisit how they implement cron in core.

By: arena

arena — Wed, 10 Aug 2011 03:44:02 +0000

Hi,

Thank you for this post.

Here is a new version of wp-cron-multi-blog.php

http://goo.gl/Tz9GC

By: tony

tony — Fri, 06 May 2011 17:23:17 +0000

Thanks for sharing your research and script. I was having the same issue you experienced using WP-Supercache with mod_rewrite caching not triggering garbage collection, and future posts failing to publish with “schedule missed” errors.

By: Michael

Michael — Wed, 06 Apr 2011 13:44:02 +0000

Simple but brilliant. Thank you. Your idea saved me hours.

By: Forumcivico

Forumcivico — Sat, 19 Mar 2011 14:15:00 +0000

@Joe Brewer

Just add this:

wget http://domain.tld/wp-cron-multi-blog.php > /dev/null 2>&1

For the /dev/null 2>&1 part:

If one run a cron job, any output that the script would send to stderr is sent as a mail to the owner of the script, which can be a tad annoying if the script runs regularily, with output you don’t need or want, or can do anything about.

The graceful way to handle this in any shell is as follows: Redirect the output of stderr to stdout, and then redirect this combined output to /dev/null

By: Joe Brewer

Joe Brewer — Fri, 26 Nov 2010 20:13:45 +0000

I’ve worked it out! I should have looked at the manual for wget, but anyway… Here is what I have:

wget http://www.domain.com/wp-cron.php?doing_wp_cron –output-document=cron.txt

Hope someone finds it useful.

By: Joe Brewer

Joe Brewer — Wed, 24 Nov 2010 11:45:51 +0000

I’ve successfully implemented this on one of my sites, however it is leaving a load of zero byte files in my root folder. Is there anything I can add after the wget command so that the zero byte files are not saved. If there is anything in the files, then I would need to see that for debugging purposes.

Thanks for the useful post.

By: q292u

q292u — Wed, 03 Nov 2010 12:32:06 +0000

One of my sites (www.supercars-for-sale.com) is on a free hosting account.
It kept getting suspended due to excessive resource use. (Feedwordpress plugin on wordpress..)
I’ve switched fwp to manual/cron option, AND used the disable_wp_cron setting. If it stays up 24 hours I’m going to look at implementing a Non-MU version of your script. (I’ve already written it.).
I’ll let you know what happens..

By: chovy

chovy — Fri, 08 Oct 2010 06:06:11 +0000

I’m not sure how relevant this is with WP3.0

w3 total cache is what’s killing my cpu with this internal wp-cron.php garbage.

By: DrLightman

DrLightman — Fri, 01 Oct 2010 09:53:30 +0000

@Rick : be aware if you copied the DEFINE from here, the quotes getting copied are not the ones PHP like. You have to manually edit them (I’m talking about the single charachters preceding and after DISABLE_WP_CRON)

By: Pascal

Pascal — Wed, 15 Sep 2010 00:52:28 +0000

Looks like you are breaking the PHP code.

Syntax error on line 1… hum did you put the define before the “

Pascal.

By: Rick

Rick — Sun, 05 Sep 2010 15:02:43 +0000

Pascal:

I tried your fix however when I put in line of code
define(‘DISABLE_WP_CRON’, true);
I get blank page on my wp admin panel that states “syntax error line 1″ which causes me to have to go back into wp-config.php file and delete that line of code. As a result I am unable to disable the wp-cron….Any other suggestions on how I can make this work?

Thanks,

Rick

By: Pascal

Pascal — Sat, 17 Jul 2010 17:39:11 +0000

I haven’t try WordPress 3.0 yet but I guess it would be like WordPress MU.

Also consider doing the change stated by Jason Potkanski above.

Pascal.

By: Len

Len — Thu, 15 Jul 2010 22:45:14 +0000

I just upgraded to WP 3.0 and am having issues with the wp-cron.php spiking my vps. I am looking at solutions like yours but wondering about the new multisite function in WP.

Will this need to be run like the MU example, and what difference in setup with sub-domain or sub-directory.

Thanks,
Len

By: Pascal

Pascal — Tue, 06 Jul 2010 22:21:30 +0000

I will definitly take a look at this switch_to_blog function and update my post accordingly.

Thanks!
Pascal.

By: Jason Potkanski

Jason Potkanski — Tue, 06 Jul 2010 16:36:51 +0000

Change wp_remote_post line to:

switch_to_blog($blog->blog_id);
wp_cron();
restore_current_blog();

Will run much faster.

By: Dan O'Neil

Dan O'Neil — Mon, 05 Jul 2010 19:25:32 +0000

Thank you, thank you, thank you. Switched to a standard cron job and my scheduled posts and all the other stuff is now working beautifully… saved me a big headache!

By: Binh Nguyen

Binh Nguyen — Tue, 29 Jun 2010 04:06:15 +0000

Thanks for this. I spent days looking for a solution for every minute cron run.

Well I use WPMU so also the php command didn’t work. I didn’t know I must use the wget command.

Bravo!

By: wp-popular.com » Blog Archive » Pascal’s blog » Run Wordpress tasks from real cron job

Wed, 16 Jun 2010 00:07:13 +0000

[...] the original here: Pascal’s blog » Run WordPress tasks from real cron job Tags: disable-wp-cron, good-explanation, [...]

By: Pascal

Pascal — Tue, 01 Jun 2010 01:25:46 +0000

Hi,

For a standard WordPress installation, you are right. And I would prefer that way instead of the wget method. But for a WordPress MU installation, that’s different because the API determine the current blog context based on the URI, so it cannot run from command line PHP.

Pascal.