[wp-trac] Re: [WordPress Trac] #8592: Private Pages not listed in
the Parent dropdown
WordPress Trac
wp-trac at lists.automattic.com
Tue May 5 02:48:47 GMT 2009
#8592: Private Pages not listed in the Parent dropdown
----------------------------+-----------------------------------------------
Reporter: mtdewvirus | Owner: anonymous
Type: defect (bug) | Status: new
Priority: high | Milestone: Future Release
Component: Administration | Version: 2.7
Severity: major | Keywords: needs-patch
----------------------------+-----------------------------------------------
Comment(by mtekk):
Replying to [comment:32 Denis-de-Bernardy]:
> right. and thus, it might make sense to do this instead:
>
> {{{
> where ( post_status = 'publish' or post_parent = $post->post_parent )
> }}}
>
> that way, the current behavior is kept around, without the bug you (or
I) bumped into.
That would partially fix this bug, however administrators wouldn't be able
to make pages children of private pages of editors, or other
administrators (not sure if this is a problem or not, however if an admin
can change page ownership the should be able to use it as a parent, even
if it is private).
From http://codex.wordpress.org/Roles_and_Capabilities it looks like we
can give anyone with edit_others_pages capabilities the full page list
(ends up being administrators and editors). Seems weird that only admins
and editors can create pages. I guess just using a blank would work if we
check for the edit_others_pages (or maybe even just the
read_private_pages) capability.
I guess the other question is do we want these unpublished pages showing
up outside of the dashboard for users with the proper privileges (the
answer to this may be in the code from query.php that Ryan pointed to
(it's now a few lines above the line he linked to))?
--
Ticket URL: <http://core.trac.wordpress.org/ticket/8592#comment:33>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list