<
From version < 13.1 >
edited by Vincent Massol
on 2016/03/25
To version < 14.1 >
edited by Guillaume Delhumeau
on 2016/11/30
>
Change comment: Add information about the breakage detection introduced in Nested Pages Migration 0.7.

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.VincentMassol
1 +XWiki.gdelhumeau
Content
... ... @@ -7,6 +7,7 @@
7 7  == Executive Summary ==
8 8  
9 9  Up to XWiki 7.1, there has been 2 ways to organize content in XWiki:
10 +
10 10  * Wiki > Space > Page (which includes rights inheritance and administration features)
11 11  * Page > Child Page > Child Page of child Page > ... (which is used for hierarchical navigation purposes)
12 12  
... ... @@ -13,6 +13,7 @@
13 13  Note that both are independent: a page can have a parent Page in a different Space/Wiki than its own .
14 14  
15 15  While this was working, we've found that it could create confusion for users, leading to questions such as:
17 +
16 16  * Should I create a sub-Wiki or a Space for my team?
17 17  * Which navigation should I put on my home page: list of Spaces or tree view of Pages?
18 18  * Can I set rights on a page that is under a space?
... ... @@ -19,6 +19,7 @@
19 19  
20 20  At the same time, for a long time there have been discussions on the list about the future "new model" of XWiki, which would ideally include
21 21  Nested Spaces, offering the following features:
24 +
22 22  * Unified way to handle hierarchical navigation (Page > Sub-page > Sub-sub-page >...)
23 23  * Navigation reflected in URLs (.../PageA/PageB/PageC)
24 24  * Inheritance of access rights (rights on PageA apply to PageB and PageC, unless defined otherwise. Rights on PageB supersede those on PageA
... ... @@ -27,6 +27,7 @@
27 27  In the end, we took the opportunity to move from the previous way to this new way of organizing pages in XWiki 7.2.
28 28  
29 29  In an ideal world, going from the old model to the new one would imply a total rewrite of the model. However, in order not to break retro-compatibility with many existing features and applications we had to keep the concepts of "Page" and "Space" in XWiki while adapting them to emulate the Nested Pages feature. Here's what we've done to achieve this by default:
33 +
30 30  * We've hidden the parent-child feature(((
31 31  {{info}}
32 32  Even though it's hidden you can still turn it back on if you need it while you migrate your content to use Nested Spaces: set the ##core.hierarchyMode## property to ##parentchild## in the ##xwiki.properties## configuration file.
... ... @@ -38,6 +38,7 @@
38 38  == Detailed Explanations ==
39 39  
40 40  Before the introduction of the Nested Pages concept (in 7.2), the content in a wiki was organized like this:
45 +
41 41  * we had some **Spaces**, that you can conceptually consider like file system "folders"
42 42  * inside these spaces, we had **Pages**, where you were able to write content or store applications entries.
43 43  
... ... @@ -131,9 +131,11 @@
131 131  
132 132  {{image reference="Migrator1.png"/}}
133 133  
134 -There are 2 actions:
139 +There are 3 actions:
140 +
135 135  * **compute a plan**: the migration first generate a plan of actions to perform. You can see what the migrator proposes to do and disable some actions, or modify the options, for example.
136 136  * **execute the plan**: when a plan has been computed and if you agree with its content, you can execute the plan: the pages will be moved as proposed.
143 +* **detect breakages** {{info}}(since 0.7){{/info}}: detect the hierarchies that are broken if you don't run the migrator. [[Read the migrator page to have more information>>extensions:Extension.Nested Pages Migrator Application||anchor="HBreakagesDetection"]].
137 137  
138 138  === Options ===
139 139  
... ... @@ -185,6 +185,7 @@
185 185  Each action has a checkbox. Only checked actions will be performed. So if you notice some changes that you don't want to perform, you can easily uncheck them. When you uncheck an action, it also affects its children. But you can also select the children one by one if you need to.
186 186  
187 187  Other actions are available:
195 +
188 188  * **exclude page**: click on this button to add the page to the exclude list (in the options). The plan might be recomputed.
189 189  * **exclude space**: click on this button to add the space of that page to the exclude list (in the options). Then plan might be recomputed.
190 190  * **set parent**: click on this button to manually set a parent for that page. {{warning}}Note: this action will be performed immediately, not when the plan will be executed. It is a shortcut to help you changing the parent without having to navigate to the page.{{/warning}}
... ... @@ -231,4 +231,3 @@
231 231  ** before 7.2: the code would create/display a Space named "my.space"
232 232  ** after 7.2: the code will create/display a Space named "my\.space"
233 233  * Various XWiki APIs that used to return a space name have been returning a space reference string (i.e. list of spaces separated by dots and escaped {{{"\."}}}, {{{"\:"}}} and {{{"\\"}}} characters). Code using those API may need to be updated. See [[XWiki 7.2 release notes>>xwiki:ReleaseNotes.ReleaseNotesXWiki72||anchor="HSpaceReferenceinsteadofSpacename"]] for more details (this content could be copied in a section of the migration guide).
234 -

Get Connected