ContentsThe [toc] macro is a standalone macro and it cannot be used inline. Click on this message for details.

Release Notes for XWiki Enterprise 1.8

The focus on 1.8 branch was on making the new rendering architecture and the new GWT based WYSIWYG able to fully replace the "old" rendering and TinyMCE based WYSIWYG. This version introduce conditional loading of JavaScript and StyleSheet 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. See Applications migration section for more details

Changes since XWiki Enterprise 1.7

1. First usable version of new rendering and new WYSIWYG editor

  • Add ability to configure xwiki to use the XWiki Syntax 2.0 as default when creating new pages
  • First usable version of the new GWT WYSIWYG editor
  • Upgrade to groovy 1.6.
  • new "useravatar" macro for 2.0 syntax
  • new "rss" macro for 2.0 syntax
  • Added wiki syntax for embedded documents
  • Syntax API to convert a document from one syntax to another + new converter from XWiki Syntax 1.0 to XWiki Syntax 2.0. You can try it by changing the syntax identifier of a page.
  • Many bug fixes and improvements in the new GWT WYSIWYG editor
  • Many bug fixes and improvements in the new XWiki 2.0 syntax rendering

2. Usability Improvements

  • New Wiki Dashboard on the home page:
    • Spaces: all the spaces within your wiki (technical spaces are hidden):
      • Links to the list of pages within each spaces.
      • Links to the administration of each space.
      • Allows to create new spaces.
    • Tags: all the tags in the wiki under the form of a tag cloud.
    • Recent changes: all the recent modifications in the wiki, grouped by author and by date.

      * New way of displaying tags, with 2 new features:
    • Tag rename.
    • Tag delete.

      * Page loading time reduced by 30%. Statistics on Sandbox.WebHome, without client-side file caching (most of the downloaded files are cached on the client after the first request):{table}
  • | XE 1.8M1 | XE 1.8M2

    Requests number | 37 | 25 Total size | 332Ko | 200Ko Download @ T1 (seconds) | 9.16 | 6.06 {table}

  • Improved information section in document footer, including document children:

3. Authentication

  • Improved authentication performance for LDAP. By default the authentication system now calls the authenticator only once by session, this means it does not call the LDAP authenticator and does not generate queries on the LDAP server for each request anymore. This can be changed using the

4. Translations

  • New or improved translations:
    • french
    • german
    • spanish

5. Important bugs fixed

  • Scaled images in exported PDF and RTF have wrong dimensions
  • When a wiki is removed, it's not removed form the cache
  • Including a document with first or second heading level breaks the including document section edit link
  • PDF export does not take into account the encoding specified in xwiki.cfg

6. Others

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.

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
Tags:
   

Get Connected