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

Summary of changes since XWiki Enterprise 1.6

Main changes:
  • New XWiki Syntax 2.0 (xwiki/2.0) :
    • Allow wiki syntax inside links.
    • New syntax for tables.
    • Images can be defined as URLs.
    • New Code macro (experimental).

      You'll find information on how to enter content using the new syntaxes in the Page Editing Guide.

  • New WYSIWYG 2.0 (Alpha version) :
    • Link feature implemented (link to wiki page, web page, email).
    • Lots of bug fixes.

      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 start using the new editor, check out the Page Editing Guide. Again this is work in progress but we'd like as much feedback as possible. Please raise any issue you find in JIRA.

  • New script macro (xwiki/2.0): The new script macros add the ability to use any scripting language supporting JSR-223. For now the default XWiki distribution comes with only a groovy 1.6 support but it easy to add support for other language (like ruby, python, etc.) simply by adding the corresponding engine and implementation. See https://scripting.dev.java.net/.

    To use the new script macro:

{{script language="groovy"}}
  println "Hello World"
{{/script}}
or you can use the groovy shortcut:
{{groovy}}
  println "Hello World"
{{/groovy}}
  • New Box macro (xwiki/2.0), this macro allow to put content in a visual container.

    Usage :

{{box}}
==some==
* wiki
* content
{{/box}}
  • New Code macro (xwiki/2.0), this macro highlight it's content. Only support html, xml and php yet. See Code Macro.

    Usage:

{{code language=xml}}
<hello>
 <world>Cool!</world>
</hello>
{{/code}}
  • Multiwiki (a.k.a farm mode or virtual mode) is now available without using subdomains for wikis. Note that this option is available from xwiki.cfg and not enabled by default. Example of URLs (the "/wiki/" part is configurable) :
http://mydomain.com/xwiki/wiki/mywiki1/view/Main/WebHome
http://mydomain.com/xwiki/wiki/mywiki2/view/Main/WebHome
  • Webdav support : XWiki now expose a webdav server interface. This means you can now access/edit/delete page sources and attachments from any webdav client.
  • Groovy upgrade : The groovy engine has been upgraded to the last 1.6 beta version. You can now use all the new features of groovy as well as speed improvements and bugfixes from groovy 1.0 to 1.6 beta 2. See http://groovy.codehaus.org/ for more information.
  • New Attachment view in the Index : you can now see all the attachments of the wiki in the index, under the "Attachment" tab.
  • Reorganized, documented and enhanced * Added a ROOT webapp to the standalone distribution.

    Important bug fixes:

  • Saving a blank wiki page throws exception in Oracle
  • Registration is still possible when right to register for Unregistered user is explicit set to deny
  • Documents with name with spaces or other special chars can't properly save added image in WYSIWYG editor
  • Support of dots in ldap login has introduce a security hole
  • SMTP server address is not re-read when it's changed in global preferences
  • Watchlist update sent by email does not contain the full path to a changed attachment
  • Wrong user name is inserted in group during LDAP membership synchronisation

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.

Tags:
   

Get Connected