ReleaseNotesXWikiEnterprise17M3

Last modified by Thomas Mortagne on 2017/03/24

ContentsThe [toc] macro is a standalone macro and it cannot be used inline. Click on this message for details.

Release Notes for XWiki Enterprise 1.7 Milestone 3

Third milestone of the XWiki Enterprise 1.7 version (Roadmap).

Summary of changes since XWiki Enterprise 1.7 Milestone 2

Main changes:
  • Webdav support

    XWiki now expose a webdav server interface. This means you can now access/edit/delete page sources and attachments from any webdav client.

  • Groovy upgrade

    The groovy engine has been upgraded to the last 1.6 beta version. You can now use all the new features of groovy as well as speed improvements and bugfixes from groovy 1.0 to 1.6 beta 2. See http://groovy.codehaus.org/ for more.

  • New script macro

    The new script macros add the ability to use any scripting language supporting JSR-223. For now the default XWiki distribution comes with only a groovy 1.6 support but it easy to add support for other language (like ruby, python, etc.) simply by adding the corresponding engine and implementation. See https://scripting.dev.java.net/.

    To use the new script macro:

{{script language="groovy"}}
  println "Hello World"
{{/script}}
or you can use the groovy shortcut:
{{groovy}}
  println "Hello World"
{{/groovy}}
Important bug fixes:
  • The old LDAP authenticator is still used by default in some cases

Known issues

Common Migration notes

If you're running in a multiwiki setup you'll also need to define the property xwiki.store.migration.databases=all to your xwiki.cfg file or explicitly name all databases to be migrated as in xwiki.store.migration.databases=db1,db2,....

You may also want to import the default wiki XAR in order to benefit from improvements listed above.

Always make sure you compare your xwiki.cfg file with the newest version since some configuration parameters were added. Of note, you should add xwiki.store.migration=1 so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.

Tags:
   

Get Connected