working cron for restrictive hosts

[cookeal]

I see a lot of posts regarding the inability to have a working cron on hosts who put a block on HTTP callbacks to servers that have firewalls blocking calls to themselves. I did post a fix for this which my hosts kindly provided to get around this problem - it was marked as a duplicate and subsequently ignored. I awaited 2.8 with the fanfare of "improved cron spawning" but alas this also doesnt work in my, and many others situation. Once again I am posting the patched files which worked perfectly for 2.7.1 in the hope that someone with a more in depth knowledge can take a look and explain why this cannot be incorporated into the build? Many thanks

[azaozz]

Unfortunately this solution is host specific. Preferable way to do this is to configure the "real" cron when available in the hosting control panel adding the same command there (/wp-cron.php supports this now).

Alternatively try adding

define('ALTERNATE_WP_CRON', true);

to wp-config.php. This changes the spawning method for the pseudo-cron.