Migrating from a previous release
Migration from an earlier version of Sakai typically involves a database conversion (for which scripts are supplied with the release), an update to any custom skins, and possibly changes to any custom code.
For links to the conversion scripts, see the Database Migration section of this guide.
Changes in sakai.properties
In addition to new sakai.properties values introduced for Sakai 2.5, there are also some changes to address when upgrading from a previous version of Sakai:
SAK-10762Getting issue details...
: In Worksite Setup/Site Info the names of properties associated with the ability to add participants via email address have changed:
Old Name (Sakai 2.4 and earlier)
New Name (Sakai 2.5.0 and later)
SAK-13205Getting issue details...
: Upgrade OSP Permissions. If you are upgrading from a pre-2.5.0 version of Sakai, then you need to force conversion of the OSP permissions by setting
sakai.propertiesfile. (See also discussion.)
- - SAK-13403Getting issue details... STATUS : The properties associated with the WebDAV authentication cache have changed. In Sakai 2.5.0 and earlier the following properties were used: These settings have been replaced as of Sakai 2.5.2 with:
SAK-10451Getting issue details...
: Those upgrading from a pre-2.5.0 version need to change
SAKAI_PERSON_T.NOTES field size change
Users who have been running Sakai prior to 19 July 2006 release of Sakai 2.2.0 should check the field size of the SAKAI_PERSON_T "Notes" field. A field size change was added to the 2.1.2 to 2.2.0 conversion script on 17 January 2007. Depending on when deployers executed the 2.1.2->2.2.0 conversion script for the 2.1->2.2 upgrade, this update may have been missed. See the following Jiras as well as the sakai-dev list discussion for more information.
sakai-dev "Notes in SAKAI_PERSON_T table" thread