...
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
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-33701 |
|---|
|
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.
...
The Assignment XML that is exported in Sakai 12 is significantly different than in Sakai 11 and earlier.
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-33845 |
|---|
|
Assignments - For Attachment only assignments, student must upload a file. Links are not accepted.
...
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.
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-33724 |
|---|
|
Course management SIS Load using CSV files
Jira:
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-33915 |
|---|
|
Documentation:
...
MathJax - now a site level instead of a tool level setting
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-32421 |
|---|
|
MySQL and MariaDB - upgrade to Hibernate resulted in new dialect
hibernate.dialect=org.hibernate.dialect.MySQL57InnoDBDialect
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | KNL-945 |
|---|
|
Profile tool "wall" disabled by default in Sakai 12
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-32243 |
|---|
|
Signup tool properties documented
...
Site Management - Duplicating sites disabled by default due to performance concerns
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-27908 |
|---|
|
A JIRA is open, but not PR (pull request, aka source code contribution) for it yet.
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-33400 |
|---|
|
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.
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-33328 |
|---|
|
and
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-33769 |
|---|
|
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,
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAM-3359 |
|---|
|
. Related Jiras include
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAM-2729 |
|---|
|
and
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAM-3128 |
|---|
|
Web Services
Please note that the default for webservices.log-allowed has been changed from true to false. | Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | KNL-1538 |
|---|
|
----------------------------------
...
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 a security tradeoff. There are security risks from opening a web page written by someone else. That page can contain Javascript, which will execute with your own permissions. For this reason, by default Sakai will not open web pages in Resources. If you click on an HTML file there, it will download. We considered this inaccessible for Lessons, since the whole point of Lessons is to present content online. But we still had to deal with the security problem. So the page is served with an HTTP header that causes browsers to open the page in a “sandbox.” This restricts what the page can do.
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:
lessonbuilder.use-csp-headers=false
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
...
There was an issue noted in | Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-40275 |
|---|
|
and | Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-40141 |
|---|
|
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.
...