4.1 is not released yet, this is a work in progress

This is the second release of the 4.x cycle (Roadmap). This release brings TODO

New and Noteworthy (since XWiki Enterprise 4.0 version)

Here are notable new features and improvements. For the full list of issues (including statistics) see the JIRA Dashboard.

Improvements to the Extension Manager

The speed and reliability of the Extension Repository has been improved considerably. For example the XWiki.org Extension Repository is now much faster when you access it from XWiki Enterprise and you should now be able to browse and install extensions in no time.

Upgrading applications with related configuration documents is now handled using the merge conflict resolution UI. Changes are displayed as if you were comparing versions from a document's history.

EM-mergeConflict.png

If extension installation fails, the error message is extracted from the logs and displayed. You can view the full stack trace by clicking on the error message.

(in the image below the job of computing the install plan fails) 

EM-extensionLog.png

The install and uninstall plans display extensions like in the dependency section. This way you can follow the link of an extension to find out more about what is going to be installed.

EM-uninstallPlan.png

The install and uninstall process is now completely asynchronous. You can see below how the progress is indicated.

EM-asyncInstall.png

See the Extension Manager Application documentation for more details.

Hide technical documents from non-technical users

  • Users who do not opt to see hidden documents do not see them on panels or in search results.
  • For advanced users, it is now possible to specify that a document should be hidden when editing the document (only wiki or wysiwyg edit modes):

    hidden.png

    And now there's a new setting in the user profiles, letting users choose whether they want hidden documents to appear in search results or not:

    hiddenSettings.png

    • If the user doesn't set explicitly the Hidden setting value in his profile, he won't see hidden documents by default. Thus seeing hidden documents is an explicit choice.

New types of charts

We've added 2 new types of charts, bar3D and line3D, which draw 3D charts.

For example the following code:

{{chart type='bar3D' source='inline' params='range:B2-B9;series:columns'}}
|=Date|=Value
|2012-02-21|1.97
|2012-02-26|2.96
|2012-03-04|3.93
|2012-03-11|4.84
|2012-03-18|5.83
|2012-03-25|4.5
|2012-04-01|3.85
|2012-04-08|4.87
{{/chart}}

Will be rendered as this:

chart-example.png

It's now possible to select custom colors in Chart graphs. For example:

{{chart type="pie" source="inline" params="range:B2-D5;series:columns;colors:C3E3F7,1D9FF5,015891,012A45" title="Chart Test" width="320" height="240"}}
|  |X  |Y  |Z
|Q1|1.2|3.4|1.3
|Q2|4.5|3.4|2.3
|Q3|1.2|4.5|9.0
|Q4|3.4|1.2|1.2
{{/chart}}

Will generate:

customcolors.png

Miscellaneous

For developers

Diff module

A new diff/merge module has been added to make easier to deal with diff and merge both from component and scripts. See Diff module  for details.

Miscellaneous

Bug Fixes

  • XWIKI-7913 Could not register a Javascript or CSS skin extension for the whole wiki.

Upgrades

The following dependencies have been upgraded:

TODO

Tested Browsers

Here's the list of browsers tested with this version (i.e. browsers that we've tested as working - Check the list of supported browsers):

TODO

Tested Databases

TODO

Known issues

Test Report

You can check the manual test report to learn about what was tested and the results on various browsers.

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 in your xwiki.cfg file if you want to explicitly name some databases to be migrated as the default is now to migrate all databases. Database that are not migrated could not be accessed.

You may also want to import the default wiki XAR in order to benefit from all the improvements listed above.

Always make sure you compare your xwiki.cfg and xwiki.properties files with the newest version since some configuration parameters were added. Note that 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 version 4.0:

{{todo/}}
Tags:
Created by Caleb James DeLisle on 2012/06/15
   

Get Connected