[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:
     Type:  task (blessed)                       |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
Component:  Posts, Post Types                    |  Release
 Severity:  normal                               |     Version:  3.0
 Keywords:  has-patch westi-likes needs-testing  |  Resolution:
  needs-refresh needs-unit-tests editorial-flow  |     Focuses:
-------------------------------------------------+-------------------------

Comment (by uxtremist):

 Here's my case for additional post statuses:

 For blogs.ft.com we have a custom post type called ''webchat'', which is
 used for live sessions. These sessions are events, with a duration of an
 hour or so, where content is added in a real-time, instant-messaging,
 streaming fashion.

 We still use the usual WordPress statuses (well, just Draft and Published,
 really).

 I'd like to have a kind of sub-status feature in WP core, so that:

 1. When a webchat post is first published, its status is "Coming soon".
 This lets users know when to tune in for the event, which is scheduled to
 start in a day or so.
 2. When the event starts, the status is "In progress". We use the
 transition to trigger other things (that aren't important to this case,
 except that we do want to be able to hook the transition.)
 3. When the event concludes, the status becomes "Closed". It's still
 published, but it's clear the event is now over.

 Notes:
 • Webchats appear alongside standard posts in the homepage loop, in other
 words they're treated as just another post.
 • It would be beneficial to not only be able to add these semantic status
 types, but also alias them depending on different kinds of webchat
 session. For example, ''question-and-answer discussions'' (with multiple
 participants), as opposed to ''as-it-happens liveblogging'' (with a single
 author). Conceptually these are sufficiently different to warrant bespoke
 terminology for (what are essentially the same) statuses.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/12706#comment:199>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform