Moodle 3.5.7 release notes: Difference between revisions
From MoodleDocs
(Version officially out now) |
No edit summary |
||
Line 10: | Line 10: | ||
* MDL-65581 - Hidden blocks can once again be unhidden | * MDL-65581 - Hidden blocks can once again be unhidden | ||
* MDL-65249 - Redis cache store correctly displays exception after failed connections | * MDL-65249 - Redis cache store correctly displays exception after failed connections | ||
===Security fixes and improvements=== | |||
====Security fixes==== | |||
Details of any security fixes will be released after a period of approximately one week to allow system administrators to safely update to the latest version. | |||
====Security improvements==== | |||
The following bug fixes or improvements were made, which contribute to improving security or privacy best practices: | |||
* MDL-60347 - SMTP debugging now also requires developer level debugging messages to be enabled before being displayed. Although SMTP debugging is not intended for production site use, this provides an additional fallback measure to prevent verbose debugging from being unintentionally being visible to users. | |||
==See also== | ==See also== | ||
*[[Moodle 3.5.6 release notes]] | *[[Moodle 3.5.6 release notes]] |
Revision as of 08:15, 9 July 2019
Releases > Moodle 3.5.7 release notes
Release date: 8 July 2019
Here is the full list of fixed issues in 3.5.7.
Fixes and improvements
- MDL-58315 - Boost theme no longer ignores HTML block custom classes
- MDL-65581 - Hidden blocks can once again be unhidden
- MDL-65249 - Redis cache store correctly displays exception after failed connections
Security fixes and improvements
Security fixes
Details of any security fixes will be released after a period of approximately one week to allow system administrators to safely update to the latest version.
Security improvements
The following bug fixes or improvements were made, which contribute to improving security or privacy best practices:
- MDL-60347 - SMTP debugging now also requires developer level debugging messages to be enabled before being displayed. Although SMTP debugging is not intended for production site use, this provides an additional fallback measure to prevent verbose debugging from being unintentionally being visible to users.