Make WordPress Core

Opened 9 years ago

Closed 9 years ago

Last modified 3 years ago

#10353 closed feature request (wontfix)

working cron for restrictive hosts

Reported by: cookeal Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.7.1
Component: Cron API Keywords: cron callback
Focuses: Cc:


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

Attachments (2)

cron_patched.php (11.2 KB) - added by cookeal 9 years ago.
wp-cron_new.php (1.3 KB) - added by cookeal 9 years ago.

Download all attachments as: .zip

Change History (4)

9 years ago

9 years ago

#1 @azaozz
9 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

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.

#2 @DrewAPicture
3 years ago

  • Milestone 2.8.1 deleted
Note: See TracTickets for help on using tickets.