Page Comparison

Jira Legacy

	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.6.0 and later)
`invalidEmailInIdAccountString`	`invalidNonOfficialAccountString`
`noEmailInIdAccountName`	`officialAccountName`
`noEmailInIdAccountLabel`	`officialAccountLabel`
`emailInIdAccountName`	`nonOfficialAccountName`
`emailInIdAccountLabel`	`nonOfficialAccountLabel`
`emailInIdAccount.url`	`nonOfficialAccount.url`
`emailInIdAccountInstru`	`nonOfficialAccountInstru`
`noEmailInIdAccountValue`	`officialAccountValue`
`emailInIdAccountValue`	`nonOfficialAccountValue`

Jira Legacy
SAK-13205
SAK-13205
: Upgrade OSP Permissions. If you are upgrading from a pre-2.7.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.)

Jira Legacy

	SAK-13403
	SAK-13403

: The properties associated with the WebDAV authentication cache have changed. In Sakai 2.6.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.6.2 with:

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

Jira Legacy
SAK-10451
SAK-10451
: Those upgrading from a pre-2.6.0 version need to change osp.reports.useWarehouse to sakai.reports.useWarehouse.

...

Versions Compared