Sakai CLE 2.9 release notes new properties and permissions

# Force the use of the legacy html content processor (used in versions before and including 2.9),
# if this is not overridden then the antisamy html cleaner will be used
# Default: false (use AntiSamy)
#content.cleaner.use.legacy.html=true

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

# Force the user of a lower security profile for content processing and scanning,
# if this is not overridden then high security settings are used.
# The standard high and low files are located in "kernel/sakai-kernel-impl/src/main/resources/antisamy/"
# Override the standard files by placing your own files in:
# ${sakai.home}/antisamy/high-security-policy.xml
# ${sakai.home}/antisamy/low-security-policy.xml
# NOTE: only works if AntiSamy is enabled (see content.cleaner.use.legacy.html)
# Default: false (use high security - no unsafe embeds or objects)
#content.cleaner.default.low.security=true

searchServer@org.sakaiproject.search.api.SearchService

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Controls access to the Admin page within search.
This should only be activated on the actual search server node and all other nodes should have this turned off to restrict access.

Allows an instructor or any user with assignments management permissions to submit the assignment on behalf of a student who has no submission yet (via the View Assignment list by student)

2.9.0

Configuration

config.dereference.on.load.initial

true

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

# ######################################################################## 
# CONFIGURATION 
# ######################################################################## 

... 

# Control the dereferencing of configuration values on initial load 
# (values are always dereferenced but this affects whether they are done on config load or not) 
# Dereferencing values means that all values like "${property.name}" are replaced 
# with the value from the config item of that name (unmatched ones are left as is) 
# Default: true (dereference all values loaded from the config properties files) 
#config.dereference.on.load.initial=false 
# Default: false (do not dereference all values including those loaded from other sources - e.g. database) 
#config.dereference.on.load.all=true

Example:

turnitin.repository.setting.count=2
   turnitin.repository.setting.1=0
   turnitin.repository.setting.2=1

Option appears in GUI to check paper against Journals.

userid=Student ID
usereid=Student unique ID
useremail= Student Email
username= Student Name
sortname= Student Name
coursegrades= Course Grade
gradeitem= Grade Item
siteid= Site ID
sitetitle= Site Title

#Uncomment this to use the built in URL randomiser/shortener (recommended) #shortenedurl.implementation=org.sakaiproject.shortenedurl.api.RandomisedUrlService

Unable to locate Jira server for this macro. It may be due to Application Link configuration. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

shortenedurl.implementation

shortenedurl.implementation.bitly.login

shortenedurl.implementation.bitly.key

# ########################################################################
# Shortened URLs
# ######################################################################## # https://confluence.sakaiproject.org/display/SHRTURL
# Note: short URLs are disabled by default
## RANDOMISED
# Uncomment this to use the built in URL randomiser/shortener (recommended) #shortenedurl.implementation=org.sakaiproject.shortenedurl.api.RandomisedUrlService

## BIT.LY
# Uncomment this to use the bit.ly URL shortner
#shortenedurl.implementation=org.sakaiproject.shortenedurl.api.BitlyUrlService
# You must also have a bitly account. So signup, navigate to http://bit.ly/a/your_api_key,
# retrieve your details, uncomment and set the following:
#shortenedurl.implementation.bitly.login=johnsmith
#shortenedurl.implementation.bitly.key=123qwe456asd789zxc

## EXTERNAL URL SHORTENING
# By default, external URLs (ie a URL for another site) cannot be shortened using the /direct/url entity provider
# You can change this by setting the following to true.
#shortenedurl.external.enabled=false

new sakai.properties:
================

#For each worksitesetup.sort.key property that is specified, the associated worksitesetup.sort.order property must also be specified

#The following are all comma separated values. If these properties are not present, the drop-downs will be sorted as they were sorted before (on eid, then title).
#The key on which the sessions are sorted. Possible values are authority, description, eid, endDate, startDate, title
worksitesetup.sort.key.session=

#The key on which the courseSets are sorted. Possible values are authority, category, description, eid, parent, title
worksitesetup.sort.key.courseSet=

#The key on which the courseOfferings are sorted. Possible values are academicSession, authority, canonicalCourseEid, courseSetEids, description, eid, endDate, startDate, status, title
worksitesetup.sort.key.courseOffering=

#The key on which the sections are sorted. Possible values are authority, category, courseOfferingEid, description, eid, enrollmentSet, maxSize, meetings, parent, title
worksitesetup.sort.key.section=

#The following are all comma separated lists of sorting orders that correspond to the above keys. They have values of 'asc' or 'desc' for ascending/descending
#The order on which the sessions are sorted
worksitesetup.sort.order.session=

#The order on which the courseSets are sorted
worksitesetup.sort.order.courseSet=

#The order on which the courseOfferings are sorted
worksitesetup.sort.order.courseOfferings=

#The order on which the sections are sorted
worksitesetup.sort.order.section=

# Controls the portal chat feature
# portal.neochat=false

# Controls whether or not an individual user's profile image will appear in the portal chat
# portal.neoavatar=true

timeoutDialogEnabled=true

timeoutDialogWarningSeconds=600

Allows for finer control over the way user lookups occur in Entity Broker user endpoint. The current implementation is preserved by default but this property will adjust it to never attempt an ID lookup unless it was requested explicitly (using "id=" as the prefix for the id).

"user.explicit.id.only=true"

Set this to true to disable id/eid failover checks (this means lookups will only attempt to use id or eid as per the exact params which are passed or as per the endpoint API)

In other words, the user id must be prefixed with "id=", otherwise it will be treated like an eid.

This contributed code improves performance by pre-caching Sakai users. So the full improvement of user caching does not require waiting for a second user interaction. This user pre-caching is done optionally on servlet container (Tomcat) restart and is also done optionally according to a configurable daily schedule.

used the raw redirecting code in

RequestFilter.java. The end result is pretty simple, and you can

actually host it on just 1 app node if you have multiple domain names

pointing to it from Apache [1].

msgcntr.forums.showProfileInfo

*also requires profile2.profile.link.enabled=true

2.9.0

Site Stats

sitestats.admin.view

Admin access to statistics across all sites. Change for this setting?