Show last authors
1 {{box cssClass="floatinginfobox" title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
4
5 XWiki offers to perform several actions on a document (a.k.a a page).
6
7 = Create =
8
9 There are three ways to create new pages.
10
11 == By adding a wanted link ==
12
13 You can **edit an existing page and create a link to your new page** (either in Wiki mode or in WYSIWYG mode). The resulting link will show up with a question mark next to it, showing it as a non-existent page. Simply click on the link to create the page as a child of the current page.
14
15 {{image reference="CreateInWYSIWYG.PNG"/}}
16
17 This will take you directly to the edit mode for the missing page. **This is the recommended approach** as it'll allow you to create a hierarchy while you create new pages.
18
19 Users and applications can provide pages that can be used as [[templates>>extensions:Extension.Administration Application#HTemplates]] when creating new pages. The new page content (content, objects and other meta data) will be replicated from the template. When clicking on a "wanted link", if there are available templates, you will be asked to select one:
20
21 {{image reference="templateSelectorForWantedLink.png"/}}
22
23 Then you will be taken to the Inline Form edit mode corresponding to the selected page template.
24
25 == By using the Add Page action ==
26
27 You can create a new child page for the current page by using the plus icon located to the right of the page title.
28
29 {{image reference="AddPage.png"/}}
30
31 This will open the Create Page wizard where you can specify the title of the new page.
32
33 By default, the new page will be created as a child of the current page. If you don't want that, then you can change the location of the target page using the page picker (by selecting an existing parent).
34
35 Note: When creating a new page from the wiki's homepage (i.e. clicking the plus icon from the wiki's homepage), there is an exception to the above behavior. In this case, the default is to create a top level page instead of a child of the current page (homepage). If your intention was really to create a child of the homepage (which is not usually the case for homepages), then you can use the page picker and select the homepage as parent of the new page.
36
37 You can also select a [[template>>extensions:Extension.Administration Application#HTemplatesCreationandAdministration]] for the new page.
38
39 Once you're done click the "Create" button and you will be able to edit your newly created page right away.
40
41 This is what you'll see if you're a [[simple user>>platform:Features.PageEditing#HSimpleandAdvancededitingmodes]]:
42 {{image reference="CreatePageSimple.png"/}}
43
44 And if you're an [[advanced user>>platform:Features.PageEditing#HSimpleandAdvancededitingmodes]] you'll be able to control whether the page created will be a Terminal page (i.e. a page that cannot have children, see also [[Terminology>>platform:Features.ContentOrganization.WebHome#HTerminology]]) or not:
45
46 {{image reference="CreatePageAdvanced.png"/}}
47
48 == By entering directly the URL of the new page ==
49
50 You can also **enter the new page name (and its path) directly in the URL of your browser**. For example ##http:~/~/localhost:8080/xwiki/bin/view/Movies/Thriller/Rear Window##. If the target page doesn't exist then you'll get an empty page with a message saying that the page doesn't exist and there'll be a link to create it:
51
52 {{image reference="CreateInURL.PNG"/}}
53
54 = Edit =
55
56 This allows the editing of a page. See the [[page editing>>platform:Features.PageEditing]] tutorial for more details.
57
58 = Show =
59
60 Whenever you click on a link to a page XWiki automatically shows the page in view mode. This is the default mode. XWiki also supports displaying the page in other formats that may be more adapted to specific circumstances:
61
62 {{toc start="2" depth="2" numbered="false" scope="local"/}}
63
64 == Code ==
65
66 You can view the content of a page without having to edit it (and thus you don't need edit rights). This option is shown only for users in [[Advanced Mode>>platform:Features.PageEditing#HAdvancedMode]].
67
68 To see the code when using the Flamingo skin, you have to go to the More Actions menu, and click on View Source.
69
70 {{image reference="ViewSourceFlamingo.png"/}}
71
72 {{image reference="WikiCodeResultFlamingo.png"/}}
73
74 == XML ==
75
76 XWiki allows exposing a page in XML. This is not ordinarily useful, but it can prove useful for example if you want to write a tool that automatically parses the content of a page. As the XML format is well-defined for all pages, this is much easier than doing screen-scrapping for example. In addition this XML format is used internally by XWiki for performing imports/exports of pages and whole wikis.
77
78 == Comments ==
79
80 Users with the comment right can leave comments on pages. This allows them to provide feedback without requiring edit rights.
81
82 {{image reference="AddComment.png"/}}
83
84 On the Flamingo skin
85 {{image reference="CommentsFlamingo.png"/}}
86
87 By pressing the permalink button, it is provided the comment link, giving to the user the functionality of going to that comment location.
88 {{image reference="permalinkModal.png"/}}
89
90 If a user has the specific rights, he can delete a comment.
91 {{image reference="deleteModal.png"/}}
92
93 == Attachments ==
94
95 A page can contain attachments. See [[Attachments>>platform:Features.Attachments]] for more details.
96
97 == History ==
98
99 Displays the version history of the page. See [[Version Control>>platform:Features.VersionControl]] for more details.
100
101 = Print =
102
103 There are several possible printing options (what you see may vary depending on the Skin used).
104
105 When using the Flamingo Skin, you will find the Print Preview by clicking on More Actions:
106
107 * Print Preview: Generates a page which is formatted so that it can be easily printed using your browser's Print feature.(((
108 {{image reference="PrintFlamingo.png"/}}
109 )))
110
111 = Export =
112
113 There are several possible exporting formats that XWiki supports: PDF, RTF, XAR, HTML. See the [[Export feature>>platform:Features.Exports]] for more information.
114
115 On the Flamingo skin:
116
117 {{gallery}}
118 image:[email protected]
119 image:[email protected]
120 image:[email protected]
121 {{/gallery}}
122
123 = Delete =
124
125 Removes a page and puts it in the trash.
126
127 {{image reference="DeletePageFlamingo.png"/}}
128
129 A confirmation is asked before the removal is done. Here, you can decide either or not to delete the children along with the current page.
130
131 {{image reference="DeleteConfirmFlamingo.png"/}}
132
133 Note: When deleting a non-terminal page and the only child of that page is the 'WebPreferences' terminal page, the 'Affect children' checkbox will be checked by default. Normally, it would be unchecked, but in this case we`ve noticed that it`s very easy to forget about that page (since it's hidden and automatically created when going into 'Page Administration') and your deleted page might still show up in some places because of that leftover. You can still uncheck it if you know what you are doing.
134
135 Then, you have to wait during the deletion of the page:
136
137 {{image reference="Deleting.png"/}}
138
139 And finally, you have the success message:
140
141 {{image reference="DeleteFlamingoConfirm.png"/}}
142
143 == Pages that belong to extensions ==
144
145 Before the success message, you might see the following screen:
146
147 {{gallery}}
148 image:DeleteExtensionPage.png
149 {{/gallery}}
150
151 It happens when you try to delete a page that belong to an extension. This page could be one of the children of the current page. If you continue the delete action, the extension will not work anymore.
152
153 Moreover, it is not recommended to delete pages that belong to extensions manually. You should use the [[Extension Manager>>extensions:Extension.Extension Manager Application]] instead.
154
155 This screen makes you able to select precisely which pages to remove and which ones to preserve. You can also abort the action by clicking on the "Cancel" button.
156
157 == Pages that contains an used XClass ==
158
159 Starting with {{info}}10.10RC1{{/info}}, you might also see one of the following screen:
160
161 {{gallery}}
162 image:delete_simpleuser_xclass.png
163 image:delete_advanceduser_xclass.png
164 {{/gallery}}
165
166 It happens when you try to delete a page that contains an XClass which is used somewhere. This page could be one of the children of the current page. If you continue the delete action, some other pages will not work anymore. That is why the action is completely forbidden for simple users. Advanced users are allowed to chose precisely the pages to remove and those to preserve. They can also abort the action by clicking on the "Cancel" button.
167
168 = Restore =
169
170 To restore a deleted page or remove it from the trash (you'll need to have Admin permissions), check the documentation for the [[Index Application>>extensions:Extension.Index Application]].
171
172 = Copy =
173
174 If you want to create a copy of an existing page then you have to navigate to that page (access that page in view mode) and then select the Copy entry from the page menu (that is located to the right of the page title).
175
176 {{image reference="CopyPageFlamingo.png"/}}
177
178 This will take you to the Copy Page Wizard where you can specify the title of the copy and its new location.
179
180 {{image reference="CopyPageConfirmFlamingo.png"/}}
181
182 If the page is translated in multiple languages then you can select which translation to copy, or you can copy all the translations. If the page has child pages then you can choose to copy them as well (this way you can replicate a hierarchy of pages).
183
184 {{image reference="copyStatus.png"/}}
185
186 Once you click the Copy button you are taken to the Copy Status page where you can see the options that you have selected and the progress of the copy operation. The copy is performed asynchronously. The progress bar is replaced with the operation status at the end in order to let you know if the operation succeeded or failed. You can use the breadcrumbs to navigate to the new page or the old one.
187
188 = Move/Rename =
189
190 If you want to rename or move an existing page then you have to navigate to that page (access that page in view mode) and then select the Rename entry from the page menu (that is located to the right of the page title).
191
192 {{image reference="RenameFlamingo.png"/}}
193
194 This will take you to the Rename Page Wizard where you can specify the new page title (if you want to rename) and/or the new page location (if you want to move the page to a different location).
195
196 This is what you'll see if you're a [[simple user>>platform:Features.PageEditing#HSimpleandAdvancededitingmodes]] (**Note**: you can only see the options to Move / Rename or Delete if you have the Delete Rights or if you are making the changes on a page you've created):
197 {{image reference="RenameConfirmFlamingoSimple.png"/}}
198
199 And if you're an [[advanced user>>platform:Features.PageEditing#HSimpleandAdvancededitingmodes]] you'll be able to also control whether the new page will be a Terminal page (i.e. a page that cannot have children, see also [[Terminology>>platform:Features.ContentOrganization.WebHome#HTerminology]]) or not:
200
201 {{image reference="RenameConfirmFlamingoAdvanced.png"/}}
202
203 If the page has child pages then you can choose to move them to the new location as well. This way the hierarchy under the renamed page is going to be preserved. Otherwise, if you choose to preserve the current path of the child pages (keep the children in place) then they will become "orphans": they will still be accessible with the same URLs (bookmarks are not broken) but they will have a missing parent (which you can fix by creating the parent page later).
204
205 You can also select whether to update the wiki pages that have links pointing to the affected pages.
206
207 In case there are external links (e.g. bookmarks) to the renamed page (or its child pages) they will be broken after the rename unless you choose to create an automatic redirect from the old location to the new one.
208
209 {{image reference="renameProgress.png"/}}
210
211 Once you click the Rename button you are taken to the Rename Status page where you can see the options that you have selected and the progress of the rename operation. The rename, like the copy, is performed asynchronously. The progress bar is replaced with the operation status at the end in order to let you know if the operation succeeded or failed. You can use the breadcrumbs to navigate to the new page or the old one.
212
213 == Pages that belong to extensions ==
214
215 Before the success message, you might see the following screen:
216
217 {{gallery}}
218 image:renameextension.png
219 {{/gallery}}
220
221 It happens when you try to rename a page that belong to an extension. This page could be one of the children of the current page. If you continue the rename action, the extension might not work anymore.
222
223 This screen makes you able to select precisely which pages to rename and which ones to preserve. You can also abort the action by clicking on the "Cancel" button.
224
225 == Pages that contains an used XClass ==
226
227 Starting with {{info}}10.10RC1{{/info}}, you might also see one of the following screen:
228
229 {{gallery}}
230 image:rename_simpleuser_xclass.png
231 image:rename_advanceduser_xclass.png
232 {{/gallery}}
233
234 It happens when you try to rename or move a page that contains an XClass which is used somewhere. This page could be one of the children of the current page. If you continue the renaming/moving action, some other pages will not work anymore. That is why the action is completely forbidden for simple users. Advanced users are allowed to chose precisely the pages to move and those to preserve. They can also abort the action by clicking on the "Cancel" button.
235
236 == Limitations ==
237
238 There are still some limitations on renaming:
239
240 * backlinks have to be turned on (they are turned on by default but if you have turned them off, rename will not rename backlinks and you'll have to turn them on again to benefit from this feature)
241 * backlinks located in XObjects and translated content are not currently renamed. You can track this issue [[XWIKI-981>>https://jira.xwiki.org/browse/XWIKI-981]] to follow the progress.
242 * backlinks are saved when a page is saved thus it may happen with a clean XWiki database that backlinks are not saved. In this special case, you can call the following in a page to refresh all links (you'll need to be admin to do this):(((
243 {{code language="none"}}
244 $xwiki.refreshLinks()
245 {{/code}}
246 )))

Get Connected