Show last authors
1 {{box cssClass="floatinginfobox" title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
4
5 This is the release notes for [[XWiki Commons>>http://commons.xwiki.org]], [[XWiki Rendering>>http://rendering.xwiki.org]], [[XWiki Platform>>http://platform.xwiki.org]] and [[XWiki Enterprise>>http://enterprise.xwiki.org]]. They share the same release notes as they are released together and have the same version.
6
7 This release is probably one of the biggest releases we have done in XWiki for years (more than 900 commits)! We have worked hard during all the summer to finally achieve the introduction of a new concept: **//Nested Pages//**. This big change affects both the platform and the user interface, and you will discover many differences while using XWiki.
8
9 {{warning}}
10 As a consequence, we do not recommend using this version in production because we still need to fine-tune the UI to fully adapt it to Nested Pages. This will be done in XWiki 7.3. However, in order to flush out all issues, especially about usability, please try upgrading to this version and play with it to let us know what you like/don't like. There's still time to adjust things. Thanks for your help!
11 {{/warning}}
12
13 For developers, this release also introduces a new //Script// right and some changes in the REST, Job and Refactoring modules, just to list a few...
14
15 Finally, it also brings a lot of bugs fixes!
16
17 = New and Noteworthy (since XWiki 7.1) =
18
19 [[Full list of issues fixed and Dashboard for 7.2>>http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=13499]].
20
21 == Nested Pages ==
22
23 It's now possible to create wiki pages inside other wiki pages. More specifically we've decided to drop the concept of Space in the UI (it's still there at the API/platform level) and instead, to replace it with the concept of Nested Pages.
24
25 We've also decided to drop the concept of Parent/Child relationship since it was too complex for end users to have 2 hierarchies: the Space/Page hierarchy and the Parent/Child hierarchy. The Parent/Child hierarchy also had limitations: you couldn't inherit page permissions for example. Thus the idea is to have a single hierarchy based on Nested Pages.
26
27 Advantages of Nested Pages:
28
29 * The URL reflects the page hierarchy
30 * Finer-grained control: Ability to set permissions at each level
31 * Generally speaking, a nicer and simpler way to organize your content hierarchically
32 * Moving and Deleting pages updates the hierarchy
33
34 Terminology:
35
36 * **Nested Page** (a.k.a **Non-Terminal Page**): This is a wiki page that can have children pages. Technically a Nested Page is implemented as a Nested Space (i.e. a **WebHome** page).
37 * **Non-Nested Page** (a.k.a **Terminal Page**): This a wiki page that cannot have children pages. Applications and script can create Terminal Pages. Advanced Users will also be able to create Terminal Pages from the UI. Standard Users will only be able to create Nested Pages.
38 * **Nested Space**: A Space which has another Space as parent. As mentioned above, a Nested Page is technically implemented as a Nested Space. You will used the term Nested Space when speaking technically about XWiki APIs for example but when talking about UI you should favor using the term Nested Page instead.
39
40 For more information, see [[Content Organization>>platform:Features.ContentOrganization||anchor="HHistory"]].
41
42 We have worked a lot to minimize the retro-compatibility issues. However, some Extensions are not adapted for //Nested Pages// yet, and their execution is still sub-optimal. For the next releases, we plan to work on the adaptation of these Extensions.
43
44 == Script right ==
45
46 A new Script Right has been added to allow controlling who has the right to write Scripts. Specifically anyone with Edit rights can edit a page and write a Script in it. However, when the page is rendered the script will only execute if the last author of the page has the Script right.
47
48 Example when the author of a script doesn't have the Script right:
49
50 {{image reference="scriptRightsErrorNotAllowed.png"/}}
51
52 The Script Right is set to DENY by default, meaning that if you do not have it explicitly, you will not be able to execute the scripts that you write with your user account.
53
54 However, for backward-compatibility reasons, the standard XWiki Enterprise distribution comes with the Script Right being allowed for all users at the main wiki level, so that, unless you (as an Admin) explicitly revoke the right for some users or explicitly deny it, they will be able to execute the scripts they wrote, just like before.
55
56 {{image reference="scriptRightsExplicitlyAllowedInXWikiPreferences.png"/}}
57
58 == Hiding of the Parent-Child Relationship ==
59
60 Following our decision to drop the Parent-Child relationship (see above), it's now been turned off by default in favor of Nested Pages.
61
62 Note that it's possible to go back to the previous behavior, in which the Breadcrumb was following the Parent/Child relationship, by setting the ##core.hierarchyMode## property to ##parentchild## in the ##xwiki.properties## configuration file.
63
64 === New Breadcrumb ===
65
66 The Breadcrumb has been reworked to reflect the location of a Page in the reference hierarchy. For example for a Page "CEO" inside a Page "Boarding" inside a Page "Management" inside a Page "Staff" you would have the following Breadcrumb:
67
68 {{image reference="[email protected]"/}}
69
70 === New Index Tree ===
71
72 The Index Tree is now using the [[reworked Document Tree Macro>>extensions:Extension.Document Tree Macro]] and is thus honoring the Nested Pages hierarchy. For example:
73
74 {{image reference="[email protected]"/}}
75
76 === Updated Edit Mode ===
77
78 In Edit mode, the ability to change the Parent has been removed by default since we're now honoring the Nested Pages hierarchy. For example:
79
80 {{image reference="[email protected]"/}}
81
82 == Flamingo ==
83
84 Following the introduction of the Nested Pages feature, we have changed a lot our default skin, Flamingo:
85
86 * The top menu has been removed and replaced by a //drawer// menu that you can expand by clicking on the top right icon
87 * The add menu has been relocated near the edit one
88 * The L&F of the Add, Edit, and "More Actions" menus has been changed
89 * A lot of actions have been moved to the "More Actions" menu
90 * The page breadcrumb has suffered some changes:
91 ** it is now also displayed on the wiki home page
92 ** the wiki home page is now included when it is part of the current document's hierarchy, i.e. for children and descendants of the wiki home page. See [[XWIKI-12423>>http://jira.xwiki.org/browse/XWIKI-12423]] for more details.
93 ** the sub-wiki pretty name is included between the home icon and the local page path
94 * The actions menus (edit, create, more actions) are now available from the rename, copy and delete actions.
95 * The create, copy and rename page actions have been modified to support nested pages:
96 ** The source and target pages are displayed using the breadcrumb
97 ** The target page can be selected using a document tree picker
98 ** For advanced users there is also the option to specify the target page using some text input fields (location advanced edit mode). This is useful especially if you want to create/move the page under a parent that doesn't exist yet (you cannot use the tree picker in this case because the parent would not be available in the tree).
99 * The delete action proposes to delete the children of the page.
100 * The welcome message from the main wiki home page has been updated.
101 * The "Spaces" widget from the wiki dashboard has been replaced with "Pages" which shows the hierarchy of nested pages from that wiki.
102 * For non terminal pages, we have introduced a "Page Administration", where you will find settings that concern the page and its children (it's actually the old space administration behind the scene). But we have also introduced 2 sections for setting rights on these pages:
103 ** a section to set rights for the page only.
104 ** a section to set rights for the page and its children.
105 * For terminal pages, nothing changes, you can change the access rights of the page in the "edit" menu. The only addition is a "Administer Parent" link in the "More actions" menu to administer the parent page (which again is the space administration behind the scene).
106 * The create action has been re-looked (with the introduction of the "page type" field) and proposes to import an office document.
107 * A new "children" viewer is now accessible in the "more actions" menu, along with the other viewers.
108 * For Terminal Pages, a new "siblings" viewer is present, which replaces the old "space index" feature.
109
110 {{gallery}}
111 image:[email protected]
112 image:[email protected]
113 image:[email protected]_actions.png
114 image:[email protected]
115 image:[email protected]
116 image:[email protected]
117 image:[email protected]
118 image:[email protected]
119 image:[email protected]
120 image:[email protected]
121 image:[email protected]
122 image:[email protected]
123 image:[email protected]
124 image:[email protected]
125 image:[email protected]
126 image:[email protected]
127 image:[email protected]
128 image:[email protected]
129 image:[email protected]
130 image:[email protected]
131 image:[email protected]
132 image:[email protected]
133 image:[email protected]
134 image:[email protected]
135 image:[email protected]
136 {{/gallery}}
137
138 == LDAP improvements ==
139
140 It's now possible to disable subgroups resolution using ##xwiki.authentication.ldap.group_sync_resolve_subgroups## property in ##xwiki.cfg## configuration file. Resolving each member to check if it's a group might be very expensive with big groups so if you know there is no subgroup you should really disable it.
141
142 == Solr Search ==
143
144 You can now search for nested pages using the [[Solr Search Application>>extensions:Extension.Solr Search Application]]. The display of the search result location has been updated to support nested pages.
145
146 {{image reference="[email protected]"/}}
147
148 The "Space" facet has been replaced with a "Location" facet that supports nested pages. This allows you to search in a specific location in the page hierarchy.
149
150 {{image reference="[email protected]"/}}
151
152 The "Page" facet has been removed by default because it doesn't bring value in the context of the nested pages: all non-terminal pages have the same name 'WebHome'. The "Wiki" facet is displayed by default only on the main wiki and only if you have multiple wikis.
153
154 The search results location displayed on the [[Search suggest>>extensions:Extension.Search Application||anchor="HSearchSuggest"]] has also been updated to support nested pages.
155
156 {{image reference="searchSuggestLocation.png"/}}
157
158 == Miscellaneous ==
159
160 * When a space home page has an empty title (and the space home page doesn't have a sheet or the sheet doesn't control the title) then the displayed title is now the space name instead of 'WebHome'.
161 * The [[Document Tree Macro>>extensions:Extension.Document Tree Macro]] has a new parameter called ##showSpaceAsDocument## which allows you to merge the space nodes with the space home page nodes.
162 * The list of available template providers is now sorted by document full name.
163 * The [[Orphaned Pages>>extensions:Extension.Index Application||anchor="HAllorphanedDocuments"]] tab from the [[Document Index>>extensions:Extension.Index Application||anchor="HAccessingtheIndexes"]] is now displayed only when [[the Parent-Child Hierarchy Mode>>ReleaseNotesXWiki72M2||anchor="HHidingoftheParent-ChildRelationship"]] is enabled (which is not the case by default).
164 * Import UI move to new standard tree(((
165 {{image reference="[email protected]"/}}
166 )))
167 * The size of the Job status cache is now configurable. See ##job.statusCacheSize## property in ##xwiki.properties## files.
168 * The Spaces macro (which lists all Spaces) is now working fine when there are Nested Spaces.
169 * The LiveTable macro is now working fine when there are Nested Spaces.
170 * The Navigation panel displays nested pages:(((
171 {{image reference="[email protected]"/}}
172 )))
173 * When renaming or copying a nested page the document title is updated to reflect the new page name if its previous value was equal the old page name. This was happening already for terminal pages. We extended the behaviour to nested pages.
174 * Fixed various issues for several applications bundled in XE (such as WatchList and Annotations), which should now work well with Nested Spaces.
175 * The Administration mode for spaces and wikis now uses the standard reference-based breadcrumbs instead of the previously custom section-based breadcrumbs.(((
176 {{image reference="[email protected]"/}}
177 )))
178 * The Administration mode no longer features a select input on the right side for navigation between spaces since that input does no longer scale in the context of Nested Spaces. Thus, the breadcrumbs should be used instead and the future UI improvements that will soon become available in this direction.
179 * It's now possible to create Skins in Nested Spaces.
180 * Changed the exception message displayed when a script execution fails due to lack of rights to make it clearer that it's not a problem with the current user, but with the script.
181 * When [[creating, copying or renaming a page>>platform:Features.DocumentLifecycle]] you can now select a top level location from the tree picker (e.g. copy as top level page) even if you have a single wiki (i.e. only the main wiki). You do this by selecting the root of the tree (i.e. the wiki node).
182 * The [[Document Tree Macro>>extensions:Extension.Document Tree Macro]] is now displaying a message when the tree is empty.(((
183 {{image reference="[email protected]"/}}
184
185 With the new ##showRoot## parameter you can force the document tree to show the actual root node (either the one specified by the ##root## parameter or the default root node).
186 )))
187 * A couple of bugs in the [[App Within Minutes Application>>extensions:Extension.App Within Minutes Application]], that were caused by the introduction of the Nested Pages feature, have been fixed.
188 * It's now possible create new FAQs in Nested Spaces.
189 * When using the XWiki Jetty distribution, a memory dump is automatically created in XWiki's ##data/## folder when an ##Out Of Memory## error occurs.
190 * The Activity Stream now also displays activity for Nested Spaces.
191
192 See the [[full list of JIRA issues>>http://jira.xwiki.org/issues/?filter=14213]] fixed in this release.
193
194 = For Developers =
195
196 == Nested Spaces ==
197
198 Since Nested Spaces were already planned and supported in APIs like ##DocumentReference## there are not too many changes for those who were using recent APIs but there is still some and here are the main ones.
199
200 === Space Reference instead of Space name ===
201
202 The heart of the implementation is that the field that used to contain the unique document space now contain the possibly Nested Space Reference. In practice it means that:
203
204 * "##.##" (dot), "##:##" (colon) and "##\##" (baskslash) characters, which are part of a Space name will now be escaped (using the "##\##" character) in the ##space## (##XWD_WEB##) field from the Document's table in the Database. For example a space named ##Space:with.special\char## will be stored as ##{{{Space\:with\.special\\char}}}##.
205 * Same as for the database, the ##XWikiDocument/Document#getSpace()## methods now return a serialized Reference to the Space instead of what used to be the unique Space name (basically it return what's in the database). Same logic for ##XWikiDocument#setSpace()##. Those field have been deprecated a long time ago but they are still used in lots of places...
206 * Various APIs are also affected by this Space name to Space Reference input change:
207 ** ##XWiki#getSpaceDocsName## methods (both in the public and private XWiki API)
208 ** All the default ##XWikiURLFactory## implementation methods accepting a Space as parameter have been modified to accept a serialized Space Reference. Extensions/code implementing ##XWikiURLFactory## (or extending classes implementing ##XWikiURLFactory## such as ##XWikiServletURLFactory##) will need to be modified to handle nested spaces passed in the ##space## parameter of the various APIs. Here's how to parse Spaces passed as a String:(((
209 {{code language="java"}}
210 private EntityReferenceResolver<String> relativeEntityReferenceResolver =
211 Utils.getComponent(EntityReferenceResolver.TYPE_STRING, "relative");
212 ...
213 or
214 ...
215 @Inject
216 @Named("relative")
217 private EntityReferenceResolver<String> relativeEntityReferenceResolver;
218 ...
219 private List<String> extractSpaceNames(String spaces)
220 {
221 List<String> spaceNames = new ArrayList<>();
222 // Parse the spaces list into Space References
223 EntityReference spaceReference = this.relativeEntityReferenceResolver.resolve(spaces, EntityType.SPACE);
224 for (EntityReference reference : spaceReference.getReversedReferenceChain()) {
225 spaceNames.add(reference.getName());
226 }
227 return spaceNames;
228 }
229 {{/code}}
230 )))
231 ** Extensions/code implementing ##ExportURLFactoryActionHandler## will also need to be modified to handle nested Spaces passed in the ##space## parameter.
232 * Extensions/code implementing ##EntityReferenceSerializer## or ##DocumentReferenceResolver## must now handle Nested Spaces (in the past they were already supposed to handle Nested Spaces but since it was not used they could take shortcuts and it wasn't visible. It's now going to fail, see [[XWIKI-12191>>http://jira.xwiki.org/browse/XWIKI-12191]]).
233
234 === Space separator properly taken into account ===
235
236 The Reference syntax specification was already indication that "##.##" was supposed to be escaped in the space part of the Reference but it was not really taken into account so not escaping it was not making any difference. This is now fixed in the various standard String Reference resolvers so a Reference that don't follow the specification and did not escaped the "##.##" in the space part will be cut is several nested spaces. Anything that was serialized with one of the standard serializers was properly escaped so not worry here, the issue will be more for hand written or hardcoded String References.
237
238 === New XAR format ===
239
240 To support exporting/importing nested spaces some changes has been made to the XAR format. The format remain upward and downward compatible (except that you won't get nested spaces in your < 7.2 instance obviously).
241
242 Two new attributes has been added to the ##<xwikidoc>## root XML element
243
244 * ##reference##: the complete local Reference of the document in standard Reference format. ##<web>## and ##<name>## are deprecated (but still set). ##<web>## keep containing the (unescaped) space name when there is only one space and will contain the space Reference when there is several (when imported in a < 7.2 instance a document exported from a nested space will end up in a space having as name the space reference).
245 * ##locale##: the locale of the document. ##<language>## is deprecated. It was not technically needed in the context of nested spaces but it makes having the Reference as attribute more consistent. It also make getting all the entries from a new format XAR easier and faster since document space and name would be placed anywhere in the document.
246
247 === REST module ===
248
249 * The REST module now supports Nested Spaces. Example of url to access the page ##A.B.C.MyPage##: ##/xwiki/rest/wikis/xwiki/spaces/A/spaces/B/spaces/C/pages/MyPage##.
250
251 === URL modules ===
252
253 The URL modules have been modified to support Nested Spaces. As a consequence the [[URL formats supported by the ##standard## URL scheme have been modified>>extensions:Extension.Standard URL API]].
254
255 === New Rename/Delete Jobs ===
256
257 New code has been developed to support Nested Pages/Nested Spaces and Script Services have been provided and they now run inside Jobs to better handle the fact that they are long-running operations.
258
259 The corresponding Script Services APIs have been added:
260
261 * Copy a Space(((
262 {{code language="none"}}
263 #set ($source = $services.model.resolveSpace('Path.To.Source'))
264 #set ($destination = $services.model.resolveSpace('Path.To.New.Parent'))
265 $services.refactoring.copy($source, $destination).join()
266 {{/code}}
267 )))
268 * Copy a Space As(((
269 {{code language="none"}}
270 #set ($source = $services.model.resolveSpace('Path.To.Source'))
271 #set ($destination = $services.model.resolveSpace('Path.To.New.Name'))
272 $services.refactoring.copyAs($source, $destination).join()
273 {{/code}}
274 )))
275 * Move a Space(((
276 {{code language="none"}}
277 #set ($source = $services.model.resolveSpace('Path.To.Source'))
278 #set ($destination = $services.model.resolveSpace('Path.To.New.Parent'))
279 $services.refactoring.move($source, $destination).join()
280 {{/code}}
281 )))
282 * Move a Page(((
283 {{code language="none"}}
284 #set ($source = $services.model.resolveDocument('Path.To.Source.WebHome'))
285 #set ($destination = $services.model.resolveSpace('Path.To.New.Parent'))
286 $services.refactoring.move($source, $destination).join()
287 {{/code}}
288 )))
289 * Rename a Space(((
290 {{code language="none"}}
291 #set ($source = $services.model.resolveSpace('Path.To.Source'))
292 $services.refactoring.rename($source, 'NewName').join()
293 {{/code}}
294 )))
295 * Rename a Page(((
296 {{code language="none"}}
297 #set ($source = $services.model.resolveDocument('Path.To.Source.WebHome'))
298 $services.refactoring.rename($source, 'NewName').join()
299 {{/code}}
300 )))
301 * Delete a Page(((
302 {{code language="none"}}
303 #set ($source = $services.model.resolveDocument('Path.To.Source.WebHome'))
304 $services.refactoring.delete($source).join()
305 {{/code}}
306 )))
307 * Delete a Space(((
308 {{code language="none"}}
309 #set ($source = $services.model.resolveSpace('Path.To.Source'))
310 $services.refactoring.delete($source).join()
311 {{/code}}
312 )))
313 * Convert a Terminal Page to a Nested Page(((
314 {{code language="none"}}
315 #set ($source = $services.model.resolveDocument('Path.To.Page'))
316 $services.refactoring.convertToNestedDocument($source).join()
317 {{/code}}
318 )))
319 * Convert a Nested Page to a Terminal Page(((
320 {{code language="none"}}
321 #set ($source = $services.model.resolveDocument('Path.To.Source.WebHome'))
322 $services.refactoring.convertToTerminalDocument($source).join()
323 {{/code}}
324 )))
325
326 === New create action parameters and logic ===
327
328 The create action now accepts a ##spaceReference## parameter and a ##name## parameter, together with an optional ##tocreate=terminal## parameter (usable on non-terminal pages). The previous space parameters was not scalable in the context of Nested Spaces since it was just a top-level space name so it did not allow the creation of deeper space levels. More details are available in the [[create action's documentation>>platform:DevGuide.Standard URL Format||anchor="HAction:create"]].
329
330 As explained previously, these logic is also available in the improved create UI, with the terminal pages option appearing only for advanced users and being checked or unchecked by default, depending on the type of the current page.
331
332 === JS API Improvements ===
333
334 * It's now possible to create a Nested Spaces Reference using XWiki's Javascript API. For example:(((
335 {{code language="javascript"}}
336 // Construct a Nested Space reference
337 var reference = new XWiki.SpaceReference('wiki', ['space1', 'space2']);
338 expect(XWiki.Model.serialize(reference)).toEqual('wiki:space1.space2');
339 reference = new XWiki.DocumentReference('wiki', ['space1', 'space2'], 'page');
340 expect(XWiki.Model.serialize(reference)).toEqual('wiki:space1.space2.page');
341 // Construct a non-Nested Space reference
342 reference = new XWiki.SpaceReference('wiki', 'space');
343 expect(XWiki.Model.serialize(reference)).toEqual('wiki:space');
344 // Try passing non-valid space parameters
345 expect(function() {new XWiki.SpaceReference('wiki', [])}).toThrow('Missing mandatory space name or invalid type for: []');
346 expect(function() {new XWiki.SpaceReference('wiki', 12)}).toThrow('Missing mandatory space name or invalid type for: [12]');
347 {{/code}}
348 )))
349 * A new ##XWiki.EntityReference.equals()## method has been added. For example:(((
350 {{code language="javascript"}}
351 var reference1 = new XWiki.DocumentReference('wiki', ['space1', 'space2'], 'page');
352 var reference2 = new XWiki.DocumentReference('wiki', ['space1', 'space2'], 'page');
353 var reference3 = new XWiki.DocumentReference('wiki2', ['space1', 'space2'], 'page');
354 expect(reference1.equals(reference2)).toBe(true);
355 expect(reference1.equals(reference3)).toBe(false);
356 {{/code}}
357 )))
358 * A new ##XWiki.EntityReference.fromJSONObject(obejct)## has been added to create a Javascript ##XWiki.EntityReference## from a Java ##EntityReference## directly serialized as JSON:(((
359 {{code language="javascript"}}
360 var reference = XWiki.EntityReference.fromJSONObject(jsonText.evalJSON());
361 {{/code}}
362 )))
363 * A new ##XWiki.EntityReferenceTree## JS class has been added, which partially mimics the Java ##EntityReferenceTree## Class. It's still missing features though as it was introduced mostly to make it easier to manipulate a serialized Java ##EntityReferenceTree##.
364
365 === Updated Document Tree Macro ===
366
367 The [[Document Tree Macro>>extensions:Extension.Document Tree Macro]] now supports Nested Pages and Nested Spaces modes. Specifically, the following changes have been made:
368
369 * removed the ##showSpaceAsDocument## parameter (was introduced recently in 7.2M1)
370 * deprecated the ##showChildDocuments## parameter
371 * added the ##hierarchyMode## parameter with two supported values: ##reference## (default) and ##parentchild##
372
373 As a result, you can use the document tree macro like this:
374
375 * Nested Page Tree(((
376 {{code language="none"}}
377 {{documentTree/}}
378 {{/code}}
379 )))
380 * Nested Space + Page Tree(((
381 {{code language="none"}}
382 {{documentTree showSpaces="true" /}}
383 {{/code}}
384 )))
385 * Parent-Child Page Tree(((
386 {{code language="none"}}
387 {{documentTree hierarchyMode="parentchild" /}}
388 {{/code}}
389 )))
390 * Old Page Index Tree (i.e. Parent-Child mixed with space grouping)(((
391 {{code language="none"}}
392 {{documentTree hierarchyMode="parentchild" showSpaces="true" /}}
393 {{/code}}
394 )))
395
396 == New Reference-related APIs ==
397
398 Various new API around References has been introduced while adding support for nested spaces.
399
400 === Complete References Providers ===
401
402 Complete References Providers (for DocumentReference, SpaceReference and WikiReference) with default or ##current## hints. They allow getting complete Reference created from each default or current part of those references (for example in SpaceReference you end up with the space of the XWikiContext document and the XWikiContext wiki)
403
404 {{code language="java"}}
405 @Inject
406 Provider<DocumentReference> defaultDocumentReference;
407
408 @Inject
409 @Named("current")
410 Provider<DocumentReference> currentDocumentReference;
411 {{/code}}
412
413 === org.xwiki.model.reference.EntityReferenceProvider ===
414
415 ##org.xwiki.model.reference.EntityReferenceProvider## replaces ##org.xwiki.model.reference.EntityReferenceValueProvider##. It's essentially the same thing but with ##EntityReference## instead of string which allow getting multiple spaces when you ask for the current ##EntityType.SPACE## for example.
416
417 {{code language="java"}}
418 @Inject
419 EntityReferenceProvider provider;
420 {{/code}}
421
422 === Properly support any kind of References in getDocument and getURL ===
423
424 ##com.xpn.xwiki.XWiki#getDocument(EntityReference)## and ##com.xpn.xwiki.api.XWiki#getDocument(EntityReference)## support any kind of Reference properly (e.g. a Space Reference will return the space home page, an Object Reference will return the Object Document Reference, etc).
425
426 Same for ##com.xpn.xwiki.XWiki#getURL(EntityReference)## and ##com.xpn.xwiki.api.XWiki#getURL(EntityReference)## (e.g. passing a Document Reference with Locale will return the URL to the specified document translation, by adding ##language=xx## to the query string).
427
428 === New helpers in EntityReference ===
429
430 * ##boolean equals(EntityReference otherReference, EntityType to)##: same as equals but only take into account Reference parts up to the passed entity type (included)
431 * ##boolean equals(EntityReference otherReference, EntityType from, EntityType to)##: same as equals but only take into account Reference parts between passed entity types (included)
432 * ##boolean equalsNonRecursive(EntityReference otherReference)##: same as equals but does not take into account the parent
433
434 === New helpers in LocalDocumentReference ===
435
436 * ##LocalDocumentReference(String pageName, EntityReference spaceReference)##: allowed created a LocalDocumentReference from a Space Reference instead of just the space name
437
438 === org.xwiki.model.reference.SpaceReferenceResolver ===
439
440 New default ##String## and ##EntityReference## based SpaceReferenceResolver has been added. It's the same behavior then ##DocumentReferenceBehavior## but for spaces.
441
442 {{code language="java"}}
443 @Inject
444 SpaceReferenceResolver<String> stringResolver;
445
446 @Inject
447 SpaceReferenceResolver<EntityReference> referenceResolver;
448 {{/code}}
449
450 === New model Script Service helpers ===
451
452 * new help to escape an entity name according to default Reference syntax as in:(((
453 {{code language="velocity"}}
454 $services.model.escape('some.space:with\specialchars', 'SPACE')
455 {{/code}}
456
457 will print
458
459 {{code language="nonde"}}
460 some\.space\:with\\specialchars
461 {{/code}}
462 )))
463 * you can retrieve a node from an ##EntityReferenceTree## using its reference:(((
464 {{code language="velocity"}}
465 #set ($alice = $services.model.resolveDocument('wiki:Users.Alice.WebHome'))
466 #set ($bob = $services.model.resolveDocument('wiki:Users.Directory'))
467 #set ($tree = $services.model.toTree($alice, $bob))
468 #set ($usersNode = $tree.get($bob.lastSpaceReference))
469 {{/code}}
470 )))
471
472 === New components to generate REST URLs ===
473
474 * The component ##RestURLGenerator## has been added. Its role, in the long term, is to generate a REST URL for any kind of EntityReference. It currently handles ##DocumentReference## and ##SpaceReference##.
475 * The corresponding script service has been added: ##$services.rest## with the method ##$services.rest.url($entityReference)##.
476
477 === Reference Scripting API for Nested Spaces ===
478
479 The Script API for Entity References has been updated with new APIs to support creating Nested Spaces references. For example:
480
481 {{code language="none"}}
482 {{velocity}}
483 $services.model.createDocumentReference("wiki", ["space1", "space2"], "page")
484 $services.model.createDocumentReference("wiki", ["space1", "space2"], "page", "default")
485 $services.model.createSpaceReference(["space1", "space2"], $services.model.createWikiReference("wiki"))
486 {{/velocity}}
487 {{/code}}
488
489 === Resolve nested spaces in JavaScript ===
490
491 {{code language="js"}}
492 var spaceReference = XWiki.Model.resolve('A.B.C', XWiki.EntityType.SPACE);
493 spaceReference.getReversedReferenceChain().map(function(entityReference) {
494 return entityReference.name;
495 }).join(' > ');
496 // Produces: A > B > C
497 {{/code}}
498
499 See the [[JavaScript API documentation>>platform:DevGuide.JavaScriptAPI||anchor="HWorkwithEntityReferences"]] for more details.
500
501 == New readonly XWikiContext provider ==
502
503 You can inject a new "readonly" XWikiContext the following way:
504
505 {{code language="java"}}
506 @Inject
507 @Named("readonly")
508 Provider<XWikiContext> roXWikiContextProvider;
509 {{/code}}
510
511 The difference with default provider is that the readonly one won't try to create a new XWikiContext and will return null if it can't find any. It's been introduce for some low level components that were used during XWikiContext creation but in general it should be used by any component that only search for some XWikiContext property that might be null even in a valid XWikiContext.
512
513 == New Space/XWikiSpace table ==
514
515 A [[new table dedicated to Spaces has been introduced>>platform:DevGuide.DatabaseSchema]], in order to have performant and scalable Space-related queries (like supporting getting paginated Space which is useful for the Document Tree macro for example).
516
517 == Queries improvement ==
518
519 === Allow executing complete SELECT queries ===
520
521 In HQL and XWQL it's now possible to execute full ##SELECT## queries without Programming Right as long as you follow some rules currently defined in ##com.xpn.xwiki.internal.store.hibernate.query.HqlQueryUtils##, which contains a list of the database field allowed in the SELECT clause. Namely:
522
523 * For the ##Document##/##XWikiDocument## table: ##fullName##, ##name##, ##space##, ##language##, ##defaultLanguage##, ##translation##, ##hidden##
524 * For the ##Space##/##XWikiSpace## table: ##reference##, ##name##, ##parent##, ##hidden##
525
526 This is also true for the Named Queries located in the ##queries.hbm.xml## file.
527
528 === New Secure Query ===
529
530 The right to execute or not some Query is now controlled by each ##org.xwiki.query.QueryExecutor##.
531
532 Anyone can ask the executor to check or ignore Right through the new ##org.xwiki.query.SecureQuery## extending ##org.xwiki.query.Query##:
533
534 * ##checkCurrentAuthor()##: indicate if the current author right should be checked
535 * ##checkCurrentUser()##: indicate if the result should be filtered based on current user Right (only implemented by SOLR right now)
536
537 == XWiki Select Widget ==
538
539 A [[new widget has been introduced>>platform:DevGuide.XWikiSelect]], to have a rich select box:
540
541 {{image reference="[email protected]"/}}
542
543 == Document Picker ==
544
545 Two new Velocity macros has been added to allow selecting a page from a tree picker and to display the path (breadcrumbs) to the selected page.
546
547 {{image reference="[email protected]"/}}
548
549 Check the [[Document Picker documentation>>extensions:Extension.Document Picker]] for more details.
550
551 == REST ==
552
553 2 new resources have been exposed to the REST API:
554
555 * [[JobStatus>>platform:Features.XWikiRESTfulAPI||anchor="HJobresources"]]
556 * [[JobLog>>platform:Features.XWikiRESTfulAPI||anchor="HJobresources"]]
557
558 === REST script services ===
559
560 The Script service changed a bit, ##url(EntityReference)## now return relative URL String by default and a new ##url(EntityReference reference, boolean external)## has been added to force returning an external form URL. See [[Generate a REST URL for a resource>>platform:Features.XWikiRESTfulAPI||anchor="HGenerateaRESTURLforaresource"]] for more details.
561
562 == Miscellaneous ==
563
564 * Objects, attachments and the document's class are now clearly not considered content, but metadata. Thus, any change in these will set the document's (XWikiDocument) metadataDirty flag to true and not touch the document's contentDirty flag unless there is an actual change in the document's content or title fields. This is also in line with the original intent of the contentAuthor document field. The direct impact of this is that the contentAuthor field will be updated only when the content is changed and thus the programming/script rights of a document will be changed much less often than before and much less by accident.
565 * custom Maven properties which have a special meaning (like ##xwiki.extension.features##) are not ##duplicated## in Extension custom properties anymore.
566 * standard fields names have been added to ##org.xwiki.extension.rating.RatingExtension##.
567 * URL configuration now use default ##ConfigurationSource## provider instead of only ##xwiki.properties## one which means it's possible to overwrite properties for each wiki among other things.
568 * Added ability to set and change the URL scheme to use in the Execution Context. This allows code to dynamically change the generated URLs when Rendering a document (useful when performing an Export for example).
569 * Started a new ##filesystem## URL Scheme for exporting Resources to the filesystem and generating URLs to them (useful for the HTML Export for example). At the moment, only the ##webjars## Resource Type is using it and all other Resource Types are using the old ##XWikiURLFactory## class.
570 * A new DocumentModelBridge.getContentAuthorReference() method has been added to allow accessing the content author of a document without depending on oldcore.
571 * Deprecate XWiki.parseContent(...) since it is was misleading and outdated. Its documentation mentioned that the passed content is parsed as velocity code, but it was actually doing much more than that and had some unwanted side-effect. Instead, use the parse/renderer that is specific to the type of content you have. See more details in [[XWIKI-12299>>http://jira.xwiki.org/browse/XWIKI-12299]].
572 * A new script service is available to retrieve the status of a specified job or the status of the currently running job from a specified group. See the [[Job Module>>extensions:Extension.Job Module||anchor="HScriptService"]] documentation for details.
573 * Custom displayers are now executed with the Rights of the user who wrote them (i.e. author of the class document or content author of the displayer document), and not the Rights of the user who wrote the script that uses them (i.e. current context document's content author). See [[XWIKI-12306>>http://jira.xwiki.org/browse/XWIKI-12306]] for more details.
574 * In the [[Active Install Extension>>extensions:Extension.Active Installs Server Application]], a new Velocity Macro has been introduced to compute the number of Active Installs having a specific Extension. Example usage:(((
575 {{code language="none"}}
576 {{include reference="ActiveInstalls.ExtensionCount"/}}
577
578 {{velocity}}
579 #set ($extensionIds = [
580 'org.xwiki.contrib:xwiki-totem-application',
581 'jsimard:event-reporter-application',
582 'mouhb:likeapplication'
583 ])
584 |=Extension Id|=Count
585 #foreach($extensionId in $extensionIds)
586 #countActiveInstallsUsingExtension($extensionId $count)
587 |$extensionId|$count
588 #end
589 {{/velocity}}
590 {{/code}}
591 )))
592 * Better support of non-DOCUMENT ##EntityReferences## in ##DocumentReferenceConverter##. It now behaves like ##XWiki#getDocument(EntityReference)##.
593 * The Copy/Rename/Delete UI actions are now using the [[Refactoring Module's Script Services>>extensions:Extension.Refactoring Module]].
594 * You can see the children and backlinks of any document with the new parameters ##?xpage=children## and ##?xpage=backlinks## to add to the document URL. To get the children according to the parent/child mechanism, you can use ##?xpage=children&hierarchy=parentchild##.
595 ** The features are also available as viewers: ##?viewer=children## and ##?viewer=backlinks##
596 ** A new "siblings" viewer has been added, accessible both with ##?viewer=siblings## and ##?xpage=siblings##.
597 ** For this viewers, a ##displayHidden## parameter has been added. By default, the hidden pages are not displayed unless the user's configuration overwrites this.
598 * You can now reuse the velocity ##hierarchy## macros defined in the Flamingo Skin's ##hierarchy_macros.vm## template to display the breadcrumbs for a particular document. See [[XWIKI-12408>>http://jira.xwiki.org/browse/XWIKI-12408]].
599
600 * In JavaScript, the class ##XWiki.Document## has been modified to handle nested spaces. A new constructor have been created, and the old one is deprecated.
601
602 == Deprecated and Retired projects ==
603
604 * The [[OSCache-based Cache Extension>>extensions:Extension.Cache OSCache]] has been [[moved to ##xwiki-contrib##>>https://github.com/xwiki-contrib/xwiki-platform-cache-oscache]] since we've been using the Infinispan implementation for a while now and the XWiki Core developers don't intend to continue supporting the OSCache-based one (it can be maintained by the Community, by whoever's interested in supporting it).
605
606 == Upgrades ==
607
608 The following dependencies have been upgraded:
609
610 * [[Bootstrap 3.3.5>>http://jira.xwiki.org/browse/XWIKI-12211]]
611 * [[Cssparser 0.9.16>>http://jira.xwiki.org/browse/XCOMMONS-817]]
612 * [[Commons-compress 1.10>>http://jira.xwiki.org/browse/XCOMMONS-842]]
613 * [[Groovy 2.4.4>>http://jira.xwiki.org/browse/XCOMMONS-831]]
614 * [[Hibernate Validator 4.3.2>>http://jira.xwiki.org/browse/XWIKI-12365]]
615 * [[HSQLDB 2.3.3>>http://jira.xwiki.org/browse/XE-1491]]
616 * [[Httpclient 4.5>>http://jira.xwiki.org/browse/XCOMMONS-815]]
617 * [[Httpcore 4.4.3>>http://jira.xwiki.org/browse/XCOMMONS-845]]
618 * [[Infinispan 7.2.5>>http://jira.xwiki.org/browse/XWIKI-12557]]
619 * [[Jackson 2.6.1>>http://jira.xwiki.org/browse/XCOMMONS-839]]
620 * [[JGroups 3.6.6>>http://jira.xwiki.org/browse/XWIKI-12507]]
621 * [[Joda-Time 2.8.2>>http://jira.xwiki.org/browse/XWIKI-12402]]
622 * [[JRuby 1.7.21>>http://jira.xwiki.org/browse/XWIKI-12344]]
623 * [[Less4j 1.14.0>>http://jira.xwiki.org/browse/XWIKI-12400]]
624 * [[Tika 1.10>>http://jira.xwiki.org/browse/XWIKI-12401]]
625
626 = Translations =
627
628 The following translations have been updated:
629
630 {{language codes="da, de, fr, hu, ko, pt_BR, sk, sv"/}}
631
632 = Tested Browsers & Databases =
633
634 {{warning}}
635 The QA Tests are executed after the release has been done. Thus, they are being prepared now and will be published soon.
636 {{/warning}}
637
638 {{comment}}
639 {{include reference="TestReports.ManualTestReportTemplateSummary"/}}
640 {{/comment}}
641
642 = Performances tests compared to 6.4.5 =
643
644 There hasn't really been much performance work on this version so we get mostly the same result than in [[7.1 release note>>ReleaseNotesXWiki71||anchor="HPerformancestestscomparedto6.4.4"]]. The important point here was to check if nested spaces ha much impact on performances.
645
646 {{warning}}
647 It's important to note that the way to measure performances has changed in this version ([[Dumbbench>>https://github.com/tsee/dumbbench]] was used) and this is why you'll some differences if you compare this Performance report with the one for 7.1 for example.
648 {{/warning}}
649
650 {{display reference="test:Performances.Jetty HSQLDB single wiki 645 to 72" section="HSummary"/}}
651
652 More details on [[performance comparison on single wiki between 7.2 and 6.4.5>>test:Performances.Jetty HSQLDB single wiki 645 to 72]].
653
654 = Known issues =
655
656 * [[Bugs we know about>>http://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=category+%3D+%22Top+Level+Projects%22+AND+issuetype+%3D+Bug+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC]]
657
658 = Backward Compatibility and Migration Notes =
659
660 == General Notes ==
661
662 When upgrading make sure you compare your ##xwiki.cfg##, ##xwiki.properties## and ##web.xml## files with the newest version since some configuration parameters may have been modified or added. Note that you should add ##xwiki.store.migration=1## so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.
663
664 == Issues specific to XWiki 7.2 ==
665
666 === Nested spaces ===
667
668 See [[previous Nested spaces section>>||anchor="HNestedSpaces"]] for details on what changes in the way some API and the database are dealing with the Document Space.
669
670 Note that some existing Extensions are impacted and may break slightly: Extensions taking some user input and creating Spaces based on that will most likely display {{{"\."}}}, {{{"\:"}}} and {{{"\\"}}} in the UI. Unless they already clean the user input and remove ".", ":" and "\" characters. So for example if a user enter a Space name of "my.space":
671
672 * before 7.2: the Extension would create/display a Space named "my.space"
673 * after 7.2: the Extension will create/display a Space named "my\.space"
674
675 === URLs ===
676
677 In order to support Nested Pages and have the ability that typing a URL such as ##/A## will lead to ##A.WebHome## we have stopped supporting URLs that don't specify the ##view## action (when ##xwiki.showviewaction=1##). Thus URLs such as ##/xwiki/bin/Something## now need to be written as ##/xwiki/bin/view/Something##. If ##xwiki.showviewaction=0## then you can still write ##/xwiki/bin/<something>## provided that ##<something>## isn't equal to ##view##. If it is (you have a space named ##view##) then you need to use ##/xwiki/bin/view/view[...]##.
678
679 === Templates ===
680
681 All the templates specific to [[extensions:Extension.Colibri Skin]] had been moved to it. If your skin depends on some of these templates, you should set Colibri as parent of your skin.
682
683 == API Breakages ==
684
685 The following APIs were modified since XWiki 7.1.2:
686
687 * New configuration option to change the size of the Job statuses cache:(((
688 {{code language="none"}}
689 org.xwiki.job.JobManagerConfiguration: Method 'public int getJobStatusCacheSize()' has been added to an interface
690 {{/code}}
691 )))
692
693 * Added missing methods to the ##DocumentModelBridge## class, which are already implemented by XWikiDocument:(((
694 {{code language="none"}}
695 org.xwiki.bridge.DocumentModelBridge: Method 'public org.xwiki.model.reference.DocumentReference getContentAuthorReference()' has been added to an interface
696 {{/code}}
697 )))
698
699 * AbstractWrappingObject, AbstractSafeObject and ScriptSafeProvider have been moved to xwiki-commons-script:(((
700 {{code language="none"}}
701 org.xwiki.extension.wrap.WrappingIterableResult: Removed org.xwiki.extension.internal.safe.AbstractSafeObject from the list of superclasses
702 org.xwiki.extension.wrap.WrappingIterableResult: Removed org.xwiki.extension.wrap.AbstractWrappingObject from the list of superclasses
703 org.xwiki.extension.wrap.WrappingIterableResult: Parameter 2 of 'public WrappingIterableResult(org.xwiki.extension.repository.result.IterableResult, org.xwiki.extension.internal.safe.ScriptSafeProvider)' has changed its type to org.xwiki.script.internal.safe.ScriptSafeProvider
704 org.xwiki.filter.script.AbstractFilterScriptService: Changed type of field scriptProvider from org.xwiki.extension.internal.safe.ScriptSafeProvider to org.xwiki.script.internal.safe.ScriptSafeProvider
705 org.xwiki.extension.script.AbstractExtensionScriptService: Changed type of field scriptProvider from org.xwiki.extension.internal.safe.ScriptSafeProvider to org.xwiki.script.internal.safe.ScriptSafeProvider
706 {{/code}}
707 )))
708
709 * com.xpn.xwiki.XWiki#localStringEntityReferenceSerializer now exists in oldcore, we do not need it in the aspect anymore:(((
710 {{code language="none"}}
711 com.xpn.xwiki.XWikiCompatibilityAspect: Method 'public org.xwiki.model.reference.EntityReferenceSerializer ajc$interFieldGetDispatch$com_xpn_xwiki_XWikiCompatibilityAspect$com_xpn_xwiki_XWiki$localStringEntityReferenceSerializer(com.xpn.xwiki.XWiki)' has been removed
712 com.xpn.xwiki.XWikiCompatibilityAspect: Method 'public void ajc$interFieldInit$com_xpn_xwiki_XWikiCompatibilityAspect$com_xpn_xwiki_XWiki$localStringEntityReferenceSerializer(com.xpn.xwiki.XWiki)' has been removed
713 com.xpn.xwiki.XWikiCompatibilityAspect: Method 'public void ajc$interFieldSetDispatch$com_xpn_xwiki_XWikiCompatibilityAspect$com_xpn_xwiki_XWiki$localStringEntityReferenceSerializer(com.xpn.xwiki.XWiki, org.xwiki.model.reference.EntityReferenceSerializer)' has been removed
714 {{/code}}
715 )))
716
717 * Not a breakage. The legacy method was not in the right place (which mean that it was not available so it actually fix a breakage):(((
718 {{code language="none"}}
719 com.xpn.xwiki.XWikiCompatibilityAspect: Method 'public java.lang.Object getRenderingEngine()' has been removed
720 {{/code}}
721 )))
722
723 * Young API. ExportURLFactoryContext been renamed to FilesystemExportContext and moved to the Filesystem URL scheme module
724 {{comment}}Eduard @ 7.2RC1:
725 I have found 3 differences in xwiki-platform that have not generated a clirr error, maybe they are leftovers or the clirr report did not catch them for some reason. See https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/pom.xml#L493:L510{{/comment}}

Get Connected