Migration - sakai.properties changes (2.x)

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:

New `preference.pages` property ( SAK-6545 - Getting issue details... STATUS )

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:

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

enable.privacy.status = true

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

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

WebDAV properties changes SAK-13403 - Getting 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:

maximumSize@org.sakaiproject.user.impl.AuthenticationCache
timeoutMs@org.sakaiproject.user.impl.AuthenticationCache
failureThrottleTimeoutMs@org.sakaiproject.user.impl.AuthenticationCache

These settings have been replaced as of Sakai 2.5.2 with:

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) ( SAK-10762 - Getting issue details... STATUS )

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) ( SAK-13205 - Getting issue details... STATUS )

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) ( SAK-10451 - Getting issue details... STATUS )

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