Moodle 3.6 release notes

Note: This page will continue to be updated until Moodle 3.6 is released.

Releases > Moodle 3.6 release notes   Release date: Not yet released - scheduled for 26 November 2018

Here is the full list of fixed issues in 3.6.

If you are upgrading from a previous version, please see Upgrading in the user docs. In particular, for sites using a custom theme or login form, from 3.6 onwards, the login form must include a new login token field. See Login token for details.

Server requirements

These are just the minimum supported versions. We recommend keeping all of your software and operating systems up-to-date.

• Moodle upgrade: Moodle 3.1 or later
• PHP version: minimum PHP 7.0.0 Note: minimum PHP version has increased since Moodle 3.3. PHP 7.1.x and 7.2.x are supported too. PHP 7.x could have some engine limitations.
• PHP extension intl is required since Moodle 3.4 (it was recommended in 2.0 onwards)

Database requirements

Moodle supports the following database servers. Again, version numbers are just the minimum supported version. We recommend running the latest stable version of any software.

Database	Minimum version	Recommended
PostgreSQL	9.4	Latest
MySQL	5.6	Latest
MariaDB	5.5.31	Latest
Microsoft SQL Server	2008	Latest
Oracle Database	11.2	Latest

Client requirements

Browser support

Moodle is compatible with any standards compliant web browser. We regularly test Moodle with the following browsers:

Desktop:

• Chrome
• Firefox
• Safari
• Edge
• Internet Explorer

Mobile:

• MobileSafari
• Google Chrome

For the best experience and optimum security, we recommend that you keep your browser up to date. https://whatbrowser.org

Note: Legacy browsers with known compatibility issues with Moodle 3.5:

• Internet Explorer 10 and below
• Safari 7 and below

 

Other Highlights

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.

For developers

Privacy API update

Two new methods need to be implemented in the privacy provider class for plugins that store user data:

• get_users_in_context()
• delete_data_for_users()

  Note these changes are also required for latest Moodle 3.4.6, 3.5.3 versions.

Behat scenario files

MDL-57281 - The behat step I navigate to "ITEM" node in "MAINNODE > PATH" has been deprecated and throws an exception with details on how to replace it. The recommended replacement steps work in all recent Moodle versions, the updated Behat will pass with Moodle 3.4, too.

Login token

If your plugin provides an alternative login form (e.g. it is a theme replacing the default login form template / renderer), the login form must include a new login token field. For details of required changes, see Login token. Note that this also affects latest stable branches, too.

Component APIs upgrades

Please refer to the upgrade.txt files in the relevant component directory for changes in particular Moodle release.

• admin/tool/log/upgrade.txt
• admin/tool/upgrade.txt
• auth/shibboleth/upgrade.txt
• auth/upgrade.txt
• badges/upgrade.txt
• blocks/upgrade.txt
• cache/upgrade.txt
• calendar/upgrade.txt
• course/format/upgrade.txt
• course/upgrade.txt
• enrol/upgrade.txt
• filter/upgrade.txt
• grade/grading/form/upgrade.txt
• grade/report/upgrade.txt
• grade/upgrade.txt
• lib/upgrade.txt
• media/upgrade.txt
• message/upgrade.txt
• mod/assign/upgrade.txt
• mod/feedback/upgrade.txt
• mod/forum/upgrade.txt
• mod/quiz/upgrade.txt
• mod/scorm/report/basic/upgrade.txt
• mod/scorm/upgrade.txt
• mod/upgrade.txt
• mod/workshop/upgrade.txt
• question/format/upgrade.txt
• report/upgrade.txt
• tag/upgrade.txt
• theme/upgrade.txt
• user/upgrade.txt

See also

• Moodle 3.5 release notes