[wp-trac] [WordPress Trac] #12706: Custom post status bugs in the admin

[WordPress Trac]

#12706: Custom post status bugs in the admin
-------------------------------------------------+-------------------------
 Reporter:  ptahdunbar                           |       Owner:  ptahdunbar
     Type:  feature request                      |      Status:  new
 Priority:  normal                               |   Milestone:  Future
Component:  Post Types                           |  Release
 Severity:  normal                               |     Version:
 Keywords:  has-patch westi-likes needs-testing  |  Resolution:
-------------------------------------------------+-------------------------

Comment (by kevinB):

 Currently, post_status is used to track workflow until publication. Then,
 upon publication it is primarily a visibility control (with corresponding
 editability control).

 The current patch would expand that model as follows:
 1. additional moderation stages prior to publication (with corresponding
 set/edit/delete caps)
 2. additional visibility (privacy) statuses
 3. additional public statuses, which could be used to indicate further
 post-publication workflow (with possible distinctions in editing access)

 The problem I see with (3) is that it could quickly overtax the one-
 status-per-post schema.  What if you have already used a custom privacy
 status to customize visibility, but now want to make the post "final"?  It
 seems that further post-publication editing access would be better handled
 via a separate status field that is dedicated to editability.


 Replying to [comment:84 sirzooro]:
 > @kevinB: in fact post statuses are a special kind of taxonomy, dedicated
 to manage "post" workflow. In addition they have extra support for
 visibility in core...

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12706#comment:86>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software