Page MenuHomePhabricator

Option to move child pages when parent in renamed
Closed, DuplicatePublic


If I create the pages w/haystack and w/haystack/needle, both show up in my top level hierarchy as expected, and viewing w/haystack shows needle in it's hierarchy. Then I move w/haystack to w/haybale, but it does not move needle with it. Now when I go to the hierarchy at w/ I see haybale only, and the hierarchy at w/haybale does not show needle either. Fortunately the direct URL to needle still works.

If I go to w/haystack it tells me the page has moved, and does show needle in it's hierarchy. If I edit and save this page (creating a new w/haystack) I can again see haystack and needle in the top-level hierarchy.

I do not think the descendants should be orphaned in the hierarchy when their ancestor is moved. Maybe this means moving the descendants automatically at the same time, or maybe auto-create a placeholder document to replace the moved document, or some other solution.

See also PHI987.

Related Objects

Event Timeline

FWIW, I'm running 2015 week 43.

commit 9520a6b0ed2ee110d517a3b33df8fc5d90cbc2d8
Merge: 064d9a9 b038041
Author: epriestley <>
Date:   Sat Oct 24 05:41:48 2015 -0700

    (stable) Promote 2015 Week 43

Rule #1 of bug reporting:

  • Update your install.

You are welcome to reproduce on a Phacility test instance if you are unable to update, but as a rule we only take bug reports at HEAD.

chad renamed this task from Renaming a wiki page hides decedents from the hierarchy to Option to move child pages when parent in renamed.Feb 9 2016, 9:21 PM
chad edited projects, added Feature Request; removed Bug Report.

I can reproduce this. Not sure this should happen "by default" but at least a checkbox seems reasonable to also rename child slugs.

In T10307#158056, @chad wrote:

Rule #1 of bug reporting:

  • Update your install.

Will do from now on. Thanks!

You’re missing soo much good stuff with new projects.