[wp-trac] Re: [WordPress Trac] #3742: Future dated posts not publishing

[WordPress Trac]

#3742: Future dated posts not publishing
--------------------------------+-------------------------------------------
 Reporter:  fleety              |        Owner:  anonymous   
     Type:  defect              |       Status:  reopened    
 Priority:  normal              |    Milestone:  2.4 (future)
Component:  Administration      |      Version:  2.2         
 Severity:  normal              |   Resolution:              
 Keywords:  future dated posts  |  
--------------------------------+-------------------------------------------
Comment (by intoxination):

 Replying to [comment:33 johnmarkschofield]:
 > Got a response from my host -- which doesn't shed much light on the
 matter:
 >
 > Hi John -- If done properly this should work, but if you are connecting
 to yourself, there are numerous ways to break it. Unfortunately there's
 not enough information in that thread to give us a good clue what is going
 on. Check the response code from the fsockopen() call to see if it works.
 >
 > If Wordpress is ignoring a failure, that would definitely be a Wordpress
 bug.
 >
 > Cheers,
 >
 > Kirsten
 >
 > On Wed, 20 Jun 2007, 18:40:11 UTC, John Schofield wrote:

 I would ask them to give a little more detail, particularly on "if you are
 connecting to yourself, there are numerous ways to break it". The
 fsockopen will call your site address/cron.php.

 To get the error reported from fsockopen, you need to edit the wp-includes
 /wp-cron.php file (keep a back up - once you get the error, you will want
 to restore it to the original state). Look for this:


 {{{
         } else {
                 $argyle = @ fsockopen( $parts['host'],
 $_SERVER['SERVER_PORT'], $errno, $errstr, 0.01 );
         }
 }}}


 And after that add:

 {{{
 echo $errno."  ".$errstr;
 }}}

 Once you do that, check your front page. It will print out the error
 number and string. It will also tell you that it cannot modify the header
 information. You can ignore that part. Once you get the error, reupload
 your original cron.php file, so your visitors don't get nagged by all
 that.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/3742#comment:36>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software