Hello everyone,
The following versions of Totara Learn have now been released:
- Release Evergreen
- Release 12.14
- Release 11.23
- Release 10.29
- Release 9.40
- Release 2.9.49
- Release 2.7.56
- Release 2.6.73
- Release 2.5.79
These versions contain bug fixes and improvements.
Kind regards Riana Rossouw
Release Evergreen (22nd January 2020):
Key: + Evergreen only
Important:
TL-23121 + Upgraded Bootstrap to 3.4.1
Bootstrap JavaScript has been upgraded from version 3.3.4 to 3.4.1 and
Bootstrap CSS has been upgraded from 3.3.7 to 3.4.1. This includes a number
of minor bug fixes and improvements. All security issues had previously
been backported.
Performance improvements:
TL-22824 Improved performance of bulk delete of questions in a quiz
TL-23390 Improved performance of building the course category tree
Improvements:
TL-22841 Added a cleanup step as the last task in the course restore process to prevent unnecessary creation of the random questions
TL-23117 + Improved CSS of the Reports page
Previously there was some browser-specific CSS leading to different
experiences in different browsers. The CSS has been improved so that this
is no longer the case.
This will require CSS to be regenerated for themes that use LESS
inheritance.
TL-23354 Improved alignment of the folder resource on the course page
This will require CSS to be regenerated for themes that use LESS
inheritance.
Bug fixes:
TL-23085 Fixed 'Type of activity' selector not being populated for roles in category when single activity format is default
TL-23171 Fixed an issue where not having permission to view another user's learning plan would result in an exception
Users without permission to view the learning plan now see a proper error
message when trying to access it.
Updated get_component_setting() function in development_plan.class to
return false when setting not found (instead of throwing an exception).
TL-23312 Fixed Seminar event 'normal cost' and 'discount cost' visibility for seminar notifications
Previously the 'Hide normal cost' and 'Hide discount cost' seminar global
settings were not taken into account when seminar notifications were sent.
This fix ensures that these global settings are always taken into account.
TL-23314 Fixed a bug that had unnecessarily replaced non-HTML line breaks with HTML tags when displaying a course summary in the grid catalogue
TL-23415 'Choose file' button in filepicker form element is now disabled correctly
Previously when using disabledIf form functionality, the 'Choose file ...'
button was not being disabled correctly. This is now been fixed.
TL-23416 Removed unnecessary sanitisation of 'Consumer key' and 'Shared secret' fields in the LTI external tool configuration forms
Previously, the forms stripped out values or removed them completely if '<'
or '>' characters were entered.
TL-23440 Made sure system context is set on the main menu item display
Previously when the multi-language content filter was disabled at the
course level the site's main menu would be displayed as unfiltered when
being viewed from the course page. This now has been fixed and the main
menu always takes the general system settings for content filtering into
account.
TL-23441 Allowed the case of job assignment ID number to be changed when using a case-insensitive database
TL-23446 Fixed migration of HR Import file settings when upgrading from Totara 11 to new major version
In Totara 12 we introduced separate file settings for each element in HR
Import. When migrating from Totara 11 to Totara 12+, the existing settings
were not correctly migrated to these new element-specific settings.
TL-23452 Improved display of Messages contacts selector when searching within a course with a long name
TL-23458 Fixed permission check when sending plan approval request message to manager
The permissions check done when sending a plan approval request message to
a manager was only checking if they had the 'Allow' permission in the plan
template for the Approve setting. The 'Approve' option for the setting is
also now checked.
TL-23490 Fixed minor custom field display issues in auth_approved reports
TL-23519 Fixed placement of the 'Upload HR Import files' menu option in HR Import
A performance fix applied in Totara 12.7 caused the 'Upload HR Import
files' menu item to appear in the middle of the list of elements in the HR
Import settings menu. This has now been fixed.
TL-23520 + Fixed shadow being hidden by graph image on the Reports page
This will require CSS to be regenerated for themes that use LESS
inheritance.
TL-23529 Fixed an error while viewing evidence for another user when the teams feature is disabled
TL-23593 Ensured HR Import database source classes have the USES_FILES defined as false
TL-23613 Fixed seminar direct enrolment session table overflowing display on small screens
API changes:
TL-23511 The new minimum required Node.js version has changed to 12
It is required now to run at least Node.js 12 to run grunt builds. It is
recommended to always use the latest NPM version.
Release 12.14 (22nd January 2020):
Performance improvements:
TL-22824 Improved performance of bulk delete of questions in a quiz
TL-23390 Improved performance of building the course category tree
Improvements:
TL-22841 Added a cleanup step as the last task in the course restore process to prevent unnecessary creation of the random questions
TL-23354 Improved alignment of the folder resource on the course page
This will require CSS to be regenerated for themes that use LESS
inheritance.
Bug fixes:
TL-23085 Fixed 'Type of activity' selector not being populated for roles in category when single activity format is default
TL-23171 Fixed an issue where not having permission to view another user's learning plan would result in an exception
Users without permission to view the learning plan now see a proper error
message when trying to access it.
Updated get_component_setting() function in development_plan.class to
return false when setting not found (instead of throwing an exception).
TL-23312 Fixed Seminar event 'normal cost' and 'discount cost' visibility for seminar notifications
Previously the 'Hide normal cost' and 'Hide discount cost' seminar global
settings were not taken into account when seminar notifications were sent.
This fix ensures that these global settings are always taken into account.
TL-23314 Fixed a bug that had unnecessarily replaced non-HTML line breaks with HTML tags when displaying a course summary in the grid catalogue
TL-23415 'Choose file' button in filepicker form element is now disabled correctly
Previously when using disabledIf form functionality, the 'Choose file ...'
button was not being disabled correctly. This is now been fixed.
TL-23416 Removed unnecessary sanitisation of 'Consumer key' and 'Shared secret' fields in the LTI external tool configuration forms
Previously, the forms stripped out values or removed them completely if '<'
or '>' characters were entered.
TL-23440 Made sure system context is set on the main menu item display
Previously when the multi-language content filter was disabled at the
course level the site's main menu would be displayed as unfiltered when
being viewed from the course page. This now has been fixed and the main
menu always takes the general system settings for content filtering into
account.
TL-23441 Allowed the case of job assignment ID number to be changed when using a case-insensitive database
TL-23446 Fixed migration of HR Import file settings when upgrading from Totara 11 to new major version
In Totara 12 we introduced separate file settings for each element in HR
Import. When migrating from Totara 11 to Totara 12+, the existing settings
were not correctly migrated to these new element-specific settings.
TL-23452 Improved display of Messages contacts selector when searching within a course with a long name
TL-23458 Fixed permission check when sending plan approval request message to manager
The permissions check done when sending a plan approval request message to
a manager was only checking if they had the 'Allow' permission in the plan
template for the Approve setting. The 'Approve' option for the setting is
also now checked.
TL-23490 Fixed minor custom field display issues in auth_approved reports
TL-23519 Fixed placement of the 'Upload HR Import files' menu option in HR Import
A performance fix applied in Totara 12.7 caused the 'Upload HR Import
files' menu item to appear in the middle of the list of elements in the HR
Import settings menu. This has now been fixed.
TL-23529 Fixed an error while viewing evidence for another user when the teams feature is disabled
TL-23559 CSS cursor when hovering over an item in the grid catalogue is now a hand icon
This will require CSS to be regenerated for themes that use LESS
inheritance.
TL-23593 Ensured HR Import database source classes have the USES_FILES defined as false
TL-23613 Fixed seminar direct enrolment session table overflowing display on small screens
API changes:
TL-23511 The new minimum required Node.js version has changed to 12
It is recommended now to run at least Node.js 12 to run grunt builds.
Node.js 8 is almost out of support; we recommend to use the latest Node.js
12 to run grunt builds. However to avoid compatibility issues in stable
releases running Node 8 is still supported.
Release 11.23 (22nd January 2020):
Improvements:
TL-22841 Added a cleanup step as the last task in the course restore process to prevent unnecessary creation of the random questions
Bug fixes:
TL-23085 Fixed 'Type of activity' selector not being populated for roles in category when single activity format is default
TL-23416 Removed unnecessary sanitisation of 'Consumer key' and 'Shared secret' fields in the LTI external tool configuration forms
Previously, the forms stripped out values or removed them completely if '<'
or '>' characters were entered.
TL-23441 Allowed the case of job assignment ID number to be changed when using a case-insensitive database
API changes:
TL-23511 The new minimum required Node.js version has changed to 12
It is recommended now to run at least Node.js 12 to run grunt builds.
Node.js 8 is almost out of support; we recommend to use the latest Node.js
12 to run grunt builds. However to avoid compatibility issues in stable
releases running Node 8 is still supported.
Release 10.29 (22nd January 2020):
Bug fixes:
TL-23416 Removed unnecessary sanitisation of 'Consumer key' and 'Shared secret' fields in the LTI external tool configuration forms
Previously, the forms stripped out values or removed them completely if '<'
or '>' characters were entered.
API changes:
TL-23511 The new minimum required Node.js version has changed to 12
It is recommended now to run at least Node.js 12 to run grunt builds.
Node.js 8 is almost out of support; we recommend to use the latest Node.js
12 to run grunt builds. However to avoid compatibility issues in stable
releases running Node 8 is still supported.
Release 9.40 (22nd January 2020):
API changes:
TL-23511 The new minimum required Node.js version has changed to 12
It is recommended now to run at least Node.js 12 to run grunt builds.
Node.js 8 is almost out of support; we recommend to use the latest Node.js
12 to run grunt builds. However to avoid compatibility issues in stable
releases running Node 8 is still supported.
Release 2.9.49 (22nd January 2020):
API changes:
TL-23511 The new minimum required Node.js version has changed to 12
It is recommended now to run at least Node.js 12 to run grunt builds.
Node.js 8 is almost out of support; we recommend to use the latest Node.js
12 to run grunt builds. However to avoid compatibility issues in stable
releases running Node 8 is still supported.
Release 2.7.56 (22nd January 2020):
API changes:
TL-23511 The new minimum required Node.js version has changed to 12
It is recommended now to run at least Node.js 12 to run grunt builds.
Node.js 8 is almost out of support; we recommend to use the latest Node.js
12 to run grunt builds. However to avoid compatibility issues in stable
releases running Node 8 is still supported.
Release 2.6.73 (22nd January 2020):
API changes:
TL-23511 The new minimum required Node.js version has changed to 12
It is recommended now to run at least Node.js 12 to run grunt builds.
Node.js 8 is almost out of support; we recommend to use the latest Node.js
12 to run grunt builds. However to avoid compatibility issues in stable
releases running Node 8 is still supported.
Release 2.5.79 (22nd January 2020):
API changes:
TL-23511 The new minimum required Node.js version has changed to 12
It is recommended now to run at least Node.js 12 to run grunt builds.
Node.js 8 is almost out of support; we recommend to use the latest Node.js
12 to run grunt builds. However to avoid compatibility issues in stable
releases running Node 8 is still supported.