If you are running Sakai 10.6 this upgrade is of critical importance. Several of the fixes in 10.7 were regressions from 10.6, especially against Assignment and Samigo Test and Quizzes. Also, if your institution is using Oracle, the standard upgrade scripts need to be run, and in addition a few extra lines.
- Assignments tool (problems with older assignments after fixes in 10.6)
- SAK-30233 - Regression after SAK-30087 cleanup on old assignment submissions.
- SAK-30644 - Problems with assignment submissions that were created prior to 10.6
- Samigo Test and Quizzes tool
- SAM-2679 - Matrix question / answers change back to original selection after save/next/previous
- SAM-2622 - Access denied error when attempting to download all responses, can only download responses individually
- SAM-2690 - IllegalArgumentException when clicking 'preview' or 'print' while editing a published assessment
- Portal
- SAK-30173 - Error page when the URL requested is /portal. You could work around this by just running an older version of tomcat (prior to 7.0.66)
- Oracle with Lessons - see
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | LSNBLDR-600 |
|---|
|
. See specifics below under Database upgrades.
...
- Sakai 10.7 includes 47 fixes, including 10 blocker priority, and 7 critical priority bugs, and translation updates for Turkish and Chinese.
- Database upgrades
- There is an Oracle, but not MySQL, upgrade script from Sakai 10.6 -> 10.7, related to
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-30667 |
|---|
|
. - Sakai 10 upgrade scripts. Please use database upgrade scripts from Github.
- For Oracle, additional database updates need to be made. They will be in the 10.7 -> 10.8 upgrade script when 10.8 is released.
- Java - Sakai 10 builds with Java 7, and can run on Java 7 or 8. Recommend using Java 1.7.082.
- Tomcat 7.0.68 compatibility and later versions of 7.0.x supported. For details see the Jira ticket. Please note that Tomcat 7.0.65 worked fine, but 7.0.66 and 7.0.67 have problems.
- Blocker bugs fixed in 10.7
- Security issues - 2 issues resolved. Please check with your security team for details. A security announcement follows soon after the release announcement.
- QA tested on jdk 1.7.0_76 and tomcat 7.0.65
New Feature
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-27809 |
|---|
|
Known Issues
Sakai| System JIRA | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
66e9c5b5d22c30a2a9d4703f4354570c
Sakai| System JIRA | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
66e9c5b5d22c30a2a9d4703f4354570c| 8363adfc350a | | key | LSNBLDR-642 |
|---|
|
New Properties
| Property | Default value | Description | Jira |
|---|
site-manage.pageorder.allowreorder
| true | # SAK-27809 Disabling of page order feature on page order helper | | Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-27809 |
|---|
|
|
| mail.sendfromsakai | true | +# Replacing From addresses in email
+# Major mail providers are starting to use DMARC, to demand that all mail From addresses from their domain
+# must be signed. Since we can't sign messages for another mail service, this means that email passed through
+# the archiver or generated by Mailtool / Messages will fail the test, and be rejected.
+# By default we now replace From addresses with postmaster@site, and move the original From address to
+# Reply-To. These properties control that behavior.
+#
+# Should we replace the From address? true|false
+# Can also be an email address. If not specified the new from address is postmaster@site.
+# Example: mailagent@sakai.myinstitution.edu
+# false if you don't want any replacement
+# DEFAULT: true
+#mail.sendfromsakai=false
+
+# Should we have exceptions for the replacement? Any from address matching this Java regular expression
+# will be retained unmodified. You might want to include addresses within your own institution, since
+# they shouldn't cause any trouble unless your own institution is using DMAEC.
+# Note that mail addresses using your Sakai instance's server name will always be exceptions
+# DEFAULT: missing, no exceptions
+#mail.sendfromsakai.exceptions=.*[@.]institution\\.edu
+
+# When replacing the From address, what text should we use. {} will be
+# replaced with the original From address, e.g. John Smith (jsmith@site.edu)
+# DEFAULT: {}
+#mail.sendfromsakai.fromtext=On behalf of {} | | Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | KNL-1400 |
|---|
|
|
| mail.sendfromsakai.exceptions | missing, no exceptions | see above. | see above. |
| mail.sendfromsakai.fromtext | {} | see above. | see above. |
wsetup.track.membership.change | false | # SAK-14210 - Enable tracking of membership changing, a lot more events
# DEFAULT: false
# wsetup.track.membership.change=true
# SAK-23555 - Enabling tracking of roster changing, a lot more events
# DEFAULT: false
# wsetup.track.roster.change=true | | Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-14210 |
|---|
|
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-23555 |
|---|
|
|
| wsetup.track.roster.change | false | see above. | see above. |
| msgcntr.forums.ranks.enable | true | # SAK-29934 Enable/disable the Forums rank feature
# DEFAULT: true
# msgcntr.forums.ranks.enable=false | | Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-29934 |
|---|
|
|
Known Issues
Sakai 10 Oracle upgrade scripts. Please use database upgrade scripts from Github. There are no upgrade scripts needed to go from Sakai 10.5 to Sakai 10.6 .
...
List of Issues Fixed
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | type,key,summary |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | filter=15628 |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
|