From version < 1.4 >
edited by Guillaume Delhumeau
on 2016/02/15
To version < 1.2 >
edited by Guillaume Delhumeau
on 2016/02/15
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,17 +1,5 @@
1 1  After having upgrade the XWiki instance to a recent version (7.4+), you should convert your existing pages to nested ones. This will permit:
2 -* (1) to keep the existing hierarchy between pages, made with the parent/child relationship, which will be lost otherwise.
3 -* (2) give you the opportunity to create pages under any old page, as you could under new pages.
2 +* to keep the existing hierarchy between pages, made with the parent/child relationship, which will be lost otherwise.
3 +* give you the opportunity to create pages under any old page, as you could under new pages.
4 4  
5 -To perform this conversion, we have developed an application called [[Nested Pages Migrator Application>>extensions:Extension.Nested Pages Migrator Application]]. Its principle is to move all existing pages under their parent, so that the old parent/child relationship become physically represented by the Nested Pages hierarchy.
6 -
7 7  = Fix the hierarchy =
8 -
9 -However, the current hierarchy may be messy. For example, so pages inside the space ##Proposal## could have ##Main.WebHome## as parent instead of ##Proposal.WebHome## which would be more logical. It happens when the user is invited to create pages in the space ##Proposal## directly from the main page (ex: http://design.xwiki.org/).
10 -
11 -It's important to identify such a case before applying the migration tool, because the tool won't be able to detect this kind of unwanted hierarchies.
12 -
13 -In the previous example, the solution was to put manually the parent of all pages of the ##Proposal## space that had ##Main.WebHome## as parent, to ##Proposal.WebHome##. The following script have been used to migrate (ex: http://design.xwiki.org/):
14 -
15 -{{code language="velocity"}}
16 -
17 -{{/code}}

Get Connected