Closed Bug 764423 Opened 12 years ago Closed 12 years ago

Kuma: Need ability to move page and all its subpages

Categories

(developer.mozilla.org Graveyard :: Wiki pages, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 764431

People

(Reporter: sheppy, Unassigned)

Details

(Whiteboard: u=contributor c=wiki s=2012-07-03 p=3)

We need to be able to easily (but not too easily, so that it can't be done my mistake) relocate a page in the hierarchy.

For example, let's say we have the page /en-US/CSS/someprop and it needs to be moved into the CSS reference. That means moving it to /en-US/CSS/CSS_reference/someprop.

But let's say someone writes an entire reference for a new API:

en-US/NewAPI
en-US/NewAPI/class1
en-US/NewAPI/class2
...
en-US/NewAPI/class34

And we realize this all needs to be moved into the DOM reference. We need to be able to move the page en-US/NewAPI to en-US/DOM/NewAPI and have it and all of its subpages relocated accordingly:

en-US/DOM/NewAPI
en-US/DOM/NewAPI/class1
en-US/DOM/NewAPI/class2
...
en-US/DOM/NewAPI/class34

This doesn't need to be done at launch, but it does need to be done by no later than the second sprint after launch.
The most common use case for this: someone creates new content in the wrong place, and we need to move it. This can either be because they just got it wrong, or because we told them to put it wherever and we'd fix it later (that can be easier than figuring out the right spot when they ask).
Looks like we should keep bug 730790 in mind when doing this.
Whiteboard: u=contributor c=wiki s=2012-07-03 p=
Whiteboard: u=contributor c=wiki s=2012-07-03 p= → u=contributor c=wiki s=2012-07-03 p=3
Seems like this might be a duplicate of bug 764431? Bug 730790 seems covered there, too.
Seems to be the case, yeah. Cleaning that up...
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Version: Kuma → unspecified
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.