[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):

 Although custom moderation and private stati are clearly useful and mesh
 well with the existing post_status implementation, custom public stati
 seem questionable. Can anyone think of a scenario in which they would be
 beneficial? All that comes to mind is:

 1. a single-term pseudo-taxonomy (probably unnecessary)
 2. allowing for distinctions in editing access without altering read
 access (potentially useful but arguably cludgy)

 I'm not arguing for or against; just think it should be discussed before
 any code commits.

 Another suggested topic for conversation: capability definitions and
 requirements related to custom stati. Any solution needs to regulate read,
 edit, delete and '''set''' (i.e. publish) of each custom post status, for
 each post type.  The current patch does address these (just inviting
 further ideas).

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