Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:ReleaseNotes.ReleaseNotesXWikiEnterprise14M2]. 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.4 Milestone 2

Second milestone of the XWiki Enterprise 1.4 version.

Note that general goals for XWiki Enterprise 1.4 are:

  • Switch to Java 1.5
  • Improved stats performances
  • XMLRPC improvements
  • Improved performances (less Javascript files, more optimized CSS, better caching, etc)
  • Skins extensions
  • Bug fixes
  • More automated tests

Summary of changes since XWiki Enterprise 1.4 Milestone 1

Main changes:

  • New colors for the toucan skin : black and dark blue
  • New option to deactivate attachment versioning
  • New http://dev.xwiki.org/xwiki/bin/view/Design/SkinExtensions
  • Improved statistics performances
  • Print and Print Preview now print the whole content of a document
  • User creation from the administration lightbox is working fine now
  • Fixed character escaping using \

+ lots of other changes, see Platform details.

Known issues

Common Migration notes

The database structure has been changed but we have set up an automatic migration system so you shouldn't have to touch your Database to upgrade to 1.4M2. Thus you can simply install this version and configure it to point to your existing database. 

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:
Created by Jean-Vincent Drean on 2008/04/28
   

Get Connected