[wp-trac] Re: [WordPress Trac] #5608: Future Private Post is immediately visible

[WordPress Trac]

#5608: Future Private Post is immediately visible
-------------------------------+--------------------------------------------
 Reporter:  mattyrob           |        Owner:  anonymous
     Type:  defect             |       Status:  new      
 Priority:  low                |    Milestone:  2.6      
Component:  Administration     |      Version:  2.3.2    
 Severity:  normal             |   Resolution:           
 Keywords:  reporter-feedback  |  
-------------------------------+--------------------------------------------
Comment (by MattyRob):

 Replying to [comment:4 Otto42]:
 > Seems like a lot of trouble to go to. I think it's simpler than that.
 >
 > The post_status should be set to "future", but the cron job that is
 scheduled should a parameter indicating the private status of the post.
 The publish_future_post hook will pass this along to whatever function is
 publishing it, and then the post will get changed to private, along with
 all the future_to_private hooks getting run and such.
 >
 > Posts are published by the cron job. That's what future means. If we
 have the job itself send along how to publish the post, then it will take
 care of it for you.

 This seems a better way - in the WordPress tables we can set post_status
 as future and set post_type as private (currently thought post_type is
 only 'post' or 'page'.

 Then in the transitions looking at 'future' posts we can future_to_publish
 if it a post or page and future_to_private if its a private.

 How does that sound?

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