Child pages
  • Migration - sakai.properties changes (2.x)

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

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:(warning)

New preference.pages property (
Jira
SAK-

...

6545
SAK-

...

Old Name (Sakai 2.4 and earlier)

New Name (Sakai 2.5.0 and later)

invalidEmailInIdAccountString

invalidNonOfficialAccountString

noEmailInIdAccountName

officialAccountName

noEmailInIdAccountLabel

officialAccountLabel

emailInIdAccountName

nonOfficialAccountName

emailInIdAccountLabel

nonOfficialAccountLabel

emailInIdAccount.url

nonOfficialAccount.url

emailInIdAccountInstru

nonOfficialAccountInstru

noEmailInIdAccountValue

officialAccountValue

emailInIdAccountValue

nonOfficialAccountValue

...

6545
)

This property controls page order and visibility in the Preferences tool. The property takes comma-separated list of values identifying the pages (and toolbar actions) to display. Available pages are Notifications, Customize Tabs, Time Zone and Language. Below is an example of prefences.pages setting:

No Format

preference.pages=prefs_tab_title, prefs_noti_title, prefs_timezone_title, prefs_lang_title

The order of values in the comma-separated list determines page order and also the order of actions in the toolbar. If a value is missing, that page's action will not appear in the toolbar and the page will not be reachable via the UI. If the preference.pages property is not set, page order will be the (current) default.

If you remove

No Format

enable.privacy.status = true

you can achieve a similar effect by defining preferences.pages as follows:

No Format

preference.pages=prefs_tab_title, prefs_noti_title, prefs_timezone_title, prefs_lang_title, prefs_privacy_title

WebDAV properties changes
Jira
SAK-13403
SAK-13403

: The properties associated with the WebDAV authentication cache have changed. In Sakai 2.5.0 and earlier the following properties were used:

...

Code Block
maxElementsInMemory@org.sakaiproject.user.api.AuthenticationManager.cache
timeToLive@org.sakaiproject.user.api.AuthenticationManager.cache

...

Worksite Setup/Site Info properties changes (pre-2.5 to 2.6 upgrade) (
Jira
SAK-

...

10762
SAK-

...

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 "Notes in SAKAI_PERSON_T table" thread discussion for more information.

MySQL

No Format

--- reference/trunk/docs/conversion/sakai_2_1_2-2_2_0_mysql_conversion.sql	2007/01/17 18:57:13	20392
+++ reference/trunk/docs/conversion/sakai_2_1_2-2_2_0_mysql_conversion.sql	2007/01/17 19:10:09	20393
@@ -2237,3 +2237,9 @@
 ----------------------------------------------------------------------------------------------------------------------------------------

 ALTER TABLE SAKAI_SESSION CHANGE SESSION_IP SESSION_IP VARCHAR (128);
+
+----------------------------------------------------------------------------------------------------------------------------------------
+-- Increase the field size for the NOTES field in the SAKAI_PERSON_T table
+----------------------------------------------------------------------------------------------------------------------------------------
+
+ALTER TABLE SAKAI_PERSON_T CHANGE NOTES NOTES varchar(4000);

Oracle

...

10762
)

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)

invalidEmailInIdAccountString

invalidNonOfficialAccountString

noEmailInIdAccountName

officialAccountName

noEmailInIdAccountLabel

officialAccountLabel

emailInIdAccountName

nonOfficialAccountName

emailInIdAccountLabel

nonOfficialAccountLabel

emailInIdAccount.url

nonOfficialAccount.url

emailInIdAccountInstru

nonOfficialAccountInstru

noEmailInIdAccountValue

officialAccountValue

emailInIdAccountValue

nonOfficialAccountValue

Portfolios (OSP) permission settings (pre-2.5 to 2.6 upgrade) (
Jira
SAK-13205
SAK-13205
)

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 osp.upgrade25=true in your sakai.properties file. (See also discussion.)

Portfolios (OSP) reports property changes (pre-2.5 to 2.6 upgrade) (
Jira
SAK-10451
SAK-10451
)

Those upgrading from a pre-2.5.0 version of Sakai need to change osp.reports.useWarehouse to sakai.reports.useWarehouse.