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

Comment (by aaroncampbell):

 Replying to [comment:180 helen]:
 > Replying to [comment:178 MikeSchinkel]:
 > > I'd propose we start with the following: ''SIMPLY'' add custom statues
 to the list of potential selectable statues in the post add/edit UI and
 require any new workflow to be handled by the developer.  Period.  That
 could easily be implemented in time for 3.9.
 >
 > It isn't simple. The existing metabox makes almost no sense when you
 step back and look at it. Visibility and status are separate in the UI,
 but not in the data, and they mess with button labeling in different and
 sometimes unpredictable ways - how can we add to this in any sane way?
 Shoving more in there just makes it even harder to change later.

 There's more that's making this "not simple" than just the UI too.
 There's also the issue that we hardcode "publish" as the only status for
 published posts.  This means that we need filters in several other places
 unless we relegate custom statuses to being all non-published.  For
 example, an "archived" status that is still live (but is maybe used to
 prevent it from being edited), wouldn't work.

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