ticket	summary	owner	component	_version	priority	severity	milestone	type	_status	workflow	_created	modified	_description	_reporter
11697	Keep private posts in the admin area / Was: Make private posts a canonical plugin		General	2.9	normal	normal	Future Release	defect (bug)	assigned	has-patch	2010-01-02T21:33:21Z	2011-04-11T23:15:01Z	"Said Matt:
> Also, a lot of the complexity of private posts could be avoided by a relatively simple change: saying they're only viewable in the dashboard. (Which I think is close to how people use them already.)

----

There are quite a few tickets related to private posts that can be viewed by users who should, and even more tickets related to private comments that can be viewed by users who aren't authorized to view the post.

There also is at least one ticket that highlights a performance issue related to private posts.

http://core.trac.wordpress.org/search?q=private

Would it be an option to turn this into a canonical plugin and begone with the problems?"	Denis-de-Bernardy
11375	allow to disable the private status	ryan	Query	2.9	normal	normal	Future Release	enhancement	new	dev-feedback	2009-12-09T20:54:17Z	2013-01-14T13:27:48Z	"The private status generates all sorts of OR clauses in SQL queries, which is bad from a performance standpoint.

Blogs that do not have any private posts or pages should have the ability to disable the feature altogether, in order to optimize the SQL statements.

Adding an option in a Settings page arguably is plugin material, but WP doesn't currently allow to remove the status altogether.

Were it to be implemented, WP should keep a trace (in a transient) of the following:

{{{
$has_private_posts = (bool) $wpdb->get_var(""SELECT EXISTS 1 FROM $wpdb->posts WHERE post_status = 'private';"");
}}}

checking its value and disabling the type = private type accordingly in non-admin areas would significantly enhance the user experience for those who never use such things."	Denis-de-Bernardy
4711	get_pages and get_posts do not work well with private posts		Template	2.9.1	normal	normal	Future Release	defect (bug)	new		2007-08-07T17:41:32Z	2011-02-24T17:15:26Z	"The get_pages function has no way to retrieve private pages.
The get_posts function uses a post_status parameter, meaning that it can retrieve (and potentially display) private posts regardless of the user.

While get_pages() simply lacks a feature, I would argue that get_posts() is defective in that it can display things that it should not be able to display.

Both of these functions need to be updated to use the get_private_posts_cap_sql() function for building the correct post_status query segment.
"	Otto42
6939	wp_list_pages() should also lists private pages if the user has capability 'read_private_pages'		Template	2.5.1	normal	normal	Future Release	enhancement	new	has-patch	2008-05-08T18:19:29Z	2011-02-24T17:15:57Z	"If the user has the capability ""read_private_pages"" wp_list_pages() don't lists private pages in no way. I've noticed this problem by some comments on my ""Role Manager"" Plugin page.

Two patches are attached to this ticket.

wp_list_pages() gets a new option ""include_private_pages"". The default value is 1 for lists private pages too if the user has the capability ""read_private_pages"".
If private pages should not be listed also if the user has the cap ""read_private_pages"" the syntax is as an example:
wp_list_pages('title_li=<h2>Pages</h2>&include_private_pages=0');

The second patch is for get_pages() - with the same option and default value.

And of course: if a user don't has the cap ""read_private_pages"" private pages are listed in no case :)"	imwebgefunden
6492	Guids No Longer Have Permalink Format		General	2.5	normal	trivial	Awaiting Review	enhancement	reopened	has-patch	2008-03-31T06:03:30Z	2013-05-18T21:41:12Z	"When you create a new post using WordPress 2.5 the GUID is created in the http://siteurl/?p=<PostId> format even when permalinks are enabled.  This is because the _transition_post_status function in /wp-includes/post.php now checks if the guid is empty (which it never is) before resetting/creating it with the proper permalink structure.  Line 2841 should be removed.
"	brianwhite