<
From version < 3.10 >
edited by Guillaume Delhumeau
on 2016/02/25
To version < 3.12 >
edited by Guillaume Delhumeau
on 2016/02/25
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -42,7 +42,7 @@
42 42  
43 43  == Issue with the Parent/Child relationship ==
44 44  
45 -Now, it is clear that we had 2 different hierarchies in the wiki. One, made of sub-pages (sub-spaces in the reality), and one made with the old parent/child relationship. Then, clearly, it becomes confusing for the user. Which hierarchy should be displayed in the breadcrumb? What is the parent of page, the "container" page or the parent set in the field?
45 +Now, it is clear that we have 2 different hierarchies in the wiki. One, made of sub-pages (sub-spaces in the reality), and one made with the old parent/child relationship. Then, clearly, it becomes confusing for the user. Which hierarchy should be displayed in the breadcrumb? What is the parent of page, the "container" page or the parent set in the field?
46 46  
47 47  The choice have been made to drop the notion of parent/child relationship, since we can now really have children pages, implemented as sub-pages (with inherited rights, preferences, etc...).
48 48  
... ... @@ -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 -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.
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/).

Get Connected