This is the release notes for XWiki Commons, XWiki Rendering and XWiki Platform. They share the same release notes as they are released together and have the same version.

<insert description of release here>

New and Noteworthy (since XWiki <version - 1>)

Full list of issues fixed and Dashboard for <full version here even for RC, e.g. 10.5>.

For Users

Merge on save

Continuing the work started on XWiki 11.1 to warn users when performing conflicting edits on the same page, we finally implemented a merge on save mechanism.

This means that in case of conflict edition (two users saving the same document at the same time), instead of always displaying a window to the user asking what to do, we first try to perform a merge of both document. If the changes concerned two very different parts of the document (two different sections, an edit performed on an object against an edit of the content, etc) the user won't notice that a merge has been performed.

Now, some conflicts might still occur if both users tried to edit the same part of the document. In that case, a new window is displayed asking the user what to do.
The user will now have three different choices:

  • Merge the document and fix conflict with his/her own changes: this means that as much as possible, we try to merge the changes. Only for the part that are conflicting, we only kept the changes from the last user. This is the recommended choice.
  • Force save the document: this means no merge at all will be performed. Only the changes performed by the last user will be saved. It basically discards the changes made by the previous user.
  • Reload the editor: this choice might be taken very carefully as it might cause a loss of data. It means that the current changes performed on the document will be completely lost and the editor will be reloaded with the last changes.

The conflict window now display the changes that will be performed for each choices. Be careful with the parts in red since it shows what part of the document will be lost during the operation. Note that it's also possible to select two specific versions of the document to perform a comparison before making a choice.

Line numbers in code macro

A new parameter has been introduced to enable line number display in the code macro. See Code Macro for more details.


  • Display content in restricted mode: A new URL parameter is available for viewing pages in restricted mode.
    You can now use restricted parameter, with the following values:

    • false (default): the macro transformations are normally executed
    • true: macro transformations are executed in degraded mode or not executed at all, depending on the macro implementation.

    In particular, various scripting macro such as Velocity Macro or Groovy Macro are not executed in restricted mode.
    This parameter might be then use to check if a page is well displayed for user who cannot execute those scripts for example.

  • The deleter of a document is now allowed to restore it even without admin right (provided the user have enough right to create a document at this location).

For Admins

No changes!

For Developers

No changes!


  • Allow to specify the content type when creating a wikimacro: It is now possible to specify the content type of a wikimacro when creating it. A new field Macro Content Type is available for this purpose.
    Before 11.5RC1 release, a field Macro Content Type was existing and have been renamed Macro content availability in this release.

    The Macro content type field will be used in the future to propose the right editor depending on the content type. It currently proposes two values: WIKI to specify that the content should be edited with an editor for wiki content, or UNKNOWN to specify it should be edited with a plain text editor.
    Note that it also accepts any kind of custom Java values, such as java.util.List<java.lang.String>.

    If left blank, the default value would be UNKWOWN. This is also the value for macro created before 11.5RC1.

  • Allow to create Static List class with value suggestion: It is now possible to create a Static List class that will display a suggest picker for the values that are entered.
    Note that the displayer is only available when using the input display type.

  • Allow to store a StaticList value in a large string: When creating a Static List class, it is now possible to choose to  Allow large string. This can be useful if this list aims at storing large values. 

  • Dedicated macro for inserting and inline editing of wikimacro parameters: It is now possible to use a dedicated macro to insert a wikimacro parameter

    For example, you can specify the following macro content:
    Here's the content of my macro parameter **foo**:

    {{wikimacroparameter name="foo" /}}

    The content of the macro parameter will be displayed and will be inline editable in the WYSIWYG editor.

Moved Modules

<description deprecated, retired and moved projects>


The following runtime dependencies have been upgraded (they have a different release cycle than XWiki Commons, XWiki Rendering and XWiki Platform):


The following translations have been updated: 

  • Language
  • Language

Known issues

Backward Compatibility and Migration Notes

Renaming of WikiMacro field

The field Macro content type has been renamed Macro content availability in WikiMacroClass UI.

General Notes

  • When upgrading make sure you compare and merge the following XWiki configuration files since some parameters may have been modified, removed or added:
    • xwiki.cfg
    • web.xml
    • hibernate.cfg.xml
  • Add in xwiki.cfg so that XWiki will attempt to automatically migrate your current database to any new schema. Make sure you backup your Database before doing anything.

Issues specific to XWiki 11.5RC1

XWiki now requires JDBC 4.2

In practice it just means you need to make sure the database connector you are using is not too old (JDBC 4.2 came with Java 8 so you should be fine if you downloaded the connector in recent years).

Hibernate 5.4.3 upgrade

Hibernate has (finally) been upgraded to the very last version. While it means you will benefit from bugfix/improvement/new features it's also a huge jump (previous version was close to 10 years old) and you will probably have issues if you are directly manipulating Hibernate APIs or some library expecting a much older version of Hibernate. You can find the details on but here is an extract from XWiki point of view:

  • HQL '?'-based wildcards are not supported anymore at all by Hibernate. We added an automatic converter (to '?1' JPQL style) which seems to work well but it might not be perfect and it's producing a deprecating warning log
  • You might need to update your hibernate.cfg.xml file
  • Various Hibernate classes have been removed or moved to different Java packages
  • Various Hibernate methods have been removed from the APIs or not having any effect anymore even if still here and deprecated

HTML head extension point identifier update

The identifier of the HTML header extension point allowing to inject HTML in the pages head tag has been changed from org.xwiki.platform.head to org.xwiki.platform.html.head. Update your UI Extension Points if you were using the old id. This was done to disambiguate between HTML head and page head.

API Breakages

The following APIs were modified since <project> <version - 1>:


The following people have contributed code and translations to this release (sorted alphabetically):

<code contributors>

Created by Vincent Massol on 2019/05/22

Get Connected