This is the release notes for XWiki Commons, XWiki Rendering, XWiki Platform and XWiki Enterprise. 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 7.0)

Full list of issues fixed and Dashboard for 7.1.

Extension Diff View Summary

Since XWiki 7.0RC1 you can view the local changes that have been made to the wiki pages of an installed extension. In this release we have improved the diff view by adding a summary that will help you navigate the changes.


See the Extension Manager Application for more details.

Responsive Search UI

We worked on making the search UI responsive on small screens. On mobile phones the list of search facets is now collapsed above the search results and the user can toggle it with a tap. We improved the way the search results of type Object and Object Property are displayed (check the result title and location / breadcrumb). We switched to using the icon themes for the search result icons and we also fixed some small spacing and alignment issues introduced by the migration from the old Colibri skin to the new Flamingo skin. Last but not least, we worked on refreshing the search UI without reloading the entire page when the user sorts the search results, uses the pagination or drills down the results using the search facets.


See the Solr Search Application documentation for more details.


  • The Script Macro has been improved to return any type of value even no binding is used to output content.
  • The default Java version triggered as dependency for the Debian packages is not Java 8
  • In the Administration Application, when you change the space you are administrating, you don't lose the current section anymore (if the current section exists in that space).


  • In edit mode, Password fields do not display the obfuscation placholder () anymore when the password value is empty. For example this removes the confusion when editing the Mail Admin UI and users were thinking that the SMTP Server password was set.
  • Not existing document won't end up in the document cache anymore. That mean request lots of not existing document won't ditch "real" documents from the cache anymore.
  • The WatchList application now uses the new Mail API instead of the old and deprecated Mail Plugin.
  • The WatchList Realtime notification option has been reworked and the previous performance penalty has been removed.
  • In App Within Minutes Application, the newly created applications don't have 'App Within Minutes' as parent, but the home page of the current wiki and their home page title doesn't contain the word 'Home' any more.
  • A new option was added to Watch a page that was just shared by mail directly from the email's body.


See the full list of JIRA issues fixed in this release.

For Developers

Trigger Prototype Event Listeners from jQuery

The event listeners registered from Prototype are now notified when a custom XWiki event is fired using the jQuery API.

// Prototype (old code that you don't have time to rewrite)
document.observe('xwiki:dom:updated', function(event) {
  event.memo.elements.each(function(element) {
   // Do something.
// jQuery (new code, in a different file/page)
require(['jquery', 'xwiki-events-bridge'], function($) {
  $(document).trigger('xwiki:dom:updated', {'elements': $('.some-container').toArray()});

See the developer's guide for more details.

Integration tests for JavaScript with Jasmine + RequireJS + WebJars

Using Jasmine, we have written a few integration tests for JavaScript code that uses AMD (RequireJS) and that has dependencies packaged as Webjars. We found out that the Jasmine Maven Plugin has support for both AMD and WebJars. You can check out this commit to see how we configured the plugin in case you want to write similar tests for your extension or module.


  • The XAR plugin's verify mojo has been improved to allow passing a list of regexes to identify content and technical pages. For example:
       <!-- Consider all pages named *Translations as content pages by default -->
       <!-- The EditTranslations page is not a Translation page and thus not a content page! -->
  • New $services.rendering.escape($content, $syntax) method to escape XWiki syntax. See the documentation.
  • The HTML5 renderer is now bundled in XWiki Enterprise.
  • Added a new objectPolicy=updateOrCreate parameter to the save action that allows editing and creating objects in one request. For more details, see the documentation.
  • It is now possible to select the output syntax of a skin, in order to use the correct renderer.
  • Ability to register a custom Resource Type.
  • The WebJar integration now registers a webjar URL type using a Resource Handler (it was reusing the bin URL type before). The new WebJAR URL format is:
    http://<server>/<context path>/webjars/<path/to/resource>[?version=<version>&evaluate=true|false]

    Note that you should use the exposed Script Service method to compute a WebJAR URL.

  • The mime type of uploaded attachment is now automatically stored in the database and won't be recalculated each time it's asked. Also a new API has been introduced in com.xpn.xwiki.doc.XWikiAttachment to change it if needed.
  • The ConfigurableClass mechanism now supports adding field hints / descriptions. See the documentation.
  • The xwiki-platform-legacy-crypto-script legacy module has been removed as it was conflicting with the Bouncy Castle 1.52 upgrade and we considered that there was little chance that this module was used anywhere in any extension. If by chance (so to speak) you were using it, you'd need to use the newer xwiki-platform-crypto-script module and rebuild your extension with it.
  • Added advanced search support to org.xwiki.extension.repository.ExtensionRepositoryManager
  • The Velocity macros from the Main.SolrSearch page have been moved to a separate page, Main.SolrSearchMacros, which should ease the creation of a custom search page (e.g. if you want reuse some macros and to overwrite others).
  • Added callable support to JobProgressManager. See Job Module.


The following dependencies have been upgraded:


The following translations have been updated: 

Tested Browsers & Databases

Here is the list of browsers we support and how they have been tested for this release:

BrowserTest Result
Chrome30.pngGoogle Chrome 41Not Tested
Firefox30.pngMozilla Firefox 37Jira Tickets Marked as Fixed in the Release Notes
IE30.pngInternet Explorer 8Not Tested
IE30.pngInternet Explorer 9Not Tested

Here is the list of databases we support and how they have been tested for this release:

DatabaseTest Result
hypersql.pngHyperSQL 2.3.2Jira Tickets Marked as Fixed in the Release Notes
mysql.pngMySQL 5.6.24Not Tested
oracle.pngOracle 11.2Not Tested
postgresql.pngPostgreSQL 9.4.1Not Tested

For the full list of tests see this page.

Known issues

Backward Compatibility and Migration Notes

General Notes

When upgrading make sure you compare your xwiki.cfg, and web.xml files with the newest version since some configuration parameters may have been modified or added. Note that you should add so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.

Loading JavaScript from WebJars with RequireJS

WebJars integration, available since 6.0M1, allows us to use JavaScript code that has been packaged as JAR and which has been included in the XWiki WAR or installed as an extension. Until this version the URL used to access a resource from a WebJar was looking like this:


The file path was specified in the query string. As a consequence, if you wanted to load a JavaScript file from a WebJar using RequireJS you would have written:

require(["$services.webjars.url('angularjs', 'angular.js')"], function() {

Note that the '.js' extension had to be included because RequireJS doesn't add it automatically if the URL has a query string. Starting with this version, the WebJar URLs look like this:

http://<server>/<context path>/webjars/<path/to/resource>[?version=<version>&evaluate=true|false]

Note that the resource path is not included in the query string any more. This means you need to update the "require" calls:

require(["$services.webjars.url('angularjs', 'angular')"], function() {

Otherwise RequireJS will attempt to load "angular.js.js". BUT note that even with the new URL format there are still cases when the WebJar URLs have a query string: e.g. when the resource must be evaluated. In this case you need to keep the ".js" extension:

    'require-config.min.js', {'evaluate': true})"
], function() {

API Breakages

The following APIs were modified since XWiki 7.0.1:

<clirr output here>

Get Connected