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
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.
The Assignment XML that is exported in Sakai 12 is significantly different than in Sakai 11 and earlier.
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 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.
The properties options have been updated in default.sakai.properties. No new properties have been added, just that existing properties have been documented.
A JIRA is open, but not PR (pull request, aka source code contribution) for it yet.
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. and
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, . Related Jiras include and
Please note that the default for webservices.log-allowed has been changed from true to false.
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)
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
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.
Documentation is stored with Sakai on Github
There was an issue noted in and where Grade Statistics in Gradebook as well as Sitestats charts threw an error when running in OpenJDK. The solution that seems to works is to comment out the `assistive_technologies` line in `/etc/java-8-openjdk/accessibility.properties` or possibly to use Oracle JDK instead. I tried to install the libjfreechart-java (on Ubuntu) and restart but this didn't seem to fix it, but that could be an alternate fix. Since java is running headless on the server, removing assistive_technologies doesn't look like it does anything. This will not be an issue in Sakai 19 for Gradebook, but likely still be necessary for Sitestats to watch for.
For listings of all open issues see:
Blocker Critical Major Minor, trivial