Version 20.3 by Vincent Massol on 2010/12/15
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.ReleaseNotesXWikiEnterprise18]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.

Known issues

We've discovered that the Office Importer doesn't work on Windows in some cases because of an invalid character in filename issue. We're still analysing the problem but it could be happening when using a multi wiki setup. This will be fixed in XE 1.8.1 ASAP.

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.

Applications migration

XE 1.8M2 has introduced conditional loading of JavaScript and StyleSheet files in order for pages to load faster, sending to the browser only the files it needs to display the requested pages. This might break existing applications developed on top of XWiki that relied on such JavaScript and CSS files being present all the time. Concerned files and libraries are the following:

  • scriptaculous files
  • accordions files
  • chart wizard files
  • usersandgroups.js and usersandgroups.css
  • livetable.js and livetable.css
  • lightbox.js
  • tablefilterNsort.js and table.css
  • fullscreenEdit.js and fullscreenEdit.css

If you have applications that relies on one or several of these libraries, you will need to explicitly make them request the desired files using the Skin Extension plugin. For example, if your application needs the live-table feature (the dynamic AJAX grid), add the following lines to the code page that requires it:

$xwiki.jsfx.use('js/xwiki/table/livetable.js') ## Inject livetable.js <script> tag in the header
$xwiki.ssfx.use('js/xwiki/table/livetable.css') ## Inject livetable.css <link> tag in the header

Get Connected