[wp-trac] [WordPress Trac] #18402: Confused page ordering if filter drops parent pages

[WordPress Trac]

#18402: Confused page ordering if filter drops parent pages
-------------------------------------+-----------------------------
 Reporter:  erdnah                   |       Owner:  nacin
     Type:  enhancement              |      Status:  reviewing
 Priority:  normal                   |   Milestone:  Future Release
Component:  Posts, Post Types        |     Version:  3.2
 Severity:  normal                   |  Resolution:
 Keywords:  ui-feedback needs-patch  |     Focuses:  administration
-------------------------------------+-----------------------------

Comment (by joyously):

 I don't like the proposed change at all. This entire change is about
 disguising what is actually in the database. The production version of the
 code is accurately conveying what the database contains.
 If a Page is deleted or filtered out of the view, that does not change
 what the "parent" column of the post table has. Maybe on deletion, the
 child should be updated. I'm not sure, but having it output that there is
 still a parent set is a good thing. It allows the user to update it,
 whereas hiding it does not.

 There is an odd thing, though. When I delete the parent Page, clicking on
 Quick Edit for the child page shows a blank in the Parent Page dropdown.
 This makes sense since the number from the database is not in the Page
 list, because the Parent is Trash. So that part is not quite accurately
 saying what is in the database. Of course, restoring the parent from the
 Trash makes everything back the way it was, so if the child //had// been
 updated on deletion, it wouldn't have been able to restore exactly back.
 It seems to me that there's nothing actually wrong here.

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