Changes for page Migration Guide to Nested Pages
Last modified by Vincent Massol on 2024/04/11
From version 3.11
edited by Guillaume Delhumeau
on 2016/02/25
on 2016/02/25
Change comment:
There is no comment for this version
To version 3.12
edited by Guillaume Delhumeau
on 2016/02/25
on 2016/02/25
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -52,12 +52,14 @@ 52 52 53 53 = Principle = 54 54 55 -After having upgrade the XWiki instance to a recent version (7.4+), you should convert your existing pages to nested ones. This will permit: 56 -* (1) to keep the existing hierarchy between pages, made with the parent/child relationship, which will be lost otherwise. 57 -* (2) give you the opportunity to create pages under any old page, as you could under new pages. 55 +The idea is not convert existing pages (which most of them are terminal) to ##WebHome## pages under their own space. We call this "convert terminal pages to nested pages". This allows you to create sub-pages under any converted pages, which is impossible while they were terminal. 58 58 59 - Toperformthisconversion,we havedevelopedanapplicationcalled[[NestedPagesMigratorApplication>>extensions:Extension.NestedPagesMigratorApplication]].Itsprincipleisto moveall existing pagesunder theirparent,sothattheoldparent/childrelationshipbecomephysicallyrepresentedbythe NestedPages hierarchy.57 +But that would be a shame to lose the parent/child relationships that the user have created between its pages. The user might want to preserve its hierarchies. She might still want to have ##FrankCapra## as parent of ##ItsAWonderfulLife##. 60 60 59 +To keep this information, the principle is to **move all the pages under their parents**, so the parent/child links **becomes a real hierarchy between pages**. 60 + 61 +To perform this conversion, we have developed an application called [[Nested Pages Migrator Application>>extensions:Extension.Nested Pages Migrator Application]]. 62 + 61 61 = Fix the hierarchy = 62 62 63 63 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/).