[wp-trac] Re: [WordPress Trac] #3565: Future Posting Bug (2.1 REV 4722)

[WordPress Trac]

#3565: Future Posting Bug (2.1 REV 4722)
----------------------------+-----------------------------------------------
 Reporter:  Trent           |        Owner:  anonymous  
     Type:  defect          |       Status:  reopened   
 Priority:  high            |    Milestone:  2.3 (trunk)
Component:  Administration  |      Version:  2.2        
 Severity:  normal          |   Resolution:             
 Keywords:  cron future     |  
----------------------------+-----------------------------------------------
Changes (by gosuser):

  * version:  2.1.2 => 2.2

Comment:

 With a brute hack, finally i got this feature working again. Sorry for the
 last 3 posts, but i'm making a lot of test and i reported each single
 progress.
 To solve it:

 chmod -R 775 * to set executable flag to each wp script.

 Then edit wp-cron.php and comment the following lines:

 #if ( $_GET['check'] != wp_hash('187425') )
 # exit;

 #if ( get_option('doing_cron') > time() )
 # exit;

 Then edit index.php and force the execution of wp-cron.php each time that
 the index.php webpage is loaded (yes i know that it will increase database
 calls... this is why it's a brute hack). To do so change your index.php
 with this one:

 <?php
 /* Short and sweet */
 define('WP_USE_THEMES', true);
 require('./wp-cron.php');
 require('./wp-blog-header.php');
 ?>

 Now everyting should work, when the timestamp is reached && an user views
 your blog, it's automatically updated with new posts.

 I'm still working for a "real" fix for this problem. until now it seems
 that normal wp 2.2 installation can't call wp-cron.php.

 Ps: probably there should be a better solution, but for now it works...

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