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

New tip about typing the [ character when editing in WYSIWYG to get autocompletion for links.

For Admins

No changes!


  • 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.

For Developers

No changes!


  • Maven "legacy" profile: The Extension Manager now automatically activates the legacy profile when reading a pom.

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

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.0 Release Candidate 1

New filesystem store paths

The paths of the filesystem store have been completely modified and the store itself is now at a different location:

  • moved from <permdir>/storage to <permdir>/store/file/ to give room for potential future store implementations based on the filesystem
  • moved from complete hierarchy-based encoded URLs to reference hashes (to fix the issue with some languages)

In most cases there is nothing to do since a migration will take care of the upgrade automatically. However if you were directly manipulating the old stored files (something you shoudln't do!) it won't work anymore and you'll need to adjust your script/code.

Legacy profile

Extension Manager now automatically activate the legacy profile when reading a pom.

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/01/10

Get Connected