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

 Replying to [comment:82 benbalter]:
 >
 > Anything that's not a blog post; that you don't "publish."
 I don't follow the correlation between being a blog post and having
 'publish' status.  Pages and other custom types have post_status =
 'publish' too.

 My working concept of the three post_status types:
 1. $status_obj->public : published to everyone
 2. $status_obj->private : published to those with sufficient capabilities
 3. $status_obj->moderation : not published at all, and editable based on
 capabilities

 Maybe you would rather rename (3) to "workflow" or something else, but I
 don't see "something you don't publish" as a public status.

 > If the final step of my workflow is "submitted" (think malange with
 applications) or "final" (think alfresco with press releases).
 "Submitted" is a moderation status in my book (not yet public).

 "Final" would mean public but no longer editable by anyone, right?  If so,
 that says my scenario (2) is real world and there are usages where a
 sequential post_status workflow that retains visibility but changes
 editability is not a cludge. Glad to hear it.

 > If I'm a news organization and want to have a "breaking" post status at
 an intermediate step in my editorial process to display a teaser on the
 front-end.
 That's a compelling feature, but how would you retain that "breaking" flag
 '''and''' track progress through various steps of moderation, all with a
 single post_status field?  Or do you have some other schema in mind to
 implement these stati?

 > If I'm a car dealership (think autorader) and use my cars custom post
 type as either "available" (listed) or "sold" (not listed).
 If you want it for display customization, that sounds like a good job for
 a custom taxonomy.  If for suppression (non-publishing), it sounds like a
 workflow status, not a public status.

 > If I have a coupon site (think retailmenot) in which everything is
 either valid or expired.
 Same as above.

 > (not to mention it's kinda silly to abstract 2/3s and hard code 1/3
 which makes building queries, etc. a bit less intuitive).
 Yeah, I already wrote the code to implement custom public stati.  Just
 wanted some confirmation that it's worthwhile and optimal.

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