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

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: JIRA Issue macro params updated with additional server info

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 (
Jira
SAK-6545
SAK-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
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:

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-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.