Changes Report
External URL generation improvements
It's now possible to set the port to use when generating an URL for a wiki in the each wiki descriptor. When the port is not set for a wiki, XWiki fallback on the main wiki descriptor.
Subwiki secure property (which indicate if HTTPS should be used instead of HTTP when generating a URL for the wiki) now inherit main wiki value if not explicitly set.
The first time XWiki is accessed the main wiki descriptor is generated using what can be found in the request's URL. For example if you access your wiki using https:mydomain:9898/xwiki/ you will end up with the following main wiki descriptor:
- alias: mydomain
- secure: true
- port: 9898
Also XWiki now supports the Forwarded (RFC7239) standard HTTP header when extracting information from the URL used by the client.
Notifications Auto Watch is now disabled by default
An important bug has been discovered in the Notification Applications that prevents using the Auto Watch feature when the wiki contains a lot of pages. For this reason, the default behavior for the Auto Watch feature has been set to not automatically follow any page. Nevertheless, users and administrators can still decide to change their own settings.
Macro Content Prefill in WYSIWYG Editor
When inserting a macro, the macro content text area is prefilled with the text selected within the editing area. This means you can for instance transform a paragraph into an error message by selecting the paragraph text, click the Insert Macro button from the tool bar, select the Error Message macro and insert it. Checkout the CKEditor Integration documentation for more information.
Notifications Filters Store
Due to scaling issue, we have changed the way the notification filter preferences are stored in the wiki. They are not saved in the user profile pages anymore, but in their own database table.
Thanks to this improvement, we have re-enabled the default behavior for the Auto Watch feature so that users automatically watch pages they have contributed to.
User membership in the profile
It's now possible to see the groups a user is member of in the profile. See User Profile Application.
Group manager
A new org.xwiki.user.group.GroupManager and corresponding services.user.group script service are now available.
See more details on User Module.
The notifications macro can now handle tags
The "tags" parameters can be used to filter events that concern pages marked with some given tags. In a multi-wikis environment, it works only on the current wiki.
The name of the wiki is now displayed in the notifications
When a notification concerns a page that is not in the current wiki, the name of the wiki is now displayed in the notification.
Larger attachments by default
Till now the default limit for attachments was set at 32MB. It's now been increased to 100GB.
Default empty choice for list properties
In the default list property editor an empty choice (generally displayed as "---" but it can be translated) is now always added for non multi select based editing. This avoid hacks like the "---" value which used to be used in various XWikiPreferences properties choices.
Followed users in the user profile
A user can now see again (it was temporarily removed in past version while we migrated from WatchList to Notifications) the list of the users she is watching in the "network" panel of her user profile.
Improved Users Administration Section
The Users section from the Wiki Administration has been improved:
- Shows the user avatar
- Shows the user scope (Global vs. Local) when you are on a subwiki
- Has nicer modal popups for creating, editing and deleting the users
Improved Groups Administration Section
The Groups section from the Wiki Administration has been improved:
- Shows the group avatar
- Shows the member type (User vs. Group) when listing the members of a group
- Shows the group scope (Global vs. Local) when you are on a subwiki
- Has nicer modal popups for creating, editing and deleting the groups
Propertly support long paths in filesystem store
The way the filesystem store organizes the data has been completely modified to fix a bug with some languages. There should not be any issue with the size of the path anymore.
Easily edit the app title
The title of an application created with App Within Minutes can now be edited from the last step of the application wizard. The application title is displayed on the application home page, on the applications panel and live table, on the breadcrumb, etc. See the App Within Minutes documentation for more information.
Macro Parameter Groups
The WYSIWYG editor is now able to group macro parameters as indicated in the macro descriptor. Currently only the Include Macro has grouped parameters. There can be two types of macro parameter groups:
- groups of related parameters (e.g. reference and type in the case of the Include Macro)
- groups of alternative parameters (only one parameter in the group should be set); this type of groups are displayed using tabs (e.g. "Resource" and "Page" in the case of the Include Macro)
See the CKEditor Integration documentation for more information.
Macro Parameter Pickers
The WYSIWYG editor is now able to load pickers for macro parameters based on their type. The binding between macro parameter types and the associated pickers is done on the server side (check the templates/html_displayer folder inside the XWiki WAR). For instance, if you have a wiki-based rendering macro, you can set the type of a macro parameter to "org.xwiki.model.reference.DocumentReference" in order to get a document picker when inserting or editing your macro from the WYSIWYG editor. Check the CKEditor Integration documentation for more information.
Allow to disable authentication security mechanism
In order to avoid any problem in the future with the Authentication Security that we recently introduced, we created a dedicated UI to easily disable/enable this mechanism. Note that disabling the authentication security will also clear the information about login failures, which might unlock users in case of problems.
Inline editing of macro parameters
It is now possible to allow inline editing of macro parameters when using the WYSIWYG editor. In order to do that, we reuse the same principle as for allowing inline editing of content in macro: you have to specify the type of the macro parameter by using @PropertyDisplayType on the parameter, and then you have to specify the metadata to put where the macro parameter is used in the UI, by using the AbstractMacro#getNonGeneratedContentMetaData("parameterName") method.
