[wp-trac] Re: [WordPress Trac] #4566: Cron Not Getting Called (fsockopen failing)

WordPress Trac wp-trac at lists.automattic.com
Mon Dec 22 12:37:05 GMT 2008

#4566: Cron Not Getting Called (fsockopen failing)
 Reporter:  chewblocka      |        Owner:  Nazgul  
     Type:  defect (bug)    |       Status:  reopened
 Priority:  normal          |    Milestone:          
Component:  Administration  |      Version:  2.2.1   
 Severity:  normal          |   Resolution:          
 Keywords:  cron future     |  
Changes (by CiaranG):

  * status:  closed => reopened
  * resolution:  invalid =>


 It's all very well saying "your firewall is broken, get someone to fix it"
 but as noted in the original description we are talking about a somewhat
 common, if misguided, configuration. I am aware of two shared hosting
 providers that have this setup, neither of which is prepared to even
 consider changing it.

 I suggest that at least the filter hook be put in place (as per Nazgul's
 patch) in order to allow this situation to be rectified by a plugin,
 rather than those affected having to rely on a code hack with every new
 Wordpress release.

Ticket URL: <http://trac.wordpress.org/ticket/4566#comment:12>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list