Show last authors
1 #startfloatingbox()
2 *Contents*
3 #toc ("2" "3" "")
4 #endfloatingbox()
6 1 Release Notes for XWiki Enterprise 1.6
8 Our development team has been working quite hard for the past 2 months on bringing a number of improvements to our flagship product [XWiki Enterprise>enterprise:Main.WebHome]. The focus for the 1.6 release was on having beta versions of new rendering and new WYSIWYG editor, improving the stability and performance.
10 We closed more than 150 [JIRA>] issues during the release timespan.
12 1.1 Changes since XWiki Enterprise 1.5.x
14 1.1.1 1. Beta version of new rendering and new WYSIWYG editor
16 * New experimental support for other syntaxes (Confluence, JSPWiki, Creole, MediaWiki, TWiki and XHTML), including a new [XWiki Syntax v2.0>platform:Main.XWikiSyntax].#info("You'll find information on how to enter content using the new syntaxes in the [Page Editing Guide>platform:Features.PageEditing].")
18 ~~Users can choose the syntax they want to use to edit their wiki pages :~~<br />
19 <img style="border: 1px solid #000;" src="$doc.getAttachmentURL('syntax.png')" /><br />
21 * New experimental WYSIWYG editor (Work In Progress).
23 #info("The look & feel is not the final one. Please look at the [new WYSIWYG Design page>dev:Design.NewWysiwygEditorInterface] 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>platform:Features.PageEditing]. Again this is work in progress but we'd like *as much feedback as possible*. Please raise any issue you find in [JIRA>].")
25 ~~XWiki's new WYSIWYG editor :~~<br />
26 <img style="border: 1px solid #000;" src="$doc.getAttachmentURL('wysiwyg.png')" /><br />
28 1.1.1 2. Usability Improvements
30 * XWiki Enterprise's User Interface was improved through *the refactoring of page footers :* they now provide a quick access to page comments, attachments and history. They also add a new document information tab that lists the page backlinks and let users edit page tags easily.
32 ~~The new footer is available at the bottom of every wiki page page :~~<br />
33 <img style="border: 1px solid #000;" src="$doc.getAttachmentURL('XEFooter.png')" /><br />
35 ~~The footer features a brand new document information tab :~~<br />
36 <img style="border: 1px solid #000;" src="$doc.getAttachmentURL('XEInfo.png')" /><br />
38 * The much-needed *password recovery feature is now available :* now, an user who has fogotten his password can simply click on a link available on the login page in order to have a password recovery email sent to him. Similarly, an user who forgot her username can provide her email address and have her username sent back to her.
40 ~~Users can retrieve their passwords by clicking on the relevant link on the login page :~~<br />
41 <img style="border: 1px solid #000;" src="$doc.getAttachmentURL('PasswordReset.png')" /><br />
43 * The [Rights Management interface>platform:Features.RightsManagement] now supports adding groups into groups
45 1.1.1 3. Platform Improvements
47 * Default account validation & confirmation emails provided in the wiki preferences
48 * Added .xml extensions to all exported wiki pages (XAR)
49 * The generated HTML for wiki titles now start at h1 instead of h2
50 * The name of the main database in virtual wiki mode is not hardcoded to 'xwiki' anymore, and in virtual mode all database names can be prefixed with a configurable value
51 * 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:
52 ** Ability to use positional parameters in Query (only named parameters supported earlier).
53 ** Ability to add a new Query Language easily simply by adding a JAR to the Classpath.
54 * New experimental XWiki Query Language called XWQL. #info("More about the language in the [Query Module documentation>extensions:Extension.Query Module]. 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 <tt>$</tt> methods in XE 1.7. The XWQL language is accessible via the Query Manager. Example: <tt>\$'from doc.object(XWiki.XWikiUsers) as user', 'xwql').execute()</tt>.")
56 1.1.1 4. Translations
58 * New or improved translations:
59 ** german
60 ** french
61 ** czech
62 ** norwegian
63 ** ukrainian
65 1.1.1 5. LDAP
67 * Use of "." in LDAP logins fixed
69 1.1.1 6. Important bugs fixed
71 * Various fixes in the watchlist:
72 ** Watchlist now works with platform 1.5 and 1.6
73 ** Fixed rights checks in multiwiki mode
74 ** Fixed RSS feed generation in multiwiki
75 * In some context URLFactory generate URL with wrong server/domain
77 1.1.1 7. Others
79 * XWIKI-2623 - Update MSSQL hibernate mapping file and ship it with xwiki distributions
80 * XE-300 - The treeview should sort spaces by their name
81 * XWIKI-2573 - viewrev action fails with ugly stacktrace for documents with attachments when no revision number is requested
82 * XWIKI-2649 - xwiki.authentication.ldap.mode_group_sync is not "always" by default
83 * XE-244 - Upgrade IzPack installer to version 4.0.1
85 1.1 Known issues
87 * [Bugs we know about>]
89 1.1 Common Migration notes
91 #warning("If you're running in a multiwiki setup you'll also need to define the property <tt></tt> to your <tt>xwiki.cfg</tt> file or explicitely name all databases to be migrated as in <tt>,db2,...</tt>.")
93 You may also want to import the [default wiki XAR>Main.Download] in order to benefit from improvements listed above. Make sure you read the [XWiki upgrade guide>platform:AdminGuide.Installation#HUpgradinganXWikiInstallation] before importing the new XAR since it can cause an overwrite of changes you made to some pages.
95 #warning("Always make sure you compare your <tt>xwiki.cfg</tt> file with the newest version since some configuration parameters were added. Of note, you should add <tt></tt> 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