ReleaseNotesXWikiEnterprise15M2

Version 2.1 by Jean-Vincent Drean on 2008/06/25
Warning: For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:ReleaseNotes.ReleaseNotesXWikiEnterprise15M2]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.

Release Notes for XWiki Enterprise 1.5 Milestone 2

Last milestone of the XWiki Enterprise 1.5 version (Roadmap). 

Summary of changes since XWiki Enterprise 1.5 Milestone 1

Main changes:

  • [Experimental] New ability to set the wiki syntax used in a page (Confluence,MediaWiki,TWiki,JSPWiki,Creole), thanks to the new Rendering Engine
  • Brand new Administration Application (see http://tinyurl.com/4qym7w)
  • Universal Edit button support (see http://universaleditbutton.org/)
  • Reduced execution time of Selenium tests (from 12-15 minutes to 7 minutes)
  • An administrator can modify a user profile or password when visiting a user profile page
  • The copy page feature is now available from the top menu (Actions > Copy)
  • XWiki properties names are now translatable
  • new renamePage method in the XML-RPC API
  • Slightly modified header
  • New Croatian translation

+ lots of other changes, see Platform details.

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 explicitely 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