[wp-trac] Re: [WordPress Trac] #2715: Future Posting Functionality Broken

[WordPress Trac]

#2715: Future Posting Functionality Broken
----------------------------+-----------------------------------------------
       Id:  2715            |      Status:  new                     
Component:  Administration  |    Modified:  Sat May 13 14:17:40 2006
 Severity:  normal          |   Milestone:  2.1                     
 Priority:  high            |     Version:  2.1                     
    Owner:  anonymous       |    Reporter:  bloodylamer             
----------------------------+-----------------------------------------------
Comment (by masquerade):

 It appears my testing of this on CGI environments wasn't extensive enough.
 Like skeltoac warned before, it looks like the faux-fork we do isn't
 working.

 I'll work up a patch this weekend that will transparently run the request
 to the cron daemon via iframe in themes (this will require compliant
 themes or the user to visit the login page or admin, is requiring a
 compliant theme something we can rely on (We just need a hook to the
 header and footer area, header to add a tad of css to hide our iframe, and
 footer to inject our iframe.)

 Optionally, we could (Matt, this is pinging you), have requests that
 should trigger the spawn on CGI environments ping a special script on the
 wp.org server that would cause the wp.org server to spider the wp-cron.php
 file, although this does bring up worries on uptime on such a script.

 Can anybody else think of another way besides the two listed above to
 achieve what we need?

-- 
Ticket URL: <http://trac.wordpress.org/ticket/2715>
WordPress Trac <http://wordpress.org/>
WordPress blogging software