Assignments - Submission History field for Assignment Submissions has been removed in Sakai 12
Sakai 11 shows a submission history for an assignment. This submission history in the user interface was removed as part of the Sakai 12 assignments tool refactor. A replacement is being explored at - SAK-33701Getting issue details... STATUS
A screenshot showing the submission history in Sakai 11 for instructor view after re-submitting on behalf of the student. This field does not exist in Sakai 12.
A screenshot showing the submission history when the student is view his assignment grades. This field does not exist in Sakai 12.
Assignments - Site Archive is no longer compatible between Sakai 12 and earlier versions of Sakai
Assignments - For Attachment only assignments, student must upload a file. Links are not accepted.
The option "Select files from workspace or site" has been removed for Attachment only assignment types to prevent students from submitting a URL to a mutable document, like a Google doc, which potentially could be altered even after submission and due date have passed.
Bullhorn Notifications - A new feature which is off by default in 12
Bullhorn notifications is off by default in Sakai 12. It is for academic and social notifications. To be turned on by default in the future, some work may be needed to identify the desired behavior, which activities should generate notifications, which should not, and which potentially create double notifications, and then addressing those gaps to have desired default behavior. - SAK-33724Getting issue details... STATUS
Course management SIS Load using CSV files
MathJax - now a site level instead of a tool level setting
MySQL and MariaDB - upgrade to Hibernate resulted in new dialect
Profile tool "wall" disabled by default in Sakai 12
Signup tool properties documented
The properties options have been updated in default.sakai.properties. No new properties have been added, just that existing properties have been documented.
Site Management - Duplicating sites disabled by default due to performance concerns
Syllabus - editing process has changed
Syllabus items can no longer be edited in place. Instead you must use the Bulk Edit UI. There is a request (Jira) to change the name of Bulk Edit to just "Edit" since this is the only option for editing a Syllabus item in Sakai 12. - SAK-33328Getting issue details... STATUS and - SAK-33769Getting issue details... STATUS
Test and Quizzes - Autosubmit in Samigo Tests and Quizzes always includes submission even if only partial
Doesn't affect when take highest score is in effect, but does impact average scoring of submissions or taking the score of the latest submission. There is a JIRA (not yet in 12) to update the text that is displayed to instructors and students, - SAM-3359Getting issue details... STATUS . Related Jiras include - SAM-2729Getting issue details... STATUS and - SAM-3128Getting issue details... STATUS
samigo.email.autoSubmit.errorNotification.enabled=true calendar.external.subscriptions.institutional.cacheentries - NEW property membership.enrolments.blurb Zip download feature Option is not available unless the next properties are configured with a value (in bytes) greater than 0. content.zip.download.maxindividualfilesize content.zip.download.maxtotalsize
Release Tool/Service Property Jira 12.0 Samigo Test and Quizzes samigo.eventlog.ipaddress.enabled
SAM-3016Getting issue details...
12.0 Samigo Test and Quizzes
SAM-2940Getting issue details...
12.0 Resources (Content)
SAK-33672Getting issue details...
12.0 Unused cache properties for calendar
Existing properties but had not been implemented before 12.
SAK-33381Getting issue details...
12.0 Web Services webservices.allow-request
SAK-32728Getting issue details...
12.0 Login ?
SAK-32699Getting issue details...
12.0 Signup tool signup.default.email.selected=all
SAK-32655Getting issue details...
12.0 Site management portal.forceOverviewToTop=false
SAK-32386Getting issue details...
12.0 MySQL/MariaDB driverClassName@javax.sql.BaseDataSource=org.mariadb.jdbc.Driver
SAK-32155Getting issue details...
SAK-32087Getting issue details...
12.0 Portal Bullhorns (notifications) portal.bullhorns.enabled , default false
SAK-30461Getting issue details...
12.0 CK Editor (Rich Text Editor) autosave_delay set in ckeditor.launch.js (not in sakai.properties)
SAK-31712Getting issue details...
12.0 Duplicate Site default of site.setup.allowDuplicateSite set to false. Duplicate site is off by default.
SAK-27908Getting issue details...
12.0 Resources (Content)
SAK-25438Getting issue details...
12.0 Site Titles using Templates site.tool.custom.titles
KNL-1535Getting issue details...
12.0 User Experience - Auto Favorites portal.default.tabs
SAK-32296Getting issue details...
Changing default values of properties
calendar.external.subscriptions.institutional.cacheentries - NEW property
Zip download feature
Option is not available unless the next properties are configured with a value (in bytes) greater than 0.
Recommend storing files on your file system instead of database
Sakai will store the file content in the database as BLOBs by default. Set this value to change it to store the content on the filesystem instead.
The file system root for content hosting's external stored files (default is null, i.e. store them in the db).
# KNL-309 : To enable support for deleted files set this property to some location
# When storing content hosting's body bits in files, an optional set of folders just within the bodyPath -
# to act as volumes to distribute the files among - a comma separate list of folders. If left out, no volumes will be used.
# see the readme file (2.2.7 File Based Content Hosting) for more details
# Set to true to enable the release/retract and hiding of resources in ContentHostingService, Default: true
# Set to true to enable custom sorts within folders in ContentHostingService and the Resources tool
# DEFAULT: true
You might also want to enable the soft deletion feature of Sakai
Soft site deletion.
If enabled, sites that are deleted will be inaccessible to normal users but won't be deleted immediately, in case they need to be recovered.
You also need to set the gracetime value, in days. After this period, the softly deleted sites will be hard deleted. Defaults to 30 days.
There is a Quartz job that must be configured to run periodically (once per day or so) to expunge those sites.
site.soft.deletion=true (default is false)
Lessons management of HTML pages
By default, Lessons uses Content Security Policy headers to restrict what an HTML page can do, when the page is loaded from Sakai.
This is new in 11. In Sakai 10, Lessons would simply open any HTML page specified.
You can restore the Sakai 10 behavior by adding the following to sakai.properties:
The recommended approach for dealing with this security risk is to use Sakai’s content domain support. This causes HTML pages stored in resources to be served from a different hostname than the main Sakai hostname. E.g. if your institution uses sakai.univ.edu, you might use content.sakai.univ.edu for content, resulting in URL such as https://content.sakai.univ.edu/access/content/group …. Using a separate domain prevents web pages from executing with your Sakai privileges. Thus if you are using a separate content domain, Lessons does not add the Content Security Policy headers.
Note that it is up to the browser to enforce Content Security Policy. Safari, Chrome, and Edge do. Firefox does not. Thus Firefox users are still at risk when opening HTML pages in Lessons. I believe IE 10 and 11 also support it.
Sakai skins using Morpheus
Documentation is stored with Sakai on Github
Sakai 11 changes the way sites are marked as "favorites"
You can run this script at any time following the upgrade to Sakai 11, The time required for the conversion will depend on how many users you To run the script, open a shell and run the following commands: Then, for Unix systems: Or under Windows:
in the database. If you are upgrading from an earlier version of
Sakai, you should run the "ConvertUserFavoriteSitesSakai11" script to
migrate your users' existing favorite sites to the new format.
and Sakai does not need to be running for the script to work. If you
are planning an upgrade, a good time to run this is right before
starting Sakai 11 up for the first time.
have in your system. As a rule of thumb, you can expect it to take
between 2-5 minutes per hundred thousand users.
java -cp "lib/*" -Dtomcat.dir="$PWD" org.sakaiproject.user.util.ConvertUserFavoriteSitesSakai11
java -cp "lib\*" -Dtomcat.dir=%cd% org.sakaiproject.user.util.ConvertUserFavoriteSitesSakai11
You can run this script at any time following the upgrade to Sakai 11,
The time required for the conversion will depend on how many users you
To run the script, open a shell and run the following commands:
Then, for Unix systems:
Or under Windows:
|11.0||Dropbox||dropbox.maintain.own.groups||SAK-11647||Courses with multiple TAs (teaching assistants) managing multiple discussion sections have a need for the TAs to be able to access student dropboxes by their sections.|
|11.0||Samigo Test and Quizzes||samigo.pdf.convertformattedtext||SAM-2502|
|11.0||Samigo Test and Quizzes||samigo.SelectAssessmentBean.warnUserOfModification||SAM-1331|
# SAM-1331: Warn user of modification to edited quiz
|11.0||Samigo Test and Quizzes||samigo.fromAddress||SAM-1947|
+# SAM-1947 Email notifications on Samigo Submission
|10.0||Samigo Test and Quizzes||varies by question type||SAM-2296||Allow question types to be selectively disabled via Sakai properties. Added in Sakai 10|
|11.0||Samigo Test and Quizzes||samigo.allowMinScore||SAM-948|
## TEST & QUIZZES (SAMIGO)
|11.0||CK Editor (Rich Text Editor)||auto save||SAK-22495|
not a Sakai property!
ckeditor.launch.properties in the source code, so there are properties but not Sakai properties like we think of them. We're really just including a CKEditor community plugin so the configuration and code maintenance of the plugin is up to them (http://ckeditor.com/addon/autosave).
|11.0||MathJax||on by default. several properties.||SAK-22384|
+# SAK-22384 - MathJax support is enabled by default
It enables an institution to define what site types are by default publicly available via the "Site Browser" tool on the Gateway.
It also enables an institution to define what site types are or are not changeable by the maintainer, with regards to the "public" vs. "private" setting (site browser).
Currently, More Sites tab classifies the sites by their site type and course term if there is one, but this has several issues.
-New site types can't be classified apart without hardcoding them.
Our proposal is two optional properties in sakai.properties. One (moresites.externalConfig.siteTypes) with the list of site types and other (moresites.externalConfig.prefix) with the prefix to use in the properties files, so every site type in the list can be classified in More Sites tab by its internationalized property key.
For example, for setting two new site types (courseAsig is a new course type and course 2 is a new site type), sakai.properties would have this:
And the properties "moresites_course_asig" and "moresites_course_2" would be used for the i18n texts in sitenav.properties.
If moresites.externalConfig.siteTypes is not set or is empty, the usual logic is applied.
# The file browser to use for picking files in ckeditor
Open and Awaiting Review Jira tickets
For listings of all open issues see: