Changes Report
Configuration modifications
There's now a setProperty() API to modify a single ConfigurationSource property.
#displayUser and #displayGroup now allow displaying a link to the profile
The standard velocity macros #displayUser and #displayGroup can now be configured to display a link to the user or group profile with the parameter displayLink. The parameter defaults to true.
The rights livetables display user first name and last name
User first name and last name are now displayed in the rights UI using the standard user and group displayers.
Users can be filtered based on first name and last name in the rights UI
The rights UI now allows filtering based on the user first name last name and username. This is particularily helpful in cases where usernames do not contain any character from the user first name or last name (for example, uuid-based usernames).
Block attributes
Rendering Blocks now have the concept of attributes. The main difference between Block parameters and block attributes is that attributes are not meant to be parser/serialized, the point is to use them as internal metadata associated to a block. The current main use case is to store the result of pre-executed macros.
Tour Application in platform
The Tour Application is now part of xwiki-platform and the contrib extension has been moved to the attic.
Extensions Security Vulnerabilities Application
After some forum discussions we agreed that the extension is current not useful to fix security vulnerabilities, and is at risk of presenting false-positive. Until those issues are fixed, we decided to stop bundling it as part of the standard distribution.
Pre-edit document check
It is now possible for extensions to define a pre-edit document check, similar to what already exists for locked pages, or pages owned by extensions.
Required Rights
The Required Rights Application analysis is deactivated by default as the analysis is still incomplete and the presentation needs to be improved to more clearly show what's wrong. Still, the analysis can already provide useful warnings and this is a good opportunity to provide feedback as this feature will be activated by default in a future version of XWiki. It can be activated by setting the security.requiredRights.protection to warning.
#-# [Since 15.9RC1]
#-# Indicates how documents are protected by required rights.
#-#
#-# The possible choices are:
#-# * none (the default): no required rights check
#-# * warning: a warning is presented to the user when trying to edit a document with required rights issues
# security.requiredRights.protection=none
Added links towards documentation under the videos in the Help section.
Change viewer UI update
Improved the layout and added icons in the version comparison UI.
Improved contrast of the metadata display on the change viewer.
Added various HTML landmarks to improve the view page semantics.
Improved the visibility of the focus state of the "Create", "Edit" and "more actions" buttons found on the top right of every page content.
Added autocompletion to the login page and the register form.
New API to safely evaluate XObject properties
A new API to provide safe evaluation of XObject properties has been introduced to allow developers to control which properties from which XClasses should be evaluable, and how they should be evaluated. For XObjects that have assigned evaluators, the evaluated properties can be recovered in scripts through the new evaluate() method.
Affected children during page delete is now displayed with a Live Data
The list of affected children during page delete is now displayed with a Live Data.
Supported language setting is not shown anymore when irrelevant
The "Supported Languages" setting is now hidden when the wiki is not multilingual.
PDF Export Page Order
Starting with this version, when exporting multiple pages to PDF, by selecting them from the page tree, their content will appear in the generated PDF following the order from the tree:
- parent / ancestor pages are printed before child pages
- child pages are printed in the order they appear in the tree
This also means that we can now use the Pinned Child Pages feature to enforce a particular order in the PDF export.
