If you are migrating from an earlier version than 4.0, and your database contains statistics collected using a version earlier than 2.2, you will probably encounter an issue during our automated database migration. To avoid that issue, you will need to clean up your statistics by executing some SQL commands described in issue XWIKI-8129. Be sure to apply these before attempting the migration. If your are in doubt, apply it, these could not hurt. If you don't, you will face duplicate IDs errors during the migration process, and it will fail, preventing you to run your wiki.
If you are upgrading to this version from an older version which uses Lucene 3.x, you have to manually delete the lucene directory in the xwiki data directory. For example, that could cause Lucene to loop endlessly while trying to index pages, among other things. This is caused by  the Lucene migration to 4.0 (see XWIKI-8404).

This is the release notes for XWiki Platform, XWiki Enterprise and XWiki Enterprise Manager. They share the same release notes as they are released together and have the same version.

New and Noteworthy (since XWiki 4.5)

Full list of issues fixed and Dashboard for 4.5.1.

Extension Manager improvements

We added more information to the Description section and we added the ability to retrieve the list of stable versions that are available in the configured extension repositories.

EM-extensionDescription.png

We also grouped the action buttons (e.g. Install and Install of farm) as you can see in the image above. This allowed us to move the Apply button that you had to click to confirm an extension action like install from the bottom of the Progress section to the extension actions section. The Install and Install of farm buttons are still available in the drop down menu to allow you recompute the install plan if you want to.

EM-continueInstall.png

See the Extension Manager Application documentation for more information.

Distribution Wizard improvements

We fixed an important bug in Distribution Wizard (Closed XWIKI-8749) that was preventing you from properly upgrading the installed extensions in the second step. We now list extensions by the namespace (wiki) where they have been installed. For now you have to review and upgrade each extension individually. We hope to improve this soon by allowing you upgrade more extensions at once.

DW-upgradeExtensions.png

Full Issue List

Failed to execute the [jira] macro. Cause: [Server returned HTTP response code: 400 for URL: https://jira.xwiki.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=Project+in+%28%22XWiki+Commons%22%2C+%22XWiki+Rendering%22%2C+%22XWiki+Platform%22%2C+%22XWiki+Enterprise%22%2C+%22XWiki+Enterprise+Manager%22%29+and+fixVersion+in+%28%224.5.1%22%29+and+resolution+in+%28%22Fixed%22%29+and+component+not+in+%28%22Build%2C+Infrastructure+and+Tests%22%29]. Click on this message for details.

For Developers

Button Group Widget

We added a small widget to group form buttons.

buttonGroup.png

It can be used either with a static list of buttons, when you know beforehand that you have more than 1 button and you know the main one, or with a dynamic list of buttons, if you want the buttons to be grouped on the client side if there are more than one.

The static button group works even with JavaScript disabled (in a modern browser):

<p class="buttons">
  <span class="buttonwrapper button-group">
    <button>Action</button><a href="#foo" class="dropdown-toggle" tabindex="0"><span/></a>
    <span id="foo" class="dropdown-menu">
      <button>First item</button>
      <input type="submit" value="Second item" class="button" />
      <a href="#third">Third item</a>
    </span>
  </span>
</p>

The dynamic group obviously requires JavaScript. The first button found in the group is considered the main one. The buttons are grouped only if there are more than one. If the main button is secondary then the button group is styled as a secondary button.

<span class="dynamic-button-group">
  <span class="buttonwrapper">
    <button>One</button>
  </span>
  <span class="buttonwrapper">
    <input type="submit" class="button secondary" value="Two" />
  </span>
  <span class="buttonwrapper">
    <a href="#three" class="secondary">Three</a>
  </span>
</span>

In both cases you need to include the widget resources:

#set ($discard = $xwiki.ssfx.use('uicomponents/widgets/buttonGroup.css', true))
#set ($discard = $xwiki.jsfx.use('uicomponents/widgets/buttonGroup.js'))

Translations

The following translations have been updated: 

  • French

Tested Browsers & Databases

Here's the list of browsers we support and how they've been tested specifically for this release:

BrowserTestedDetails
Chrome30.pngGoogle Chrome 25Not Tested
Firefox30.pngMozilla Firefox 19FullyManual Test Report for XWiki 4.5.1
IE30.pngInternet Explorer 8PartiallyTested the WYSIWYG Editor
IE30.pngInternet Explorer 9PartiallyTested the WYSIWYG Editor

Here's the list of databases we support and how they've been tested specifically for this release:

DatabaseTestedDetails
hypersql.pngHyperSQL 2.2.9FullyManual Test Report for XWiki 4.5.1
mysql.pngMySQL 5.5.29PartiallyTested the Distribution Wizard and the migration from 3.5.1 to this version using the Distribution Wizard
oracle.pngOracle 11.2PartiallyTested the Distribution Wizard and the migration from 3.5.1 to this version using the Distribution Wizard
postgresql.pngPostgreSQL 9.1.3PartiallyTested XE and migration from 3.5.1 to this version

Known issues

Backward Compatibility and Migration Notes

General Notes

PLEASE, BACKUP YOUR DATABASE BEFORE STARTING YOUR WIKI.
AUTOMATED MIGRATION PROCEDURE TAKE PLACE AT STARTUP AND YOU MAY NEED TO START OVER IF YOU ENCOUNTER AN UNEXPECTED ISSUE.

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.
If you are migrating from an earlier version than 4.0, and your database contains statistics collected using a version earlier than 2.2, you will probably encounter an issue during our automated database migration. To avoid that issue, you will need to clean up your statistics by executing some SQL commands described in issue XWIKI-8129. Be sure to apply these before attempting the migration. If your are in doubt, apply it, these could not hurt. If you don't, you will face duplicate IDs errors during the migration process, and it will fail, preventing you to run your wiki.
If you have encountered an issue with the migration, you may need to start over from a backup. Be careful that during the migration, two new tables have been created (in each xwiki database for a farm) and should be dropped when you restore a backup of a database coming from a version earlier than 4.x. These two tables are DATABASECHANGELOG and DATABASECHANGELOGLOCK. These should only be removed if you restore a pre-4.x database schema. Mixing an old database with these two tables will surely cause issue during schema updates (liquibase checksum failure).

API Breakages

No API breakage since XWiki 4.5.

Tags:
Created by Vincent Massol on 2013/02/25
   

Get Connected