Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Moodle 3.3.1 release notes

From MoodleDocs
Revision as of 04:08, 10 July 2017 by Marina Glancy (talk | contribs)

Releases > Moodle 3.3.1 release notes

Release date: 10 July 2017

Here is the full list of fixed issues in 3.3.1.

Highlights

  • MDL-58136 - Show only "in progress" courses in the My courses list in Booost flat navigation
  • MDL-56046 - Fixed bug when downloading Quiz statistics report and other multiple-sheet reports
  • MDL-58646, MDL-59122 - Number of performance improvements in Boost cache rebuilding
  • MDL-58310, MDL-59312, MDL-58103 - Correctly display AJAX errors and ignore interrupted requests caused by page unload (occasional "undefined" popup)
  • MDL-44961 - When restoring course with rolling start date never change log dates

Security issues

A number of security related issues were resolved. Details of these issues will be released after a period of approximately one week to allow system administrators to safely update to the latest version.

Fixes and improvements

  • MDL-46322 - Assignment: Only enrolled users may be assigned as markers, if admins/managers can view course but are not enrolled they will not be assigned
  • MDL-58907 - Course overview: Remember last view mode (Timeline/Courses), add a setting for a default mode
  • MDL-58729 - Performance impovement in MySQL collation change script (follow up for Full UTF-8 Support in MySQL)
  • MDL-57957 - Assignment: Fixed bug with feedback files not being shown to students if assignment has no grading
  • MDL-57021 - Use normal password form field during sign up, adding new user and enrolling in a course
  • MDL-49988 - Wiki: line breaks in HTML source code should not affect page layout
  • MDL-58811 - Quiz: fixed bug preventing quiz duplication if questions have file links in their texts

For developers

  • MDL-58911 - Change of behavior when writing unittests for the dashboard events - now callback from module are executed in unittests same way they would be executed on the dashboard


See also