[wp-trac] [WordPress Trac] #28006: Add visual cues when viewing drafts on the frontend

[WordPress Trac]

#28006: Add visual cues when viewing drafts on the frontend
------------------------------------------+--------------------------
 Reporter:  hlashbrooke                   |       Owner:  johnbillion
     Type:  enhancement                   |      Status:  reopened
 Priority:  normal                        |   Milestone:  4.0
Component:  Posts, Post Types             |     Version:  3.9
 Severity:  normal                        |  Resolution:
 Keywords:  has-patch revert 2nd-opinion  |     Focuses:  template
------------------------------------------+--------------------------
Changes (by nacin):

 * keywords:  has-patch => has-patch revert 2nd-opinion
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I agree with krogsgard here. I think it's cruft, unnecessary, and also a
 nightmare for those trying to control their widows.

 The only reason why this is here for Private is it is a terminal status.
 (I'm not even a fan of it there, but that stems more from disliking
 private posts in general.) Meanwhile, Draft is transitional.

 There are limited situations where you need a body class at all. But
 especially for a post status on a single post. post_class() is still in
 play here, which will give you the status classes. How often are you
 really going to need to style outside the post based on status? This is
 redundant and crufty. If your design ''happens'' to need this, then you
 should add it yourself.

 I'm not saying the use cases are invalid. I'm simply saying core shouldn't
 do anything for them. Happy to be disagreed with, but I think both changes
 here are unnecessary and that [28963] should be reverted. Maybe there is a
 solution here to help with confusion but these are not it.

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