Version 8.1 by Vincent Massol on 2008/09/12
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.ReleaseNotesXWikiEnterprise16M2]. 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.6 Milestone 2

Last milestone of the XWiki Enterprise 1.6 version before the release candidates (Roadmap). The 2 main features of this release are the new rendering/new syntax and the new WYSIWYG editor (both in alpha versions).

Summary of changes since XWiki Enterprise 1.6 Milestone 2

Main changes:

  • New experimental support for other syntaxes (Confluence, JSPWiki, Creole, MediaWiki, TWiki and XHTML), including a new XWiki Syntax v2.0 (work in progress, see XWiki Syntax 2.0 Draft).To start entering page content using the new syntaxes, you must be logged with admin rights, go to the page you wish to edit and change the Syntax for the page to the one you wish to use. Note that all syntaxes except the XWiki 1.0 and XWiki 2.0 ones have important limitations (like links not working).
  • New experimental WYSIWYG editor (Work In Progress)The look & feel is not the final one. Please look at the new WYSIWYG Design page to see what it'll look like (except for the colors which will be different). To activate the new editor you must be logged with admin rights, go to the page you wish to edit, change the Syntax of the page to XWiki 2.0 (right panel in edit mode), save. From then on when you edit with the WYSIWYG editor you'll be using the new editor. For some details about the new syntax please see the XWiki Syntax 2.0 Draft. Again this is work in progress but we'd like as much feedback as possible. Known issues with the editor:- Heading doesn't work in IE6/7.- Nested lists does not work.- Switching from any heading level to normal leaves the id that was previously associated with that heading.- Editing in wiki mode and then switching to wysiwyg may determine an unexpected behavior from the wysiwyg (like being unable to un-bold the text).
  • Improvement of Query Manager which was introduced in 1.6M1. The purpose of the Query Manager is to allow using multiple Query Languages and manage them (HQL is one such language). The changes are:
    • Ability to use positional parameters in Query (only named parameters supported earlier).
    • Ability to add a new Query Language easily simply by adding a JAR to the Classpath.
  • New experimental XWiki Query Language called XWQL. More about the language in XWQL design page. The Main syntax and a translator to HQL are implemented. It currently requires programming rights to use in scripts. The current XWQL syntax is not the final one. We'd like some feedback to improve it. The language will fully replace current $ methods in XE 1.7. The XWQL language is accessible via the Query Manager. Example: $'from doc.object(XWiki.XWikiUsers) as user', 'xwql').execute().

Other changes:

  • XWIKI-2623 - Update MSSQL hibernate mapping file and ship it with xwiki distributions
  • XE-300 - The treeview should sort spaces by their name 
  • XWIKI-2573 - viewrev action fails with ugly stacktrace for documents with attachments when no revision number is requested
  • XWIKI-2649 - xwiki.authentication.ldap.mode_group_sync is not "always" by default

Known issues

Common Migration notes

If you're running in a multiwiki setup you'll also need to define the property to your xwiki.cfg file or explicitely name all databases to be migrated as in,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 so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.

Get Connected