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

WordPress Trac wp-trac at lists.automattic.com
Wed Jun 20 19:22:57 GMT 2007


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

  * status:  new => closed
  * resolution:  => worksforme

Comment:

 If you have pings on, and you post a link to one of your own posts in
 another of your posts, then you should, very shortly after running wp-
 cron, automatically get a new "comment" posted in the original post.

 Like this:[[BR]]
 You make post A, and leave pings enabled on that post.[[BR]]
 You make post B (which contains a link to post A).[[BR]]
 You run wp-cron manually (as discussed before) or it runs
 automatically.[[BR]]
 Post A automatically gets a new comment that says, basically, post B
 exists.

 That's a pingback. If these do not appear, then your site is blocked from
 connecting back to itself for whatever reason.

 And because of the way 2.1 and up now uses wp-cron, this sort of thing
 will also prevent wp-cron from running and thus prevent future posting
 from working as well.

 In order for wp-cron to run automatically, the code has to be able to open
 a connection to itself. Sometimes this is prevented due to bad DNS
 settings, sometimes it's prevented due to stupid security policies. But
 regardless, it'll break wp-cron from working, which now prevents a lot of
 other things from working.

 Solutions:[[BR]]
 -Get the host to fix it[[BR]]
 -Get a better host[[BR]]
 -Switch back to Wordpress 2.0.whatever.

 In any case, this is not a Wordpress bug, it's a hosting issue.

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


More information about the wp-trac mailing list