Changes Report

New parameter in the Location Picker Macro

New parameters have been added to the locationPicker velocity macro: filterHiddenDocuments, root and sortDocumentsBy.

These new parameters are just passed to the Document tree macro.

Improved Solr search indexing speed

The batch size of the Solr search index has been increased to speed up indexing. To further speed up indexing, documents are now submitted in batches to Solr (using the same batch size) and batches are now prepared in parallel to the indexing of the previous batch. This slightly increases the memory usage as two full batches of data to index might be kept in memory. You can control the memory usage by adapting the number of characters after which a batch is committed, the (new) default is 10 million.

Updated the Live Data pagination

Standardized the look of the Live Data pagination to fit better in the standard Flamingo Skin.

Started enforcing required rights in some bundled pages

After adding the possibility to configure required rights of pages in XWiki 17.4.0, we're now starting to slowly enforce required rights for wiki pages that are part of a standard XWiki installation. In this release, we're starting with the Alerts Application and the Annotation Application.

Skin extensions on this wiki require just wiki admin right

Skin extensions that are always active on this wiki now require just wiki admin right instead of programming right. This makes the required rights more consistent as UI extensions with the same scope also just require wiki admin right and already allowed activating skin extensions on a whole wiki. Further, this should reduce problems when admins without programming right install extensions, for example, on a subwiki.

New ordering property

A new bean property has been added allowing to specify the order of a parameter. This is currently used for defined the order to display the macro parameters in the macro configuration UI. The order is defined such as the lower the value the higher the priority, with a default value defined to -1, meaning no order set.

Possibility to define the order of content and parameters in Wiki Macros

It's now possible to specify the order of the wiki macro parameters: a new property "order" is available in the WikiMacroParameterClass allowing to define the order of each parameter. This order defines how the parameters are sorted in the macro configuration UI. The lower the value for the order, the higher the priority to display them in the configuration UI. Note that it's also possible to define the order of the content, which is displayed in same UI, to order it with the other parameters. The default value is -1 and means no preset order.

Support for the conversion of new collection types

To make it much easier to use the properties converter API which takes a default value, support for the types of the following very common objects has been added:

• List.of()
• List.of(1)
• List.of(1, 2, 3)
• Arrays.asList()
• Collections.emptyList()
• Collections.unmodifiableList(Collections.emptyList())
• Set.of()
• Set.of(1)
• Set.of(1, 2, 3)
• Collections.emptySet()
• Collections.unmodifiableSet

Faster loading of icons

We've made rendering icons faster, leading to slightly improved loading times of all pages and significantly improved loading times of UIs that involve lots of icons like the quick action for inserting icons in the editor.

Override Default WYSIWYG Editor from Request

XWiki already supports configuring the default WYSIWYG editor from the dedicated administration section, but this affects all users. When testing an experimental editor it's better to overwrite the default WYSIWYG editor from request, i.e. for a single editing session. Starting with this version, you can use a request parameter like this to overwrite the WYSIWYG editor:

<simpleTypeName>.<category>.editor

For instance, for a WYSIWYG editor with hint "blocknote", registered for the data type "org.xwiki.rendering.syntax.SyntaxContent" and category "wysiwyg" you can use a URL like this to change the editor:

## Standalone edit mode
/xwiki/bin/edit/Some/Page?editor=wysiwyg&SyntaxContent.wysiwyg.editor=blocknote

## Inplace edit mode
/xwiki/bin/view/Some/Page?SyntaxContent.wysiwyg.editor=blocknote#edit

VirtualMachineError always logged

Any log with a VirtualMachineError (for example, OutOfMemoryError or StackOverflowError) are now forced to go through any job log filtering and will always end up in the main log. It's important to be able to catch them there, since they are very often death sentences for the instance.

Faster notification dispatching

Notifications in large wikis with lots of changes arrive faster.

Annotation bubble can now be displayed on the left of the annotation

When there is not enough space on the right of the annotated place, the annotation bubble appearing when creating an annotation will now be placed on its left instead of overflowing the viewport.

Added a logo-description field to color themes

It contains the alternative text for the logo of the wiki. The localized value associated to the key core.document.header.logo.image.text is used by default. This field contains an hint in the editor. Hints provided as a specific translation value can now be used for all fields in the editor.

Return to view without creating revisions

You can now use the Done button to return to view mode from realtime collaboration without fearing that useless empty page revisions are created. The page is saved, and a new revision is created, only if the content has changed since the last (auto)save. This behavior applies to the Save & Continue shortcut key (Alt+Shift+S) as well. You can force a new empty revision only by specifying a change summary, using either the "Summarize & Done" or the "Summarize Changes" actions from the realtime toolbar. See the Realtime WYSIWYG Editor documentation for more information.

Support for several CSS files in icon themes

When creating an icon set, you can now specify several CSS files, making it easier to support icon sets that require several style sheets.

Documentation Linking in Repository Application

There's now a "Documentation" button displayed when using the website xproperty to link to an extension's documentation. In addition, that button is styled as a primary button, and the "Download" button is now styled as a default button and has been moved to be the last button displayed (since it's the less useful one).

LESS customizations now impact CSS properties

CSS and LESS variables now share a common source of truth. In addition, the LESS customization will now have an impact on CSS variables as long as LESS computation works. Read more

The gallery macro now uses the alt provided on the images in its content.

Administration categories are now consistently ordered. When viewing page administration, the order of the categories could change in unpredictable ways. Now they always respect the order that can be seen in the global administration.