ReleaseNotesXWikiEnterprise20M3

Version 11.1 by Thomas Mortagne on 2009/08/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.ReleaseNotesXWikiEnterprise20M3]. 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 2.0 Milestone 3

Second milestone of the XWiki Enterprise 2.0 version (Roadmap).

New and Noteworthy (since XWiki Enterprise 2.0 Milestone 2)

At a glance (see below for details):

  • Lots of improvements and new features in the new WYSIWYG editor
  • Lots of improvements and bugfixes in the rendering engine and the syntax converter
  • Smaller XHTML output
  • Upgrade to SmartGWT 1.2
  • New footnote macro
  • New experimental network event distribution module
  • Macros can expose nicer human readable names
  • It's now possible to add renderers easily
  • New plain text parser

Smaller XHTML output

We introduced a light XHTML renderer which avoid having all extra datas needed by the WYSIWYG. You will not get any weird XHTML comment anymore in the rendered page.

Footnote macro

See Footnote macro documentation.

Remote Observation Manager

It's now possible to make different instances of XWiki or other programs shares events.

The main use cases for this are:

  • clustering
  • external monitoring of XWiki

This release include documents events support for code using new Observation Manager and remote events support in document cache so that's it's possible to do basic clustering already. The old code using old notification system will be upgraded during the RC process before the final 2.0 version and support will be added for other types of events. Note that Remote Observation Manager already support any kind of fully Serializable events.

Nicer macro names

WYSIWYG does not expose macro identifier anymore but human readable names provided by the different macros.

Renderers are now real components

The same way it's possible to add any parser it's not possible to add any renderer for a specific output simply by registering it as a component.

See RenderingModule.

New plain text parser

Plain text parser make possible to put in a page some plain text to render it exactly as it. The syntax name of plain text renderer is plain/1.0, you can enable it in xwiki.cfg.

Important bugs fixed

  • XWIKI-4140 - Wiki macros are evaluating programming rights on wrong (local) documents when executed in virtual wikis
  • XWIKI-4114 - Not possible to put content in info, warning and error macro from the WYSIWYG

Known issues

Backward Compatibility and Migration Notes

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

API Breakages

The following APIs were modified since XWiki Enterprise 2.0M2:

  • Rendering Module
    • Macro have to provide a human readable name in various AbstractMacro helpers constructors
    • Big refactor around renderers and the way to use them since they are real components now
    • Details:\

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected