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-33701 - Audit Log for Submissions Open
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
The Assignment XML that is exported in Sakai 12 is significantly different than in Sakai 11 and earlier. SAK-33845 - Assignment is not working with archive Closed
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-33724 - Disable bullhorns by default for the Sakai 12.0 release Resolved
Course management SIS Load using CSV files
SAK-33915 - Create documentation for SIS CSV Verified
MathJax - now a site level instead of a tool level setting
SAK-32421 - Add NYU MathJax Customizations and "Preview" CKEditor Plugin Resolved
MySQL and MariaDB - upgrade to Hibernate resulted in new dialect
SAK-39652 - Upgrade to Hibernate 4.3.x Resolved
Profile tool "wall" disabled by default in Sakai 12
SAK-32243 - Disable Profile2 wall by default. Resolved
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
SAK-27908 - Disable duplicating sites since it's not threaded Resolved
A JIRA is open, but not PR (pull request, aka source code contribution) for it yet. SAK-33400 - Duplicating sites should be threaded just like importing sites Open
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-33328 - Remove syllabus date/title edit as it uses out of date library Verified and SAK-33769 - Change string "Bulk Edit" to "Edit" Open
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, SAK-34145 - Clarify to user what will happen with autosubmit feature Open . Related Jiras include SAK-36393 - Autosubmit should also submit opened exams with no questions answered Verified and SAK-37079 - Text change: Autosubmit job submitting numerous attempts instead of only the first attempt Verified
Please note that the default for webservices.log-allowed has been changed from true to false. SAK-39648 - Consider disabling webservices.log-allowed in default config Verified
Sakai 12 properties
|12.0||Samigo Test and Quizzes||samigo.eventlog.ipaddress.enabled||SAK-36875 - Tests & Quizzes (Samigo) - Event Log IP Address column is empty Verified|
|12.0||Samigo Test and Quizzes|
|SAK-34943 - Refactor autosubmit to enclose each update in a separate transaction and notify on failure Closed|
|SAK-33672 - Make customizable the default value for notify options in resources Closed|
|12.0||Unused cache properties for calendar|
calendar.external.subscriptions.institutional.cacheentries - NEW property
Existing properties but had not been implemented before 12.
calendar.external.subscriptions.institutional.cachetime=120 calendar.external.subscriptions.user.cacheentries=32 calendar.external.subscriptions.user.cachetime=120
|SAK-33381 - Unused cache properties for calendar Verified|
|12.0||Web Services||webservices.allow-request||SAK-32728 - RemoteHostFilter should allow certain endpoints to work Resolved|
|12.0||Login||?||SAK-32699 - IP whitelisting for internal user authentication Resolved|
|12.0||Signup tool||signup.default.email.selected=all||SAK-32655 - Add default property for signup email notification availability and ensure default is "all" Verified|
|12.0||Site management||portal.forceOverviewToTop=false||SAK-32386 - Force 'Overview' tool to the top of the tool menu via sakai.property Verified|
|12.0||MySQL/MariaDB||driverClassName@javax.sql.BaseDataSource=org.mariadb.jdbc.Driver||SAK-32155 - Include MariaDB driver property in default.sakai.properties Resolved|
|SAK-32087 - New UI for students to see which courses they're enrolled in Resolved|
|12.0||Portal Bullhorns (notifications)||portal.bullhorns.enabled , default false||SAK-30461 - Add academic and social bullhorn alerts to portal topbar Resolved|
|12.0||CK Editor (Rich Text Editor)||autosave_delay set in ckeditor.launch.js (not in sakai.properties)||SAK-31712 - Change the autosave delay and put the message in status bar Verified|
|12.0||Duplicate Site||default of site.setup.allowDuplicateSite set to false. Duplicate site is off by default.||SAK-27908 - Disable duplicating sites since it's not threaded Resolved|
Zip download feature
Option is not available unless the next properties are configured with a value (in bytes) greater than 0.
|SAK-25438 - Add ability to download files and folders from resources/dropbox into a zip file on the fly. Verified|
|12.0||Site Titles using Templates||site.tool.custom.titles||SAK-38986 - Sites with custom title changes created from templates don't keep change Resolved|
|12.0||User Experience - Auto Favorites||portal.default.tabs||SAK-32296 - Deliver NYU Auto-Favoriting Customizations Resolved|
Changing default values of properties
|12.0||Site Info||site-manage.importoption.siteinfo||SAK-32067 - Change default value of site-manage.importoption.siteinfo to true Resolved|
|12.0||Portal||portal.showSubsitesAsFlyout||SAK-32499 - Change default property of portal.showSubsitesAsFlyout to true Resolved|
|12.0||Content (Resources)||content.url.rightsdialog||SAK-32590 - Change default property for content.url.rightsdialog to be true Resolved|
|12.0||Filesize Upload limit|
Because of recent improvements in file upload handling,
you may want to increase your file size limits on your system.
You should be using file system based storage
(by setting bodyPath@org.sakaiproject.content.api.ContentHostingService)
rather than database storage if you increase these limits. "ceiling" is used for resources.
"max" is used for attachments.
In the case when both are set, resources are limited to the smaller of the two.
If only one of the two are set, resource uploadsare limited to the value whichever is set.
Attachments are limited at either 20 or the setting of "max"
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 - Changes to how Events are stored
These events were removed
lessonbuilder.create - creating a page or item lessonbuilder.update - updating a page or item lessonbuilder.delete - deleting a page or item
These events were added
lessonbuilder.page.create - creating a page lessonbuilder.page.read - reading a page lessonbuilder.page.update - updating a page lessonbuilder.page.delete - deleting a page lessonbuilder.item.create - creating a item lessonbuilder.item.read - reading a item lessonbuilder.item.update - updating a item lessonbuilder.comment.create - creating a comment lessonbuilder.comment.update - updating a comment lessonbuilder.comment.delete - deleting a comment
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"
Sakai 11 changes the way that sites marked as "favorites" are stored 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:
Open and Awaiting Review Jira tickets
For listings of all open issues see: