Changes for page Migration Guide to Nested Pages
Last modified by Vincent Massol on 2019/04/03
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -6,12 +6,3 @@ 6 6 7 7 = Fix the hierarchy = 8 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}}