[wp-trac] Re: [WordPress Trac] #8592: Private Pages not listed in the Parent dropdown

[WordPress Trac]

#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 bethallen):

 Replying to [comment:28 mtekk]:
 > Replying to [comment:27 Denis-de-Bernardy]:
 > > Replying to [comment:26 mtekk]:
 > > > I'll test this tonight, but private pages still should not show up
 with the patch unless the user has permissions to see them.
 > >
 > > Err. They should. Or at least the current parent pages should show.
 Suppose user A publishes a private page that gets used as a stub. And user
 B publishes a public page whose parent is the private page.
 >
 > I'm not sure if that is really part of this bug, it's more of a behavior
 question that is opened by any fix to this bug. All child pages, if
 "public" should really inherit their status from their parent (otherwise
 what's the point of having them hierarchical if they do not). With the
 patch I submitted you can have future pages be parents as well, but again,
 their children should really not be allowed to be public until the parent
 is (otherwise you'll get a "chicken and egg paradox"). Neither of these
 were problems before as you "couldn't" have a non-published page be a
 parent.


 -- Here is what has happened to me.  I created a website for someone under
 2.5 or so.  I used private pages to create sets of child pages.  For
 example: Current events is page id 2.  I can create a bunch of child pages
 that are public for current events.

 The template I wrote for this site does not show all pages the same way in
 the sidebar.  I can write code, for example, that only shows the children
 of page id 2 in my sidebar.  At least that is how it worked until 2.7
 changed it.  So the site got hosed as soon as someone edited one of those
 child pages.  They could no longer make the private or draft page the
 parent as it worked originally.

 The philosophy that child pages should inherit parent page status is a
 valid argument, but the latest version broke the way something worked in
 the older version.

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