[wp-testers] Re: RC1: "Publish Status" UI is missing some backend

[Kevin & Lorie Behrens]

Mark Jaquith wrote:
> This is intentional. We want private posts to DEFINITELY be private. 
> Before, hitting "Publish" would set your post to be published (i.e. 
> override Private). By making Private a checkbox, we can be 100% sure 
> about your intention, and make sure we're not ever exposing a private 
> post.
Makes sense.  I do have RC2 now, and have no major gripe with the system 
as is; nice work and I like where it's headed.

Still, it would feel more consistent if the "Save" button never moved 
status to published OR private.  What about storing a postmeta 
"_keep_private" when saving an unpublished/pending post.  On edits, 
"keep private" is checked if  (post_status == 'private') OR postmeta 
_keep_private is set.  Then when it's published, clear out the postmeta 
entry.

That would also allow you to reinstate the "keep private" option for 
contributors.  They indicate their intent for the post, if approved, to 
be published privately.  Of course, the editor could choose to manually 
clear the private setting before publishing.