MoodleDocs - User contributions [en]

Moodle 3.9.15 release notes

2022-05-20T07:00:57Z

Abgreeve: Copy of template for this version

[[Releases]] > Moodle 3.9.15 release notes

Release date: Not yet released

Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%223.9.15%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in 3.9.15].

==General fixes and improvements==

''Items to be added soon...''

==Security fixes==

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.

==See also==
*[[Moodle 3.9.14 release notes]]

[[Category:DevDocs Migration]]
[[Category:Release notes]]
[[Category:Moodle 3.9]]

[[fr:Notes de version de Moodle 3.9]]
[[es:Notas de Moodle 3.9]]

Moodle 3.11.8 release notes

2022-05-20T06:58:35Z

Abgreeve: Copy of template for this version

[[Releases]] > Moodle 3.11.8 release notes

Release date: Not yet released

Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%223.11.8%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in 3.11.8].

==General fixes and improvements==

''Items to be added soon...''

==Security fixes==

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.

==See also==
*[[Moodle 3.11.7 release notes]]

[[Category:DevDocs Migration]]
[[Category:Release notes]]
[[Category:Moodle 3.11]]

[[fr:Notes de version de Moodle 3.11]]
[[es:Notas de Moodle 3.11]]

Moodle 4.0.2 release notes

2022-05-20T06:54:39Z

Abgreeve: Copy of template for this version

[[Releases]] > Moodle 4.0.2 release notes

Release date: Not yet released

Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%224.0.2%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in 4.0.2].

==General fixes and improvements==

''Items to be added soon...''

==Security fixes==

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.

==See also==
*[[Moodle 4.0.1 release notes]]

[[Category:DevDocs Migration]]
[[Category:Release notes]]
[[Category:Moodle 4.0]]

[[fr:Notes de version de Moodle 4.0]]
[[es:Notas de Moodle 4.0]]

Moodle 4.1 release notes

2022-05-20T06:48:04Z

Abgreeve: Copy of template for this version

[[Releases]] > Moodle 4.1 release notes

Release date: Not yet released

Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%224.1%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in 4.1].

==Server requirements==

===Database requirements===

==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

Note: Moodle 4.0 does NOT support Internet Explorer 11.

Safari 7 and below has known compatibility issues with Moodle 4.0.

Mobile:

* MobileSafari
* Google Chrome

For the best experience and optimum security, we recommend that you keep your browser up to date.

==Major features==

''Items to be added soon...''

==Other highlights==

''Items to be added soon...''

==For admins==

''Items to be added soon...''

==For developers==

''Items to be added soon...''

==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.

==See also==
*[[Moodle 4.0 release notes]]

[[Category:DevDocs Migration]]
[[Category:Release notes]]
[[Category:Moodle 4.1]]

[[fr:Notes de version de Moodle 4.1]]
[[es:Notas de Moodle 4.1]]

Releases

2022-05-09T01:47:55Z

Abgreeve: /* Moodle 3.10 support end */

This page lists all official releases of Moodle, grouped by branch in reverse chronological order.
==Version support==
From Moodle 2.6 onwards, the end of support, both general and security, happens the second Monday of May and November, observing the 12, 18... month periods, no matter if the major release date was moved or not.

The most recent [https://en.wikipedia.org/wiki/Long-term_support long-term support release (LTS)] version is Moodle 3.9.
{| class="wikitable" border="1px solid #dee2e6;"
|-
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Version
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Release status
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Initial release
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:rgba(0, 0, 0, 0.05);" | General support ends
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Security support ends
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.9 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 15 June 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 10 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 November 2023 (ext 6M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.11
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 17 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 14 Nov 2022 (ext 6M)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 Nov 2023 (ext 12M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |4.0
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |19 April 2022
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |8 May 2023
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |13 November 2023
|-
|4.1 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
|November 2022
|November 2023
|November 2025
|}
[[Image:401_release_graph.png|alt=Release graph]]

Release graph key:
{| class="wikitable" border="1px solid #dee2e6;"
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Currently supported stable releases.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | Current release of versions still receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Future point releases receiving bug fixes, as well as security updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#316d5e; color:white; adding: .3rem 0.5rem 0.3rem 0.5rem;" |Future security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Future point releases receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#686566; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Previously released versions containing bug fixes, as well as security updates. Updating to a currently supported version is recommended.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#282828; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Previously released versions containing security updates only. Updating to a currently supported version is recommended.
|}

==General release calendar==
These are the target dates for releases. These dates may vary slightly due to unforeseen circumstances.
{| class="wikitable"
|-
!Release type
!Frequency
!Months
|-
|[[Process#Major_release_cycles|Major]] (eg. 3.x)
|6 monthly
|Second Monday of May and November
|-
|[[Process#Stable_maintenance_cycles|Minor]] (Point) (eg. 3.x.y)
| 2 monthly
|Second Monday of July, September, November, March and May.
Third Monday of January.
|}
All releases are preceded by a one week warning. Upcoming release dates can be found in the [https://www.google.com/calendar/ical/moodle.com_p4c2oe7hsb77ltaro5qtihb5d4%40group.calendar.google.com/public/basic.ics Moodle development calendar] (Note, this is an iCAL link that will try to add the dates to your personal calendar. If you just want to browse the dates online, use [https://calendar.google.com/calendar/embed?src=moodle.com_p4c2oe7hsb77ltaro5qtihb5d4@group.calendar.google.com&pli=1 this link].).

==Moodle 4.0==
{| class="wikitable"
|-
!Moodle 4.0
|19 April 2022
|2022041900
|[[Moodle 4.0 release notes|Release Notes]]
|[https://docs.moodle.org/400/en/Upgrading Upgrading to 4.0]
|-
!Moodle 4.0.1
|9 May 2022
|2022041901
|[[Moodle 4.0.1 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 4.0.x will end 8 May 2023 (12 months).
Bug fixes for security issues in 4.0.x will end 13 November 2023 (18 months).

==Moodle 3.11==
{| class="wikitable"
|-
!Moodle 3.11
|17 May 2021
|2021051700
|[[Moodle 3.11 release notes|Release Notes]]
|[https://docs.moodle.org/311/en/Upgrading Upgrading to 3.11]
|-
!Moodle 3.11.1
|12 July 2021
|2021051701
|[[Moodle 3.11.1 release notes|Release Notes]]
|
|-
!Moodle 3.11.2
|29 July 2021
|2021051702
|[[Moodle 3.11.2 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.11.3
|13 September 2021
|2021051703
|[[Moodle 3.11.3 release notes|Release Notes]]
|
|-
! Moodle 3.11.4
|8 November 2021
|2021051704
|[[Moodle 3.11.4 release notes|Release Notes]]
|
|-
! Moodle 3.11.5
|17 January 2022
|2021051705
|[[Moodle 3.11.5 release notes|Release Notes]]
|
|-
! Moodle 3.11.6
|14 March 2022
|2021051706
|[[Moodle 3.11.6 release notes|Release Notes]]
|
|-
! Moodle 3.11.7
|9 May 2022
|2021051707
|[[Moodle 3.11.7 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.11.x will end 14 Nov 2022 (12 months plus 6 months extension).
Bug fixes for security issues in 3.11.x will end 13 Nov 2023 (18 months plus 12 months extension).

==Moodle 3.10==
{| class="wikitable"
|-
! Moodle 3.10
|9 November 2020
|2020110900
|
[[Moodle 3.10 release notes|Release Notes]]
|[https://docs.moodle.org/310/en/Upgrading Upgrading to 3.10]
|-
!Moodle 3.10.1
|18 January 2021
|2020110901
| [[Moodle 3.10.1 release notes|Release Notes]]
|
|-
!Moodle 3.10.2
|8 March 2021
|2020110902
|[[Moodle 3.10.2 release notes|Release Notes]]
|
|-
! Moodle 3.10.3
|25 March 2021
|2020110903
|[[Moodle 3.10.3 release notes|Release Notes]]
|
|-
!Moodle 3.10.4
|10 May 2021
|2020110904
|[[Moodle 3.10.4 release notes|Release Notes]]
|
|-
!Moodle 3.10.5
|12 July 2021
|2020110905
|[[Moodle 3.10.5 release notes|Release Notes]]
|
|-
!Moodle 3.10.6
|29 July 2021
|2020110906
|[[Moodle 3.10.6 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.10.7
|13 September 2021
|2020110907
|[[Moodle 3.10.7 release notes|Release Notes]]
|
|-
!Moodle 3.10.8
|8 November 2021
|2020110908
|[[Moodle 3.10.8 release notes|Release Notes]]
|
|-
!Moodle 3.10.9
|17 January 2022
|2020110909
|[[Moodle 3.10.9 release notes|Release Notes]]
|
|-
!Moodle 3.10.10
|14 March 2022
|2020110910
|[[Moodle 3.10.10 release notes|Release Notes]]
|
|-
!Moodle 3.10.11
|9 May 2022
|2020110911
|[[Moodle 3.10.11 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.10.x ended 8 November 2021 (12 months).
Bug fixes for security issues in 3.10.x will end 9 May 2022 (18 months).

==Moodle 3.9 (LTS)==
{| class="wikitable"
|-
! Moodle 3.9
|15 June 2020
|2020061500
|[[Moodle 3.9 release notes|Release Notes]]
|
[https://docs.moodle.org/39/en/Upgrading Upgrading to 3.9]
|-
!Moodle 3.9.1
|13 July 2020
|2020061501
|[[Moodle 3.9.1 release notes|Release Notes]]
|
|-
!Moodle 3.9.2
|14 September 2020
|2020061502
| [[Moodle 3.9.2 release notes|Release Notes]]
|
|-
!Moodle 3.9.3
|9 November 2020
|2020061503
| [[Moodle 3.9.3 release notes|Release Notes]]
|
|-
!Moodle 3.9.4
|18 January 2021
|2020061504
|[[Moodle 3.9.4 release notes|Release Notes]]
|
|-
!Moodle 3.9.5
|8 March 2021
|2020061505
|[[Moodle 3.9.5 release notes|Release Notes]]
|
|-
!Moodle 3.9.6
|25 March 2021
|2020061506
|[[Moodle 3.9.6 release notes|Release Notes]]
|
|-
!Moodle 3.9.7
|10 May 2021
|2020061507
|[[Moodle 3.9.7 release notes|Release Notes]]
|
|-
! Moodle 3.9.8
|12 July 2021
|2020061508
|[[Moodle 3.9.8 release notes|Release Notes]]
|
|-
!Moodle 3.9.9
|29 July 2021
|2020061509
|[[Moodle 3.9.9 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.9.10
|13 September 2021
|2020061510
|[[Moodle 3.9.10 release notes|Release Notes]]
|
|-
!Moodle 3.9.11
| 8 November 2021
|2020061511
|[[Moodle 3.9.11 release notes|Release Notes]]
|
|-
!Moodle 3.9.12
| 17 January 2022
|2020061512
|[[Moodle 3.9.12 release notes|Release Notes]]
|-
!Moodle 3.9.13
| 14 March 2022
|2020061513
|[[Moodle 3.9.13 release notes|Release Notes]]
|
|-
!Moodle 3.9.14
| 9 May 2022
|2020061514
|[[Moodle 3.9.14 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.9.x ended 10 May 2021 (12 months).
Bug fixes for security issues in 3.9.x will end 13 Nov 2023 (36 months plus 6 months extension).
==Moodle 3.8==
{| class="wikitable"
|-
!Moodle 3.8
|18 November 2019
|2019111800
|[[Moodle 3.8 release notes|Release Notes]]
|
[https://docs.moodle.org/38/en/Upgrading Upgrading to 3.8]
|-
!Moodle 3.8.1
|13 January 2020
|2019111801
|[[Moodle 3.8.1 release notes|Release Notes]]
|
|-
!Moodle 3.8.2
|9 March 2020
|2019111802
|[[Moodle 3.8.2 release notes|Release Notes]]
|
|-
!Moodle 3.8.3
|11 May 2020
|2019111803
|[[Moodle 3.8.3 release notes|Release Notes]]
|
|-
!Moodle 3.8.4
|13 July 2020
|2019111804
|[[Moodle 3.8.4 release notes|Release Notes]]
|
|-
!Moodle 3.8.5
|14 September 2020
|2019111805
| [[Moodle 3.8.5 release notes|Release Notes]]
|
|-
!Moodle 3.8.6
|9 November 2020
|2019111806
| [[Moodle 3.8.6 release notes|Release Notes]]
|
|-
!Moodle 3.8.7
|18 January 2021
|2019111807
|[[Moodle 3.8.7 release notes|Release Notes]]
|
|-
!Moodle 3.8.8
|8 March 2021
|2019111808
|[[Moodle 3.8.8 release notes|Release Notes]]
|
|-
!Moodle 3.8.9
|10 May 2021
|2019111809
|[[Moodle 3.8.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.8.x ended 9 November 2020 (12 months).
Bug fixes for security issues in 3.8.x ended 10 May 2021 (18 months).
==Moodle 3.7==
{| class="wikitable"
|-
!Moodle 3.7
|20 May 2019
|2019052000
|[[Moodle 3.7 release notes|Release Notes]]
|[https://docs.moodle.org/37/en/Upgrading Upgrading to 3.7]
|-
!Moodle 3.7.1
|8 July 2019
|2019052001
|[[Moodle 3.7.1 release notes|Release Notes]]
|
|-
!Moodle 3.7.2
|9 September 2019
|2019052002
|[[Moodle 3.7.2 release notes|Release Notes]]
|
|-
!Moodle 3.7.3
|11 November 2019
|2019052003
| [[Moodle 3.7.3 release notes|Release Notes]]
|
|-
!Moodle 3.7.4
|13 January 2020
|2019052004
|[[Moodle 3.7.4 release notes|Release Notes]]
|
|-
!Moodle 3.7.5
|9 March 2020
|2019052005
|[[Moodle 3.7.5 release notes|Release Notes]]
|
|-
!Moodle 3.7.6
|11 May 2020
|2019052006
|[[Moodle 3.7.6 release notes|Release Notes]]
|
|-
!Moodle 3.7.7
|13 July 2020
|2019052007
|[[Moodle 3.7.7 release notes|Release Notes]]
|
|-
!Moodle 3.7.8
|14 September 2020
|2019052008
| [[Moodle 3.7.8 release notes|Release Notes]]
|
|-
!Moodle 3.7.9
|9 November 2020
|2019052009
|[[Moodle 3.7.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.7.x ended 11 May 2020 (12 months).
Bug fixes for security issues in 3.7.x ended 9 November 2020 (18 months).
==Moodle 3.6==
{| class="wikitable"
|-
!Moodle 3.6
| 3 December 2018
|2018120300
|[[Moodle 3.6 release notes|Release Notes]]
|
[https://docs.moodle.org/36/en/Upgrading Upgrading to 3.6]
|-
!Moodle 3.6.1
|5 December 2018
|2018120301
| [[Moodle 3.6.1 release notes|Release Notes]]
|
|-
! Moodle 3.6.2
|14 January 2019
|2018120302
|[[Moodle 3.6.2 release notes|Release Notes]]
|
|-
!Moodle 3.6.3
|11 March 2019
|2018120303
|[[Moodle 3.6.3 release notes|Release Notes]]
|
|-
!Moodle 3.6.4
|13 May 2019
|2018120304
|[[Moodle 3.6.4 release notes|Release Notes]]
|
|-
!Moodle 3.6.5
|8th July 2019
|2018120305
|[[Moodle 3.6.5 release notes|Release Notes]]
|
|-
!Moodle 3.6.6
|9th September 2019
|2018120306
|[[Moodle 3.6.6 release notes|Release Notes]]
|
|-
!Moodle 3.6.7
| 11th November 2019
|2018120307
|[[Moodle 3.6.7 release notes|Release Notes]]
|
|-
!Moodle 3.6.8
|13th January 2020
|2018120308
|[[Moodle 3.6.8 release notes|Release Notes]]
|
|-
!Moodle 3.6.9
|9th March 2020
|2018120309
| [[Moodle 3.6.9 release notes|Release Notes]]
|
|-
!Moodle 3.6.10
|11th May 2020
|2018120310
|[[Moodle 3.6.10 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.6.x ended 11 November 2019 (12 months).
Bug fixes for security issues in 3.6.x ended 11 May 2020 (18 months).
==Moodle 3.5 (LTS)==
{| class="wikitable"
|-
!Moodle 3.5
|17 May 2018
|2018051700
|[[Moodle 3.5 release notes|Release Notes]]
|[https://docs.moodle.org/35/en/Upgrading Upgrading to 3.5]
|-
! Moodle 3.5.1
|9 July 2018
|2018051701
|[[Moodle 3.5.1 release notes|Release Notes]]
|
|-
!Moodle 3.5.2
|10 September 2018
|2018051702
|[[Moodle 3.5.2 release notes|Release Notes]]
|
|-
!Moodle 3.5.3
|12 November 2018
|2018051703
| [[Moodle 3.5.3 release notes|Release Notes]]
|
|-
! Moodle 3.5.4
|14 January 2019
|2018051704
|[[Moodle 3.5.4 release notes|Release Notes]]
|
|-
!Moodle 3.5.5
|11 March 2019
|2018051705
|[[Moodle 3.5.5 release notes|Release Notes]]
|
|-
!Moodle 3.5.6
|13 May 2019
|2018051706
|[[Moodle 3.5.6 release notes|Release Notes]]
|
|-
!Moodle 3.5.7
|8 July 2019
|2018051707
|[[Moodle 3.5.7 release notes|Release Notes]]
|
|-
!Moodle 3.5.8
|9 September 2019
|2018051708
|[[Moodle 3.5.8 release notes|Release Notes]]
|
|-
!Moodle 3.5.9
|11 November 2019
|2018051709
|[[Moodle 3.5.9 release notes|Release Notes]]
|
|-
!Moodle 3.5.10
|13 January 2020
|2018051710
| [[Moodle 3.5.10 release notes|Release Notes]]
|
|-
!Moodle 3.5.11
|9 March 2020
|2018051711
|[[Moodle 3.5.11 release notes|Release Notes]]
|
|-
!Moodle 3.5.12
|11 May 2020
|2018051712
| [[Moodle 3.5.12 release notes|Release Notes]]
|
|-
!Moodle 3.5.13
|13 July 2020
|2018051713
|[[Moodle 3.5.13 release notes|Release Notes]]
|
|-
!Moodle 3.5.14
| 14 September 2020
|2018051714
|[[Moodle 3.5.14 release notes|Release Notes]]
|
|-
!Moodle 3.5.15
|9 November 2020
|2018051715
|[[Moodle 3.5.15 release notes|Release Notes]]
|
|-
!Moodle 3.5.16
|18 January 2021
|2018051716
| [[Moodle 3.5.16 release notes|Release Notes]]
|
|-
!Moodle 3.5.17
|8 March 2021
| 2018051717
|[[Moodle 3.5.17 release notes|Release Notes]]
|
|-
!Moodle 3.5.18
| 10 May 2021
| 2018051718
|[[Moodle 3.5.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.5.x ended May 2019 (12 months).
Bug fixes for security issues in 3.5.x ended 10 May 2021 (36 months).
==Moodle 3.4==
{| class="wikitable"
|-
!Moodle 3.4
|13 November 2017
|2017111300
|[[Moodle 3.4 release notes|Release Notes]]
|
[https://docs.moodle.org/34/en/Upgrading Upgrading to 3.4]
|-
! Moodle 3.4.1
|15 January 2018
|2017111301
|[[Moodle 3.4.1 release notes|Release Notes]]
|
|-
!Moodle 3.4.2
|19 March 2018
|2017111302
|[[Moodle 3.4.2 release notes|Release Notes]]
|
|-
!Moodle 3.4.3
|17 May 2018
|2017111303
|[[Moodle 3.4.3 release notes|Release Notes]]
|
|-
! Moodle 3.4.4
|9 July 2018
|2017111304
|[[Moodle 3.4.4 release notes|Release Notes]]
|
|-
!Moodle 3.4.5
|10 September 2018
|2017111305
|[[Moodle 3.4.5 release notes|Release Notes]]
|
|-
!Moodle 3.4.6
|12 November 2018
|2017111306
| [[Moodle 3.4.6 release notes|Release Notes]]
|
|-
! Moodle 3.4.7
|14 January 2019
|2017111307
|[[Moodle 3.4.7 release notes|Release Notes]]
|
|-
!Moodle 3.4.8
|11 March 2019
|2017111308
|[[Moodle 3.4.8 release notes|Release Notes]]
|
|-
!Moodle 3.4.9
|13 May 2019
|2017111309
| [[Moodle 3.4.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.4.x ended 12 November 2018 (12 months).
Bug fixes for security issues in 3.4.x ended 13 May 2019 (18 months).
==Moodle 3.3==
{| class="wikitable"
|-
!Moodle 3.3
|15 May 2017
|2017051500
|[[Moodle 3.3 release notes|Release Notes]]
|
[https://docs.moodle.org/33/en/Upgrading Upgrading to 3.3]
|-
!Moodle 3.3.1
|10 July 2017
|2017051501
|[[Moodle 3.3.1 release notes|Release Notes]]
|
|-
!Moodle 3.3.2
|11 September 2017
|2017051502
|[[Moodle 3.3.2 release notes|Release Notes]]
|
|-
!Moodle 3.3.3
|13 November 2017
|2017051503
| [[Moodle 3.3.3 release notes|Release Notes]]
|
|-
! Moodle 3.3.4
|15 January 2018
|2017051504
|[[Moodle 3.3.4 release notes|Release Notes]]
|
|-
!Moodle 3.3.5
|19 March 2018
|2017051505
|[[Moodle 3.3.5 release notes|Release Notes]]
|
|-
!Moodle 3.3.6
|17 May 2018
|2017051506
|[[Moodle 3.3.6 release notes|Release Notes]]
|
|-
! Moodle 3.3.7
|9 July 2018
|2017051507
|[[Moodle 3.3.7 release notes|Release Notes]]
|
|-
!Moodle 3.3.8
|10 September 2018
|2017051508
|[[Moodle 3.3.8 release notes|Release Notes]]
|
|-
! Moodle 3.3.9
|12 November 2018
|2017051509
|[[Moodle 3.3.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.3.x ended 17 May 2018 (12 months).
Bug fixes for security issues in 3.3.x ended 12 November 2018 (18 months).
==Moodle 3.2==
{| class="wikitable"
|-
!Moodle 3.2
| 5 December 2016
|2016120500
|[[Moodle 3.2 release notes|Release Notes]]
|[https://docs.moodle.org/32/en/Upgrading Upgrading to 3.2]
|-
!Moodle 3.2.1
|9 January 2017
|2016120501
|[[Moodle 3.2.1 release notes|Release Notes]]
|
|-
!Moodle 3.2.2
|13 March 2017
|2016120502
|[[Moodle 3.2.2 release notes|Release Notes]]
|
|-
!Moodle 3.2.3
|8 May 2017
|2016120503
|[[Moodle 3.2.3 release notes|Release Notes]]
|
|-
!Moodle 3.2.4
|10 July 2017
|2016120504
|[[Moodle 3.2.4 release notes|Release Notes]]
|
|-
!Moodle 3.2.5
|11 September 2017
|2016120505
|[[Moodle 3.2.5 release notes|Release Notes]]
|
|-
!Moodle 3.2.6
|13 November 2017
|2016120506
| [[Moodle 3.2.6 release notes|Release Notes]]
|
|-
! Moodle 3.2.7
|15 January 2018
|2016120507
|[[Moodle 3.2.7 release notes|Release Notes]]
|
|-
!Moodle 3.2.8
|19 March 2018
|2016120508
|[[Moodle 3.2.8 release notes|Release Notes]]
|
|-
!Moodle 3.2.9
|17 May 2018
|2016120509
| [[Moodle 3.2.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.2.x ended 13 November 2017 (12 months).
Bug fixes for security issues in 3.2.x ended 17 May 2018 (18 months).
==Moodle 3.1 (LTS)==
{| class="wikitable"
|-
!Moodle 3.1
|23 May 2016
|2016052300
|[[Moodle 3.1 release notes|Release Notes]]
|
[https://docs.moodle.org/31/en/Upgrading Upgrading to 3.1]
|-
!Moodle 3.1.1
|11 July 2016
|2016052301
|[[Moodle 3.1.1 release notes|Release Notes]]
|
|-
!Moodle 3.1.2
|12 September 2016
|2016052302
|[[Moodle 3.1.2 release notes|Release Notes]]
|
|-
!Moodle 3.1.3
|14 November 2016
|2016052303
|[[Moodle 3.1.3 release notes|Release Notes]]
|
|-
!Moodle 3.1.4
|9 January 2017
|2016052304
|[[Moodle 3.1.4 release notes|Release Notes]]
|
|-
!Moodle 3.1.5
|13 March 2017
|2016052305
|[[Moodle 3.1.5 release notes|Release Notes]]
|
|-
!Moodle 3.1.6
|8 May 2017
|2016052306
|[[Moodle 3.1.6 release notes|Release Notes]]
|
|-
!Moodle 3.1.7
|10 July 2017
|2016052307
|[[Moodle 3.1.7 release notes|Release Notes]]
|
|-
!Moodle 3.1.8
|11 September 2017
|2016052308
|[[Moodle 3.1.8 release notes|Release Notes]]
|
|-
!Moodle 3.1.9
|13 November 2017
|2016052309
|[[Moodle 3.1.9 release notes|Release Notes]]
|
|-
!Moodle 3.1.10
|15 January 2018
|2016052310
|[[Moodle 3.1.10 release notes|Release Notes]]
|
|-
! Moodle 3.1.11
|19 March 2018
|2016052311
|[[Moodle 3.1.11 release notes|Release Notes]]
|
|-
!Moodle 3.1.12
|17 May 2018
|2016052312
|[[Moodle 3.1.12 release notes|Release Notes]]
|
|-
!Moodle 3.1.13
|9 July 2018
|2016052313
|[[Moodle 3.1.13 release notes|Release Notes]]
|
|-
!Moodle 3.1.14
|10 September 2018
|2016052314
|[[Moodle 3.1.14 release notes|Release Notes]]
|
|-
! Moodle 3.1.15
|12 November 2018
|2016052315
|[[Moodle 3.1.15 release notes|Release Notes]]
|
|-
!Moodle 3.1.16
|14 January 2019
|2016052316
|[[Moodle 3.1.16 release notes|Release Notes]]
|
|-
! Moodle 3.1.17
|11 March 2019
| 2016052317
|[[Moodle 3.1.17 release notes|Release Notes]]
|
|-
!Moodle 3.1.18
|13 May 2019
|2016052318
|[[Moodle 3.1.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.1.x ended 8 May 2017 (12 months).
Bug fixes for security issues in 3.1.x ended 13 May 2019 (36 months).
==Moodle 3.0==
{| class="wikitable"
|-
!Moodle 3.0
|16 November 2015
|2015111600
|[[Moodle 3.0 release notes|Release Notes]]
|[https://docs.moodle.org/30/en/Upgrading Upgrading to 3.0]
|-
!Moodle 3.0.1
|21 December 2015
|2015111601
| [[Moodle 3.0.1 release notes|Release Notes]]
|
|-
! Moodle 3.0.2
|11 January 2016
|2015111602
|[[Moodle 3.0.2 release notes|Release Notes]]
|
|-
!Moodle 3.0.3
|14 March 2016
|2015111603
|[[Moodle 3.0.3 release notes|Release Notes]]
|
|-
!Moodle 3.0.4
|9 May 2016
|2015111604
|[[Moodle 3.0.4 release notes|Release Notes]]
|
|-
!Moodle 3.0.5
|11 July 2016
|2015111605
|[[Moodle 3.0.5 release notes|Release Notes]]
|
|-
!Moodle 3.0.6
|12 September 2016
|2015111606
|[[Moodle 3.0.6 release notes|Release Notes]]
|
|-
!Moodle 3.0.7
|14 November 2016
|2015111607
|[[Moodle 3.0.7 release notes|Release Notes]]
|
|-
!Moodle 3.0.8
|9 January 2017
|2015111608
|[[Moodle 3.0.8 release notes|Release Notes]]
|
|-
!Moodle 3.0.9
|13 March 2017
|2015111609
|[[Moodle 3.0.9 release notes|Release Notes]]
|
|-
!Moodle 3.0.10
|8 May 2017
|2015111610
|[[Moodle 3.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.0.x ended 14 November 2016 (12 months).
Bug fixes for security issues in 3.0.x ended 8 May 2017 (18 months).
==Moodle 2.9==
{| class="wikitable"
|-
!Moodle 2.9
| 11 May 2015
|2015051100
|[[Moodle 2.9 release notes|Release Notes]]
| [https://docs.moodle.org/29/en/Upgrading_to_Moodle_2.9 Upgrading to 2.9]
|-
! Moodle 2.9.1
|6 July 2015
|2015051101
|[[Moodle 2.9.1 release notes|Release Notes]]
|
|-
!Moodle 2.9.2
|14 September 2015
|2015051102
| [[Moodle 2.9.2 release notes|Release Notes]]
|
|-
!Moodle 2.9.3
|9 November 2015
|2015051103
| [[Moodle 2.9.3 release notes|Release Notes]]
|
|-
! Moodle 2.9.4
|11 January 2016
|2015051104
|[[Moodle 2.9.4 release notes|Release Notes]]
|
|-
!Moodle 2.9.5
|14 March 2016
|2015051105
|[[Moodle 2.9.5 release notes|Release Notes]]
|
|-
!Moodle 2.9.6
|9 May 2016
|2015051106
|[[Moodle 2.9.6 release notes|Release Notes]]
|
|-
!Moodle 2.9.7
|11 July 2016
|2015051107
|[[Moodle 2.9.7 release notes|Release Notes]]
|
|-
!Moodle 2.9.8
|12 September 2016
|2015051108
|[[Moodle 2.9.8 release notes|Release Notes]]
|
|-
! Moodle 2.9.9
|14 November 2016
|2015051109
|[[Moodle 2.9.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.9.x ended 9 May 2016 (12 months).
Bug fixes for security issues in 2.9.x ended 14 November 2016 (18 months).
==Moodle 2.8==
{| class="wikitable"
|-
!Moodle 2.8
|10 November 2014
|2014111000
| [[Moodle 2.8 release notes|Release Notes]]
|[https://docs.moodle.org/28/en/Upgrading_to_Moodle_2.8 Upgrading to 2.8]
|-
!Moodle 2.8.1
|13 November 2014
|2014111001
| [[Moodle 2.8.1 release notes|Release Notes]]
|
|-
!Moodle 2.8.2
|12 January 2015
|2014111002
| [[Moodle 2.8.2 release notes|Release Notes]]
|
|-
!Moodle 2.8.3
|2 February 2015
|2014111003
|[[Moodle 2.8.3 release notes|Release Notes]]
|
|-
!Moodle 2.8.4
|9 March 2015
|2014111004
|[[Moodle 2.8.4 release notes|Release Notes]]
|
|-
!Moodle 2.8.5
|10 March 2015
|2014111005
|[[Moodle 2.8.5 release notes|Release Notes]]
|
|-
!Moodle 2.8.6
|11 May 2015
|2014111006
|[[Moodle 2.8.6 release notes|Release Notes]]
|
|-
! Moodle 2.8.7
|6 July 2015
|2014111007
|[[Moodle 2.8.7 release notes|Release Notes]]
|
|-
!Moodle 2.8.8
|14 September 2015
|2014111008
| [[Moodle 2.8.8 release notes|Release Notes]]
|
|-
!Moodle 2.8.9
|9 November 2015
|2014111009
|[[Moodle 2.8.9 release notes|Release Notes]]
|
|-
!Moodle 2.8.10
|11 January 2016
|2014111010
|[[Moodle 2.8.10 release notes|Release Notes]]
|
|-
!Moodle 2.8.11
|14 March 2016
|2014111011
|[[Moodle 2.8.11 release notes|Release Notes]]
|
|-
!Moodle 2.8.12
|9 May 2016
|2014111012
| [[Moodle 2.8.12 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.8.x ended 9 November 2015 (12 months).
Bug fixes for security issues in 2.8.x ended 9 May 2016 (18 months).
==Moodle 2.7 (LTS)==
{| class="wikitable"
|-
!Moodle 2.7
| 12 May 2014
|2014051200
|[[Moodle 2.7 release notes|Release Notes]]
|[https://docs.moodle.org/27/en/Upgrading_to_Moodle_2.7 Upgrading to 2.7]
|-
! Moodle 2.7.1
|14 July 2014
|2014051201
|[[Moodle 2.7.1 release notes|Release Notes]]
|
|-
!Moodle 2.7.2
|8 September 2014
|2014051202
|[[Moodle 2.7.2 release notes|Release Notes]]
|
|-
!Moodle 2.7.3
|10 November 2014
|2014051203
| [[Moodle 2.7.3 release notes|Release Notes]]
|
|-
!Moodle 2.7.4
|12 January 2015
|2014051204
| [[Moodle 2.7.4 release notes|Release Notes]]
|
|-
!Moodle 2.7.5
|2 February 2015
|2014051205
|[[Moodle 2.7.5 release notes|Release Notes]]
|
|-
!Moodle 2.7.6
|9 March 2015
|2014051206
|[[Moodle 2.7.6 release notes|Release Notes]]
|
|-
!Moodle 2.7.7
|10 March 2015
|2014051207
|[[Moodle 2.7.7 release notes|Release Notes]]
|
|-
!Moodle 2.7.8
|11 May 2015
|2014051208
|[[Moodle 2.7.8 release notes|Release Notes]]
|
|-
!Moodle 2.7.9
|6 July 2015
|2014051209
|[[Moodle 2.7.9 release notes|Release Notes]]
|
|-
!Moodle 2.7.10
| 14 September 2015
|2014051210
|[[Moodle 2.7.10 release notes|Release Notes]]
|
|-
!Moodle 2.7.11
|9 November 2015
|2014051211
|[[Moodle 2.7.11 release notes|Release Notes]]
|
|-
!Moodle 2.7.12
|11 January 2016
|2014051212
|[[Moodle 2.7.12 release notes|Release Notes]]
|
|-
!Moodle 2.7.13
|14 March 2016
|2014051213
|[[Moodle 2.7.13 release notes|Release Notes]]
|
|-
!Moodle 2.7.14
|9 May 2016
|2014051214
| [[Moodle 2.7.14 release notes|Release Notes]]
|
|-
!Moodle 2.7.15
|11 July 2016
|2014051215
|[[Moodle 2.7.15 release notes|Release Notes]]
|
|-
!Moodle 2.7.16
|12 September 2016
|2014051216
|[[Moodle 2.7.16 release notes|Release Notes]]
|
|-
!Moodle 2.7.17
|14 November 2016
|2014051217
|[[Moodle 2.7.17 release notes|Release Notes]]
|
|-
!Moodle 2.7.18
|9 January 2017
|2014051218
|[[Moodle 2.7.18 release notes|Release Notes]]
|
|-
!Moodle 2.7.19
|13 March 2017
|2014051219
|[[Moodle 2.7.19 release notes|Release Notes]]
|
|-
!Moodle 2.7.20
|8 May 2017
|2014051220
| [[Moodle 2.7.20 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.7.x ended 11 May 2015 (12 months).
Bug fixes for security issues in 2.7.x ended 8 May 2017 (36 months).
==Moodle 2.6==
{| class="wikitable"
|-
!Moodle 2.6
|18 November 2013
|2013111800
|[[Moodle 2.6 release notes|Release Notes]]
|[https://docs.moodle.org/26/en/Upgrading_to_Moodle_2.6 Upgrading to 2.6]
|-
!Moodle 2.6.1
|13 January 2014
| 2013111801
| [[Moodle 2.6.1 release notes|Release Notes]]
|
|-
!Moodle 2.6.2
|10 March 2014
|2013111802
|[[Moodle 2.6.2 release notes|Release Notes]]
|
|-
!Moodle 2.6.3
|12 May 2014
|2013111803
|[[Moodle 2.6.3 release notes|Release Notes]]
|
|-
!Moodle 2.6.4
|14 July 2014
|2013111804
|[[Moodle 2.6.4 release notes|Release Notes]]
|
|-
!Moodle 2.6.5
|8 September 2014
|2013111805
|[[Moodle 2.6.5 release notes|Release Notes]]
|
|-
!Moodle 2.6.6
|10 November 2014
|2013111806
|[[Moodle 2.6.6 release notes|Release Notes]]
|
|-
!Moodle 2.6.7
|12 January 2015
|2013111807
|[[Moodle 2.6.7 release notes|Release Notes]]
|
|-
! Moodle 2.6.8
|2 February 2015
|2013111808
|[[Moodle 2.6.8 release notes|Release Notes]]
|
|-
! Moodle 2.6.9
|9 March 2015
|2013111809
|[[Moodle 2.6.9 release notes|Release Notes]]
|
|-
!Moodle 2.6.10
|10 March 2015
|2013111810
| [[Moodle 2.6.10 release notes|Release Notes]]
|
|-
!Moodle 2.6.11
|11 May 2015
|2013111811
|[[Moodle 2.6.11 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 2.6.x ended 10 November 2014 (12 months).
Bug fixes for security issues in 2.6.x ended 11 May 2015 (18 months).
==Moodle 2.5==
{| class="wikitable"
|-
!Moodle 2.5
| 14 May 2013
|2013051400
|[[Moodle 2.5 release notes|Release Notes]]
| [https://docs.moodle.org/25/en/Upgrading_to_Moodle_2.5 Upgrading to 2.5]
|-
! Moodle 2.5.1
|8 July 2013
|2013051401
|[[Moodle 2.5.1 release notes|Release Notes]]
|
|-
!Moodle 2.5.2
|9 September 2013
|2013051402
|[[Moodle 2.5.2 release notes|Release Notes]]
|
|-
!Moodle 2.5.3
|11 November 2013
|2013051403
|[[Moodle 2.5.3 release notes|Release Notes]]
|
|-
!Moodle 2.5.4
|13 January 2014
| 2013051404
| [[Moodle 2.5.4 release notes|Release Notes]]
|
|-
!Moodle 2.5.5
|10 March 2014
|2013051405
|[[Moodle 2.5.5 release notes|Release Notes]]
|
|-
!Moodle 2.5.6
|12 May 2014
|2013051406
|[[Moodle 2.5.6 release notes|Release Notes]]
|
|-
!Moodle 2.5.7
|14 July 2014
|2013051407
|[[Moodle 2.5.7 release notes|Release Notes]]
|
|-
!Moodle 2.5.8
|8 September 2014
|2013051408
|[[Moodle 2.5.8 release notes|Release Notes]]
|
|-
! Moodle 2.5.9
| 10 November 2014
|2013051409
|[[Moodle 2.5.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.5.x ended May 2014 (12 months).
Bug fixes for security issues in 2.5.x ended 10 November 2014 (18 months).
==Moodle 2.4==
{| class="wikitable"
|-
! Moodle 2.4
|3 December 2012
|2012120300
|[[Moodle 2.4 release notes|Release Notes]]
|[https://docs.moodle.org/24/en/Upgrading_to_Moodle_2.4 Upgrading to 2.4]
|-
! Moodle 2.4.1
|14 January 2013
|2012120301
|[[Moodle 2.4.1 release notes|Release Notes]]
|
|-
!Moodle 2.4.2
|11 March 2013
|2012120302
|[[Moodle 2.4.2 release notes|Release Notes]]
|
|-
!Moodle 2.4.3
|18 March 2013
|2012120303
|[[Moodle 2.4.3 release notes|Release Notes]]
|
|-
!Moodle 2.4.4
|14 May 2013
|2012120304
|[[Moodle 2.4.4 release notes|Release Notes]]
|
|-
!Moodle 2.4.5
|8 July 2013
|2012120305
|[[Moodle 2.4.5 release notes|Release Notes]]
|
|-
!Moodle 2.4.6
|9 September 2013
|2012120306
|[[Moodle 2.4.6 release notes|Release Notes]]
|
|-
!Moodle 2.4.7
|11 November 2013
|2012120307
| [[Moodle 2.4.7 release notes|Release Notes]]
|
|-
! Moodle 2.4.8
|13 January 2014
|2012120308
|[[Moodle 2.4.8 release notes|Release Notes]]
|
|-
!Moodle 2.4.9
|10 March 2014
|2012120309
|[[Moodle 2.4.9 release notes|Release Notes]]
|
|-
!Moodle 2.4.10
|12 May 2014
|2012120310
| [[Moodle 2.4.10 release notes|Release Notes]]
|
|-
!Moodle 2.4.11
|14 July 2014
|2012120311
|[[Moodle 2.4.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.4.x ended December 2013 (12 months).
Bug fixes for security issues in 2.4.x ended June 2014 (18 months).
==Moodle 2.3==
{| class="wikitable"
|-
!Moodle 2.3
|25 June 2012
|2012062500
|[[Moodle 2.3 release notes|Release Notes]]
| [https://docs.moodle.org/23/en/Upgrading_to_Moodle_2.3 Upgrading to 2.3]
|-
!Moodle 2.3.1
|9 July 2012
|2012062501
|[[Moodle 2.3.1 release notes|Release Notes]]
|
|-
! Moodle 2.3.2
|10 September 2012
|2012062502
|[[Moodle 2.3.2 release notes|Release Notes]]
|
|-
!Moodle 2.3.3
|12 November 2012
|2012062503
|[[Moodle 2.3.3 release notes|Release Notes]]
|
|-
! Moodle 2.3.4
|14 January 2013
|2012062504
|[[Moodle 2.3.4 release notes|Release Notes]]
|
|-
!Moodle 2.3.5
|11 March 2013
|2012062505
|[[Moodle 2.3.5 release notes|Release Notes]]
|
|-
!Moodle 2.3.6
|18 March 2013
|2012062506
|[[Moodle 2.3.6 release notes|Release Notes]]
|
|-
!Moodle 2.3.7
|14 May 2013
|2012062507
|[[Moodle 2.3.7 release notes|Release Notes]]
|
|-
!Moodle 2.3.8
|8 July 2013
|2012062508
|[[Moodle 2.3.8 release notes|Release Notes]]
|
|-
!Moodle 2.3.9
|9 September 2013
|2012062509
|[[Moodle 2.3.9 release notes|Release Notes]]
|
|-
! Moodle 2.3.10
|11 November 2013
|2012062510
|[[Moodle 2.3.10 release notes|Release Notes]]
|
|-
!Moodle 2.3.11
|13 January 2014
|2012062511
|[[Moodle 2.3.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.3.x ended June 2013 (12 months).
Bug fixes for security issues in 2.3.x ended December 2013 (18 months).
==Moodle 2.2==
{| class="wikitable"
|-
! Moodle 2.2
|5 December 2011
|2011120500
|[[Moodle 2.2 release notes|Release Notes]]
|[https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 Upgrading to 2.2]
|-
!Moodle 2.2.1
|9 January 2012
|2011120501
|[[Moodle 2.2.1 release notes|Release Notes]]
|
|-
!Moodle 2.2.2
|12 March 2012
|2011120502
|[[Moodle 2.2.2 release notes|Release Notes]]
|
|-
!Moodle 2.2.3
|14 May 2012
|2011120503
|[[Moodle 2.2.3 release notes|Release Notes]]
|
|-
! Moodle 2.2.4
|9 July 2012
|2011120504
|[[Moodle 2.2.4 release notes|Release Notes]]
|
|-
!Moodle 2.2.5
|10 September 2012
|2011120505
|[[Moodle 2.2.5 release notes|Release Notes]]
|
|-
!Moodle 2.2.6
|12 November 2012
|2011120506
| [[Moodle 2.2.6 release notes|Release Notes]]
|
|-
! Moodle 2.2.7
|14 January 2013
|2011120507
|[[Moodle 2.2.7 release notes|Release Notes]]
|
|-
!Moodle 2.2.8
|11 March 2013
|2011120508
|[[Moodle 2.2.8 release notes|Release Notes]]
|
|-
!Moodle 2.2.9
|18 March 2013
|2011120509
|[[Moodle 2.2.9 release notes|Release Notes]]
|
|-
!Moodle 2.2.10
|14 May 2013
| 2011120510
|[[Moodle 2.2.10 release notes|Release Notes]]
|
|-
!Moodle 2.2.11
|8 July 2013
|2011120511
|[[Moodle 2.2.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.2.x ended December 2012 (12 months).
Bug fixes for security issues in 2.2.x ended June 2013 (18 months).
==Moodle 2.1==
{| class="wikitable"
|-
!Moodle 2.1
| 1 July 2011
|2011070100
|[[Moodle 2.1 release notes|Release Notes]]
|[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to 2.1]
|-
! Moodle 2.1.1
|1 August 2011
|2011070101
| [[Moodle 2.1.1 release notes|Release Notes]]
|
|-
!Moodle 2.1.2
|10 October 2011
|2011070102
|[[Moodle 2.1.2 release notes|Release Notes]]
|
|-
!Moodle 2.1.3
|28 November 2011
|2011070103
|[[Moodle 2.1.3 release notes|Release Notes]]
|
|-
!Moodle 2.1.4
|9 January 2012
|2011070104
|[[Moodle 2.1.4 release notes|Release Notes]]
|
|-
!Moodle 2.1.5
|12 March 2012
|2011070105
|[[Moodle 2.1.5 release notes|Release Notes]]
|
|-
!Moodle 2.1.6
|14 May 2012
|2011070106
|[[Moodle 2.1.6 release notes|Release Notes]]
|
|-
! Moodle 2.1.7
|9 July 2012
|2011070107
|[[Moodle 2.1.7 release notes|Release Notes]]
|
|-
!Moodle 2.1.8
|10 September 2012
|2011070108
|[[Moodle 2.1.8 release notes|Release Notes]]
|
|-
!Moodle 2.1.9
|12 November 2012
|2011070109
|[[Moodle 2.1.9 release notes|Release Notes]]
|
|-
!Moodle 2.1.10
|14 January 2013
|2011070110
|[[Moodle 2.1.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.1.x ended June 2012 (12 months).
Bug fixes for security issues in 2.1.x ended December 2012 (18 months).
==Moodle 2.0==
{| class="wikitable"
|-
!Moodle 2.0
|24 November 2010
|2010112400
| [[Moodle 2.0 release notes|Release Notes]]
|[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to 2.0]
|-
!Moodle 2.0.1
|25 December 2010
|2010122500
|[[Moodle 2.0.1 release notes|Release Notes]]
|
|-
!Moodle 2.0.2
|21 February 2011
|2011022100
|[[Moodle 2.0.2 release notes|Release Notes]]
|
|-
!Moodle 2.0.3
|5 May 2011
|2011033003
|[[Moodle 2.0.3 release notes|Release Notes]]
|
|-
! Moodle 2.0.4
|1 August 2011
|2011033004
| [[Moodle 2.0.4 release notes|Release Notes]]
|
|-
!Moodle 2.0.5
|10 October 2011
|2011033005
|[[Moodle 2.0.5 release notes|Release Notes]]
|
|-
!Moodle 2.0.6
|28 November 2011
|2011033006
|[[Moodle 2.0.6 release notes|Release Notes]]
|
|-
!Moodle 2.0.7
|9 January 2012
|2011033007
|[[Moodle 2.0.7 release notes|Release Notes]]
|
|-
!Moodle 2.0.8
|12 March 2012
|2011033008
|[[Moodle 2.0.8 release notes|Release Notes]]
|
|-
!Moodle 2.0.9
|14 May 2012
|2011033009
|[[Moodle 2.0.9 release notes|Release Notes]]
|
|-
!Moodle 2.0.10
|9 July 2012
|2011033010
|[[Moodle 2.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.0.x ended December 2011 (12 months).
Bug fixes for security issues in 2.0.x ended June 2012 (18 months).
==Moodle 1.9==
{| class="wikitable"
|-
!Moodle 1.9
|3 March 2008
|2007101509
|[[Moodle 1.9 release notes|Release Notes]]
|[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to 1.9]
|-
!Moodle 1.9.1
|15 May 2008
| 2007101512
|[[Moodle 1.9.1 release notes|Release Notes]]
|
|-
! Moodle 1.9.2
|11 July 2008
|2007101520
|[[Moodle 1.9.2 release notes|Release Notes]]
|
|-
!Moodle 1.9.3
|15 October 2008
|2007101530
|[[Moodle 1.9.3 release notes|Release Notes]]
|
|-
!Moodle 1.9.4
|28 January 2009
|2007101540
|[[Moodle 1.9.4 release notes|Release Notes]]
|
|-
!Moodle 1.9.5
|13 May 2009
|2007101550
|[[Moodle 1.9.5 release notes|Release Notes]]
|
|-
!Moodle 1.9.6
|21 October 2009
|2007101560
|[[Moodle 1.9.6 release notes|Release Notes]]
|
|-
!Moodle 1.9.7
|25 November 2009
|2007101570
|[[Moodle 1.9.7 release notes|Release Notes]]
|
|-
!Moodle 1.9.8
|25 March 2010
|2007101580.00
|[[Moodle 1.9.8 release notes|Release Notes]]
|
|-
! Moodle 1.9.9
| 8 June 2010
| 2007101590.00
| [[Moodle 1.9.9 release notes|Release Notes]]
|
|-
!Moodle 1.9.10
|25 October 2010
|2007101591.00
|
[[Moodle 1.9.10 release notes|Release Notes]]
|
|-
!Moodle 1.9.11
|21 February 2011
|2007101591.02
|[[Moodle 1.9.11 release notes|Release Notes]]
|
|-
! Moodle 1.9.12
|10 May 2011
|2007101591.03
|[[Moodle 1.9.12 release notes|Release Notes]]
|
|-
!Moodle 1.9.13
|1 August 2011
|2007101591.04
|[[Moodle 1.9.13 release notes|Release Notes]]
|
|-
!Moodle 1.9.14
|10 October 2011
|2007101591.06
|
[[Moodle 1.9.14 release notes|Release Notes]]
|
|-
!Moodle 1.9.15
|28 November 2011
| 2007101591.07
| [[Moodle 1.9.15 release notes|Release Notes]]
|
|-
!Moodle 1.9.16
|9 January 2012
|2007101591.10
|[[Moodle 1.9.16 release notes|Release Notes]]
|
|-
! Moodle 1.9.17
|12 March 2012
|2007101591.12
|[[Moodle 1.9.17 release notes|Release Notes]]
|
|-
!Moodle 1.9.18
|14 May 2012
|2007101591.16
|[[Moodle 1.9.18 release notes|Release Notes]]
|
|-
! Moodle 1.9.19
|9 July 2012
|2007101592.00
|[[Moodle 1.9.19 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 1.9.x has ended June 2011 (3.5 years).
Bug fixes for security issues in 1.9.x by Moodle HQ ended June 2012 (4.5 years).
Bug fixes for security issues in 1.9.19+ branch by [http://catalyst.net.nz Catalyst IT] ended [http://moodle.org/mod/forum/discuss.php?d=199706 Dec 2013] (6 years).
==Moodle 1.8 ==
*[[Moodle 1.8 release notes|Moodle 1.8]] - 30 March 2007
*[[Moodle 1.8.1 release notes|Moodle 1.8.1]] - 14 June 2007
*[[Moodle 1.8.2 release notes|Moodle 1.8.2]] - 8 July 2007
*[[Moodle 1.8.3 release notes|Moodle 1.8.3]] - 11 October 2007
*[[Moodle 1.8.4 release notes|Moodle 1.8.4]] - 11 January 2008
*[[Moodle 1.8.5 release notes|Moodle 1.8.5]] - 8 April 2008
*[[Moodle 1.8.6 release notes|Moodle 1.8.6]] - 11 July 2008
*[[Moodle 1.8.7 release notes|Moodle 1.8.7]] - 15 October 2008
*[[Moodle 1.8.8 release notes|Moodle 1.8.8]] - 28 January 2009
*[[Moodle 1.8.9 release notes|Moodle 1.8.9]] - 15 May 2009
*[[Moodle 1.8.10 release notes|Moodle 1.8.10]] - 26 October 2009
*[[Moodle 1.8.11 release notes|Moodle 1.8.11]] - 25 November 2009
*[[Moodle 1.8.12 release notes|Moodle 1.8.12]] - 27 March 2010
*[[Moodle 1.8.13 release notes|Moodle 1.8.13]] - 8 June 2010
*[[Moodle 1.8.14 release notes|Moodle 1.8.14]] - 3 December 2010
*Support has ended

==Moodle 1.7==
*[[Moodle 1.7 release notes|Moodle 1.7]] - 7 November 2006
*[[Moodle 1.7.1 release notes|Moodle 1.7.1]] - 17 January 2007
*[[Moodle 1.7.2 release notes|Moodle 1.7.2]] - 30 March 2007
*[[Moodle 1.7.3 release notes|Moodle 1.7.3]] - 11 October 2007
*[[Moodle 1.7.4 release notes|Moodle 1.7.4]] - 11 January 2008
*[[Moodle 1.7.5 release notes|Moodle 1.7.5]] - 11 July 2008
*[[Moodle 1.7.6 release notes|Moodle 1.7.6]] - 15 October 2008
*[[Moodle 1.7.7 release notes|Moodle 1.7.7]] - 28 January 2009
*Support has ended
==Moodle 1.6==
*[[Moodle 1.6 release notes|Moodle 1.6]] - 20 June 2006
*[[Moodle 1.6.1 release notes|Moodle 1.6.1]] - 20 July 2006
*[[Moodle 1.6.2 release notes|Moodle 1.6.2]] - 12 September 2006
*[[Moodle 1.6.3 release notes|Moodle 1.6.3]] - 10 October 2006
*[[Moodle 1.6.4 release notes|Moodle 1.6.4]] - 17 January 2007
*[[Moodle 1.6.5 release notes|Moodle 1.6.5]] - 30 March 2007
*Moodle 1.6.6 - 11 January 2008
*Moodle 1.6.7 - 11 July 2008
*[[Moodle 1.6.8 release notes|Moodle 1.6.8]] - 15 October 2008
*[[Moodle 1.6.9 release notes|Moodle 1.6.9]] - 28 January 2009
* Support has ended
==Moodle 1.5==
*[[Moodle 1.5 release notes|Moodle 1.5]] - 5 June 2005
*[[Moodle 1.5.1 release notes|Moodle 1.5.1]] - 8 July 2005
*[[Moodle 1.5.2 release notes|Moodle 1.5.2]] - 16 July 2005
*[[Moodle 1.5.3 release notes|Moodle 1.5.3]] - 11 November 2005
*[[Moodle 1.5.4 release notes|Moodle 1.5.4]] - 21 May 2006
*Support has ended
==Moodle 1.4==
*Moodle 1.4 - 31 August 2004
*Moodle 1.4.1 - 12 September 2004
*Moodle 1.4.2 - 5 November 2004
*Moodle 1.4.3 - 21 December 2004
*Moodle 1.4.4 - 7 March 2005
*[[Moodle 1.4.5 release notes|Moodle 1.4.5]] - 7 May 2005
*Support has ended
==Moodle 1.3==
*Moodle 1.3 - 25 May 2004
* Moodle 1.3.1 - 4 June 2004
*Moodle 1.3.2 - 9 July 2004
*Moodle 1.3.3 - 16 July 2004
* Moodle 1.3.4 - 11 August 2004
*Moodle 1.3.5 - 9 September 2004
*Support has ended
==Moodle 1.2==
*Moodle 1.2 - 20 March 2004
*Moodle 1.2.1 - 25 March 2004
*Support has ended
==Moodle 1.1==
*Moodle 1.1 - 29 August 2003
*Moodle 1.1.1 - 11 September 2003
*Support has ended
== Moodle 1.0==
*Moodle 1.0 - 20 August 2002
*Moodle 1.0.1 - 26 August 2002
*Moodle 1.0.2 - 2 September 2002
*Moodle 1.0.3 - 5 September 2002
*Moodle 1.0.4 - 10 September 2002
*Moodle 1.0.5 - 27 September 2002
* Moodle 1.0.6 - 26 October 2002
::1.0.6.1 - 6 November 2002
::1.0.6.2 - 11 November 2002
::1.0.6.3 - 14 November 2002
::1.0.6.4 - 25 November 2002
*Moodle 1.0.7 - 9 December 2002
*Moodle 1.0.8 - 7 January 2003
*Moodle 1.0.9 - 30 May 2003
*Support has ended
==See also==
*[[Roadmap]] - future versions
*[[Moodle versions]] - an explanation of how our versions work plus version numbers for each release (for $plugin->requires)
[[Category:Release notes]]
[[Category:Core development]]
[[fr:Historique des versions]]
[[es:dev/Historia de las versiones]]
[[de:Versionshistorie]]

Releases

2022-05-09T01:47:11Z

Abgreeve: /* Moodle 3.10 table padding */

This page lists all official releases of Moodle, grouped by branch in reverse chronological order.
==Version support==
From Moodle 2.6 onwards, the end of support, both general and security, happens the second Monday of May and November, observing the 12, 18... month periods, no matter if the major release date was moved or not.

The most recent [https://en.wikipedia.org/wiki/Long-term_support long-term support release (LTS)] version is Moodle 3.9.
{| class="wikitable" border="1px solid #dee2e6;"
|-
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Version
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Release status
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Initial release
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:rgba(0, 0, 0, 0.05);" | General support ends
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Security support ends
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.9 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 15 June 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 10 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 November 2023 (ext 6M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.11
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 17 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 14 Nov 2022 (ext 6M)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 Nov 2023 (ext 12M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |4.0
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |19 April 2022
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |8 May 2023
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |13 November 2023
|-
|4.1 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
|November 2022
|November 2023
|November 2025
|}
[[Image:401_release_graph.png|alt=Release graph]]

Release graph key:
{| class="wikitable" border="1px solid #dee2e6;"
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Currently supported stable releases.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | Current release of versions still receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Future point releases receiving bug fixes, as well as security updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#316d5e; color:white; adding: .3rem 0.5rem 0.3rem 0.5rem;" |Future security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Future point releases receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#686566; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Previously released versions containing bug fixes, as well as security updates. Updating to a currently supported version is recommended.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#282828; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Previously released versions containing security updates only. Updating to a currently supported version is recommended.
|}

==General release calendar==
These are the target dates for releases. These dates may vary slightly due to unforeseen circumstances.
{| class="wikitable"
|-
!Release type
!Frequency
!Months
|-
|[[Process#Major_release_cycles|Major]] (eg. 3.x)
|6 monthly
|Second Monday of May and November
|-
|[[Process#Stable_maintenance_cycles|Minor]] (Point) (eg. 3.x.y)
| 2 monthly
|Second Monday of July, September, November, March and May.
Third Monday of January.
|}
All releases are preceded by a one week warning. Upcoming release dates can be found in the [https://www.google.com/calendar/ical/moodle.com_p4c2oe7hsb77ltaro5qtihb5d4%40group.calendar.google.com/public/basic.ics Moodle development calendar] (Note, this is an iCAL link that will try to add the dates to your personal calendar. If you just want to browse the dates online, use [https://calendar.google.com/calendar/embed?src=moodle.com_p4c2oe7hsb77ltaro5qtihb5d4@group.calendar.google.com&pli=1 this link].).

==Moodle 4.0==
{| class="wikitable"
|-
!Moodle 4.0
|19 April 2022
|2022041900
|[[Moodle 4.0 release notes|Release Notes]]
|[https://docs.moodle.org/400/en/Upgrading Upgrading to 4.0]
|-
!Moodle 4.0.1
|9 May 2022
|2022041901
|[[Moodle 4.0.1 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 4.0.x will end 8 May 2023 (12 months).
Bug fixes for security issues in 4.0.x will end 13 November 2023 (18 months).

==Moodle 3.11==
{| class="wikitable"
|-
!Moodle 3.11
|17 May 2021
|2021051700
|[[Moodle 3.11 release notes|Release Notes]]
|[https://docs.moodle.org/311/en/Upgrading Upgrading to 3.11]
|-
!Moodle 3.11.1
|12 July 2021
|2021051701
|[[Moodle 3.11.1 release notes|Release Notes]]
|
|-
!Moodle 3.11.2
|29 July 2021
|2021051702
|[[Moodle 3.11.2 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.11.3
|13 September 2021
|2021051703
|[[Moodle 3.11.3 release notes|Release Notes]]
|
|-
! Moodle 3.11.4
|8 November 2021
|2021051704
|[[Moodle 3.11.4 release notes|Release Notes]]
|
|-
! Moodle 3.11.5
|17 January 2022
|2021051705
|[[Moodle 3.11.5 release notes|Release Notes]]
|
|-
! Moodle 3.11.6
|14 March 2022
|2021051706
|[[Moodle 3.11.6 release notes|Release Notes]]
|
|-
! Moodle 3.11.7
|9 May 2022
|2021051707
|[[Moodle 3.11.7 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.11.x will end 14 Nov 2022 (12 months plus 6 months extension).
Bug fixes for security issues in 3.11.x will end 13 Nov 2023 (18 months plus 12 months extension).

==Moodle 3.10==
{| class="wikitable"
|-
! Moodle 3.10
|9 November 2020
|2020110900
|
[[Moodle 3.10 release notes|Release Notes]]
|[https://docs.moodle.org/310/en/Upgrading Upgrading to 3.10]
|-
!Moodle 3.10.1
|18 January 2021
|2020110901
| [[Moodle 3.10.1 release notes|Release Notes]]
|
|-
!Moodle 3.10.2
|8 March 2021
|2020110902
|[[Moodle 3.10.2 release notes|Release Notes]]
|
|-
! Moodle 3.10.3
|25 March 2021
|2020110903
|[[Moodle 3.10.3 release notes|Release Notes]]
|
|-
!Moodle 3.10.4
|10 May 2021
|2020110904
|[[Moodle 3.10.4 release notes|Release Notes]]
|
|-
!Moodle 3.10.5
|12 July 2021
|2020110905
|[[Moodle 3.10.5 release notes|Release Notes]]
|
|-
!Moodle 3.10.6
|29 July 2021
|2020110906
|[[Moodle 3.10.6 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.10.7
|13 September 2021
|2020110907
|[[Moodle 3.10.7 release notes|Release Notes]]
|
|-
!Moodle 3.10.8
|8 November 2021
|2020110908
|[[Moodle 3.10.8 release notes|Release Notes]]
|
|-
!Moodle 3.10.9
|17 January 2022
|2020110909
|[[Moodle 3.10.9 release notes|Release Notes]]
|
|-
!Moodle 3.10.10
|14 March 2022
|2020110910
|[[Moodle 3.10.10 release notes|Release Notes]]
|
|-
!Moodle 3.10.11
|9 May 2022
|2020110911
|[[Moodle 3.10.11 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.10.x ended 8 November 2021 (12 months).
Bug fixes for security issues in 3.10.x will end 9 May 2022 (18 months).

==Moodle 3.9 (LTS)==
{| class="wikitable"
|-
! Moodle 3.9
|15 June 2020
|2020061500
|[[Moodle 3.9 release notes|Release Notes]]
|
[https://docs.moodle.org/39/en/Upgrading Upgrading to 3.9]
|-
!Moodle 3.9.1
|13 July 2020
|2020061501
|[[Moodle 3.9.1 release notes|Release Notes]]
|
|-
!Moodle 3.9.2
|14 September 2020
|2020061502
| [[Moodle 3.9.2 release notes|Release Notes]]
|
|-
!Moodle 3.9.3
|9 November 2020
|2020061503
| [[Moodle 3.9.3 release notes|Release Notes]]
|
|-
!Moodle 3.9.4
|18 January 2021
|2020061504
|[[Moodle 3.9.4 release notes|Release Notes]]
|
|-
!Moodle 3.9.5
|8 March 2021
|2020061505
|[[Moodle 3.9.5 release notes|Release Notes]]
|
|-
!Moodle 3.9.6
|25 March 2021
|2020061506
|[[Moodle 3.9.6 release notes|Release Notes]]
|
|-
!Moodle 3.9.7
|10 May 2021
|2020061507
|[[Moodle 3.9.7 release notes|Release Notes]]
|
|-
! Moodle 3.9.8
|12 July 2021
|2020061508
|[[Moodle 3.9.8 release notes|Release Notes]]
|
|-
!Moodle 3.9.9
|29 July 2021
|2020061509
|[[Moodle 3.9.9 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.9.10
|13 September 2021
|2020061510
|[[Moodle 3.9.10 release notes|Release Notes]]
|
|-
!Moodle 3.9.11
| 8 November 2021
|2020061511
|[[Moodle 3.9.11 release notes|Release Notes]]
|
|-
!Moodle 3.9.12
| 17 January 2022
|2020061512
|[[Moodle 3.9.12 release notes|Release Notes]]
|-
!Moodle 3.9.13
| 14 March 2022
|2020061513
|[[Moodle 3.9.13 release notes|Release Notes]]
|
|-
!Moodle 3.9.14
| 9 May 2022
|2020061514
|[[Moodle 3.9.14 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.9.x ended 10 May 2021 (12 months).
Bug fixes for security issues in 3.9.x will end 13 Nov 2023 (36 months plus 6 months extension).
==Moodle 3.8==
{| class="wikitable"
|-
!Moodle 3.8
|18 November 2019
|2019111800
|[[Moodle 3.8 release notes|Release Notes]]
|
[https://docs.moodle.org/38/en/Upgrading Upgrading to 3.8]
|-
!Moodle 3.8.1
|13 January 2020
|2019111801
|[[Moodle 3.8.1 release notes|Release Notes]]
|
|-
!Moodle 3.8.2
|9 March 2020
|2019111802
|[[Moodle 3.8.2 release notes|Release Notes]]
|
|-
!Moodle 3.8.3
|11 May 2020
|2019111803
|[[Moodle 3.8.3 release notes|Release Notes]]
|
|-
!Moodle 3.8.4
|13 July 2020
|2019111804
|[[Moodle 3.8.4 release notes|Release Notes]]
|
|-
!Moodle 3.8.5
|14 September 2020
|2019111805
| [[Moodle 3.8.5 release notes|Release Notes]]
|
|-
!Moodle 3.8.6
|9 November 2020
|2019111806
| [[Moodle 3.8.6 release notes|Release Notes]]
|
|-
!Moodle 3.8.7
|18 January 2021
|2019111807
|[[Moodle 3.8.7 release notes|Release Notes]]
|
|-
!Moodle 3.8.8
|8 March 2021
|2019111808
|[[Moodle 3.8.8 release notes|Release Notes]]
|
|-
!Moodle 3.8.9
|10 May 2021
|2019111809
|[[Moodle 3.8.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.8.x ended 9 November 2020 (12 months).
Bug fixes for security issues in 3.8.x ended 10 May 2021 (18 months).
==Moodle 3.7==
{| class="wikitable"
|-
!Moodle 3.7
|20 May 2019
|2019052000
|[[Moodle 3.7 release notes|Release Notes]]
|[https://docs.moodle.org/37/en/Upgrading Upgrading to 3.7]
|-
!Moodle 3.7.1
|8 July 2019
|2019052001
|[[Moodle 3.7.1 release notes|Release Notes]]
|
|-
!Moodle 3.7.2
|9 September 2019
|2019052002
|[[Moodle 3.7.2 release notes|Release Notes]]
|
|-
!Moodle 3.7.3
|11 November 2019
|2019052003
| [[Moodle 3.7.3 release notes|Release Notes]]
|
|-
!Moodle 3.7.4
|13 January 2020
|2019052004
|[[Moodle 3.7.4 release notes|Release Notes]]
|
|-
!Moodle 3.7.5
|9 March 2020
|2019052005
|[[Moodle 3.7.5 release notes|Release Notes]]
|
|-
!Moodle 3.7.6
|11 May 2020
|2019052006
|[[Moodle 3.7.6 release notes|Release Notes]]
|
|-
!Moodle 3.7.7
|13 July 2020
|2019052007
|[[Moodle 3.7.7 release notes|Release Notes]]
|
|-
!Moodle 3.7.8
|14 September 2020
|2019052008
| [[Moodle 3.7.8 release notes|Release Notes]]
|
|-
!Moodle 3.7.9
|9 November 2020
|2019052009
|[[Moodle 3.7.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.7.x ended 11 May 2020 (12 months).
Bug fixes for security issues in 3.7.x ended 9 November 2020 (18 months).
==Moodle 3.6==
{| class="wikitable"
|-
!Moodle 3.6
| 3 December 2018
|2018120300
|[[Moodle 3.6 release notes|Release Notes]]
|
[https://docs.moodle.org/36/en/Upgrading Upgrading to 3.6]
|-
!Moodle 3.6.1
|5 December 2018
|2018120301
| [[Moodle 3.6.1 release notes|Release Notes]]
|
|-
! Moodle 3.6.2
|14 January 2019
|2018120302
|[[Moodle 3.6.2 release notes|Release Notes]]
|
|-
!Moodle 3.6.3
|11 March 2019
|2018120303
|[[Moodle 3.6.3 release notes|Release Notes]]
|
|-
!Moodle 3.6.4
|13 May 2019
|2018120304
|[[Moodle 3.6.4 release notes|Release Notes]]
|
|-
!Moodle 3.6.5
|8th July 2019
|2018120305
|[[Moodle 3.6.5 release notes|Release Notes]]
|
|-
!Moodle 3.6.6
|9th September 2019
|2018120306
|[[Moodle 3.6.6 release notes|Release Notes]]
|
|-
!Moodle 3.6.7
| 11th November 2019
|2018120307
|[[Moodle 3.6.7 release notes|Release Notes]]
|
|-
!Moodle 3.6.8
|13th January 2020
|2018120308
|[[Moodle 3.6.8 release notes|Release Notes]]
|
|-
!Moodle 3.6.9
|9th March 2020
|2018120309
| [[Moodle 3.6.9 release notes|Release Notes]]
|
|-
!Moodle 3.6.10
|11th May 2020
|2018120310
|[[Moodle 3.6.10 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.6.x ended 11 November 2019 (12 months).
Bug fixes for security issues in 3.6.x ended 11 May 2020 (18 months).
==Moodle 3.5 (LTS)==
{| class="wikitable"
|-
!Moodle 3.5
|17 May 2018
|2018051700
|[[Moodle 3.5 release notes|Release Notes]]
|[https://docs.moodle.org/35/en/Upgrading Upgrading to 3.5]
|-
! Moodle 3.5.1
|9 July 2018
|2018051701
|[[Moodle 3.5.1 release notes|Release Notes]]
|
|-
!Moodle 3.5.2
|10 September 2018
|2018051702
|[[Moodle 3.5.2 release notes|Release Notes]]
|
|-
!Moodle 3.5.3
|12 November 2018
|2018051703
| [[Moodle 3.5.3 release notes|Release Notes]]
|
|-
! Moodle 3.5.4
|14 January 2019
|2018051704
|[[Moodle 3.5.4 release notes|Release Notes]]
|
|-
!Moodle 3.5.5
|11 March 2019
|2018051705
|[[Moodle 3.5.5 release notes|Release Notes]]
|
|-
!Moodle 3.5.6
|13 May 2019
|2018051706
|[[Moodle 3.5.6 release notes|Release Notes]]
|
|-
!Moodle 3.5.7
|8 July 2019
|2018051707
|[[Moodle 3.5.7 release notes|Release Notes]]
|
|-
!Moodle 3.5.8
|9 September 2019
|2018051708
|[[Moodle 3.5.8 release notes|Release Notes]]
|
|-
!Moodle 3.5.9
|11 November 2019
|2018051709
|[[Moodle 3.5.9 release notes|Release Notes]]
|
|-
!Moodle 3.5.10
|13 January 2020
|2018051710
| [[Moodle 3.5.10 release notes|Release Notes]]
|
|-
!Moodle 3.5.11
|9 March 2020
|2018051711
|[[Moodle 3.5.11 release notes|Release Notes]]
|
|-
!Moodle 3.5.12
|11 May 2020
|2018051712
| [[Moodle 3.5.12 release notes|Release Notes]]
|
|-
!Moodle 3.5.13
|13 July 2020
|2018051713
|[[Moodle 3.5.13 release notes|Release Notes]]
|
|-
!Moodle 3.5.14
| 14 September 2020
|2018051714
|[[Moodle 3.5.14 release notes|Release Notes]]
|
|-
!Moodle 3.5.15
|9 November 2020
|2018051715
|[[Moodle 3.5.15 release notes|Release Notes]]
|
|-
!Moodle 3.5.16
|18 January 2021
|2018051716
| [[Moodle 3.5.16 release notes|Release Notes]]
|
|-
!Moodle 3.5.17
|8 March 2021
| 2018051717
|[[Moodle 3.5.17 release notes|Release Notes]]
|
|-
!Moodle 3.5.18
| 10 May 2021
| 2018051718
|[[Moodle 3.5.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.5.x ended May 2019 (12 months).
Bug fixes for security issues in 3.5.x ended 10 May 2021 (36 months).
==Moodle 3.4==
{| class="wikitable"
|-
!Moodle 3.4
|13 November 2017
|2017111300
|[[Moodle 3.4 release notes|Release Notes]]
|
[https://docs.moodle.org/34/en/Upgrading Upgrading to 3.4]
|-
! Moodle 3.4.1
|15 January 2018
|2017111301
|[[Moodle 3.4.1 release notes|Release Notes]]
|
|-
!Moodle 3.4.2
|19 March 2018
|2017111302
|[[Moodle 3.4.2 release notes|Release Notes]]
|
|-
!Moodle 3.4.3
|17 May 2018
|2017111303
|[[Moodle 3.4.3 release notes|Release Notes]]
|
|-
! Moodle 3.4.4
|9 July 2018
|2017111304
|[[Moodle 3.4.4 release notes|Release Notes]]
|
|-
!Moodle 3.4.5
|10 September 2018
|2017111305
|[[Moodle 3.4.5 release notes|Release Notes]]
|
|-
!Moodle 3.4.6
|12 November 2018
|2017111306
| [[Moodle 3.4.6 release notes|Release Notes]]
|
|-
! Moodle 3.4.7
|14 January 2019
|2017111307
|[[Moodle 3.4.7 release notes|Release Notes]]
|
|-
!Moodle 3.4.8
|11 March 2019
|2017111308
|[[Moodle 3.4.8 release notes|Release Notes]]
|
|-
!Moodle 3.4.9
|13 May 2019
|2017111309
| [[Moodle 3.4.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.4.x ended 12 November 2018 (12 months).
Bug fixes for security issues in 3.4.x ended 13 May 2019 (18 months).
==Moodle 3.3==
{| class="wikitable"
|-
!Moodle 3.3
|15 May 2017
|2017051500
|[[Moodle 3.3 release notes|Release Notes]]
|
[https://docs.moodle.org/33/en/Upgrading Upgrading to 3.3]
|-
!Moodle 3.3.1
|10 July 2017
|2017051501
|[[Moodle 3.3.1 release notes|Release Notes]]
|
|-
!Moodle 3.3.2
|11 September 2017
|2017051502
|[[Moodle 3.3.2 release notes|Release Notes]]
|
|-
!Moodle 3.3.3
|13 November 2017
|2017051503
| [[Moodle 3.3.3 release notes|Release Notes]]
|
|-
! Moodle 3.3.4
|15 January 2018
|2017051504
|[[Moodle 3.3.4 release notes|Release Notes]]
|
|-
!Moodle 3.3.5
|19 March 2018
|2017051505
|[[Moodle 3.3.5 release notes|Release Notes]]
|
|-
!Moodle 3.3.6
|17 May 2018
|2017051506
|[[Moodle 3.3.6 release notes|Release Notes]]
|
|-
! Moodle 3.3.7
|9 July 2018
|2017051507
|[[Moodle 3.3.7 release notes|Release Notes]]
|
|-
!Moodle 3.3.8
|10 September 2018
|2017051508
|[[Moodle 3.3.8 release notes|Release Notes]]
|
|-
! Moodle 3.3.9
|12 November 2018
|2017051509
|[[Moodle 3.3.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.3.x ended 17 May 2018 (12 months).
Bug fixes for security issues in 3.3.x ended 12 November 2018 (18 months).
==Moodle 3.2==
{| class="wikitable"
|-
!Moodle 3.2
| 5 December 2016
|2016120500
|[[Moodle 3.2 release notes|Release Notes]]
|[https://docs.moodle.org/32/en/Upgrading Upgrading to 3.2]
|-
!Moodle 3.2.1
|9 January 2017
|2016120501
|[[Moodle 3.2.1 release notes|Release Notes]]
|
|-
!Moodle 3.2.2
|13 March 2017
|2016120502
|[[Moodle 3.2.2 release notes|Release Notes]]
|
|-
!Moodle 3.2.3
|8 May 2017
|2016120503
|[[Moodle 3.2.3 release notes|Release Notes]]
|
|-
!Moodle 3.2.4
|10 July 2017
|2016120504
|[[Moodle 3.2.4 release notes|Release Notes]]
|
|-
!Moodle 3.2.5
|11 September 2017
|2016120505
|[[Moodle 3.2.5 release notes|Release Notes]]
|
|-
!Moodle 3.2.6
|13 November 2017
|2016120506
| [[Moodle 3.2.6 release notes|Release Notes]]
|
|-
! Moodle 3.2.7
|15 January 2018
|2016120507
|[[Moodle 3.2.7 release notes|Release Notes]]
|
|-
!Moodle 3.2.8
|19 March 2018
|2016120508
|[[Moodle 3.2.8 release notes|Release Notes]]
|
|-
!Moodle 3.2.9
|17 May 2018
|2016120509
| [[Moodle 3.2.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.2.x ended 13 November 2017 (12 months).
Bug fixes for security issues in 3.2.x ended 17 May 2018 (18 months).
==Moodle 3.1 (LTS)==
{| class="wikitable"
|-
!Moodle 3.1
|23 May 2016
|2016052300
|[[Moodle 3.1 release notes|Release Notes]]
|
[https://docs.moodle.org/31/en/Upgrading Upgrading to 3.1]
|-
!Moodle 3.1.1
|11 July 2016
|2016052301
|[[Moodle 3.1.1 release notes|Release Notes]]
|
|-
!Moodle 3.1.2
|12 September 2016
|2016052302
|[[Moodle 3.1.2 release notes|Release Notes]]
|
|-
!Moodle 3.1.3
|14 November 2016
|2016052303
|[[Moodle 3.1.3 release notes|Release Notes]]
|
|-
!Moodle 3.1.4
|9 January 2017
|2016052304
|[[Moodle 3.1.4 release notes|Release Notes]]
|
|-
!Moodle 3.1.5
|13 March 2017
|2016052305
|[[Moodle 3.1.5 release notes|Release Notes]]
|
|-
!Moodle 3.1.6
|8 May 2017
|2016052306
|[[Moodle 3.1.6 release notes|Release Notes]]
|
|-
!Moodle 3.1.7
|10 July 2017
|2016052307
|[[Moodle 3.1.7 release notes|Release Notes]]
|
|-
!Moodle 3.1.8
|11 September 2017
|2016052308
|[[Moodle 3.1.8 release notes|Release Notes]]
|
|-
!Moodle 3.1.9
|13 November 2017
|2016052309
|[[Moodle 3.1.9 release notes|Release Notes]]
|
|-
!Moodle 3.1.10
|15 January 2018
|2016052310
|[[Moodle 3.1.10 release notes|Release Notes]]
|
|-
! Moodle 3.1.11
|19 March 2018
|2016052311
|[[Moodle 3.1.11 release notes|Release Notes]]
|
|-
!Moodle 3.1.12
|17 May 2018
|2016052312
|[[Moodle 3.1.12 release notes|Release Notes]]
|
|-
!Moodle 3.1.13
|9 July 2018
|2016052313
|[[Moodle 3.1.13 release notes|Release Notes]]
|
|-
!Moodle 3.1.14
|10 September 2018
|2016052314
|[[Moodle 3.1.14 release notes|Release Notes]]
|
|-
! Moodle 3.1.15
|12 November 2018
|2016052315
|[[Moodle 3.1.15 release notes|Release Notes]]
|
|-
!Moodle 3.1.16
|14 January 2019
|2016052316
|[[Moodle 3.1.16 release notes|Release Notes]]
|
|-
! Moodle 3.1.17
|11 March 2019
| 2016052317
|[[Moodle 3.1.17 release notes|Release Notes]]
|
|-
!Moodle 3.1.18
|13 May 2019
|2016052318
|[[Moodle 3.1.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.1.x ended 8 May 2017 (12 months).
Bug fixes for security issues in 3.1.x ended 13 May 2019 (36 months).
==Moodle 3.0==
{| class="wikitable"
|-
!Moodle 3.0
|16 November 2015
|2015111600
|[[Moodle 3.0 release notes|Release Notes]]
|[https://docs.moodle.org/30/en/Upgrading Upgrading to 3.0]
|-
!Moodle 3.0.1
|21 December 2015
|2015111601
| [[Moodle 3.0.1 release notes|Release Notes]]
|
|-
! Moodle 3.0.2
|11 January 2016
|2015111602
|[[Moodle 3.0.2 release notes|Release Notes]]
|
|-
!Moodle 3.0.3
|14 March 2016
|2015111603
|[[Moodle 3.0.3 release notes|Release Notes]]
|
|-
!Moodle 3.0.4
|9 May 2016
|2015111604
|[[Moodle 3.0.4 release notes|Release Notes]]
|
|-
!Moodle 3.0.5
|11 July 2016
|2015111605
|[[Moodle 3.0.5 release notes|Release Notes]]
|
|-
!Moodle 3.0.6
|12 September 2016
|2015111606
|[[Moodle 3.0.6 release notes|Release Notes]]
|
|-
!Moodle 3.0.7
|14 November 2016
|2015111607
|[[Moodle 3.0.7 release notes|Release Notes]]
|
|-
!Moodle 3.0.8
|9 January 2017
|2015111608
|[[Moodle 3.0.8 release notes|Release Notes]]
|
|-
!Moodle 3.0.9
|13 March 2017
|2015111609
|[[Moodle 3.0.9 release notes|Release Notes]]
|
|-
!Moodle 3.0.10
|8 May 2017
|2015111610
|[[Moodle 3.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.0.x ended 14 November 2016 (12 months).
Bug fixes for security issues in 3.0.x ended 8 May 2017 (18 months).
==Moodle 2.9==
{| class="wikitable"
|-
!Moodle 2.9
| 11 May 2015
|2015051100
|[[Moodle 2.9 release notes|Release Notes]]
| [https://docs.moodle.org/29/en/Upgrading_to_Moodle_2.9 Upgrading to 2.9]
|-
! Moodle 2.9.1
|6 July 2015
|2015051101
|[[Moodle 2.9.1 release notes|Release Notes]]
|
|-
!Moodle 2.9.2
|14 September 2015
|2015051102
| [[Moodle 2.9.2 release notes|Release Notes]]
|
|-
!Moodle 2.9.3
|9 November 2015
|2015051103
| [[Moodle 2.9.3 release notes|Release Notes]]
|
|-
! Moodle 2.9.4
|11 January 2016
|2015051104
|[[Moodle 2.9.4 release notes|Release Notes]]
|
|-
!Moodle 2.9.5
|14 March 2016
|2015051105
|[[Moodle 2.9.5 release notes|Release Notes]]
|
|-
!Moodle 2.9.6
|9 May 2016
|2015051106
|[[Moodle 2.9.6 release notes|Release Notes]]
|
|-
!Moodle 2.9.7
|11 July 2016
|2015051107
|[[Moodle 2.9.7 release notes|Release Notes]]
|
|-
!Moodle 2.9.8
|12 September 2016
|2015051108
|[[Moodle 2.9.8 release notes|Release Notes]]
|
|-
! Moodle 2.9.9
|14 November 2016
|2015051109
|[[Moodle 2.9.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.9.x ended 9 May 2016 (12 months).
Bug fixes for security issues in 2.9.x ended 14 November 2016 (18 months).
==Moodle 2.8==
{| class="wikitable"
|-
!Moodle 2.8
|10 November 2014
|2014111000
| [[Moodle 2.8 release notes|Release Notes]]
|[https://docs.moodle.org/28/en/Upgrading_to_Moodle_2.8 Upgrading to 2.8]
|-
!Moodle 2.8.1
|13 November 2014
|2014111001
| [[Moodle 2.8.1 release notes|Release Notes]]
|
|-
!Moodle 2.8.2
|12 January 2015
|2014111002
| [[Moodle 2.8.2 release notes|Release Notes]]
|
|-
!Moodle 2.8.3
|2 February 2015
|2014111003
|[[Moodle 2.8.3 release notes|Release Notes]]
|
|-
!Moodle 2.8.4
|9 March 2015
|2014111004
|[[Moodle 2.8.4 release notes|Release Notes]]
|
|-
!Moodle 2.8.5
|10 March 2015
|2014111005
|[[Moodle 2.8.5 release notes|Release Notes]]
|
|-
!Moodle 2.8.6
|11 May 2015
|2014111006
|[[Moodle 2.8.6 release notes|Release Notes]]
|
|-
! Moodle 2.8.7
|6 July 2015
|2014111007
|[[Moodle 2.8.7 release notes|Release Notes]]
|
|-
!Moodle 2.8.8
|14 September 2015
|2014111008
| [[Moodle 2.8.8 release notes|Release Notes]]
|
|-
!Moodle 2.8.9
|9 November 2015
|2014111009
|[[Moodle 2.8.9 release notes|Release Notes]]
|
|-
!Moodle 2.8.10
|11 January 2016
|2014111010
|[[Moodle 2.8.10 release notes|Release Notes]]
|
|-
!Moodle 2.8.11
|14 March 2016
|2014111011
|[[Moodle 2.8.11 release notes|Release Notes]]
|
|-
!Moodle 2.8.12
|9 May 2016
|2014111012
| [[Moodle 2.8.12 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.8.x ended 9 November 2015 (12 months).
Bug fixes for security issues in 2.8.x ended 9 May 2016 (18 months).
==Moodle 2.7 (LTS)==
{| class="wikitable"
|-
!Moodle 2.7
| 12 May 2014
|2014051200
|[[Moodle 2.7 release notes|Release Notes]]
|[https://docs.moodle.org/27/en/Upgrading_to_Moodle_2.7 Upgrading to 2.7]
|-
! Moodle 2.7.1
|14 July 2014
|2014051201
|[[Moodle 2.7.1 release notes|Release Notes]]
|
|-
!Moodle 2.7.2
|8 September 2014
|2014051202
|[[Moodle 2.7.2 release notes|Release Notes]]
|
|-
!Moodle 2.7.3
|10 November 2014
|2014051203
| [[Moodle 2.7.3 release notes|Release Notes]]
|
|-
!Moodle 2.7.4
|12 January 2015
|2014051204
| [[Moodle 2.7.4 release notes|Release Notes]]
|
|-
!Moodle 2.7.5
|2 February 2015
|2014051205
|[[Moodle 2.7.5 release notes|Release Notes]]
|
|-
!Moodle 2.7.6
|9 March 2015
|2014051206
|[[Moodle 2.7.6 release notes|Release Notes]]
|
|-
!Moodle 2.7.7
|10 March 2015
|2014051207
|[[Moodle 2.7.7 release notes|Release Notes]]
|
|-
!Moodle 2.7.8
|11 May 2015
|2014051208
|[[Moodle 2.7.8 release notes|Release Notes]]
|
|-
!Moodle 2.7.9
|6 July 2015
|2014051209
|[[Moodle 2.7.9 release notes|Release Notes]]
|
|-
!Moodle 2.7.10
| 14 September 2015
|2014051210
|[[Moodle 2.7.10 release notes|Release Notes]]
|
|-
!Moodle 2.7.11
|9 November 2015
|2014051211
|[[Moodle 2.7.11 release notes|Release Notes]]
|
|-
!Moodle 2.7.12
|11 January 2016
|2014051212
|[[Moodle 2.7.12 release notes|Release Notes]]
|
|-
!Moodle 2.7.13
|14 March 2016
|2014051213
|[[Moodle 2.7.13 release notes|Release Notes]]
|
|-
!Moodle 2.7.14
|9 May 2016
|2014051214
| [[Moodle 2.7.14 release notes|Release Notes]]
|
|-
!Moodle 2.7.15
|11 July 2016
|2014051215
|[[Moodle 2.7.15 release notes|Release Notes]]
|
|-
!Moodle 2.7.16
|12 September 2016
|2014051216
|[[Moodle 2.7.16 release notes|Release Notes]]
|
|-
!Moodle 2.7.17
|14 November 2016
|2014051217
|[[Moodle 2.7.17 release notes|Release Notes]]
|
|-
!Moodle 2.7.18
|9 January 2017
|2014051218
|[[Moodle 2.7.18 release notes|Release Notes]]
|
|-
!Moodle 2.7.19
|13 March 2017
|2014051219
|[[Moodle 2.7.19 release notes|Release Notes]]
|
|-
!Moodle 2.7.20
|8 May 2017
|2014051220
| [[Moodle 2.7.20 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.7.x ended 11 May 2015 (12 months).
Bug fixes for security issues in 2.7.x ended 8 May 2017 (36 months).
==Moodle 2.6==
{| class="wikitable"
|-
!Moodle 2.6
|18 November 2013
|2013111800
|[[Moodle 2.6 release notes|Release Notes]]
|[https://docs.moodle.org/26/en/Upgrading_to_Moodle_2.6 Upgrading to 2.6]
|-
!Moodle 2.6.1
|13 January 2014
| 2013111801
| [[Moodle 2.6.1 release notes|Release Notes]]
|
|-
!Moodle 2.6.2
|10 March 2014
|2013111802
|[[Moodle 2.6.2 release notes|Release Notes]]
|
|-
!Moodle 2.6.3
|12 May 2014
|2013111803
|[[Moodle 2.6.3 release notes|Release Notes]]
|
|-
!Moodle 2.6.4
|14 July 2014
|2013111804
|[[Moodle 2.6.4 release notes|Release Notes]]
|
|-
!Moodle 2.6.5
|8 September 2014
|2013111805
|[[Moodle 2.6.5 release notes|Release Notes]]
|
|-
!Moodle 2.6.6
|10 November 2014
|2013111806
|[[Moodle 2.6.6 release notes|Release Notes]]
|
|-
!Moodle 2.6.7
|12 January 2015
|2013111807
|[[Moodle 2.6.7 release notes|Release Notes]]
|
|-
! Moodle 2.6.8
|2 February 2015
|2013111808
|[[Moodle 2.6.8 release notes|Release Notes]]
|
|-
! Moodle 2.6.9
|9 March 2015
|2013111809
|[[Moodle 2.6.9 release notes|Release Notes]]
|
|-
!Moodle 2.6.10
|10 March 2015
|2013111810
| [[Moodle 2.6.10 release notes|Release Notes]]
|
|-
!Moodle 2.6.11
|11 May 2015
|2013111811
|[[Moodle 2.6.11 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 2.6.x ended 10 November 2014 (12 months).
Bug fixes for security issues in 2.6.x ended 11 May 2015 (18 months).
==Moodle 2.5==
{| class="wikitable"
|-
!Moodle 2.5
| 14 May 2013
|2013051400
|[[Moodle 2.5 release notes|Release Notes]]
| [https://docs.moodle.org/25/en/Upgrading_to_Moodle_2.5 Upgrading to 2.5]
|-
! Moodle 2.5.1
|8 July 2013
|2013051401
|[[Moodle 2.5.1 release notes|Release Notes]]
|
|-
!Moodle 2.5.2
|9 September 2013
|2013051402
|[[Moodle 2.5.2 release notes|Release Notes]]
|
|-
!Moodle 2.5.3
|11 November 2013
|2013051403
|[[Moodle 2.5.3 release notes|Release Notes]]
|
|-
!Moodle 2.5.4
|13 January 2014
| 2013051404
| [[Moodle 2.5.4 release notes|Release Notes]]
|
|-
!Moodle 2.5.5
|10 March 2014
|2013051405
|[[Moodle 2.5.5 release notes|Release Notes]]
|
|-
!Moodle 2.5.6
|12 May 2014
|2013051406
|[[Moodle 2.5.6 release notes|Release Notes]]
|
|-
!Moodle 2.5.7
|14 July 2014
|2013051407
|[[Moodle 2.5.7 release notes|Release Notes]]
|
|-
!Moodle 2.5.8
|8 September 2014
|2013051408
|[[Moodle 2.5.8 release notes|Release Notes]]
|
|-
! Moodle 2.5.9
| 10 November 2014
|2013051409
|[[Moodle 2.5.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.5.x ended May 2014 (12 months).
Bug fixes for security issues in 2.5.x ended 10 November 2014 (18 months).
==Moodle 2.4==
{| class="wikitable"
|-
! Moodle 2.4
|3 December 2012
|2012120300
|[[Moodle 2.4 release notes|Release Notes]]
|[https://docs.moodle.org/24/en/Upgrading_to_Moodle_2.4 Upgrading to 2.4]
|-
! Moodle 2.4.1
|14 January 2013
|2012120301
|[[Moodle 2.4.1 release notes|Release Notes]]
|
|-
!Moodle 2.4.2
|11 March 2013
|2012120302
|[[Moodle 2.4.2 release notes|Release Notes]]
|
|-
!Moodle 2.4.3
|18 March 2013
|2012120303
|[[Moodle 2.4.3 release notes|Release Notes]]
|
|-
!Moodle 2.4.4
|14 May 2013
|2012120304
|[[Moodle 2.4.4 release notes|Release Notes]]
|
|-
!Moodle 2.4.5
|8 July 2013
|2012120305
|[[Moodle 2.4.5 release notes|Release Notes]]
|
|-
!Moodle 2.4.6
|9 September 2013
|2012120306
|[[Moodle 2.4.6 release notes|Release Notes]]
|
|-
!Moodle 2.4.7
|11 November 2013
|2012120307
| [[Moodle 2.4.7 release notes|Release Notes]]
|
|-
! Moodle 2.4.8
|13 January 2014
|2012120308
|[[Moodle 2.4.8 release notes|Release Notes]]
|
|-
!Moodle 2.4.9
|10 March 2014
|2012120309
|[[Moodle 2.4.9 release notes|Release Notes]]
|
|-
!Moodle 2.4.10
|12 May 2014
|2012120310
| [[Moodle 2.4.10 release notes|Release Notes]]
|
|-
!Moodle 2.4.11
|14 July 2014
|2012120311
|[[Moodle 2.4.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.4.x ended December 2013 (12 months).
Bug fixes for security issues in 2.4.x ended June 2014 (18 months).
==Moodle 2.3==
{| class="wikitable"
|-
!Moodle 2.3
|25 June 2012
|2012062500
|[[Moodle 2.3 release notes|Release Notes]]
| [https://docs.moodle.org/23/en/Upgrading_to_Moodle_2.3 Upgrading to 2.3]
|-
!Moodle 2.3.1
|9 July 2012
|2012062501
|[[Moodle 2.3.1 release notes|Release Notes]]
|
|-
! Moodle 2.3.2
|10 September 2012
|2012062502
|[[Moodle 2.3.2 release notes|Release Notes]]
|
|-
!Moodle 2.3.3
|12 November 2012
|2012062503
|[[Moodle 2.3.3 release notes|Release Notes]]
|
|-
! Moodle 2.3.4
|14 January 2013
|2012062504
|[[Moodle 2.3.4 release notes|Release Notes]]
|
|-
!Moodle 2.3.5
|11 March 2013
|2012062505
|[[Moodle 2.3.5 release notes|Release Notes]]
|
|-
!Moodle 2.3.6
|18 March 2013
|2012062506
|[[Moodle 2.3.6 release notes|Release Notes]]
|
|-
!Moodle 2.3.7
|14 May 2013
|2012062507
|[[Moodle 2.3.7 release notes|Release Notes]]
|
|-
!Moodle 2.3.8
|8 July 2013
|2012062508
|[[Moodle 2.3.8 release notes|Release Notes]]
|
|-
!Moodle 2.3.9
|9 September 2013
|2012062509
|[[Moodle 2.3.9 release notes|Release Notes]]
|
|-
! Moodle 2.3.10
|11 November 2013
|2012062510
|[[Moodle 2.3.10 release notes|Release Notes]]
|
|-
!Moodle 2.3.11
|13 January 2014
|2012062511
|[[Moodle 2.3.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.3.x ended June 2013 (12 months).
Bug fixes for security issues in 2.3.x ended December 2013 (18 months).
==Moodle 2.2==
{| class="wikitable"
|-
! Moodle 2.2
|5 December 2011
|2011120500
|[[Moodle 2.2 release notes|Release Notes]]
|[https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 Upgrading to 2.2]
|-
!Moodle 2.2.1
|9 January 2012
|2011120501
|[[Moodle 2.2.1 release notes|Release Notes]]
|
|-
!Moodle 2.2.2
|12 March 2012
|2011120502
|[[Moodle 2.2.2 release notes|Release Notes]]
|
|-
!Moodle 2.2.3
|14 May 2012
|2011120503
|[[Moodle 2.2.3 release notes|Release Notes]]
|
|-
! Moodle 2.2.4
|9 July 2012
|2011120504
|[[Moodle 2.2.4 release notes|Release Notes]]
|
|-
!Moodle 2.2.5
|10 September 2012
|2011120505
|[[Moodle 2.2.5 release notes|Release Notes]]
|
|-
!Moodle 2.2.6
|12 November 2012
|2011120506
| [[Moodle 2.2.6 release notes|Release Notes]]
|
|-
! Moodle 2.2.7
|14 January 2013
|2011120507
|[[Moodle 2.2.7 release notes|Release Notes]]
|
|-
!Moodle 2.2.8
|11 March 2013
|2011120508
|[[Moodle 2.2.8 release notes|Release Notes]]
|
|-
!Moodle 2.2.9
|18 March 2013
|2011120509
|[[Moodle 2.2.9 release notes|Release Notes]]
|
|-
!Moodle 2.2.10
|14 May 2013
| 2011120510
|[[Moodle 2.2.10 release notes|Release Notes]]
|
|-
!Moodle 2.2.11
|8 July 2013
|2011120511
|[[Moodle 2.2.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.2.x ended December 2012 (12 months).
Bug fixes for security issues in 2.2.x ended June 2013 (18 months).
==Moodle 2.1==
{| class="wikitable"
|-
!Moodle 2.1
| 1 July 2011
|2011070100
|[[Moodle 2.1 release notes|Release Notes]]
|[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to 2.1]
|-
! Moodle 2.1.1
|1 August 2011
|2011070101
| [[Moodle 2.1.1 release notes|Release Notes]]
|
|-
!Moodle 2.1.2
|10 October 2011
|2011070102
|[[Moodle 2.1.2 release notes|Release Notes]]
|
|-
!Moodle 2.1.3
|28 November 2011
|2011070103
|[[Moodle 2.1.3 release notes|Release Notes]]
|
|-
!Moodle 2.1.4
|9 January 2012
|2011070104
|[[Moodle 2.1.4 release notes|Release Notes]]
|
|-
!Moodle 2.1.5
|12 March 2012
|2011070105
|[[Moodle 2.1.5 release notes|Release Notes]]
|
|-
!Moodle 2.1.6
|14 May 2012
|2011070106
|[[Moodle 2.1.6 release notes|Release Notes]]
|
|-
! Moodle 2.1.7
|9 July 2012
|2011070107
|[[Moodle 2.1.7 release notes|Release Notes]]
|
|-
!Moodle 2.1.8
|10 September 2012
|2011070108
|[[Moodle 2.1.8 release notes|Release Notes]]
|
|-
!Moodle 2.1.9
|12 November 2012
|2011070109
|[[Moodle 2.1.9 release notes|Release Notes]]
|
|-
!Moodle 2.1.10
|14 January 2013
|2011070110
|[[Moodle 2.1.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.1.x ended June 2012 (12 months).
Bug fixes for security issues in 2.1.x ended December 2012 (18 months).
==Moodle 2.0==
{| class="wikitable"
|-
!Moodle 2.0
|24 November 2010
|2010112400
| [[Moodle 2.0 release notes|Release Notes]]
|[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to 2.0]
|-
!Moodle 2.0.1
|25 December 2010
|2010122500
|[[Moodle 2.0.1 release notes|Release Notes]]
|
|-
!Moodle 2.0.2
|21 February 2011
|2011022100
|[[Moodle 2.0.2 release notes|Release Notes]]
|
|-
!Moodle 2.0.3
|5 May 2011
|2011033003
|[[Moodle 2.0.3 release notes|Release Notes]]
|
|-
! Moodle 2.0.4
|1 August 2011
|2011033004
| [[Moodle 2.0.4 release notes|Release Notes]]
|
|-
!Moodle 2.0.5
|10 October 2011
|2011033005
|[[Moodle 2.0.5 release notes|Release Notes]]
|
|-
!Moodle 2.0.6
|28 November 2011
|2011033006
|[[Moodle 2.0.6 release notes|Release Notes]]
|
|-
!Moodle 2.0.7
|9 January 2012
|2011033007
|[[Moodle 2.0.7 release notes|Release Notes]]
|
|-
!Moodle 2.0.8
|12 March 2012
|2011033008
|[[Moodle 2.0.8 release notes|Release Notes]]
|
|-
!Moodle 2.0.9
|14 May 2012
|2011033009
|[[Moodle 2.0.9 release notes|Release Notes]]
|
|-
!Moodle 2.0.10
|9 July 2012
|2011033010
|[[Moodle 2.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.0.x ended December 2011 (12 months).
Bug fixes for security issues in 2.0.x ended June 2012 (18 months).
==Moodle 1.9==
{| class="wikitable"
|-
!Moodle 1.9
|3 March 2008
|2007101509
|[[Moodle 1.9 release notes|Release Notes]]
|[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to 1.9]
|-
!Moodle 1.9.1
|15 May 2008
| 2007101512
|[[Moodle 1.9.1 release notes|Release Notes]]
|
|-
! Moodle 1.9.2
|11 July 2008
|2007101520
|[[Moodle 1.9.2 release notes|Release Notes]]
|
|-
!Moodle 1.9.3
|15 October 2008
|2007101530
|[[Moodle 1.9.3 release notes|Release Notes]]
|
|-
!Moodle 1.9.4
|28 January 2009
|2007101540
|[[Moodle 1.9.4 release notes|Release Notes]]
|
|-
!Moodle 1.9.5
|13 May 2009
|2007101550
|[[Moodle 1.9.5 release notes|Release Notes]]
|
|-
!Moodle 1.9.6
|21 October 2009
|2007101560
|[[Moodle 1.9.6 release notes|Release Notes]]
|
|-
!Moodle 1.9.7
|25 November 2009
|2007101570
|[[Moodle 1.9.7 release notes|Release Notes]]
|
|-
!Moodle 1.9.8
|25 March 2010
|2007101580.00
|[[Moodle 1.9.8 release notes|Release Notes]]
|
|-
! Moodle 1.9.9
| 8 June 2010
| 2007101590.00
| [[Moodle 1.9.9 release notes|Release Notes]]
|
|-
!Moodle 1.9.10
|25 October 2010
|2007101591.00
|
[[Moodle 1.9.10 release notes|Release Notes]]
|
|-
!Moodle 1.9.11
|21 February 2011
|2007101591.02
|[[Moodle 1.9.11 release notes|Release Notes]]
|
|-
! Moodle 1.9.12
|10 May 2011
|2007101591.03
|[[Moodle 1.9.12 release notes|Release Notes]]
|
|-
!Moodle 1.9.13
|1 August 2011
|2007101591.04
|[[Moodle 1.9.13 release notes|Release Notes]]
|
|-
!Moodle 1.9.14
|10 October 2011
|2007101591.06
|
[[Moodle 1.9.14 release notes|Release Notes]]
|
|-
!Moodle 1.9.15
|28 November 2011
| 2007101591.07
| [[Moodle 1.9.15 release notes|Release Notes]]
|
|-
!Moodle 1.9.16
|9 January 2012
|2007101591.10
|[[Moodle 1.9.16 release notes|Release Notes]]
|
|-
! Moodle 1.9.17
|12 March 2012
|2007101591.12
|[[Moodle 1.9.17 release notes|Release Notes]]
|
|-
!Moodle 1.9.18
|14 May 2012
|2007101591.16
|[[Moodle 1.9.18 release notes|Release Notes]]
|
|-
! Moodle 1.9.19
|9 July 2012
|2007101592.00
|[[Moodle 1.9.19 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 1.9.x has ended June 2011 (3.5 years).
Bug fixes for security issues in 1.9.x by Moodle HQ ended June 2012 (4.5 years).
Bug fixes for security issues in 1.9.19+ branch by [http://catalyst.net.nz Catalyst IT] ended [http://moodle.org/mod/forum/discuss.php?d=199706 Dec 2013] (6 years).
==Moodle 1.8 ==
*[[Moodle 1.8 release notes|Moodle 1.8]] - 30 March 2007
*[[Moodle 1.8.1 release notes|Moodle 1.8.1]] - 14 June 2007
*[[Moodle 1.8.2 release notes|Moodle 1.8.2]] - 8 July 2007
*[[Moodle 1.8.3 release notes|Moodle 1.8.3]] - 11 October 2007
*[[Moodle 1.8.4 release notes|Moodle 1.8.4]] - 11 January 2008
*[[Moodle 1.8.5 release notes|Moodle 1.8.5]] - 8 April 2008
*[[Moodle 1.8.6 release notes|Moodle 1.8.6]] - 11 July 2008
*[[Moodle 1.8.7 release notes|Moodle 1.8.7]] - 15 October 2008
*[[Moodle 1.8.8 release notes|Moodle 1.8.8]] - 28 January 2009
*[[Moodle 1.8.9 release notes|Moodle 1.8.9]] - 15 May 2009
*[[Moodle 1.8.10 release notes|Moodle 1.8.10]] - 26 October 2009
*[[Moodle 1.8.11 release notes|Moodle 1.8.11]] - 25 November 2009
*[[Moodle 1.8.12 release notes|Moodle 1.8.12]] - 27 March 2010
*[[Moodle 1.8.13 release notes|Moodle 1.8.13]] - 8 June 2010
*[[Moodle 1.8.14 release notes|Moodle 1.8.14]] - 3 December 2010
*Support has ended

==Moodle 1.7==
*[[Moodle 1.7 release notes|Moodle 1.7]] - 7 November 2006
*[[Moodle 1.7.1 release notes|Moodle 1.7.1]] - 17 January 2007
*[[Moodle 1.7.2 release notes|Moodle 1.7.2]] - 30 March 2007
*[[Moodle 1.7.3 release notes|Moodle 1.7.3]] - 11 October 2007
*[[Moodle 1.7.4 release notes|Moodle 1.7.4]] - 11 January 2008
*[[Moodle 1.7.5 release notes|Moodle 1.7.5]] - 11 July 2008
*[[Moodle 1.7.6 release notes|Moodle 1.7.6]] - 15 October 2008
*[[Moodle 1.7.7 release notes|Moodle 1.7.7]] - 28 January 2009
*Support has ended
==Moodle 1.6==
*[[Moodle 1.6 release notes|Moodle 1.6]] - 20 June 2006
*[[Moodle 1.6.1 release notes|Moodle 1.6.1]] - 20 July 2006
*[[Moodle 1.6.2 release notes|Moodle 1.6.2]] - 12 September 2006
*[[Moodle 1.6.3 release notes|Moodle 1.6.3]] - 10 October 2006
*[[Moodle 1.6.4 release notes|Moodle 1.6.4]] - 17 January 2007
*[[Moodle 1.6.5 release notes|Moodle 1.6.5]] - 30 March 2007
*Moodle 1.6.6 - 11 January 2008
*Moodle 1.6.7 - 11 July 2008
*[[Moodle 1.6.8 release notes|Moodle 1.6.8]] - 15 October 2008
*[[Moodle 1.6.9 release notes|Moodle 1.6.9]] - 28 January 2009
* Support has ended
==Moodle 1.5==
*[[Moodle 1.5 release notes|Moodle 1.5]] - 5 June 2005
*[[Moodle 1.5.1 release notes|Moodle 1.5.1]] - 8 July 2005
*[[Moodle 1.5.2 release notes|Moodle 1.5.2]] - 16 July 2005
*[[Moodle 1.5.3 release notes|Moodle 1.5.3]] - 11 November 2005
*[[Moodle 1.5.4 release notes|Moodle 1.5.4]] - 21 May 2006
*Support has ended
==Moodle 1.4==
*Moodle 1.4 - 31 August 2004
*Moodle 1.4.1 - 12 September 2004
*Moodle 1.4.2 - 5 November 2004
*Moodle 1.4.3 - 21 December 2004
*Moodle 1.4.4 - 7 March 2005
*[[Moodle 1.4.5 release notes|Moodle 1.4.5]] - 7 May 2005
*Support has ended
==Moodle 1.3==
*Moodle 1.3 - 25 May 2004
* Moodle 1.3.1 - 4 June 2004
*Moodle 1.3.2 - 9 July 2004
*Moodle 1.3.3 - 16 July 2004
* Moodle 1.3.4 - 11 August 2004
*Moodle 1.3.5 - 9 September 2004
*Support has ended
==Moodle 1.2==
*Moodle 1.2 - 20 March 2004
*Moodle 1.2.1 - 25 March 2004
*Support has ended
==Moodle 1.1==
*Moodle 1.1 - 29 August 2003
*Moodle 1.1.1 - 11 September 2003
*Support has ended
== Moodle 1.0==
*Moodle 1.0 - 20 August 2002
*Moodle 1.0.1 - 26 August 2002
*Moodle 1.0.2 - 2 September 2002
*Moodle 1.0.3 - 5 September 2002
*Moodle 1.0.4 - 10 September 2002
*Moodle 1.0.5 - 27 September 2002
* Moodle 1.0.6 - 26 October 2002
::1.0.6.1 - 6 November 2002
::1.0.6.2 - 11 November 2002
::1.0.6.3 - 14 November 2002
::1.0.6.4 - 25 November 2002
*Moodle 1.0.7 - 9 December 2002
*Moodle 1.0.8 - 7 January 2003
*Moodle 1.0.9 - 30 May 2003
*Support has ended
==See also==
*[[Roadmap]] - future versions
*[[Moodle versions]] - an explanation of how our versions work plus version numbers for each release (for $plugin->requires)
[[Category:Release notes]]
[[Category:Core development]]
[[fr:Historique des versions]]
[[es:dev/Historia de las versiones]]
[[de:Versionshistorie]]

Releases

2022-05-09T01:46:19Z

Abgreeve: /* Moodle 3.11 table padding */

This page lists all official releases of Moodle, grouped by branch in reverse chronological order.
==Version support==
From Moodle 2.6 onwards, the end of support, both general and security, happens the second Monday of May and November, observing the 12, 18... month periods, no matter if the major release date was moved or not.

The most recent [https://en.wikipedia.org/wiki/Long-term_support long-term support release (LTS)] version is Moodle 3.9.
{| class="wikitable" border="1px solid #dee2e6;"
|-
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Version
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Release status
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Initial release
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:rgba(0, 0, 0, 0.05);" | General support ends
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Security support ends
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.9 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 15 June 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 10 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 November 2023 (ext 6M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.11
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 17 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 14 Nov 2022 (ext 6M)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 Nov 2023 (ext 12M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |4.0
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |19 April 2022
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |8 May 2023
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |13 November 2023
|-
|4.1 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
|November 2022
|November 2023
|November 2025
|}
[[Image:401_release_graph.png|alt=Release graph]]

Release graph key:
{| class="wikitable" border="1px solid #dee2e6;"
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Currently supported stable releases.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | Current release of versions still receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Future point releases receiving bug fixes, as well as security updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#316d5e; color:white; adding: .3rem 0.5rem 0.3rem 0.5rem;" |Future security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Future point releases receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#686566; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Previously released versions containing bug fixes, as well as security updates. Updating to a currently supported version is recommended.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#282828; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Previously released versions containing security updates only. Updating to a currently supported version is recommended.
|}

==General release calendar==
These are the target dates for releases. These dates may vary slightly due to unforeseen circumstances.
{| class="wikitable"
|-
!Release type
!Frequency
!Months
|-
|[[Process#Major_release_cycles|Major]] (eg. 3.x)
|6 monthly
|Second Monday of May and November
|-
|[[Process#Stable_maintenance_cycles|Minor]] (Point) (eg. 3.x.y)
| 2 monthly
|Second Monday of July, September, November, March and May.
Third Monday of January.
|}
All releases are preceded by a one week warning. Upcoming release dates can be found in the [https://www.google.com/calendar/ical/moodle.com_p4c2oe7hsb77ltaro5qtihb5d4%40group.calendar.google.com/public/basic.ics Moodle development calendar] (Note, this is an iCAL link that will try to add the dates to your personal calendar. If you just want to browse the dates online, use [https://calendar.google.com/calendar/embed?src=moodle.com_p4c2oe7hsb77ltaro5qtihb5d4@group.calendar.google.com&pli=1 this link].).

==Moodle 4.0==
{| class="wikitable"
|-
!Moodle 4.0
|19 April 2022
|2022041900
|[[Moodle 4.0 release notes|Release Notes]]
|[https://docs.moodle.org/400/en/Upgrading Upgrading to 4.0]
|-
!Moodle 4.0.1
|9 May 2022
|2022041901
|[[Moodle 4.0.1 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 4.0.x will end 8 May 2023 (12 months).
Bug fixes for security issues in 4.0.x will end 13 November 2023 (18 months).

==Moodle 3.11==
{| class="wikitable"
|-
!Moodle 3.11
|17 May 2021
|2021051700
|[[Moodle 3.11 release notes|Release Notes]]
|[https://docs.moodle.org/311/en/Upgrading Upgrading to 3.11]
|-
!Moodle 3.11.1
|12 July 2021
|2021051701
|[[Moodle 3.11.1 release notes|Release Notes]]
|
|-
!Moodle 3.11.2
|29 July 2021
|2021051702
|[[Moodle 3.11.2 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.11.3
|13 September 2021
|2021051703
|[[Moodle 3.11.3 release notes|Release Notes]]
|
|-
! Moodle 3.11.4
|8 November 2021
|2021051704
|[[Moodle 3.11.4 release notes|Release Notes]]
|
|-
! Moodle 3.11.5
|17 January 2022
|2021051705
|[[Moodle 3.11.5 release notes|Release Notes]]
|
|-
! Moodle 3.11.6
|14 March 2022
|2021051706
|[[Moodle 3.11.6 release notes|Release Notes]]
|
|-
! Moodle 3.11.7
|9 May 2022
|2021051707
|[[Moodle 3.11.7 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.11.x will end 14 Nov 2022 (12 months plus 6 months extension).
Bug fixes for security issues in 3.11.x will end 13 Nov 2023 (18 months plus 12 months extension).

==Moodle 3.10==
{| class="wikitable"
|-
! Moodle 3.10
|9 November 2020
|2020110900
|
[[Moodle 3.10 release notes|Release Notes]]
|[https://docs.moodle.org/310/en/Upgrading Upgrading to 3.10]
|-
!Moodle 3.10.1
|18 January 2021
|2020110901
| [[Moodle 3.10.1 release notes|Release Notes]]
|
|-
!Moodle 3.10.2
|8 March 2021
|2020110902
|[[Moodle 3.10.2 release notes|Release Notes]]
|
|-
! Moodle 3.10.3
|25 March 2021
|2020110903
|[[Moodle 3.10.3 release notes|Release Notes]]
|
|-
!Moodle 3.10.4
|10 May 2021
|2020110904
|[[Moodle 3.10.4 release notes|Release Notes]]
|
|-
!Moodle 3.10.5
|12 July 2021
|2020110905
|[[Moodle 3.10.5 release notes|Release Notes]]
|
|-
!Moodle 3.10.6
|29 July 2021
|2020110906
|[[Moodle 3.10.6 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.10.7
|13 September 2021
|2020110907
|[[Moodle 3.10.7 release notes|Release Notes]]
|
|-
!Moodle 3.10.8
|8 November 2021
|2020110908
|[[Moodle 3.10.8 release notes|Release Notes]]
|
|-
!Moodle 3.10.9
|17 January 2022
|2020110909
|[[Moodle 3.10.9 release notes|Release Notes]]
|-
!Moodle 3.10.10
|14 March 2022
|2020110910
|[[Moodle 3.10.10 release notes|Release Notes]]
|-
!Moodle 3.10.11
|9 May 2022
|2020110911
|[[Moodle 3.10.11 release notes|Release Notes]]
|}
Bug fixes for general core bugs in 3.10.x ended 8 November 2021 (12 months).
Bug fixes for security issues in 3.10.x will end 9 May 2022 (18 months).
==Moodle 3.9 (LTS)==
{| class="wikitable"
|-
! Moodle 3.9
|15 June 2020
|2020061500
|[[Moodle 3.9 release notes|Release Notes]]
|
[https://docs.moodle.org/39/en/Upgrading Upgrading to 3.9]
|-
!Moodle 3.9.1
|13 July 2020
|2020061501
|[[Moodle 3.9.1 release notes|Release Notes]]
|
|-
!Moodle 3.9.2
|14 September 2020
|2020061502
| [[Moodle 3.9.2 release notes|Release Notes]]
|
|-
!Moodle 3.9.3
|9 November 2020
|2020061503
| [[Moodle 3.9.3 release notes|Release Notes]]
|
|-
!Moodle 3.9.4
|18 January 2021
|2020061504
|[[Moodle 3.9.4 release notes|Release Notes]]
|
|-
!Moodle 3.9.5
|8 March 2021
|2020061505
|[[Moodle 3.9.5 release notes|Release Notes]]
|
|-
!Moodle 3.9.6
|25 March 2021
|2020061506
|[[Moodle 3.9.6 release notes|Release Notes]]
|
|-
!Moodle 3.9.7
|10 May 2021
|2020061507
|[[Moodle 3.9.7 release notes|Release Notes]]
|
|-
! Moodle 3.9.8
|12 July 2021
|2020061508
|[[Moodle 3.9.8 release notes|Release Notes]]
|
|-
!Moodle 3.9.9
|29 July 2021
|2020061509
|[[Moodle 3.9.9 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.9.10
|13 September 2021
|2020061510
|[[Moodle 3.9.10 release notes|Release Notes]]
|
|-
!Moodle 3.9.11
| 8 November 2021
|2020061511
|[[Moodle 3.9.11 release notes|Release Notes]]
|
|-
!Moodle 3.9.12
| 17 January 2022
|2020061512
|[[Moodle 3.9.12 release notes|Release Notes]]
|-
!Moodle 3.9.13
| 14 March 2022
|2020061513
|[[Moodle 3.9.13 release notes|Release Notes]]
|
|-
!Moodle 3.9.14
| 9 May 2022
|2020061514
|[[Moodle 3.9.14 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.9.x ended 10 May 2021 (12 months).
Bug fixes for security issues in 3.9.x will end 13 Nov 2023 (36 months plus 6 months extension).
==Moodle 3.8==
{| class="wikitable"
|-
!Moodle 3.8
|18 November 2019
|2019111800
|[[Moodle 3.8 release notes|Release Notes]]
|
[https://docs.moodle.org/38/en/Upgrading Upgrading to 3.8]
|-
!Moodle 3.8.1
|13 January 2020
|2019111801
|[[Moodle 3.8.1 release notes|Release Notes]]
|
|-
!Moodle 3.8.2
|9 March 2020
|2019111802
|[[Moodle 3.8.2 release notes|Release Notes]]
|
|-
!Moodle 3.8.3
|11 May 2020
|2019111803
|[[Moodle 3.8.3 release notes|Release Notes]]
|
|-
!Moodle 3.8.4
|13 July 2020
|2019111804
|[[Moodle 3.8.4 release notes|Release Notes]]
|
|-
!Moodle 3.8.5
|14 September 2020
|2019111805
| [[Moodle 3.8.5 release notes|Release Notes]]
|
|-
!Moodle 3.8.6
|9 November 2020
|2019111806
| [[Moodle 3.8.6 release notes|Release Notes]]
|
|-
!Moodle 3.8.7
|18 January 2021
|2019111807
|[[Moodle 3.8.7 release notes|Release Notes]]
|
|-
!Moodle 3.8.8
|8 March 2021
|2019111808
|[[Moodle 3.8.8 release notes|Release Notes]]
|
|-
!Moodle 3.8.9
|10 May 2021
|2019111809
|[[Moodle 3.8.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.8.x ended 9 November 2020 (12 months).
Bug fixes for security issues in 3.8.x ended 10 May 2021 (18 months).
==Moodle 3.7==
{| class="wikitable"
|-
!Moodle 3.7
|20 May 2019
|2019052000
|[[Moodle 3.7 release notes|Release Notes]]
|[https://docs.moodle.org/37/en/Upgrading Upgrading to 3.7]
|-
!Moodle 3.7.1
|8 July 2019
|2019052001
|[[Moodle 3.7.1 release notes|Release Notes]]
|
|-
!Moodle 3.7.2
|9 September 2019
|2019052002
|[[Moodle 3.7.2 release notes|Release Notes]]
|
|-
!Moodle 3.7.3
|11 November 2019
|2019052003
| [[Moodle 3.7.3 release notes|Release Notes]]
|
|-
!Moodle 3.7.4
|13 January 2020
|2019052004
|[[Moodle 3.7.4 release notes|Release Notes]]
|
|-
!Moodle 3.7.5
|9 March 2020
|2019052005
|[[Moodle 3.7.5 release notes|Release Notes]]
|
|-
!Moodle 3.7.6
|11 May 2020
|2019052006
|[[Moodle 3.7.6 release notes|Release Notes]]
|
|-
!Moodle 3.7.7
|13 July 2020
|2019052007
|[[Moodle 3.7.7 release notes|Release Notes]]
|
|-
!Moodle 3.7.8
|14 September 2020
|2019052008
| [[Moodle 3.7.8 release notes|Release Notes]]
|
|-
!Moodle 3.7.9
|9 November 2020
|2019052009
|[[Moodle 3.7.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.7.x ended 11 May 2020 (12 months).
Bug fixes for security issues in 3.7.x ended 9 November 2020 (18 months).
==Moodle 3.6==
{| class="wikitable"
|-
!Moodle 3.6
| 3 December 2018
|2018120300
|[[Moodle 3.6 release notes|Release Notes]]
|
[https://docs.moodle.org/36/en/Upgrading Upgrading to 3.6]
|-
!Moodle 3.6.1
|5 December 2018
|2018120301
| [[Moodle 3.6.1 release notes|Release Notes]]
|
|-
! Moodle 3.6.2
|14 January 2019
|2018120302
|[[Moodle 3.6.2 release notes|Release Notes]]
|
|-
!Moodle 3.6.3
|11 March 2019
|2018120303
|[[Moodle 3.6.3 release notes|Release Notes]]
|
|-
!Moodle 3.6.4
|13 May 2019
|2018120304
|[[Moodle 3.6.4 release notes|Release Notes]]
|
|-
!Moodle 3.6.5
|8th July 2019
|2018120305
|[[Moodle 3.6.5 release notes|Release Notes]]
|
|-
!Moodle 3.6.6
|9th September 2019
|2018120306
|[[Moodle 3.6.6 release notes|Release Notes]]
|
|-
!Moodle 3.6.7
| 11th November 2019
|2018120307
|[[Moodle 3.6.7 release notes|Release Notes]]
|
|-
!Moodle 3.6.8
|13th January 2020
|2018120308
|[[Moodle 3.6.8 release notes|Release Notes]]
|
|-
!Moodle 3.6.9
|9th March 2020
|2018120309
| [[Moodle 3.6.9 release notes|Release Notes]]
|
|-
!Moodle 3.6.10
|11th May 2020
|2018120310
|[[Moodle 3.6.10 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.6.x ended 11 November 2019 (12 months).
Bug fixes for security issues in 3.6.x ended 11 May 2020 (18 months).
==Moodle 3.5 (LTS)==
{| class="wikitable"
|-
!Moodle 3.5
|17 May 2018
|2018051700
|[[Moodle 3.5 release notes|Release Notes]]
|[https://docs.moodle.org/35/en/Upgrading Upgrading to 3.5]
|-
! Moodle 3.5.1
|9 July 2018
|2018051701
|[[Moodle 3.5.1 release notes|Release Notes]]
|
|-
!Moodle 3.5.2
|10 September 2018
|2018051702
|[[Moodle 3.5.2 release notes|Release Notes]]
|
|-
!Moodle 3.5.3
|12 November 2018
|2018051703
| [[Moodle 3.5.3 release notes|Release Notes]]
|
|-
! Moodle 3.5.4
|14 January 2019
|2018051704
|[[Moodle 3.5.4 release notes|Release Notes]]
|
|-
!Moodle 3.5.5
|11 March 2019
|2018051705
|[[Moodle 3.5.5 release notes|Release Notes]]
|
|-
!Moodle 3.5.6
|13 May 2019
|2018051706
|[[Moodle 3.5.6 release notes|Release Notes]]
|
|-
!Moodle 3.5.7
|8 July 2019
|2018051707
|[[Moodle 3.5.7 release notes|Release Notes]]
|
|-
!Moodle 3.5.8
|9 September 2019
|2018051708
|[[Moodle 3.5.8 release notes|Release Notes]]
|
|-
!Moodle 3.5.9
|11 November 2019
|2018051709
|[[Moodle 3.5.9 release notes|Release Notes]]
|
|-
!Moodle 3.5.10
|13 January 2020
|2018051710
| [[Moodle 3.5.10 release notes|Release Notes]]
|
|-
!Moodle 3.5.11
|9 March 2020
|2018051711
|[[Moodle 3.5.11 release notes|Release Notes]]
|
|-
!Moodle 3.5.12
|11 May 2020
|2018051712
| [[Moodle 3.5.12 release notes|Release Notes]]
|
|-
!Moodle 3.5.13
|13 July 2020
|2018051713
|[[Moodle 3.5.13 release notes|Release Notes]]
|
|-
!Moodle 3.5.14
| 14 September 2020
|2018051714
|[[Moodle 3.5.14 release notes|Release Notes]]
|
|-
!Moodle 3.5.15
|9 November 2020
|2018051715
|[[Moodle 3.5.15 release notes|Release Notes]]
|
|-
!Moodle 3.5.16
|18 January 2021
|2018051716
| [[Moodle 3.5.16 release notes|Release Notes]]
|
|-
!Moodle 3.5.17
|8 March 2021
| 2018051717
|[[Moodle 3.5.17 release notes|Release Notes]]
|
|-
!Moodle 3.5.18
| 10 May 2021
| 2018051718
|[[Moodle 3.5.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.5.x ended May 2019 (12 months).
Bug fixes for security issues in 3.5.x ended 10 May 2021 (36 months).
==Moodle 3.4==
{| class="wikitable"
|-
!Moodle 3.4
|13 November 2017
|2017111300
|[[Moodle 3.4 release notes|Release Notes]]
|
[https://docs.moodle.org/34/en/Upgrading Upgrading to 3.4]
|-
! Moodle 3.4.1
|15 January 2018
|2017111301
|[[Moodle 3.4.1 release notes|Release Notes]]
|
|-
!Moodle 3.4.2
|19 March 2018
|2017111302
|[[Moodle 3.4.2 release notes|Release Notes]]
|
|-
!Moodle 3.4.3
|17 May 2018
|2017111303
|[[Moodle 3.4.3 release notes|Release Notes]]
|
|-
! Moodle 3.4.4
|9 July 2018
|2017111304
|[[Moodle 3.4.4 release notes|Release Notes]]
|
|-
!Moodle 3.4.5
|10 September 2018
|2017111305
|[[Moodle 3.4.5 release notes|Release Notes]]
|
|-
!Moodle 3.4.6
|12 November 2018
|2017111306
| [[Moodle 3.4.6 release notes|Release Notes]]
|
|-
! Moodle 3.4.7
|14 January 2019
|2017111307
|[[Moodle 3.4.7 release notes|Release Notes]]
|
|-
!Moodle 3.4.8
|11 March 2019
|2017111308
|[[Moodle 3.4.8 release notes|Release Notes]]
|
|-
!Moodle 3.4.9
|13 May 2019
|2017111309
| [[Moodle 3.4.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.4.x ended 12 November 2018 (12 months).
Bug fixes for security issues in 3.4.x ended 13 May 2019 (18 months).
==Moodle 3.3==
{| class="wikitable"
|-
!Moodle 3.3
|15 May 2017
|2017051500
|[[Moodle 3.3 release notes|Release Notes]]
|
[https://docs.moodle.org/33/en/Upgrading Upgrading to 3.3]
|-
!Moodle 3.3.1
|10 July 2017
|2017051501
|[[Moodle 3.3.1 release notes|Release Notes]]
|
|-
!Moodle 3.3.2
|11 September 2017
|2017051502
|[[Moodle 3.3.2 release notes|Release Notes]]
|
|-
!Moodle 3.3.3
|13 November 2017
|2017051503
| [[Moodle 3.3.3 release notes|Release Notes]]
|
|-
! Moodle 3.3.4
|15 January 2018
|2017051504
|[[Moodle 3.3.4 release notes|Release Notes]]
|
|-
!Moodle 3.3.5
|19 March 2018
|2017051505
|[[Moodle 3.3.5 release notes|Release Notes]]
|
|-
!Moodle 3.3.6
|17 May 2018
|2017051506
|[[Moodle 3.3.6 release notes|Release Notes]]
|
|-
! Moodle 3.3.7
|9 July 2018
|2017051507
|[[Moodle 3.3.7 release notes|Release Notes]]
|
|-
!Moodle 3.3.8
|10 September 2018
|2017051508
|[[Moodle 3.3.8 release notes|Release Notes]]
|
|-
! Moodle 3.3.9
|12 November 2018
|2017051509
|[[Moodle 3.3.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.3.x ended 17 May 2018 (12 months).
Bug fixes for security issues in 3.3.x ended 12 November 2018 (18 months).
==Moodle 3.2==
{| class="wikitable"
|-
!Moodle 3.2
| 5 December 2016
|2016120500
|[[Moodle 3.2 release notes|Release Notes]]
|[https://docs.moodle.org/32/en/Upgrading Upgrading to 3.2]
|-
!Moodle 3.2.1
|9 January 2017
|2016120501
|[[Moodle 3.2.1 release notes|Release Notes]]
|
|-
!Moodle 3.2.2
|13 March 2017
|2016120502
|[[Moodle 3.2.2 release notes|Release Notes]]
|
|-
!Moodle 3.2.3
|8 May 2017
|2016120503
|[[Moodle 3.2.3 release notes|Release Notes]]
|
|-
!Moodle 3.2.4
|10 July 2017
|2016120504
|[[Moodle 3.2.4 release notes|Release Notes]]
|
|-
!Moodle 3.2.5
|11 September 2017
|2016120505
|[[Moodle 3.2.5 release notes|Release Notes]]
|
|-
!Moodle 3.2.6
|13 November 2017
|2016120506
| [[Moodle 3.2.6 release notes|Release Notes]]
|
|-
! Moodle 3.2.7
|15 January 2018
|2016120507
|[[Moodle 3.2.7 release notes|Release Notes]]
|
|-
!Moodle 3.2.8
|19 March 2018
|2016120508
|[[Moodle 3.2.8 release notes|Release Notes]]
|
|-
!Moodle 3.2.9
|17 May 2018
|2016120509
| [[Moodle 3.2.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.2.x ended 13 November 2017 (12 months).
Bug fixes for security issues in 3.2.x ended 17 May 2018 (18 months).
==Moodle 3.1 (LTS)==
{| class="wikitable"
|-
!Moodle 3.1
|23 May 2016
|2016052300
|[[Moodle 3.1 release notes|Release Notes]]
|
[https://docs.moodle.org/31/en/Upgrading Upgrading to 3.1]
|-
!Moodle 3.1.1
|11 July 2016
|2016052301
|[[Moodle 3.1.1 release notes|Release Notes]]
|
|-
!Moodle 3.1.2
|12 September 2016
|2016052302
|[[Moodle 3.1.2 release notes|Release Notes]]
|
|-
!Moodle 3.1.3
|14 November 2016
|2016052303
|[[Moodle 3.1.3 release notes|Release Notes]]
|
|-
!Moodle 3.1.4
|9 January 2017
|2016052304
|[[Moodle 3.1.4 release notes|Release Notes]]
|
|-
!Moodle 3.1.5
|13 March 2017
|2016052305
|[[Moodle 3.1.5 release notes|Release Notes]]
|
|-
!Moodle 3.1.6
|8 May 2017
|2016052306
|[[Moodle 3.1.6 release notes|Release Notes]]
|
|-
!Moodle 3.1.7
|10 July 2017
|2016052307
|[[Moodle 3.1.7 release notes|Release Notes]]
|
|-
!Moodle 3.1.8
|11 September 2017
|2016052308
|[[Moodle 3.1.8 release notes|Release Notes]]
|
|-
!Moodle 3.1.9
|13 November 2017
|2016052309
|[[Moodle 3.1.9 release notes|Release Notes]]
|
|-
!Moodle 3.1.10
|15 January 2018
|2016052310
|[[Moodle 3.1.10 release notes|Release Notes]]
|
|-
! Moodle 3.1.11
|19 March 2018
|2016052311
|[[Moodle 3.1.11 release notes|Release Notes]]
|
|-
!Moodle 3.1.12
|17 May 2018
|2016052312
|[[Moodle 3.1.12 release notes|Release Notes]]
|
|-
!Moodle 3.1.13
|9 July 2018
|2016052313
|[[Moodle 3.1.13 release notes|Release Notes]]
|
|-
!Moodle 3.1.14
|10 September 2018
|2016052314
|[[Moodle 3.1.14 release notes|Release Notes]]
|
|-
! Moodle 3.1.15
|12 November 2018
|2016052315
|[[Moodle 3.1.15 release notes|Release Notes]]
|
|-
!Moodle 3.1.16
|14 January 2019
|2016052316
|[[Moodle 3.1.16 release notes|Release Notes]]
|
|-
! Moodle 3.1.17
|11 March 2019
| 2016052317
|[[Moodle 3.1.17 release notes|Release Notes]]
|
|-
!Moodle 3.1.18
|13 May 2019
|2016052318
|[[Moodle 3.1.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.1.x ended 8 May 2017 (12 months).
Bug fixes for security issues in 3.1.x ended 13 May 2019 (36 months).
==Moodle 3.0==
{| class="wikitable"
|-
!Moodle 3.0
|16 November 2015
|2015111600
|[[Moodle 3.0 release notes|Release Notes]]
|[https://docs.moodle.org/30/en/Upgrading Upgrading to 3.0]
|-
!Moodle 3.0.1
|21 December 2015
|2015111601
| [[Moodle 3.0.1 release notes|Release Notes]]
|
|-
! Moodle 3.0.2
|11 January 2016
|2015111602
|[[Moodle 3.0.2 release notes|Release Notes]]
|
|-
!Moodle 3.0.3
|14 March 2016
|2015111603
|[[Moodle 3.0.3 release notes|Release Notes]]
|
|-
!Moodle 3.0.4
|9 May 2016
|2015111604
|[[Moodle 3.0.4 release notes|Release Notes]]
|
|-
!Moodle 3.0.5
|11 July 2016
|2015111605
|[[Moodle 3.0.5 release notes|Release Notes]]
|
|-
!Moodle 3.0.6
|12 September 2016
|2015111606
|[[Moodle 3.0.6 release notes|Release Notes]]
|
|-
!Moodle 3.0.7
|14 November 2016
|2015111607
|[[Moodle 3.0.7 release notes|Release Notes]]
|
|-
!Moodle 3.0.8
|9 January 2017
|2015111608
|[[Moodle 3.0.8 release notes|Release Notes]]
|
|-
!Moodle 3.0.9
|13 March 2017
|2015111609
|[[Moodle 3.0.9 release notes|Release Notes]]
|
|-
!Moodle 3.0.10
|8 May 2017
|2015111610
|[[Moodle 3.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.0.x ended 14 November 2016 (12 months).
Bug fixes for security issues in 3.0.x ended 8 May 2017 (18 months).
==Moodle 2.9==
{| class="wikitable"
|-
!Moodle 2.9
| 11 May 2015
|2015051100
|[[Moodle 2.9 release notes|Release Notes]]
| [https://docs.moodle.org/29/en/Upgrading_to_Moodle_2.9 Upgrading to 2.9]
|-
! Moodle 2.9.1
|6 July 2015
|2015051101
|[[Moodle 2.9.1 release notes|Release Notes]]
|
|-
!Moodle 2.9.2
|14 September 2015
|2015051102
| [[Moodle 2.9.2 release notes|Release Notes]]
|
|-
!Moodle 2.9.3
|9 November 2015
|2015051103
| [[Moodle 2.9.3 release notes|Release Notes]]
|
|-
! Moodle 2.9.4
|11 January 2016
|2015051104
|[[Moodle 2.9.4 release notes|Release Notes]]
|
|-
!Moodle 2.9.5
|14 March 2016
|2015051105
|[[Moodle 2.9.5 release notes|Release Notes]]
|
|-
!Moodle 2.9.6
|9 May 2016
|2015051106
|[[Moodle 2.9.6 release notes|Release Notes]]
|
|-
!Moodle 2.9.7
|11 July 2016
|2015051107
|[[Moodle 2.9.7 release notes|Release Notes]]
|
|-
!Moodle 2.9.8
|12 September 2016
|2015051108
|[[Moodle 2.9.8 release notes|Release Notes]]
|
|-
! Moodle 2.9.9
|14 November 2016
|2015051109
|[[Moodle 2.9.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.9.x ended 9 May 2016 (12 months).
Bug fixes for security issues in 2.9.x ended 14 November 2016 (18 months).
==Moodle 2.8==
{| class="wikitable"
|-
!Moodle 2.8
|10 November 2014
|2014111000
| [[Moodle 2.8 release notes|Release Notes]]
|[https://docs.moodle.org/28/en/Upgrading_to_Moodle_2.8 Upgrading to 2.8]
|-
!Moodle 2.8.1
|13 November 2014
|2014111001
| [[Moodle 2.8.1 release notes|Release Notes]]
|
|-
!Moodle 2.8.2
|12 January 2015
|2014111002
| [[Moodle 2.8.2 release notes|Release Notes]]
|
|-
!Moodle 2.8.3
|2 February 2015
|2014111003
|[[Moodle 2.8.3 release notes|Release Notes]]
|
|-
!Moodle 2.8.4
|9 March 2015
|2014111004
|[[Moodle 2.8.4 release notes|Release Notes]]
|
|-
!Moodle 2.8.5
|10 March 2015
|2014111005
|[[Moodle 2.8.5 release notes|Release Notes]]
|
|-
!Moodle 2.8.6
|11 May 2015
|2014111006
|[[Moodle 2.8.6 release notes|Release Notes]]
|
|-
! Moodle 2.8.7
|6 July 2015
|2014111007
|[[Moodle 2.8.7 release notes|Release Notes]]
|
|-
!Moodle 2.8.8
|14 September 2015
|2014111008
| [[Moodle 2.8.8 release notes|Release Notes]]
|
|-
!Moodle 2.8.9
|9 November 2015
|2014111009
|[[Moodle 2.8.9 release notes|Release Notes]]
|
|-
!Moodle 2.8.10
|11 January 2016
|2014111010
|[[Moodle 2.8.10 release notes|Release Notes]]
|
|-
!Moodle 2.8.11
|14 March 2016
|2014111011
|[[Moodle 2.8.11 release notes|Release Notes]]
|
|-
!Moodle 2.8.12
|9 May 2016
|2014111012
| [[Moodle 2.8.12 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.8.x ended 9 November 2015 (12 months).
Bug fixes for security issues in 2.8.x ended 9 May 2016 (18 months).
==Moodle 2.7 (LTS)==
{| class="wikitable"
|-
!Moodle 2.7
| 12 May 2014
|2014051200
|[[Moodle 2.7 release notes|Release Notes]]
|[https://docs.moodle.org/27/en/Upgrading_to_Moodle_2.7 Upgrading to 2.7]
|-
! Moodle 2.7.1
|14 July 2014
|2014051201
|[[Moodle 2.7.1 release notes|Release Notes]]
|
|-
!Moodle 2.7.2
|8 September 2014
|2014051202
|[[Moodle 2.7.2 release notes|Release Notes]]
|
|-
!Moodle 2.7.3
|10 November 2014
|2014051203
| [[Moodle 2.7.3 release notes|Release Notes]]
|
|-
!Moodle 2.7.4
|12 January 2015
|2014051204
| [[Moodle 2.7.4 release notes|Release Notes]]
|
|-
!Moodle 2.7.5
|2 February 2015
|2014051205
|[[Moodle 2.7.5 release notes|Release Notes]]
|
|-
!Moodle 2.7.6
|9 March 2015
|2014051206
|[[Moodle 2.7.6 release notes|Release Notes]]
|
|-
!Moodle 2.7.7
|10 March 2015
|2014051207
|[[Moodle 2.7.7 release notes|Release Notes]]
|
|-
!Moodle 2.7.8
|11 May 2015
|2014051208
|[[Moodle 2.7.8 release notes|Release Notes]]
|
|-
!Moodle 2.7.9
|6 July 2015
|2014051209
|[[Moodle 2.7.9 release notes|Release Notes]]
|
|-
!Moodle 2.7.10
| 14 September 2015
|2014051210
|[[Moodle 2.7.10 release notes|Release Notes]]
|
|-
!Moodle 2.7.11
|9 November 2015
|2014051211
|[[Moodle 2.7.11 release notes|Release Notes]]
|
|-
!Moodle 2.7.12
|11 January 2016
|2014051212
|[[Moodle 2.7.12 release notes|Release Notes]]
|
|-
!Moodle 2.7.13
|14 March 2016
|2014051213
|[[Moodle 2.7.13 release notes|Release Notes]]
|
|-
!Moodle 2.7.14
|9 May 2016
|2014051214
| [[Moodle 2.7.14 release notes|Release Notes]]
|
|-
!Moodle 2.7.15
|11 July 2016
|2014051215
|[[Moodle 2.7.15 release notes|Release Notes]]
|
|-
!Moodle 2.7.16
|12 September 2016
|2014051216
|[[Moodle 2.7.16 release notes|Release Notes]]
|
|-
!Moodle 2.7.17
|14 November 2016
|2014051217
|[[Moodle 2.7.17 release notes|Release Notes]]
|
|-
!Moodle 2.7.18
|9 January 2017
|2014051218
|[[Moodle 2.7.18 release notes|Release Notes]]
|
|-
!Moodle 2.7.19
|13 March 2017
|2014051219
|[[Moodle 2.7.19 release notes|Release Notes]]
|
|-
!Moodle 2.7.20
|8 May 2017
|2014051220
| [[Moodle 2.7.20 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.7.x ended 11 May 2015 (12 months).
Bug fixes for security issues in 2.7.x ended 8 May 2017 (36 months).
==Moodle 2.6==
{| class="wikitable"
|-
!Moodle 2.6
|18 November 2013
|2013111800
|[[Moodle 2.6 release notes|Release Notes]]
|[https://docs.moodle.org/26/en/Upgrading_to_Moodle_2.6 Upgrading to 2.6]
|-
!Moodle 2.6.1
|13 January 2014
| 2013111801
| [[Moodle 2.6.1 release notes|Release Notes]]
|
|-
!Moodle 2.6.2
|10 March 2014
|2013111802
|[[Moodle 2.6.2 release notes|Release Notes]]
|
|-
!Moodle 2.6.3
|12 May 2014
|2013111803
|[[Moodle 2.6.3 release notes|Release Notes]]
|
|-
!Moodle 2.6.4
|14 July 2014
|2013111804
|[[Moodle 2.6.4 release notes|Release Notes]]
|
|-
!Moodle 2.6.5
|8 September 2014
|2013111805
|[[Moodle 2.6.5 release notes|Release Notes]]
|
|-
!Moodle 2.6.6
|10 November 2014
|2013111806
|[[Moodle 2.6.6 release notes|Release Notes]]
|
|-
!Moodle 2.6.7
|12 January 2015
|2013111807
|[[Moodle 2.6.7 release notes|Release Notes]]
|
|-
! Moodle 2.6.8
|2 February 2015
|2013111808
|[[Moodle 2.6.8 release notes|Release Notes]]
|
|-
! Moodle 2.6.9
|9 March 2015
|2013111809
|[[Moodle 2.6.9 release notes|Release Notes]]
|
|-
!Moodle 2.6.10
|10 March 2015
|2013111810
| [[Moodle 2.6.10 release notes|Release Notes]]
|
|-
!Moodle 2.6.11
|11 May 2015
|2013111811
|[[Moodle 2.6.11 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 2.6.x ended 10 November 2014 (12 months).
Bug fixes for security issues in 2.6.x ended 11 May 2015 (18 months).
==Moodle 2.5==
{| class="wikitable"
|-
!Moodle 2.5
| 14 May 2013
|2013051400
|[[Moodle 2.5 release notes|Release Notes]]
| [https://docs.moodle.org/25/en/Upgrading_to_Moodle_2.5 Upgrading to 2.5]
|-
! Moodle 2.5.1
|8 July 2013
|2013051401
|[[Moodle 2.5.1 release notes|Release Notes]]
|
|-
!Moodle 2.5.2
|9 September 2013
|2013051402
|[[Moodle 2.5.2 release notes|Release Notes]]
|
|-
!Moodle 2.5.3
|11 November 2013
|2013051403
|[[Moodle 2.5.3 release notes|Release Notes]]
|
|-
!Moodle 2.5.4
|13 January 2014
| 2013051404
| [[Moodle 2.5.4 release notes|Release Notes]]
|
|-
!Moodle 2.5.5
|10 March 2014
|2013051405
|[[Moodle 2.5.5 release notes|Release Notes]]
|
|-
!Moodle 2.5.6
|12 May 2014
|2013051406
|[[Moodle 2.5.6 release notes|Release Notes]]
|
|-
!Moodle 2.5.7
|14 July 2014
|2013051407
|[[Moodle 2.5.7 release notes|Release Notes]]
|
|-
!Moodle 2.5.8
|8 September 2014
|2013051408
|[[Moodle 2.5.8 release notes|Release Notes]]
|
|-
! Moodle 2.5.9
| 10 November 2014
|2013051409
|[[Moodle 2.5.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.5.x ended May 2014 (12 months).
Bug fixes for security issues in 2.5.x ended 10 November 2014 (18 months).
==Moodle 2.4==
{| class="wikitable"
|-
! Moodle 2.4
|3 December 2012
|2012120300
|[[Moodle 2.4 release notes|Release Notes]]
|[https://docs.moodle.org/24/en/Upgrading_to_Moodle_2.4 Upgrading to 2.4]
|-
! Moodle 2.4.1
|14 January 2013
|2012120301
|[[Moodle 2.4.1 release notes|Release Notes]]
|
|-
!Moodle 2.4.2
|11 March 2013
|2012120302
|[[Moodle 2.4.2 release notes|Release Notes]]
|
|-
!Moodle 2.4.3
|18 March 2013
|2012120303
|[[Moodle 2.4.3 release notes|Release Notes]]
|
|-
!Moodle 2.4.4
|14 May 2013
|2012120304
|[[Moodle 2.4.4 release notes|Release Notes]]
|
|-
!Moodle 2.4.5
|8 July 2013
|2012120305
|[[Moodle 2.4.5 release notes|Release Notes]]
|
|-
!Moodle 2.4.6
|9 September 2013
|2012120306
|[[Moodle 2.4.6 release notes|Release Notes]]
|
|-
!Moodle 2.4.7
|11 November 2013
|2012120307
| [[Moodle 2.4.7 release notes|Release Notes]]
|
|-
! Moodle 2.4.8
|13 January 2014
|2012120308
|[[Moodle 2.4.8 release notes|Release Notes]]
|
|-
!Moodle 2.4.9
|10 March 2014
|2012120309
|[[Moodle 2.4.9 release notes|Release Notes]]
|
|-
!Moodle 2.4.10
|12 May 2014
|2012120310
| [[Moodle 2.4.10 release notes|Release Notes]]
|
|-
!Moodle 2.4.11
|14 July 2014
|2012120311
|[[Moodle 2.4.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.4.x ended December 2013 (12 months).
Bug fixes for security issues in 2.4.x ended June 2014 (18 months).
==Moodle 2.3==
{| class="wikitable"
|-
!Moodle 2.3
|25 June 2012
|2012062500
|[[Moodle 2.3 release notes|Release Notes]]
| [https://docs.moodle.org/23/en/Upgrading_to_Moodle_2.3 Upgrading to 2.3]
|-
!Moodle 2.3.1
|9 July 2012
|2012062501
|[[Moodle 2.3.1 release notes|Release Notes]]
|
|-
! Moodle 2.3.2
|10 September 2012
|2012062502
|[[Moodle 2.3.2 release notes|Release Notes]]
|
|-
!Moodle 2.3.3
|12 November 2012
|2012062503
|[[Moodle 2.3.3 release notes|Release Notes]]
|
|-
! Moodle 2.3.4
|14 January 2013
|2012062504
|[[Moodle 2.3.4 release notes|Release Notes]]
|
|-
!Moodle 2.3.5
|11 March 2013
|2012062505
|[[Moodle 2.3.5 release notes|Release Notes]]
|
|-
!Moodle 2.3.6
|18 March 2013
|2012062506
|[[Moodle 2.3.6 release notes|Release Notes]]
|
|-
!Moodle 2.3.7
|14 May 2013
|2012062507
|[[Moodle 2.3.7 release notes|Release Notes]]
|
|-
!Moodle 2.3.8
|8 July 2013
|2012062508
|[[Moodle 2.3.8 release notes|Release Notes]]
|
|-
!Moodle 2.3.9
|9 September 2013
|2012062509
|[[Moodle 2.3.9 release notes|Release Notes]]
|
|-
! Moodle 2.3.10
|11 November 2013
|2012062510
|[[Moodle 2.3.10 release notes|Release Notes]]
|
|-
!Moodle 2.3.11
|13 January 2014
|2012062511
|[[Moodle 2.3.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.3.x ended June 2013 (12 months).
Bug fixes for security issues in 2.3.x ended December 2013 (18 months).
==Moodle 2.2==
{| class="wikitable"
|-
! Moodle 2.2
|5 December 2011
|2011120500
|[[Moodle 2.2 release notes|Release Notes]]
|[https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 Upgrading to 2.2]
|-
!Moodle 2.2.1
|9 January 2012
|2011120501
|[[Moodle 2.2.1 release notes|Release Notes]]
|
|-
!Moodle 2.2.2
|12 March 2012
|2011120502
|[[Moodle 2.2.2 release notes|Release Notes]]
|
|-
!Moodle 2.2.3
|14 May 2012
|2011120503
|[[Moodle 2.2.3 release notes|Release Notes]]
|
|-
! Moodle 2.2.4
|9 July 2012
|2011120504
|[[Moodle 2.2.4 release notes|Release Notes]]
|
|-
!Moodle 2.2.5
|10 September 2012
|2011120505
|[[Moodle 2.2.5 release notes|Release Notes]]
|
|-
!Moodle 2.2.6
|12 November 2012
|2011120506
| [[Moodle 2.2.6 release notes|Release Notes]]
|
|-
! Moodle 2.2.7
|14 January 2013
|2011120507
|[[Moodle 2.2.7 release notes|Release Notes]]
|
|-
!Moodle 2.2.8
|11 March 2013
|2011120508
|[[Moodle 2.2.8 release notes|Release Notes]]
|
|-
!Moodle 2.2.9
|18 March 2013
|2011120509
|[[Moodle 2.2.9 release notes|Release Notes]]
|
|-
!Moodle 2.2.10
|14 May 2013
| 2011120510
|[[Moodle 2.2.10 release notes|Release Notes]]
|
|-
!Moodle 2.2.11
|8 July 2013
|2011120511
|[[Moodle 2.2.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.2.x ended December 2012 (12 months).
Bug fixes for security issues in 2.2.x ended June 2013 (18 months).
==Moodle 2.1==
{| class="wikitable"
|-
!Moodle 2.1
| 1 July 2011
|2011070100
|[[Moodle 2.1 release notes|Release Notes]]
|[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to 2.1]
|-
! Moodle 2.1.1
|1 August 2011
|2011070101
| [[Moodle 2.1.1 release notes|Release Notes]]
|
|-
!Moodle 2.1.2
|10 October 2011
|2011070102
|[[Moodle 2.1.2 release notes|Release Notes]]
|
|-
!Moodle 2.1.3
|28 November 2011
|2011070103
|[[Moodle 2.1.3 release notes|Release Notes]]
|
|-
!Moodle 2.1.4
|9 January 2012
|2011070104
|[[Moodle 2.1.4 release notes|Release Notes]]
|
|-
!Moodle 2.1.5
|12 March 2012
|2011070105
|[[Moodle 2.1.5 release notes|Release Notes]]
|
|-
!Moodle 2.1.6
|14 May 2012
|2011070106
|[[Moodle 2.1.6 release notes|Release Notes]]
|
|-
! Moodle 2.1.7
|9 July 2012
|2011070107
|[[Moodle 2.1.7 release notes|Release Notes]]
|
|-
!Moodle 2.1.8
|10 September 2012
|2011070108
|[[Moodle 2.1.8 release notes|Release Notes]]
|
|-
!Moodle 2.1.9
|12 November 2012
|2011070109
|[[Moodle 2.1.9 release notes|Release Notes]]
|
|-
!Moodle 2.1.10
|14 January 2013
|2011070110
|[[Moodle 2.1.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.1.x ended June 2012 (12 months).
Bug fixes for security issues in 2.1.x ended December 2012 (18 months).
==Moodle 2.0==
{| class="wikitable"
|-
!Moodle 2.0
|24 November 2010
|2010112400
| [[Moodle 2.0 release notes|Release Notes]]
|[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to 2.0]
|-
!Moodle 2.0.1
|25 December 2010
|2010122500
|[[Moodle 2.0.1 release notes|Release Notes]]
|
|-
!Moodle 2.0.2
|21 February 2011
|2011022100
|[[Moodle 2.0.2 release notes|Release Notes]]
|
|-
!Moodle 2.0.3
|5 May 2011
|2011033003
|[[Moodle 2.0.3 release notes|Release Notes]]
|
|-
! Moodle 2.0.4
|1 August 2011
|2011033004
| [[Moodle 2.0.4 release notes|Release Notes]]
|
|-
!Moodle 2.0.5
|10 October 2011
|2011033005
|[[Moodle 2.0.5 release notes|Release Notes]]
|
|-
!Moodle 2.0.6
|28 November 2011
|2011033006
|[[Moodle 2.0.6 release notes|Release Notes]]
|
|-
!Moodle 2.0.7
|9 January 2012
|2011033007
|[[Moodle 2.0.7 release notes|Release Notes]]
|
|-
!Moodle 2.0.8
|12 March 2012
|2011033008
|[[Moodle 2.0.8 release notes|Release Notes]]
|
|-
!Moodle 2.0.9
|14 May 2012
|2011033009
|[[Moodle 2.0.9 release notes|Release Notes]]
|
|-
!Moodle 2.0.10
|9 July 2012
|2011033010
|[[Moodle 2.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.0.x ended December 2011 (12 months).
Bug fixes for security issues in 2.0.x ended June 2012 (18 months).
==Moodle 1.9==
{| class="wikitable"
|-
!Moodle 1.9
|3 March 2008
|2007101509
|[[Moodle 1.9 release notes|Release Notes]]
|[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to 1.9]
|-
!Moodle 1.9.1
|15 May 2008
| 2007101512
|[[Moodle 1.9.1 release notes|Release Notes]]
|
|-
! Moodle 1.9.2
|11 July 2008
|2007101520
|[[Moodle 1.9.2 release notes|Release Notes]]
|
|-
!Moodle 1.9.3
|15 October 2008
|2007101530
|[[Moodle 1.9.3 release notes|Release Notes]]
|
|-
!Moodle 1.9.4
|28 January 2009
|2007101540
|[[Moodle 1.9.4 release notes|Release Notes]]
|
|-
!Moodle 1.9.5
|13 May 2009
|2007101550
|[[Moodle 1.9.5 release notes|Release Notes]]
|
|-
!Moodle 1.9.6
|21 October 2009
|2007101560
|[[Moodle 1.9.6 release notes|Release Notes]]
|
|-
!Moodle 1.9.7
|25 November 2009
|2007101570
|[[Moodle 1.9.7 release notes|Release Notes]]
|
|-
!Moodle 1.9.8
|25 March 2010
|2007101580.00
|[[Moodle 1.9.8 release notes|Release Notes]]
|
|-
! Moodle 1.9.9
| 8 June 2010
| 2007101590.00
| [[Moodle 1.9.9 release notes|Release Notes]]
|
|-
!Moodle 1.9.10
|25 October 2010
|2007101591.00
|
[[Moodle 1.9.10 release notes|Release Notes]]
|
|-
!Moodle 1.9.11
|21 February 2011
|2007101591.02
|[[Moodle 1.9.11 release notes|Release Notes]]
|
|-
! Moodle 1.9.12
|10 May 2011
|2007101591.03
|[[Moodle 1.9.12 release notes|Release Notes]]
|
|-
!Moodle 1.9.13
|1 August 2011
|2007101591.04
|[[Moodle 1.9.13 release notes|Release Notes]]
|
|-
!Moodle 1.9.14
|10 October 2011
|2007101591.06
|
[[Moodle 1.9.14 release notes|Release Notes]]
|
|-
!Moodle 1.9.15
|28 November 2011
| 2007101591.07
| [[Moodle 1.9.15 release notes|Release Notes]]
|
|-
!Moodle 1.9.16
|9 January 2012
|2007101591.10
|[[Moodle 1.9.16 release notes|Release Notes]]
|
|-
! Moodle 1.9.17
|12 March 2012
|2007101591.12
|[[Moodle 1.9.17 release notes|Release Notes]]
|
|-
!Moodle 1.9.18
|14 May 2012
|2007101591.16
|[[Moodle 1.9.18 release notes|Release Notes]]
|
|-
! Moodle 1.9.19
|9 July 2012
|2007101592.00
|[[Moodle 1.9.19 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 1.9.x has ended June 2011 (3.5 years).
Bug fixes for security issues in 1.9.x by Moodle HQ ended June 2012 (4.5 years).
Bug fixes for security issues in 1.9.19+ branch by [http://catalyst.net.nz Catalyst IT] ended [http://moodle.org/mod/forum/discuss.php?d=199706 Dec 2013] (6 years).
==Moodle 1.8 ==
*[[Moodle 1.8 release notes|Moodle 1.8]] - 30 March 2007
*[[Moodle 1.8.1 release notes|Moodle 1.8.1]] - 14 June 2007
*[[Moodle 1.8.2 release notes|Moodle 1.8.2]] - 8 July 2007
*[[Moodle 1.8.3 release notes|Moodle 1.8.3]] - 11 October 2007
*[[Moodle 1.8.4 release notes|Moodle 1.8.4]] - 11 January 2008
*[[Moodle 1.8.5 release notes|Moodle 1.8.5]] - 8 April 2008
*[[Moodle 1.8.6 release notes|Moodle 1.8.6]] - 11 July 2008
*[[Moodle 1.8.7 release notes|Moodle 1.8.7]] - 15 October 2008
*[[Moodle 1.8.8 release notes|Moodle 1.8.8]] - 28 January 2009
*[[Moodle 1.8.9 release notes|Moodle 1.8.9]] - 15 May 2009
*[[Moodle 1.8.10 release notes|Moodle 1.8.10]] - 26 October 2009
*[[Moodle 1.8.11 release notes|Moodle 1.8.11]] - 25 November 2009
*[[Moodle 1.8.12 release notes|Moodle 1.8.12]] - 27 March 2010
*[[Moodle 1.8.13 release notes|Moodle 1.8.13]] - 8 June 2010
*[[Moodle 1.8.14 release notes|Moodle 1.8.14]] - 3 December 2010
*Support has ended

==Moodle 1.7==
*[[Moodle 1.7 release notes|Moodle 1.7]] - 7 November 2006
*[[Moodle 1.7.1 release notes|Moodle 1.7.1]] - 17 January 2007
*[[Moodle 1.7.2 release notes|Moodle 1.7.2]] - 30 March 2007
*[[Moodle 1.7.3 release notes|Moodle 1.7.3]] - 11 October 2007
*[[Moodle 1.7.4 release notes|Moodle 1.7.4]] - 11 January 2008
*[[Moodle 1.7.5 release notes|Moodle 1.7.5]] - 11 July 2008
*[[Moodle 1.7.6 release notes|Moodle 1.7.6]] - 15 October 2008
*[[Moodle 1.7.7 release notes|Moodle 1.7.7]] - 28 January 2009
*Support has ended
==Moodle 1.6==
*[[Moodle 1.6 release notes|Moodle 1.6]] - 20 June 2006
*[[Moodle 1.6.1 release notes|Moodle 1.6.1]] - 20 July 2006
*[[Moodle 1.6.2 release notes|Moodle 1.6.2]] - 12 September 2006
*[[Moodle 1.6.3 release notes|Moodle 1.6.3]] - 10 October 2006
*[[Moodle 1.6.4 release notes|Moodle 1.6.4]] - 17 January 2007
*[[Moodle 1.6.5 release notes|Moodle 1.6.5]] - 30 March 2007
*Moodle 1.6.6 - 11 January 2008
*Moodle 1.6.7 - 11 July 2008
*[[Moodle 1.6.8 release notes|Moodle 1.6.8]] - 15 October 2008
*[[Moodle 1.6.9 release notes|Moodle 1.6.9]] - 28 January 2009
* Support has ended
==Moodle 1.5==
*[[Moodle 1.5 release notes|Moodle 1.5]] - 5 June 2005
*[[Moodle 1.5.1 release notes|Moodle 1.5.1]] - 8 July 2005
*[[Moodle 1.5.2 release notes|Moodle 1.5.2]] - 16 July 2005
*[[Moodle 1.5.3 release notes|Moodle 1.5.3]] - 11 November 2005
*[[Moodle 1.5.4 release notes|Moodle 1.5.4]] - 21 May 2006
*Support has ended
==Moodle 1.4==
*Moodle 1.4 - 31 August 2004
*Moodle 1.4.1 - 12 September 2004
*Moodle 1.4.2 - 5 November 2004
*Moodle 1.4.3 - 21 December 2004
*Moodle 1.4.4 - 7 March 2005
*[[Moodle 1.4.5 release notes|Moodle 1.4.5]] - 7 May 2005
*Support has ended
==Moodle 1.3==
*Moodle 1.3 - 25 May 2004
* Moodle 1.3.1 - 4 June 2004
*Moodle 1.3.2 - 9 July 2004
*Moodle 1.3.3 - 16 July 2004
* Moodle 1.3.4 - 11 August 2004
*Moodle 1.3.5 - 9 September 2004
*Support has ended
==Moodle 1.2==
*Moodle 1.2 - 20 March 2004
*Moodle 1.2.1 - 25 March 2004
*Support has ended
==Moodle 1.1==
*Moodle 1.1 - 29 August 2003
*Moodle 1.1.1 - 11 September 2003
*Support has ended
== Moodle 1.0==
*Moodle 1.0 - 20 August 2002
*Moodle 1.0.1 - 26 August 2002
*Moodle 1.0.2 - 2 September 2002
*Moodle 1.0.3 - 5 September 2002
*Moodle 1.0.4 - 10 September 2002
*Moodle 1.0.5 - 27 September 2002
* Moodle 1.0.6 - 26 October 2002
::1.0.6.1 - 6 November 2002
::1.0.6.2 - 11 November 2002
::1.0.6.3 - 14 November 2002
::1.0.6.4 - 25 November 2002
*Moodle 1.0.7 - 9 December 2002
*Moodle 1.0.8 - 7 January 2003
*Moodle 1.0.9 - 30 May 2003
*Support has ended
==See also==
*[[Roadmap]] - future versions
*[[Moodle versions]] - an explanation of how our versions work plus version numbers for each release (for $plugin->requires)
[[Category:Release notes]]
[[Category:Core development]]
[[fr:Historique des versions]]
[[es:dev/Historia de las versiones]]
[[de:Versionshistorie]]

Releases

2022-05-09T01:45:20Z

Abgreeve: Update of minor versions.

This page lists all official releases of Moodle, grouped by branch in reverse chronological order.
==Version support==
From Moodle 2.6 onwards, the end of support, both general and security, happens the second Monday of May and November, observing the 12, 18... month periods, no matter if the major release date was moved or not.

The most recent [https://en.wikipedia.org/wiki/Long-term_support long-term support release (LTS)] version is Moodle 3.9.
{| class="wikitable" border="1px solid #dee2e6;"
|-
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Version
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Release status
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Initial release
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:rgba(0, 0, 0, 0.05);" | General support ends
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Security support ends
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.9 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 15 June 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 10 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 November 2023 (ext 6M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.11
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 17 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 14 Nov 2022 (ext 6M)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 Nov 2023 (ext 12M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |4.0
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |19 April 2022
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |8 May 2023
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |13 November 2023
|-
|4.1 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
|November 2022
|November 2023
|November 2025
|}
[[Image:401_release_graph.png|alt=Release graph]]

Release graph key:
{| class="wikitable" border="1px solid #dee2e6;"
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Currently supported stable releases.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | Current release of versions still receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Future point releases receiving bug fixes, as well as security updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#316d5e; color:white; adding: .3rem 0.5rem 0.3rem 0.5rem;" |Future security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Future point releases receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#686566; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Previously released versions containing bug fixes, as well as security updates. Updating to a currently supported version is recommended.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#282828; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Previously released versions containing security updates only. Updating to a currently supported version is recommended.
|}

==General release calendar==
These are the target dates for releases. These dates may vary slightly due to unforeseen circumstances.
{| class="wikitable"
|-
!Release type
!Frequency
!Months
|-
|[[Process#Major_release_cycles|Major]] (eg. 3.x)
|6 monthly
|Second Monday of May and November
|-
|[[Process#Stable_maintenance_cycles|Minor]] (Point) (eg. 3.x.y)
| 2 monthly
|Second Monday of July, September, November, March and May.
Third Monday of January.
|}
All releases are preceded by a one week warning. Upcoming release dates can be found in the [https://www.google.com/calendar/ical/moodle.com_p4c2oe7hsb77ltaro5qtihb5d4%40group.calendar.google.com/public/basic.ics Moodle development calendar] (Note, this is an iCAL link that will try to add the dates to your personal calendar. If you just want to browse the dates online, use [https://calendar.google.com/calendar/embed?src=moodle.com_p4c2oe7hsb77ltaro5qtihb5d4@group.calendar.google.com&pli=1 this link].).

==Moodle 4.0==
{| class="wikitable"
|-
!Moodle 4.0
|19 April 2022
|2022041900
|[[Moodle 4.0 release notes|Release Notes]]
|[https://docs.moodle.org/400/en/Upgrading Upgrading to 4.0]
|-
!Moodle 4.0.1
|9 May 2022
|2022041901
|[[Moodle 4.0.1 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 4.0.x will end 8 May 2023 (12 months).
Bug fixes for security issues in 4.0.x will end 13 November 2023 (18 months).

==Moodle 3.11==
{| class="wikitable"
|-
!Moodle 3.11
|17 May 2021
|2021051700
|[[Moodle 3.11 release notes|Release Notes]]
|[https://docs.moodle.org/311/en/Upgrading Upgrading to 3.11]
|-
!Moodle 3.11.1
|12 July 2021
|2021051701
|[[Moodle 3.11.1 release notes|Release Notes]]
|
|-
!Moodle 3.11.2
|29 July 2021
|2021051702
|[[Moodle 3.11.2 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.11.3
|13 September 2021
|2021051703
|[[Moodle 3.11.3 release notes|Release Notes]]
|
|-
! Moodle 3.11.4
|8 November 2021
|2021051704
|[[Moodle 3.11.4 release notes|Release Notes]]
|
|-
! Moodle 3.11.5
|17 January 2022
|2021051705
|[[Moodle 3.11.5 release notes|Release Notes]]
|-
! Moodle 3.11.6
|14 March 2022
|2021051706
|[[Moodle 3.11.6 release notes|Release Notes]]
|-
! Moodle 3.11.7
|9 May 2022
|2021051707
|[[Moodle 3.11.7 release notes|Release Notes]]
|}
Bug fixes for general core bugs in 3.11.x will end 14 Nov 2022 (12 months plus 6 months extension).
Bug fixes for security issues in 3.11.x will end 13 Nov 2023 (18 months plus 12 months extension).
==Moodle 3.10==
{| class="wikitable"
|-
! Moodle 3.10
|9 November 2020
|2020110900
|
[[Moodle 3.10 release notes|Release Notes]]
|[https://docs.moodle.org/310/en/Upgrading Upgrading to 3.10]
|-
!Moodle 3.10.1
|18 January 2021
|2020110901
| [[Moodle 3.10.1 release notes|Release Notes]]
|
|-
!Moodle 3.10.2
|8 March 2021
|2020110902
|[[Moodle 3.10.2 release notes|Release Notes]]
|
|-
! Moodle 3.10.3
|25 March 2021
|2020110903
|[[Moodle 3.10.3 release notes|Release Notes]]
|
|-
!Moodle 3.10.4
|10 May 2021
|2020110904
|[[Moodle 3.10.4 release notes|Release Notes]]
|
|-
!Moodle 3.10.5
|12 July 2021
|2020110905
|[[Moodle 3.10.5 release notes|Release Notes]]
|
|-
!Moodle 3.10.6
|29 July 2021
|2020110906
|[[Moodle 3.10.6 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.10.7
|13 September 2021
|2020110907
|[[Moodle 3.10.7 release notes|Release Notes]]
|
|-
!Moodle 3.10.8
|8 November 2021
|2020110908
|[[Moodle 3.10.8 release notes|Release Notes]]
|
|-
!Moodle 3.10.9
|17 January 2022
|2020110909
|[[Moodle 3.10.9 release notes|Release Notes]]
|-
!Moodle 3.10.10
|14 March 2022
|2020110910
|[[Moodle 3.10.10 release notes|Release Notes]]
|-
!Moodle 3.10.11
|9 May 2022
|2020110911
|[[Moodle 3.10.11 release notes|Release Notes]]
|}
Bug fixes for general core bugs in 3.10.x ended 8 November 2021 (12 months).
Bug fixes for security issues in 3.10.x will end 9 May 2022 (18 months).
==Moodle 3.9 (LTS)==
{| class="wikitable"
|-
! Moodle 3.9
|15 June 2020
|2020061500
|[[Moodle 3.9 release notes|Release Notes]]
|
[https://docs.moodle.org/39/en/Upgrading Upgrading to 3.9]
|-
!Moodle 3.9.1
|13 July 2020
|2020061501
|[[Moodle 3.9.1 release notes|Release Notes]]
|
|-
!Moodle 3.9.2
|14 September 2020
|2020061502
| [[Moodle 3.9.2 release notes|Release Notes]]
|
|-
!Moodle 3.9.3
|9 November 2020
|2020061503
| [[Moodle 3.9.3 release notes|Release Notes]]
|
|-
!Moodle 3.9.4
|18 January 2021
|2020061504
|[[Moodle 3.9.4 release notes|Release Notes]]
|
|-
!Moodle 3.9.5
|8 March 2021
|2020061505
|[[Moodle 3.9.5 release notes|Release Notes]]
|
|-
!Moodle 3.9.6
|25 March 2021
|2020061506
|[[Moodle 3.9.6 release notes|Release Notes]]
|
|-
!Moodle 3.9.7
|10 May 2021
|2020061507
|[[Moodle 3.9.7 release notes|Release Notes]]
|
|-
! Moodle 3.9.8
|12 July 2021
|2020061508
|[[Moodle 3.9.8 release notes|Release Notes]]
|
|-
!Moodle 3.9.9
|29 July 2021
|2020061509
|[[Moodle 3.9.9 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.9.10
|13 September 2021
|2020061510
|[[Moodle 3.9.10 release notes|Release Notes]]
|
|-
!Moodle 3.9.11
| 8 November 2021
|2020061511
|[[Moodle 3.9.11 release notes|Release Notes]]
|
|-
!Moodle 3.9.12
| 17 January 2022
|2020061512
|[[Moodle 3.9.12 release notes|Release Notes]]
|-
!Moodle 3.9.13
| 14 March 2022
|2020061513
|[[Moodle 3.9.13 release notes|Release Notes]]
|
|-
!Moodle 3.9.14
| 9 May 2022
|2020061514
|[[Moodle 3.9.14 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.9.x ended 10 May 2021 (12 months).
Bug fixes for security issues in 3.9.x will end 13 Nov 2023 (36 months plus 6 months extension).
==Moodle 3.8==
{| class="wikitable"
|-
!Moodle 3.8
|18 November 2019
|2019111800
|[[Moodle 3.8 release notes|Release Notes]]
|
[https://docs.moodle.org/38/en/Upgrading Upgrading to 3.8]
|-
!Moodle 3.8.1
|13 January 2020
|2019111801
|[[Moodle 3.8.1 release notes|Release Notes]]
|
|-
!Moodle 3.8.2
|9 March 2020
|2019111802
|[[Moodle 3.8.2 release notes|Release Notes]]
|
|-
!Moodle 3.8.3
|11 May 2020
|2019111803
|[[Moodle 3.8.3 release notes|Release Notes]]
|
|-
!Moodle 3.8.4
|13 July 2020
|2019111804
|[[Moodle 3.8.4 release notes|Release Notes]]
|
|-
!Moodle 3.8.5
|14 September 2020
|2019111805
| [[Moodle 3.8.5 release notes|Release Notes]]
|
|-
!Moodle 3.8.6
|9 November 2020
|2019111806
| [[Moodle 3.8.6 release notes|Release Notes]]
|
|-
!Moodle 3.8.7
|18 January 2021
|2019111807
|[[Moodle 3.8.7 release notes|Release Notes]]
|
|-
!Moodle 3.8.8
|8 March 2021
|2019111808
|[[Moodle 3.8.8 release notes|Release Notes]]
|
|-
!Moodle 3.8.9
|10 May 2021
|2019111809
|[[Moodle 3.8.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.8.x ended 9 November 2020 (12 months).
Bug fixes for security issues in 3.8.x ended 10 May 2021 (18 months).
==Moodle 3.7==
{| class="wikitable"
|-
!Moodle 3.7
|20 May 2019
|2019052000
|[[Moodle 3.7 release notes|Release Notes]]
|[https://docs.moodle.org/37/en/Upgrading Upgrading to 3.7]
|-
!Moodle 3.7.1
|8 July 2019
|2019052001
|[[Moodle 3.7.1 release notes|Release Notes]]
|
|-
!Moodle 3.7.2
|9 September 2019
|2019052002
|[[Moodle 3.7.2 release notes|Release Notes]]
|
|-
!Moodle 3.7.3
|11 November 2019
|2019052003
| [[Moodle 3.7.3 release notes|Release Notes]]
|
|-
!Moodle 3.7.4
|13 January 2020
|2019052004
|[[Moodle 3.7.4 release notes|Release Notes]]
|
|-
!Moodle 3.7.5
|9 March 2020
|2019052005
|[[Moodle 3.7.5 release notes|Release Notes]]
|
|-
!Moodle 3.7.6
|11 May 2020
|2019052006
|[[Moodle 3.7.6 release notes|Release Notes]]
|
|-
!Moodle 3.7.7
|13 July 2020
|2019052007
|[[Moodle 3.7.7 release notes|Release Notes]]
|
|-
!Moodle 3.7.8
|14 September 2020
|2019052008
| [[Moodle 3.7.8 release notes|Release Notes]]
|
|-
!Moodle 3.7.9
|9 November 2020
|2019052009
|[[Moodle 3.7.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.7.x ended 11 May 2020 (12 months).
Bug fixes for security issues in 3.7.x ended 9 November 2020 (18 months).
==Moodle 3.6==
{| class="wikitable"
|-
!Moodle 3.6
| 3 December 2018
|2018120300
|[[Moodle 3.6 release notes|Release Notes]]
|
[https://docs.moodle.org/36/en/Upgrading Upgrading to 3.6]
|-
!Moodle 3.6.1
|5 December 2018
|2018120301
| [[Moodle 3.6.1 release notes|Release Notes]]
|
|-
! Moodle 3.6.2
|14 January 2019
|2018120302
|[[Moodle 3.6.2 release notes|Release Notes]]
|
|-
!Moodle 3.6.3
|11 March 2019
|2018120303
|[[Moodle 3.6.3 release notes|Release Notes]]
|
|-
!Moodle 3.6.4
|13 May 2019
|2018120304
|[[Moodle 3.6.4 release notes|Release Notes]]
|
|-
!Moodle 3.6.5
|8th July 2019
|2018120305
|[[Moodle 3.6.5 release notes|Release Notes]]
|
|-
!Moodle 3.6.6
|9th September 2019
|2018120306
|[[Moodle 3.6.6 release notes|Release Notes]]
|
|-
!Moodle 3.6.7
| 11th November 2019
|2018120307
|[[Moodle 3.6.7 release notes|Release Notes]]
|
|-
!Moodle 3.6.8
|13th January 2020
|2018120308
|[[Moodle 3.6.8 release notes|Release Notes]]
|
|-
!Moodle 3.6.9
|9th March 2020
|2018120309
| [[Moodle 3.6.9 release notes|Release Notes]]
|
|-
!Moodle 3.6.10
|11th May 2020
|2018120310
|[[Moodle 3.6.10 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.6.x ended 11 November 2019 (12 months).
Bug fixes for security issues in 3.6.x ended 11 May 2020 (18 months).
==Moodle 3.5 (LTS)==
{| class="wikitable"
|-
!Moodle 3.5
|17 May 2018
|2018051700
|[[Moodle 3.5 release notes|Release Notes]]
|[https://docs.moodle.org/35/en/Upgrading Upgrading to 3.5]
|-
! Moodle 3.5.1
|9 July 2018
|2018051701
|[[Moodle 3.5.1 release notes|Release Notes]]
|
|-
!Moodle 3.5.2
|10 September 2018
|2018051702
|[[Moodle 3.5.2 release notes|Release Notes]]
|
|-
!Moodle 3.5.3
|12 November 2018
|2018051703
| [[Moodle 3.5.3 release notes|Release Notes]]
|
|-
! Moodle 3.5.4
|14 January 2019
|2018051704
|[[Moodle 3.5.4 release notes|Release Notes]]
|
|-
!Moodle 3.5.5
|11 March 2019
|2018051705
|[[Moodle 3.5.5 release notes|Release Notes]]
|
|-
!Moodle 3.5.6
|13 May 2019
|2018051706
|[[Moodle 3.5.6 release notes|Release Notes]]
|
|-
!Moodle 3.5.7
|8 July 2019
|2018051707
|[[Moodle 3.5.7 release notes|Release Notes]]
|
|-
!Moodle 3.5.8
|9 September 2019
|2018051708
|[[Moodle 3.5.8 release notes|Release Notes]]
|
|-
!Moodle 3.5.9
|11 November 2019
|2018051709
|[[Moodle 3.5.9 release notes|Release Notes]]
|
|-
!Moodle 3.5.10
|13 January 2020
|2018051710
| [[Moodle 3.5.10 release notes|Release Notes]]
|
|-
!Moodle 3.5.11
|9 March 2020
|2018051711
|[[Moodle 3.5.11 release notes|Release Notes]]
|
|-
!Moodle 3.5.12
|11 May 2020
|2018051712
| [[Moodle 3.5.12 release notes|Release Notes]]
|
|-
!Moodle 3.5.13
|13 July 2020
|2018051713
|[[Moodle 3.5.13 release notes|Release Notes]]
|
|-
!Moodle 3.5.14
| 14 September 2020
|2018051714
|[[Moodle 3.5.14 release notes|Release Notes]]
|
|-
!Moodle 3.5.15
|9 November 2020
|2018051715
|[[Moodle 3.5.15 release notes|Release Notes]]
|
|-
!Moodle 3.5.16
|18 January 2021
|2018051716
| [[Moodle 3.5.16 release notes|Release Notes]]
|
|-
!Moodle 3.5.17
|8 March 2021
| 2018051717
|[[Moodle 3.5.17 release notes|Release Notes]]
|
|-
!Moodle 3.5.18
| 10 May 2021
| 2018051718
|[[Moodle 3.5.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.5.x ended May 2019 (12 months).
Bug fixes for security issues in 3.5.x ended 10 May 2021 (36 months).
==Moodle 3.4==
{| class="wikitable"
|-
!Moodle 3.4
|13 November 2017
|2017111300
|[[Moodle 3.4 release notes|Release Notes]]
|
[https://docs.moodle.org/34/en/Upgrading Upgrading to 3.4]
|-
! Moodle 3.4.1
|15 January 2018
|2017111301
|[[Moodle 3.4.1 release notes|Release Notes]]
|
|-
!Moodle 3.4.2
|19 March 2018
|2017111302
|[[Moodle 3.4.2 release notes|Release Notes]]
|
|-
!Moodle 3.4.3
|17 May 2018
|2017111303
|[[Moodle 3.4.3 release notes|Release Notes]]
|
|-
! Moodle 3.4.4
|9 July 2018
|2017111304
|[[Moodle 3.4.4 release notes|Release Notes]]
|
|-
!Moodle 3.4.5
|10 September 2018
|2017111305
|[[Moodle 3.4.5 release notes|Release Notes]]
|
|-
!Moodle 3.4.6
|12 November 2018
|2017111306
| [[Moodle 3.4.6 release notes|Release Notes]]
|
|-
! Moodle 3.4.7
|14 January 2019
|2017111307
|[[Moodle 3.4.7 release notes|Release Notes]]
|
|-
!Moodle 3.4.8
|11 March 2019
|2017111308
|[[Moodle 3.4.8 release notes|Release Notes]]
|
|-
!Moodle 3.4.9
|13 May 2019
|2017111309
| [[Moodle 3.4.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.4.x ended 12 November 2018 (12 months).
Bug fixes for security issues in 3.4.x ended 13 May 2019 (18 months).
==Moodle 3.3==
{| class="wikitable"
|-
!Moodle 3.3
|15 May 2017
|2017051500
|[[Moodle 3.3 release notes|Release Notes]]
|
[https://docs.moodle.org/33/en/Upgrading Upgrading to 3.3]
|-
!Moodle 3.3.1
|10 July 2017
|2017051501
|[[Moodle 3.3.1 release notes|Release Notes]]
|
|-
!Moodle 3.3.2
|11 September 2017
|2017051502
|[[Moodle 3.3.2 release notes|Release Notes]]
|
|-
!Moodle 3.3.3
|13 November 2017
|2017051503
| [[Moodle 3.3.3 release notes|Release Notes]]
|
|-
! Moodle 3.3.4
|15 January 2018
|2017051504
|[[Moodle 3.3.4 release notes|Release Notes]]
|
|-
!Moodle 3.3.5
|19 March 2018
|2017051505
|[[Moodle 3.3.5 release notes|Release Notes]]
|
|-
!Moodle 3.3.6
|17 May 2018
|2017051506
|[[Moodle 3.3.6 release notes|Release Notes]]
|
|-
! Moodle 3.3.7
|9 July 2018
|2017051507
|[[Moodle 3.3.7 release notes|Release Notes]]
|
|-
!Moodle 3.3.8
|10 September 2018
|2017051508
|[[Moodle 3.3.8 release notes|Release Notes]]
|
|-
! Moodle 3.3.9
|12 November 2018
|2017051509
|[[Moodle 3.3.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.3.x ended 17 May 2018 (12 months).
Bug fixes for security issues in 3.3.x ended 12 November 2018 (18 months).
==Moodle 3.2==
{| class="wikitable"
|-
!Moodle 3.2
| 5 December 2016
|2016120500
|[[Moodle 3.2 release notes|Release Notes]]
|[https://docs.moodle.org/32/en/Upgrading Upgrading to 3.2]
|-
!Moodle 3.2.1
|9 January 2017
|2016120501
|[[Moodle 3.2.1 release notes|Release Notes]]
|
|-
!Moodle 3.2.2
|13 March 2017
|2016120502
|[[Moodle 3.2.2 release notes|Release Notes]]
|
|-
!Moodle 3.2.3
|8 May 2017
|2016120503
|[[Moodle 3.2.3 release notes|Release Notes]]
|
|-
!Moodle 3.2.4
|10 July 2017
|2016120504
|[[Moodle 3.2.4 release notes|Release Notes]]
|
|-
!Moodle 3.2.5
|11 September 2017
|2016120505
|[[Moodle 3.2.5 release notes|Release Notes]]
|
|-
!Moodle 3.2.6
|13 November 2017
|2016120506
| [[Moodle 3.2.6 release notes|Release Notes]]
|
|-
! Moodle 3.2.7
|15 January 2018
|2016120507
|[[Moodle 3.2.7 release notes|Release Notes]]
|
|-
!Moodle 3.2.8
|19 March 2018
|2016120508
|[[Moodle 3.2.8 release notes|Release Notes]]
|
|-
!Moodle 3.2.9
|17 May 2018
|2016120509
| [[Moodle 3.2.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.2.x ended 13 November 2017 (12 months).
Bug fixes for security issues in 3.2.x ended 17 May 2018 (18 months).
==Moodle 3.1 (LTS)==
{| class="wikitable"
|-
!Moodle 3.1
|23 May 2016
|2016052300
|[[Moodle 3.1 release notes|Release Notes]]
|
[https://docs.moodle.org/31/en/Upgrading Upgrading to 3.1]
|-
!Moodle 3.1.1
|11 July 2016
|2016052301
|[[Moodle 3.1.1 release notes|Release Notes]]
|
|-
!Moodle 3.1.2
|12 September 2016
|2016052302
|[[Moodle 3.1.2 release notes|Release Notes]]
|
|-
!Moodle 3.1.3
|14 November 2016
|2016052303
|[[Moodle 3.1.3 release notes|Release Notes]]
|
|-
!Moodle 3.1.4
|9 January 2017
|2016052304
|[[Moodle 3.1.4 release notes|Release Notes]]
|
|-
!Moodle 3.1.5
|13 March 2017
|2016052305
|[[Moodle 3.1.5 release notes|Release Notes]]
|
|-
!Moodle 3.1.6
|8 May 2017
|2016052306
|[[Moodle 3.1.6 release notes|Release Notes]]
|
|-
!Moodle 3.1.7
|10 July 2017
|2016052307
|[[Moodle 3.1.7 release notes|Release Notes]]
|
|-
!Moodle 3.1.8
|11 September 2017
|2016052308
|[[Moodle 3.1.8 release notes|Release Notes]]
|
|-
!Moodle 3.1.9
|13 November 2017
|2016052309
|[[Moodle 3.1.9 release notes|Release Notes]]
|
|-
!Moodle 3.1.10
|15 January 2018
|2016052310
|[[Moodle 3.1.10 release notes|Release Notes]]
|
|-
! Moodle 3.1.11
|19 March 2018
|2016052311
|[[Moodle 3.1.11 release notes|Release Notes]]
|
|-
!Moodle 3.1.12
|17 May 2018
|2016052312
|[[Moodle 3.1.12 release notes|Release Notes]]
|
|-
!Moodle 3.1.13
|9 July 2018
|2016052313
|[[Moodle 3.1.13 release notes|Release Notes]]
|
|-
!Moodle 3.1.14
|10 September 2018
|2016052314
|[[Moodle 3.1.14 release notes|Release Notes]]
|
|-
! Moodle 3.1.15
|12 November 2018
|2016052315
|[[Moodle 3.1.15 release notes|Release Notes]]
|
|-
!Moodle 3.1.16
|14 January 2019
|2016052316
|[[Moodle 3.1.16 release notes|Release Notes]]
|
|-
! Moodle 3.1.17
|11 March 2019
| 2016052317
|[[Moodle 3.1.17 release notes|Release Notes]]
|
|-
!Moodle 3.1.18
|13 May 2019
|2016052318
|[[Moodle 3.1.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.1.x ended 8 May 2017 (12 months).
Bug fixes for security issues in 3.1.x ended 13 May 2019 (36 months).
==Moodle 3.0==
{| class="wikitable"
|-
!Moodle 3.0
|16 November 2015
|2015111600
|[[Moodle 3.0 release notes|Release Notes]]
|[https://docs.moodle.org/30/en/Upgrading Upgrading to 3.0]
|-
!Moodle 3.0.1
|21 December 2015
|2015111601
| [[Moodle 3.0.1 release notes|Release Notes]]
|
|-
! Moodle 3.0.2
|11 January 2016
|2015111602
|[[Moodle 3.0.2 release notes|Release Notes]]
|
|-
!Moodle 3.0.3
|14 March 2016
|2015111603
|[[Moodle 3.0.3 release notes|Release Notes]]
|
|-
!Moodle 3.0.4
|9 May 2016
|2015111604
|[[Moodle 3.0.4 release notes|Release Notes]]
|
|-
!Moodle 3.0.5
|11 July 2016
|2015111605
|[[Moodle 3.0.5 release notes|Release Notes]]
|
|-
!Moodle 3.0.6
|12 September 2016
|2015111606
|[[Moodle 3.0.6 release notes|Release Notes]]
|
|-
!Moodle 3.0.7
|14 November 2016
|2015111607
|[[Moodle 3.0.7 release notes|Release Notes]]
|
|-
!Moodle 3.0.8
|9 January 2017
|2015111608
|[[Moodle 3.0.8 release notes|Release Notes]]
|
|-
!Moodle 3.0.9
|13 March 2017
|2015111609
|[[Moodle 3.0.9 release notes|Release Notes]]
|
|-
!Moodle 3.0.10
|8 May 2017
|2015111610
|[[Moodle 3.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.0.x ended 14 November 2016 (12 months).
Bug fixes for security issues in 3.0.x ended 8 May 2017 (18 months).
==Moodle 2.9==
{| class="wikitable"
|-
!Moodle 2.9
| 11 May 2015
|2015051100
|[[Moodle 2.9 release notes|Release Notes]]
| [https://docs.moodle.org/29/en/Upgrading_to_Moodle_2.9 Upgrading to 2.9]
|-
! Moodle 2.9.1
|6 July 2015
|2015051101
|[[Moodle 2.9.1 release notes|Release Notes]]
|
|-
!Moodle 2.9.2
|14 September 2015
|2015051102
| [[Moodle 2.9.2 release notes|Release Notes]]
|
|-
!Moodle 2.9.3
|9 November 2015
|2015051103
| [[Moodle 2.9.3 release notes|Release Notes]]
|
|-
! Moodle 2.9.4
|11 January 2016
|2015051104
|[[Moodle 2.9.4 release notes|Release Notes]]
|
|-
!Moodle 2.9.5
|14 March 2016
|2015051105
|[[Moodle 2.9.5 release notes|Release Notes]]
|
|-
!Moodle 2.9.6
|9 May 2016
|2015051106
|[[Moodle 2.9.6 release notes|Release Notes]]
|
|-
!Moodle 2.9.7
|11 July 2016
|2015051107
|[[Moodle 2.9.7 release notes|Release Notes]]
|
|-
!Moodle 2.9.8
|12 September 2016
|2015051108
|[[Moodle 2.9.8 release notes|Release Notes]]
|
|-
! Moodle 2.9.9
|14 November 2016
|2015051109
|[[Moodle 2.9.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.9.x ended 9 May 2016 (12 months).
Bug fixes for security issues in 2.9.x ended 14 November 2016 (18 months).
==Moodle 2.8==
{| class="wikitable"
|-
!Moodle 2.8
|10 November 2014
|2014111000
| [[Moodle 2.8 release notes|Release Notes]]
|[https://docs.moodle.org/28/en/Upgrading_to_Moodle_2.8 Upgrading to 2.8]
|-
!Moodle 2.8.1
|13 November 2014
|2014111001
| [[Moodle 2.8.1 release notes|Release Notes]]
|
|-
!Moodle 2.8.2
|12 January 2015
|2014111002
| [[Moodle 2.8.2 release notes|Release Notes]]
|
|-
!Moodle 2.8.3
|2 February 2015
|2014111003
|[[Moodle 2.8.3 release notes|Release Notes]]
|
|-
!Moodle 2.8.4
|9 March 2015
|2014111004
|[[Moodle 2.8.4 release notes|Release Notes]]
|
|-
!Moodle 2.8.5
|10 March 2015
|2014111005
|[[Moodle 2.8.5 release notes|Release Notes]]
|
|-
!Moodle 2.8.6
|11 May 2015
|2014111006
|[[Moodle 2.8.6 release notes|Release Notes]]
|
|-
! Moodle 2.8.7
|6 July 2015
|2014111007
|[[Moodle 2.8.7 release notes|Release Notes]]
|
|-
!Moodle 2.8.8
|14 September 2015
|2014111008
| [[Moodle 2.8.8 release notes|Release Notes]]
|
|-
!Moodle 2.8.9
|9 November 2015
|2014111009
|[[Moodle 2.8.9 release notes|Release Notes]]
|
|-
!Moodle 2.8.10
|11 January 2016
|2014111010
|[[Moodle 2.8.10 release notes|Release Notes]]
|
|-
!Moodle 2.8.11
|14 March 2016
|2014111011
|[[Moodle 2.8.11 release notes|Release Notes]]
|
|-
!Moodle 2.8.12
|9 May 2016
|2014111012
| [[Moodle 2.8.12 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.8.x ended 9 November 2015 (12 months).
Bug fixes for security issues in 2.8.x ended 9 May 2016 (18 months).
==Moodle 2.7 (LTS)==
{| class="wikitable"
|-
!Moodle 2.7
| 12 May 2014
|2014051200
|[[Moodle 2.7 release notes|Release Notes]]
|[https://docs.moodle.org/27/en/Upgrading_to_Moodle_2.7 Upgrading to 2.7]
|-
! Moodle 2.7.1
|14 July 2014
|2014051201
|[[Moodle 2.7.1 release notes|Release Notes]]
|
|-
!Moodle 2.7.2
|8 September 2014
|2014051202
|[[Moodle 2.7.2 release notes|Release Notes]]
|
|-
!Moodle 2.7.3
|10 November 2014
|2014051203
| [[Moodle 2.7.3 release notes|Release Notes]]
|
|-
!Moodle 2.7.4
|12 January 2015
|2014051204
| [[Moodle 2.7.4 release notes|Release Notes]]
|
|-
!Moodle 2.7.5
|2 February 2015
|2014051205
|[[Moodle 2.7.5 release notes|Release Notes]]
|
|-
!Moodle 2.7.6
|9 March 2015
|2014051206
|[[Moodle 2.7.6 release notes|Release Notes]]
|
|-
!Moodle 2.7.7
|10 March 2015
|2014051207
|[[Moodle 2.7.7 release notes|Release Notes]]
|
|-
!Moodle 2.7.8
|11 May 2015
|2014051208
|[[Moodle 2.7.8 release notes|Release Notes]]
|
|-
!Moodle 2.7.9
|6 July 2015
|2014051209
|[[Moodle 2.7.9 release notes|Release Notes]]
|
|-
!Moodle 2.7.10
| 14 September 2015
|2014051210
|[[Moodle 2.7.10 release notes|Release Notes]]
|
|-
!Moodle 2.7.11
|9 November 2015
|2014051211
|[[Moodle 2.7.11 release notes|Release Notes]]
|
|-
!Moodle 2.7.12
|11 January 2016
|2014051212
|[[Moodle 2.7.12 release notes|Release Notes]]
|
|-
!Moodle 2.7.13
|14 March 2016
|2014051213
|[[Moodle 2.7.13 release notes|Release Notes]]
|
|-
!Moodle 2.7.14
|9 May 2016
|2014051214
| [[Moodle 2.7.14 release notes|Release Notes]]
|
|-
!Moodle 2.7.15
|11 July 2016
|2014051215
|[[Moodle 2.7.15 release notes|Release Notes]]
|
|-
!Moodle 2.7.16
|12 September 2016
|2014051216
|[[Moodle 2.7.16 release notes|Release Notes]]
|
|-
!Moodle 2.7.17
|14 November 2016
|2014051217
|[[Moodle 2.7.17 release notes|Release Notes]]
|
|-
!Moodle 2.7.18
|9 January 2017
|2014051218
|[[Moodle 2.7.18 release notes|Release Notes]]
|
|-
!Moodle 2.7.19
|13 March 2017
|2014051219
|[[Moodle 2.7.19 release notes|Release Notes]]
|
|-
!Moodle 2.7.20
|8 May 2017
|2014051220
| [[Moodle 2.7.20 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.7.x ended 11 May 2015 (12 months).
Bug fixes for security issues in 2.7.x ended 8 May 2017 (36 months).
==Moodle 2.6==
{| class="wikitable"
|-
!Moodle 2.6
|18 November 2013
|2013111800
|[[Moodle 2.6 release notes|Release Notes]]
|[https://docs.moodle.org/26/en/Upgrading_to_Moodle_2.6 Upgrading to 2.6]
|-
!Moodle 2.6.1
|13 January 2014
| 2013111801
| [[Moodle 2.6.1 release notes|Release Notes]]
|
|-
!Moodle 2.6.2
|10 March 2014
|2013111802
|[[Moodle 2.6.2 release notes|Release Notes]]
|
|-
!Moodle 2.6.3
|12 May 2014
|2013111803
|[[Moodle 2.6.3 release notes|Release Notes]]
|
|-
!Moodle 2.6.4
|14 July 2014
|2013111804
|[[Moodle 2.6.4 release notes|Release Notes]]
|
|-
!Moodle 2.6.5
|8 September 2014
|2013111805
|[[Moodle 2.6.5 release notes|Release Notes]]
|
|-
!Moodle 2.6.6
|10 November 2014
|2013111806
|[[Moodle 2.6.6 release notes|Release Notes]]
|
|-
!Moodle 2.6.7
|12 January 2015
|2013111807
|[[Moodle 2.6.7 release notes|Release Notes]]
|
|-
! Moodle 2.6.8
|2 February 2015
|2013111808
|[[Moodle 2.6.8 release notes|Release Notes]]
|
|-
! Moodle 2.6.9
|9 March 2015
|2013111809
|[[Moodle 2.6.9 release notes|Release Notes]]
|
|-
!Moodle 2.6.10
|10 March 2015
|2013111810
| [[Moodle 2.6.10 release notes|Release Notes]]
|
|-
!Moodle 2.6.11
|11 May 2015
|2013111811
|[[Moodle 2.6.11 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 2.6.x ended 10 November 2014 (12 months).
Bug fixes for security issues in 2.6.x ended 11 May 2015 (18 months).
==Moodle 2.5==
{| class="wikitable"
|-
!Moodle 2.5
| 14 May 2013
|2013051400
|[[Moodle 2.5 release notes|Release Notes]]
| [https://docs.moodle.org/25/en/Upgrading_to_Moodle_2.5 Upgrading to 2.5]
|-
! Moodle 2.5.1
|8 July 2013
|2013051401
|[[Moodle 2.5.1 release notes|Release Notes]]
|
|-
!Moodle 2.5.2
|9 September 2013
|2013051402
|[[Moodle 2.5.2 release notes|Release Notes]]
|
|-
!Moodle 2.5.3
|11 November 2013
|2013051403
|[[Moodle 2.5.3 release notes|Release Notes]]
|
|-
!Moodle 2.5.4
|13 January 2014
| 2013051404
| [[Moodle 2.5.4 release notes|Release Notes]]
|
|-
!Moodle 2.5.5
|10 March 2014
|2013051405
|[[Moodle 2.5.5 release notes|Release Notes]]
|
|-
!Moodle 2.5.6
|12 May 2014
|2013051406
|[[Moodle 2.5.6 release notes|Release Notes]]
|
|-
!Moodle 2.5.7
|14 July 2014
|2013051407
|[[Moodle 2.5.7 release notes|Release Notes]]
|
|-
!Moodle 2.5.8
|8 September 2014
|2013051408
|[[Moodle 2.5.8 release notes|Release Notes]]
|
|-
! Moodle 2.5.9
| 10 November 2014
|2013051409
|[[Moodle 2.5.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.5.x ended May 2014 (12 months).
Bug fixes for security issues in 2.5.x ended 10 November 2014 (18 months).
==Moodle 2.4==
{| class="wikitable"
|-
! Moodle 2.4
|3 December 2012
|2012120300
|[[Moodle 2.4 release notes|Release Notes]]
|[https://docs.moodle.org/24/en/Upgrading_to_Moodle_2.4 Upgrading to 2.4]
|-
! Moodle 2.4.1
|14 January 2013
|2012120301
|[[Moodle 2.4.1 release notes|Release Notes]]
|
|-
!Moodle 2.4.2
|11 March 2013
|2012120302
|[[Moodle 2.4.2 release notes|Release Notes]]
|
|-
!Moodle 2.4.3
|18 March 2013
|2012120303
|[[Moodle 2.4.3 release notes|Release Notes]]
|
|-
!Moodle 2.4.4
|14 May 2013
|2012120304
|[[Moodle 2.4.4 release notes|Release Notes]]
|
|-
!Moodle 2.4.5
|8 July 2013
|2012120305
|[[Moodle 2.4.5 release notes|Release Notes]]
|
|-
!Moodle 2.4.6
|9 September 2013
|2012120306
|[[Moodle 2.4.6 release notes|Release Notes]]
|
|-
!Moodle 2.4.7
|11 November 2013
|2012120307
| [[Moodle 2.4.7 release notes|Release Notes]]
|
|-
! Moodle 2.4.8
|13 January 2014
|2012120308
|[[Moodle 2.4.8 release notes|Release Notes]]
|
|-
!Moodle 2.4.9
|10 March 2014
|2012120309
|[[Moodle 2.4.9 release notes|Release Notes]]
|
|-
!Moodle 2.4.10
|12 May 2014
|2012120310
| [[Moodle 2.4.10 release notes|Release Notes]]
|
|-
!Moodle 2.4.11
|14 July 2014
|2012120311
|[[Moodle 2.4.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.4.x ended December 2013 (12 months).
Bug fixes for security issues in 2.4.x ended June 2014 (18 months).
==Moodle 2.3==
{| class="wikitable"
|-
!Moodle 2.3
|25 June 2012
|2012062500
|[[Moodle 2.3 release notes|Release Notes]]
| [https://docs.moodle.org/23/en/Upgrading_to_Moodle_2.3 Upgrading to 2.3]
|-
!Moodle 2.3.1
|9 July 2012
|2012062501
|[[Moodle 2.3.1 release notes|Release Notes]]
|
|-
! Moodle 2.3.2
|10 September 2012
|2012062502
|[[Moodle 2.3.2 release notes|Release Notes]]
|
|-
!Moodle 2.3.3
|12 November 2012
|2012062503
|[[Moodle 2.3.3 release notes|Release Notes]]
|
|-
! Moodle 2.3.4
|14 January 2013
|2012062504
|[[Moodle 2.3.4 release notes|Release Notes]]
|
|-
!Moodle 2.3.5
|11 March 2013
|2012062505
|[[Moodle 2.3.5 release notes|Release Notes]]
|
|-
!Moodle 2.3.6
|18 March 2013
|2012062506
|[[Moodle 2.3.6 release notes|Release Notes]]
|
|-
!Moodle 2.3.7
|14 May 2013
|2012062507
|[[Moodle 2.3.7 release notes|Release Notes]]
|
|-
!Moodle 2.3.8
|8 July 2013
|2012062508
|[[Moodle 2.3.8 release notes|Release Notes]]
|
|-
!Moodle 2.3.9
|9 September 2013
|2012062509
|[[Moodle 2.3.9 release notes|Release Notes]]
|
|-
! Moodle 2.3.10
|11 November 2013
|2012062510
|[[Moodle 2.3.10 release notes|Release Notes]]
|
|-
!Moodle 2.3.11
|13 January 2014
|2012062511
|[[Moodle 2.3.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.3.x ended June 2013 (12 months).
Bug fixes for security issues in 2.3.x ended December 2013 (18 months).
==Moodle 2.2==
{| class="wikitable"
|-
! Moodle 2.2
|5 December 2011
|2011120500
|[[Moodle 2.2 release notes|Release Notes]]
|[https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 Upgrading to 2.2]
|-
!Moodle 2.2.1
|9 January 2012
|2011120501
|[[Moodle 2.2.1 release notes|Release Notes]]
|
|-
!Moodle 2.2.2
|12 March 2012
|2011120502
|[[Moodle 2.2.2 release notes|Release Notes]]
|
|-
!Moodle 2.2.3
|14 May 2012
|2011120503
|[[Moodle 2.2.3 release notes|Release Notes]]
|
|-
! Moodle 2.2.4
|9 July 2012
|2011120504
|[[Moodle 2.2.4 release notes|Release Notes]]
|
|-
!Moodle 2.2.5
|10 September 2012
|2011120505
|[[Moodle 2.2.5 release notes|Release Notes]]
|
|-
!Moodle 2.2.6
|12 November 2012
|2011120506
| [[Moodle 2.2.6 release notes|Release Notes]]
|
|-
! Moodle 2.2.7
|14 January 2013
|2011120507
|[[Moodle 2.2.7 release notes|Release Notes]]
|
|-
!Moodle 2.2.8
|11 March 2013
|2011120508
|[[Moodle 2.2.8 release notes|Release Notes]]
|
|-
!Moodle 2.2.9
|18 March 2013
|2011120509
|[[Moodle 2.2.9 release notes|Release Notes]]
|
|-
!Moodle 2.2.10
|14 May 2013
| 2011120510
|[[Moodle 2.2.10 release notes|Release Notes]]
|
|-
!Moodle 2.2.11
|8 July 2013
|2011120511
|[[Moodle 2.2.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.2.x ended December 2012 (12 months).
Bug fixes for security issues in 2.2.x ended June 2013 (18 months).
==Moodle 2.1==
{| class="wikitable"
|-
!Moodle 2.1
| 1 July 2011
|2011070100
|[[Moodle 2.1 release notes|Release Notes]]
|[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to 2.1]
|-
! Moodle 2.1.1
|1 August 2011
|2011070101
| [[Moodle 2.1.1 release notes|Release Notes]]
|
|-
!Moodle 2.1.2
|10 October 2011
|2011070102
|[[Moodle 2.1.2 release notes|Release Notes]]
|
|-
!Moodle 2.1.3
|28 November 2011
|2011070103
|[[Moodle 2.1.3 release notes|Release Notes]]
|
|-
!Moodle 2.1.4
|9 January 2012
|2011070104
|[[Moodle 2.1.4 release notes|Release Notes]]
|
|-
!Moodle 2.1.5
|12 March 2012
|2011070105
|[[Moodle 2.1.5 release notes|Release Notes]]
|
|-
!Moodle 2.1.6
|14 May 2012
|2011070106
|[[Moodle 2.1.6 release notes|Release Notes]]
|
|-
! Moodle 2.1.7
|9 July 2012
|2011070107
|[[Moodle 2.1.7 release notes|Release Notes]]
|
|-
!Moodle 2.1.8
|10 September 2012
|2011070108
|[[Moodle 2.1.8 release notes|Release Notes]]
|
|-
!Moodle 2.1.9
|12 November 2012
|2011070109
|[[Moodle 2.1.9 release notes|Release Notes]]
|
|-
!Moodle 2.1.10
|14 January 2013
|2011070110
|[[Moodle 2.1.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.1.x ended June 2012 (12 months).
Bug fixes for security issues in 2.1.x ended December 2012 (18 months).
==Moodle 2.0==
{| class="wikitable"
|-
!Moodle 2.0
|24 November 2010
|2010112400
| [[Moodle 2.0 release notes|Release Notes]]
|[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to 2.0]
|-
!Moodle 2.0.1
|25 December 2010
|2010122500
|[[Moodle 2.0.1 release notes|Release Notes]]
|
|-
!Moodle 2.0.2
|21 February 2011
|2011022100
|[[Moodle 2.0.2 release notes|Release Notes]]
|
|-
!Moodle 2.0.3
|5 May 2011
|2011033003
|[[Moodle 2.0.3 release notes|Release Notes]]
|
|-
! Moodle 2.0.4
|1 August 2011
|2011033004
| [[Moodle 2.0.4 release notes|Release Notes]]
|
|-
!Moodle 2.0.5
|10 October 2011
|2011033005
|[[Moodle 2.0.5 release notes|Release Notes]]
|
|-
!Moodle 2.0.6
|28 November 2011
|2011033006
|[[Moodle 2.0.6 release notes|Release Notes]]
|
|-
!Moodle 2.0.7
|9 January 2012
|2011033007
|[[Moodle 2.0.7 release notes|Release Notes]]
|
|-
!Moodle 2.0.8
|12 March 2012
|2011033008
|[[Moodle 2.0.8 release notes|Release Notes]]
|
|-
!Moodle 2.0.9
|14 May 2012
|2011033009
|[[Moodle 2.0.9 release notes|Release Notes]]
|
|-
!Moodle 2.0.10
|9 July 2012
|2011033010
|[[Moodle 2.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.0.x ended December 2011 (12 months).
Bug fixes for security issues in 2.0.x ended June 2012 (18 months).
==Moodle 1.9==
{| class="wikitable"
|-
!Moodle 1.9
|3 March 2008
|2007101509
|[[Moodle 1.9 release notes|Release Notes]]
|[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to 1.9]
|-
!Moodle 1.9.1
|15 May 2008
| 2007101512
|[[Moodle 1.9.1 release notes|Release Notes]]
|
|-
! Moodle 1.9.2
|11 July 2008
|2007101520
|[[Moodle 1.9.2 release notes|Release Notes]]
|
|-
!Moodle 1.9.3
|15 October 2008
|2007101530
|[[Moodle 1.9.3 release notes|Release Notes]]
|
|-
!Moodle 1.9.4
|28 January 2009
|2007101540
|[[Moodle 1.9.4 release notes|Release Notes]]
|
|-
!Moodle 1.9.5
|13 May 2009
|2007101550
|[[Moodle 1.9.5 release notes|Release Notes]]
|
|-
!Moodle 1.9.6
|21 October 2009
|2007101560
|[[Moodle 1.9.6 release notes|Release Notes]]
|
|-
!Moodle 1.9.7
|25 November 2009
|2007101570
|[[Moodle 1.9.7 release notes|Release Notes]]
|
|-
!Moodle 1.9.8
|25 March 2010
|2007101580.00
|[[Moodle 1.9.8 release notes|Release Notes]]
|
|-
! Moodle 1.9.9
| 8 June 2010
| 2007101590.00
| [[Moodle 1.9.9 release notes|Release Notes]]
|
|-
!Moodle 1.9.10
|25 October 2010
|2007101591.00
|
[[Moodle 1.9.10 release notes|Release Notes]]
|
|-
!Moodle 1.9.11
|21 February 2011
|2007101591.02
|[[Moodle 1.9.11 release notes|Release Notes]]
|
|-
! Moodle 1.9.12
|10 May 2011
|2007101591.03
|[[Moodle 1.9.12 release notes|Release Notes]]
|
|-
!Moodle 1.9.13
|1 August 2011
|2007101591.04
|[[Moodle 1.9.13 release notes|Release Notes]]
|
|-
!Moodle 1.9.14
|10 October 2011
|2007101591.06
|
[[Moodle 1.9.14 release notes|Release Notes]]
|
|-
!Moodle 1.9.15
|28 November 2011
| 2007101591.07
| [[Moodle 1.9.15 release notes|Release Notes]]
|
|-
!Moodle 1.9.16
|9 January 2012
|2007101591.10
|[[Moodle 1.9.16 release notes|Release Notes]]
|
|-
! Moodle 1.9.17
|12 March 2012
|2007101591.12
|[[Moodle 1.9.17 release notes|Release Notes]]
|
|-
!Moodle 1.9.18
|14 May 2012
|2007101591.16
|[[Moodle 1.9.18 release notes|Release Notes]]
|
|-
! Moodle 1.9.19
|9 July 2012
|2007101592.00
|[[Moodle 1.9.19 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 1.9.x has ended June 2011 (3.5 years).
Bug fixes for security issues in 1.9.x by Moodle HQ ended June 2012 (4.5 years).
Bug fixes for security issues in 1.9.19+ branch by [http://catalyst.net.nz Catalyst IT] ended [http://moodle.org/mod/forum/discuss.php?d=199706 Dec 2013] (6 years).
==Moodle 1.8 ==
*[[Moodle 1.8 release notes|Moodle 1.8]] - 30 March 2007
*[[Moodle 1.8.1 release notes|Moodle 1.8.1]] - 14 June 2007
*[[Moodle 1.8.2 release notes|Moodle 1.8.2]] - 8 July 2007
*[[Moodle 1.8.3 release notes|Moodle 1.8.3]] - 11 October 2007
*[[Moodle 1.8.4 release notes|Moodle 1.8.4]] - 11 January 2008
*[[Moodle 1.8.5 release notes|Moodle 1.8.5]] - 8 April 2008
*[[Moodle 1.8.6 release notes|Moodle 1.8.6]] - 11 July 2008
*[[Moodle 1.8.7 release notes|Moodle 1.8.7]] - 15 October 2008
*[[Moodle 1.8.8 release notes|Moodle 1.8.8]] - 28 January 2009
*[[Moodle 1.8.9 release notes|Moodle 1.8.9]] - 15 May 2009
*[[Moodle 1.8.10 release notes|Moodle 1.8.10]] - 26 October 2009
*[[Moodle 1.8.11 release notes|Moodle 1.8.11]] - 25 November 2009
*[[Moodle 1.8.12 release notes|Moodle 1.8.12]] - 27 March 2010
*[[Moodle 1.8.13 release notes|Moodle 1.8.13]] - 8 June 2010
*[[Moodle 1.8.14 release notes|Moodle 1.8.14]] - 3 December 2010
*Support has ended

==Moodle 1.7==
*[[Moodle 1.7 release notes|Moodle 1.7]] - 7 November 2006
*[[Moodle 1.7.1 release notes|Moodle 1.7.1]] - 17 January 2007
*[[Moodle 1.7.2 release notes|Moodle 1.7.2]] - 30 March 2007
*[[Moodle 1.7.3 release notes|Moodle 1.7.3]] - 11 October 2007
*[[Moodle 1.7.4 release notes|Moodle 1.7.4]] - 11 January 2008
*[[Moodle 1.7.5 release notes|Moodle 1.7.5]] - 11 July 2008
*[[Moodle 1.7.6 release notes|Moodle 1.7.6]] - 15 October 2008
*[[Moodle 1.7.7 release notes|Moodle 1.7.7]] - 28 January 2009
*Support has ended
==Moodle 1.6==
*[[Moodle 1.6 release notes|Moodle 1.6]] - 20 June 2006
*[[Moodle 1.6.1 release notes|Moodle 1.6.1]] - 20 July 2006
*[[Moodle 1.6.2 release notes|Moodle 1.6.2]] - 12 September 2006
*[[Moodle 1.6.3 release notes|Moodle 1.6.3]] - 10 October 2006
*[[Moodle 1.6.4 release notes|Moodle 1.6.4]] - 17 January 2007
*[[Moodle 1.6.5 release notes|Moodle 1.6.5]] - 30 March 2007
*Moodle 1.6.6 - 11 January 2008
*Moodle 1.6.7 - 11 July 2008
*[[Moodle 1.6.8 release notes|Moodle 1.6.8]] - 15 October 2008
*[[Moodle 1.6.9 release notes|Moodle 1.6.9]] - 28 January 2009
* Support has ended
==Moodle 1.5==
*[[Moodle 1.5 release notes|Moodle 1.5]] - 5 June 2005
*[[Moodle 1.5.1 release notes|Moodle 1.5.1]] - 8 July 2005
*[[Moodle 1.5.2 release notes|Moodle 1.5.2]] - 16 July 2005
*[[Moodle 1.5.3 release notes|Moodle 1.5.3]] - 11 November 2005
*[[Moodle 1.5.4 release notes|Moodle 1.5.4]] - 21 May 2006
*Support has ended
==Moodle 1.4==
*Moodle 1.4 - 31 August 2004
*Moodle 1.4.1 - 12 September 2004
*Moodle 1.4.2 - 5 November 2004
*Moodle 1.4.3 - 21 December 2004
*Moodle 1.4.4 - 7 March 2005
*[[Moodle 1.4.5 release notes|Moodle 1.4.5]] - 7 May 2005
*Support has ended
==Moodle 1.3==
*Moodle 1.3 - 25 May 2004
* Moodle 1.3.1 - 4 June 2004
*Moodle 1.3.2 - 9 July 2004
*Moodle 1.3.3 - 16 July 2004
* Moodle 1.3.4 - 11 August 2004
*Moodle 1.3.5 - 9 September 2004
*Support has ended
==Moodle 1.2==
*Moodle 1.2 - 20 March 2004
*Moodle 1.2.1 - 25 March 2004
*Support has ended
==Moodle 1.1==
*Moodle 1.1 - 29 August 2003
*Moodle 1.1.1 - 11 September 2003
*Support has ended
== Moodle 1.0==
*Moodle 1.0 - 20 August 2002
*Moodle 1.0.1 - 26 August 2002
*Moodle 1.0.2 - 2 September 2002
*Moodle 1.0.3 - 5 September 2002
*Moodle 1.0.4 - 10 September 2002
*Moodle 1.0.5 - 27 September 2002
* Moodle 1.0.6 - 26 October 2002
::1.0.6.1 - 6 November 2002
::1.0.6.2 - 11 November 2002
::1.0.6.3 - 14 November 2002
::1.0.6.4 - 25 November 2002
*Moodle 1.0.7 - 9 December 2002
*Moodle 1.0.8 - 7 January 2003
*Moodle 1.0.9 - 30 May 2003
*Support has ended
==See also==
*[[Roadmap]] - future versions
*[[Moodle versions]] - an explanation of how our versions work plus version numbers for each release (for $plugin->requires)
[[Category:Release notes]]
[[Category:Core development]]
[[fr:Historique des versions]]
[[es:dev/Historia de las versiones]]
[[de:Versionshistorie]]

Releases

2022-05-09T01:31:21Z

Abgreeve: /* Version support - release of 4.0.1 and other minors */

This page lists all official releases of Moodle, grouped by branch in reverse chronological order.
==Version support==
From Moodle 2.6 onwards, the end of support, both general and security, happens the second Monday of May and November, observing the 12, 18... month periods, no matter if the major release date was moved or not.

The most recent [https://en.wikipedia.org/wiki/Long-term_support long-term support release (LTS)] version is Moodle 3.9.
{| class="wikitable" border="1px solid #dee2e6;"
|-
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Version
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Release status
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Initial release
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:rgba(0, 0, 0, 0.05);" | General support ends
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Security support ends
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.9 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 15 June 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 10 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 November 2023 (ext 6M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.11
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 17 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 14 Nov 2022 (ext 6M)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 Nov 2023 (ext 12M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |4.0
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |19 April 2022
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |8 May 2023
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |13 November 2023
|-
|4.1 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
|November 2022
|November 2023
|November 2025
|}
[[Image:401_release_graph.png|alt=Release graph]]

Release graph key:
{| class="wikitable" border="1px solid #dee2e6;"
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Currently supported stable releases.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | Current release of versions still receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Future point releases receiving bug fixes, as well as security updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#316d5e; color:white; adding: .3rem 0.5rem 0.3rem 0.5rem;" |Future security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Future point releases receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#686566; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Previously released versions containing bug fixes, as well as security updates. Updating to a currently supported version is recommended.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#282828; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Previously released versions containing security updates only. Updating to a currently supported version is recommended.
|}

==General release calendar==
These are the target dates for releases. These dates may vary slightly due to unforeseen circumstances.
{| class="wikitable"
|-
!Release type
!Frequency
!Months
|-
|[[Process#Major_release_cycles|Major]] (eg. 3.x)
|6 monthly
|Second Monday of May and November
|-
|[[Process#Stable_maintenance_cycles|Minor]] (Point) (eg. 3.x.y)
| 2 monthly
|Second Monday of July, September, November, March and May.
Third Monday of January.
|}
All releases are preceded by a one week warning. Upcoming release dates can be found in the [https://www.google.com/calendar/ical/moodle.com_p4c2oe7hsb77ltaro5qtihb5d4%40group.calendar.google.com/public/basic.ics Moodle development calendar] (Note, this is an iCAL link that will try to add the dates to your personal calendar. If you just want to browse the dates online, use [https://calendar.google.com/calendar/embed?src=moodle.com_p4c2oe7hsb77ltaro5qtihb5d4@group.calendar.google.com&pli=1 this link].).

==Moodle 4.0==
{| class="wikitable"
|-
!Moodle 4.0
|19 April 2022
|2022041900
|[[Moodle 4.0 release notes|Release Notes]]
|[https://docs.moodle.org/400/en/Upgrading Upgrading to 4.0]
|}
Bug fixes for general core bugs in 4.0.x will end 8 May 2023 (12 months).
Bug fixes for security issues in 4.0.x will end 13 November 2023 (18 months).

==Moodle 3.11==
{| class="wikitable"
|-
!Moodle 3.11
|17 May 2021
|2021051700
|[[Moodle 3.11 release notes|Release Notes]]
|[https://docs.moodle.org/311/en/Upgrading Upgrading to 3.11]
|-
!Moodle 3.11.1
|12 July 2021
|2021051701
|[[Moodle 3.11.1 release notes|Release Notes]]
|
|-
!Moodle 3.11.2
|29 July 2021
|2021051702
|[[Moodle 3.11.2 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.11.3
|13 September 2021
|2021051703
|[[Moodle 3.11.3 release notes|Release Notes]]
|
|-
! Moodle 3.11.4
|8 November 2021
|2021051704
|[[Moodle 3.11.4 release notes|Release Notes]]
|
|-
! Moodle 3.11.5
|17 January 2022
|2021051705
|[[Moodle 3.11.5 release notes|Release Notes]]
|-
! Moodle 3.11.6
|14 March 2022
|2021051706
|[[Moodle 3.11.6 release notes|Release Notes]]
|}
Bug fixes for general core bugs in 3.11.x will end 14 Nov 2022 (12 months plus 6 months extension).
Bug fixes for security issues in 3.11.x will end 13 Nov 2023 (18 months plus 12 months extension).
==Moodle 3.10==
{| class="wikitable"
|-
! Moodle 3.10
|9 November 2020
|2020110900
|
[[Moodle 3.10 release notes|Release Notes]]
|[https://docs.moodle.org/310/en/Upgrading Upgrading to 3.10]
|-
!Moodle 3.10.1
|18 January 2021
|2020110901
| [[Moodle 3.10.1 release notes|Release Notes]]
|
|-
!Moodle 3.10.2
|8 March 2021
|2020110902
|[[Moodle 3.10.2 release notes|Release Notes]]
|
|-
! Moodle 3.10.3
|25 March 2021
|2020110903
|[[Moodle 3.10.3 release notes|Release Notes]]
|
|-
!Moodle 3.10.4
|10 May 2021
|2020110904
|[[Moodle 3.10.4 release notes|Release Notes]]
|
|-
!Moodle 3.10.5
|12 July 2021
|2020110905
|[[Moodle 3.10.5 release notes|Release Notes]]
|
|-
!Moodle 3.10.6
|29 July 2021
|2020110906
|[[Moodle 3.10.6 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.10.7
|13 September 2021
|2020110907
|[[Moodle 3.10.7 release notes|Release Notes]]
|
|-
!Moodle 3.10.8
|8 November 2021
|2020110908
|[[Moodle 3.10.8 release notes|Release Notes]]
|
|-
!Moodle 3.10.9
|17 January 2022
|2020110909
|[[Moodle 3.10.9 release notes|Release Notes]]
|-
!Moodle 3.10.10
|14 March 2022
|2020110910
|[[Moodle 3.10.10 release notes|Release Notes]]
|}
Bug fixes for general core bugs in 3.10.x ended 8 November 2021 (12 months).
Bug fixes for security issues in 3.10.x will end 9 May 2022 (18 months).
==Moodle 3.9 (LTS)==
{| class="wikitable"
|-
! Moodle 3.9
|15 June 2020
|2020061500
|[[Moodle 3.9 release notes|Release Notes]]
|
[https://docs.moodle.org/39/en/Upgrading Upgrading to 3.9]
|-
!Moodle 3.9.1
|13 July 2020
|2020061501
|[[Moodle 3.9.1 release notes|Release Notes]]
|
|-
!Moodle 3.9.2
|14 September 2020
|2020061502
| [[Moodle 3.9.2 release notes|Release Notes]]
|
|-
!Moodle 3.9.3
|9 November 2020
|2020061503
| [[Moodle 3.9.3 release notes|Release Notes]]
|
|-
!Moodle 3.9.4
|18 January 2021
|2020061504
|[[Moodle 3.9.4 release notes|Release Notes]]
|
|-
!Moodle 3.9.5
|8 March 2021
|2020061505
|[[Moodle 3.9.5 release notes|Release Notes]]
|
|-
!Moodle 3.9.6
|25 March 2021
|2020061506
|[[Moodle 3.9.6 release notes|Release Notes]]
|
|-
!Moodle 3.9.7
|10 May 2021
|2020061507
|[[Moodle 3.9.7 release notes|Release Notes]]
|
|-
! Moodle 3.9.8
|12 July 2021
|2020061508
|[[Moodle 3.9.8 release notes|Release Notes]]
|
|-
!Moodle 3.9.9
|29 July 2021
|2020061509
|[[Moodle 3.9.9 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.9.10
|13 September 2021
|2020061510
|[[Moodle 3.9.10 release notes|Release Notes]]
|
|-
!Moodle 3.9.11
| 8 November 2021
|2020061511
|[[Moodle 3.9.11 release notes|Release Notes]]
|
|-
!Moodle 3.9.12
| 17 January 2022
|2020061512
|[[Moodle 3.9.12 release notes|Release Notes]]
|-
!Moodle 3.9.13
| 14 March 2022
|2020061513
|[[Moodle 3.9.13 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.9.x ended 10 May 2021 (12 months).
Bug fixes for security issues in 3.9.x will end 13 Nov 2023 (36 months plus 6 months extension).
==Moodle 3.8==
{| class="wikitable"
|-
!Moodle 3.8
|18 November 2019
|2019111800
|[[Moodle 3.8 release notes|Release Notes]]
|
[https://docs.moodle.org/38/en/Upgrading Upgrading to 3.8]
|-
!Moodle 3.8.1
|13 January 2020
|2019111801
|[[Moodle 3.8.1 release notes|Release Notes]]
|
|-
!Moodle 3.8.2
|9 March 2020
|2019111802
|[[Moodle 3.8.2 release notes|Release Notes]]
|
|-
!Moodle 3.8.3
|11 May 2020
|2019111803
|[[Moodle 3.8.3 release notes|Release Notes]]
|
|-
!Moodle 3.8.4
|13 July 2020
|2019111804
|[[Moodle 3.8.4 release notes|Release Notes]]
|
|-
!Moodle 3.8.5
|14 September 2020
|2019111805
| [[Moodle 3.8.5 release notes|Release Notes]]
|
|-
!Moodle 3.8.6
|9 November 2020
|2019111806
| [[Moodle 3.8.6 release notes|Release Notes]]
|
|-
!Moodle 3.8.7
|18 January 2021
|2019111807
|[[Moodle 3.8.7 release notes|Release Notes]]
|
|-
!Moodle 3.8.8
|8 March 2021
|2019111808
|[[Moodle 3.8.8 release notes|Release Notes]]
|
|-
!Moodle 3.8.9
|10 May 2021
|2019111809
|[[Moodle 3.8.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.8.x ended 9 November 2020 (12 months).
Bug fixes for security issues in 3.8.x ended 10 May 2021 (18 months).
==Moodle 3.7==
{| class="wikitable"
|-
!Moodle 3.7
|20 May 2019
|2019052000
|[[Moodle 3.7 release notes|Release Notes]]
|[https://docs.moodle.org/37/en/Upgrading Upgrading to 3.7]
|-
!Moodle 3.7.1
|8 July 2019
|2019052001
|[[Moodle 3.7.1 release notes|Release Notes]]
|
|-
!Moodle 3.7.2
|9 September 2019
|2019052002
|[[Moodle 3.7.2 release notes|Release Notes]]
|
|-
!Moodle 3.7.3
|11 November 2019
|2019052003
| [[Moodle 3.7.3 release notes|Release Notes]]
|
|-
!Moodle 3.7.4
|13 January 2020
|2019052004
|[[Moodle 3.7.4 release notes|Release Notes]]
|
|-
!Moodle 3.7.5
|9 March 2020
|2019052005
|[[Moodle 3.7.5 release notes|Release Notes]]
|
|-
!Moodle 3.7.6
|11 May 2020
|2019052006
|[[Moodle 3.7.6 release notes|Release Notes]]
|
|-
!Moodle 3.7.7
|13 July 2020
|2019052007
|[[Moodle 3.7.7 release notes|Release Notes]]
|
|-
!Moodle 3.7.8
|14 September 2020
|2019052008
| [[Moodle 3.7.8 release notes|Release Notes]]
|
|-
!Moodle 3.7.9
|9 November 2020
|2019052009
|[[Moodle 3.7.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.7.x ended 11 May 2020 (12 months).
Bug fixes for security issues in 3.7.x ended 9 November 2020 (18 months).
==Moodle 3.6==
{| class="wikitable"
|-
!Moodle 3.6
| 3 December 2018
|2018120300
|[[Moodle 3.6 release notes|Release Notes]]
|
[https://docs.moodle.org/36/en/Upgrading Upgrading to 3.6]
|-
!Moodle 3.6.1
|5 December 2018
|2018120301
| [[Moodle 3.6.1 release notes|Release Notes]]
|
|-
! Moodle 3.6.2
|14 January 2019
|2018120302
|[[Moodle 3.6.2 release notes|Release Notes]]
|
|-
!Moodle 3.6.3
|11 March 2019
|2018120303
|[[Moodle 3.6.3 release notes|Release Notes]]
|
|-
!Moodle 3.6.4
|13 May 2019
|2018120304
|[[Moodle 3.6.4 release notes|Release Notes]]
|
|-
!Moodle 3.6.5
|8th July 2019
|2018120305
|[[Moodle 3.6.5 release notes|Release Notes]]
|
|-
!Moodle 3.6.6
|9th September 2019
|2018120306
|[[Moodle 3.6.6 release notes|Release Notes]]
|
|-
!Moodle 3.6.7
| 11th November 2019
|2018120307
|[[Moodle 3.6.7 release notes|Release Notes]]
|
|-
!Moodle 3.6.8
|13th January 2020
|2018120308
|[[Moodle 3.6.8 release notes|Release Notes]]
|
|-
!Moodle 3.6.9
|9th March 2020
|2018120309
| [[Moodle 3.6.9 release notes|Release Notes]]
|
|-
!Moodle 3.6.10
|11th May 2020
|2018120310
|[[Moodle 3.6.10 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.6.x ended 11 November 2019 (12 months).
Bug fixes for security issues in 3.6.x ended 11 May 2020 (18 months).
==Moodle 3.5 (LTS)==
{| class="wikitable"
|-
!Moodle 3.5
|17 May 2018
|2018051700
|[[Moodle 3.5 release notes|Release Notes]]
|[https://docs.moodle.org/35/en/Upgrading Upgrading to 3.5]
|-
! Moodle 3.5.1
|9 July 2018
|2018051701
|[[Moodle 3.5.1 release notes|Release Notes]]
|
|-
!Moodle 3.5.2
|10 September 2018
|2018051702
|[[Moodle 3.5.2 release notes|Release Notes]]
|
|-
!Moodle 3.5.3
|12 November 2018
|2018051703
| [[Moodle 3.5.3 release notes|Release Notes]]
|
|-
! Moodle 3.5.4
|14 January 2019
|2018051704
|[[Moodle 3.5.4 release notes|Release Notes]]
|
|-
!Moodle 3.5.5
|11 March 2019
|2018051705
|[[Moodle 3.5.5 release notes|Release Notes]]
|
|-
!Moodle 3.5.6
|13 May 2019
|2018051706
|[[Moodle 3.5.6 release notes|Release Notes]]
|
|-
!Moodle 3.5.7
|8 July 2019
|2018051707
|[[Moodle 3.5.7 release notes|Release Notes]]
|
|-
!Moodle 3.5.8
|9 September 2019
|2018051708
|[[Moodle 3.5.8 release notes|Release Notes]]
|
|-
!Moodle 3.5.9
|11 November 2019
|2018051709
|[[Moodle 3.5.9 release notes|Release Notes]]
|
|-
!Moodle 3.5.10
|13 January 2020
|2018051710
| [[Moodle 3.5.10 release notes|Release Notes]]
|
|-
!Moodle 3.5.11
|9 March 2020
|2018051711
|[[Moodle 3.5.11 release notes|Release Notes]]
|
|-
!Moodle 3.5.12
|11 May 2020
|2018051712
| [[Moodle 3.5.12 release notes|Release Notes]]
|
|-
!Moodle 3.5.13
|13 July 2020
|2018051713
|[[Moodle 3.5.13 release notes|Release Notes]]
|
|-
!Moodle 3.5.14
| 14 September 2020
|2018051714
|[[Moodle 3.5.14 release notes|Release Notes]]
|
|-
!Moodle 3.5.15
|9 November 2020
|2018051715
|[[Moodle 3.5.15 release notes|Release Notes]]
|
|-
!Moodle 3.5.16
|18 January 2021
|2018051716
| [[Moodle 3.5.16 release notes|Release Notes]]
|
|-
!Moodle 3.5.17
|8 March 2021
| 2018051717
|[[Moodle 3.5.17 release notes|Release Notes]]
|
|-
!Moodle 3.5.18
| 10 May 2021
| 2018051718
|[[Moodle 3.5.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.5.x ended May 2019 (12 months).
Bug fixes for security issues in 3.5.x ended 10 May 2021 (36 months).
==Moodle 3.4==
{| class="wikitable"
|-
!Moodle 3.4
|13 November 2017
|2017111300
|[[Moodle 3.4 release notes|Release Notes]]
|
[https://docs.moodle.org/34/en/Upgrading Upgrading to 3.4]
|-
! Moodle 3.4.1
|15 January 2018
|2017111301
|[[Moodle 3.4.1 release notes|Release Notes]]
|
|-
!Moodle 3.4.2
|19 March 2018
|2017111302
|[[Moodle 3.4.2 release notes|Release Notes]]
|
|-
!Moodle 3.4.3
|17 May 2018
|2017111303
|[[Moodle 3.4.3 release notes|Release Notes]]
|
|-
! Moodle 3.4.4
|9 July 2018
|2017111304
|[[Moodle 3.4.4 release notes|Release Notes]]
|
|-
!Moodle 3.4.5
|10 September 2018
|2017111305
|[[Moodle 3.4.5 release notes|Release Notes]]
|
|-
!Moodle 3.4.6
|12 November 2018
|2017111306
| [[Moodle 3.4.6 release notes|Release Notes]]
|
|-
! Moodle 3.4.7
|14 January 2019
|2017111307
|[[Moodle 3.4.7 release notes|Release Notes]]
|
|-
!Moodle 3.4.8
|11 March 2019
|2017111308
|[[Moodle 3.4.8 release notes|Release Notes]]
|
|-
!Moodle 3.4.9
|13 May 2019
|2017111309
| [[Moodle 3.4.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.4.x ended 12 November 2018 (12 months).
Bug fixes for security issues in 3.4.x ended 13 May 2019 (18 months).
==Moodle 3.3==
{| class="wikitable"
|-
!Moodle 3.3
|15 May 2017
|2017051500
|[[Moodle 3.3 release notes|Release Notes]]
|
[https://docs.moodle.org/33/en/Upgrading Upgrading to 3.3]
|-
!Moodle 3.3.1
|10 July 2017
|2017051501
|[[Moodle 3.3.1 release notes|Release Notes]]
|
|-
!Moodle 3.3.2
|11 September 2017
|2017051502
|[[Moodle 3.3.2 release notes|Release Notes]]
|
|-
!Moodle 3.3.3
|13 November 2017
|2017051503
| [[Moodle 3.3.3 release notes|Release Notes]]
|
|-
! Moodle 3.3.4
|15 January 2018
|2017051504
|[[Moodle 3.3.4 release notes|Release Notes]]
|
|-
!Moodle 3.3.5
|19 March 2018
|2017051505
|[[Moodle 3.3.5 release notes|Release Notes]]
|
|-
!Moodle 3.3.6
|17 May 2018
|2017051506
|[[Moodle 3.3.6 release notes|Release Notes]]
|
|-
! Moodle 3.3.7
|9 July 2018
|2017051507
|[[Moodle 3.3.7 release notes|Release Notes]]
|
|-
!Moodle 3.3.8
|10 September 2018
|2017051508
|[[Moodle 3.3.8 release notes|Release Notes]]
|
|-
! Moodle 3.3.9
|12 November 2018
|2017051509
|[[Moodle 3.3.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.3.x ended 17 May 2018 (12 months).
Bug fixes for security issues in 3.3.x ended 12 November 2018 (18 months).
==Moodle 3.2==
{| class="wikitable"
|-
!Moodle 3.2
| 5 December 2016
|2016120500
|[[Moodle 3.2 release notes|Release Notes]]
|[https://docs.moodle.org/32/en/Upgrading Upgrading to 3.2]
|-
!Moodle 3.2.1
|9 January 2017
|2016120501
|[[Moodle 3.2.1 release notes|Release Notes]]
|
|-
!Moodle 3.2.2
|13 March 2017
|2016120502
|[[Moodle 3.2.2 release notes|Release Notes]]
|
|-
!Moodle 3.2.3
|8 May 2017
|2016120503
|[[Moodle 3.2.3 release notes|Release Notes]]
|
|-
!Moodle 3.2.4
|10 July 2017
|2016120504
|[[Moodle 3.2.4 release notes|Release Notes]]
|
|-
!Moodle 3.2.5
|11 September 2017
|2016120505
|[[Moodle 3.2.5 release notes|Release Notes]]
|
|-
!Moodle 3.2.6
|13 November 2017
|2016120506
| [[Moodle 3.2.6 release notes|Release Notes]]
|
|-
! Moodle 3.2.7
|15 January 2018
|2016120507
|[[Moodle 3.2.7 release notes|Release Notes]]
|
|-
!Moodle 3.2.8
|19 March 2018
|2016120508
|[[Moodle 3.2.8 release notes|Release Notes]]
|
|-
!Moodle 3.2.9
|17 May 2018
|2016120509
| [[Moodle 3.2.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.2.x ended 13 November 2017 (12 months).
Bug fixes for security issues in 3.2.x ended 17 May 2018 (18 months).
==Moodle 3.1 (LTS)==
{| class="wikitable"
|-
!Moodle 3.1
|23 May 2016
|2016052300
|[[Moodle 3.1 release notes|Release Notes]]
|
[https://docs.moodle.org/31/en/Upgrading Upgrading to 3.1]
|-
!Moodle 3.1.1
|11 July 2016
|2016052301
|[[Moodle 3.1.1 release notes|Release Notes]]
|
|-
!Moodle 3.1.2
|12 September 2016
|2016052302
|[[Moodle 3.1.2 release notes|Release Notes]]
|
|-
!Moodle 3.1.3
|14 November 2016
|2016052303
|[[Moodle 3.1.3 release notes|Release Notes]]
|
|-
!Moodle 3.1.4
|9 January 2017
|2016052304
|[[Moodle 3.1.4 release notes|Release Notes]]
|
|-
!Moodle 3.1.5
|13 March 2017
|2016052305
|[[Moodle 3.1.5 release notes|Release Notes]]
|
|-
!Moodle 3.1.6
|8 May 2017
|2016052306
|[[Moodle 3.1.6 release notes|Release Notes]]
|
|-
!Moodle 3.1.7
|10 July 2017
|2016052307
|[[Moodle 3.1.7 release notes|Release Notes]]
|
|-
!Moodle 3.1.8
|11 September 2017
|2016052308
|[[Moodle 3.1.8 release notes|Release Notes]]
|
|-
!Moodle 3.1.9
|13 November 2017
|2016052309
|[[Moodle 3.1.9 release notes|Release Notes]]
|
|-
!Moodle 3.1.10
|15 January 2018
|2016052310
|[[Moodle 3.1.10 release notes|Release Notes]]
|
|-
! Moodle 3.1.11
|19 March 2018
|2016052311
|[[Moodle 3.1.11 release notes|Release Notes]]
|
|-
!Moodle 3.1.12
|17 May 2018
|2016052312
|[[Moodle 3.1.12 release notes|Release Notes]]
|
|-
!Moodle 3.1.13
|9 July 2018
|2016052313
|[[Moodle 3.1.13 release notes|Release Notes]]
|
|-
!Moodle 3.1.14
|10 September 2018
|2016052314
|[[Moodle 3.1.14 release notes|Release Notes]]
|
|-
! Moodle 3.1.15
|12 November 2018
|2016052315
|[[Moodle 3.1.15 release notes|Release Notes]]
|
|-
!Moodle 3.1.16
|14 January 2019
|2016052316
|[[Moodle 3.1.16 release notes|Release Notes]]
|
|-
! Moodle 3.1.17
|11 March 2019
| 2016052317
|[[Moodle 3.1.17 release notes|Release Notes]]
|
|-
!Moodle 3.1.18
|13 May 2019
|2016052318
|[[Moodle 3.1.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.1.x ended 8 May 2017 (12 months).
Bug fixes for security issues in 3.1.x ended 13 May 2019 (36 months).
==Moodle 3.0==
{| class="wikitable"
|-
!Moodle 3.0
|16 November 2015
|2015111600
|[[Moodle 3.0 release notes|Release Notes]]
|[https://docs.moodle.org/30/en/Upgrading Upgrading to 3.0]
|-
!Moodle 3.0.1
|21 December 2015
|2015111601
| [[Moodle 3.0.1 release notes|Release Notes]]
|
|-
! Moodle 3.0.2
|11 January 2016
|2015111602
|[[Moodle 3.0.2 release notes|Release Notes]]
|
|-
!Moodle 3.0.3
|14 March 2016
|2015111603
|[[Moodle 3.0.3 release notes|Release Notes]]
|
|-
!Moodle 3.0.4
|9 May 2016
|2015111604
|[[Moodle 3.0.4 release notes|Release Notes]]
|
|-
!Moodle 3.0.5
|11 July 2016
|2015111605
|[[Moodle 3.0.5 release notes|Release Notes]]
|
|-
!Moodle 3.0.6
|12 September 2016
|2015111606
|[[Moodle 3.0.6 release notes|Release Notes]]
|
|-
!Moodle 3.0.7
|14 November 2016
|2015111607
|[[Moodle 3.0.7 release notes|Release Notes]]
|
|-
!Moodle 3.0.8
|9 January 2017
|2015111608
|[[Moodle 3.0.8 release notes|Release Notes]]
|
|-
!Moodle 3.0.9
|13 March 2017
|2015111609
|[[Moodle 3.0.9 release notes|Release Notes]]
|
|-
!Moodle 3.0.10
|8 May 2017
|2015111610
|[[Moodle 3.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.0.x ended 14 November 2016 (12 months).
Bug fixes for security issues in 3.0.x ended 8 May 2017 (18 months).
==Moodle 2.9==
{| class="wikitable"
|-
!Moodle 2.9
| 11 May 2015
|2015051100
|[[Moodle 2.9 release notes|Release Notes]]
| [https://docs.moodle.org/29/en/Upgrading_to_Moodle_2.9 Upgrading to 2.9]
|-
! Moodle 2.9.1
|6 July 2015
|2015051101
|[[Moodle 2.9.1 release notes|Release Notes]]
|
|-
!Moodle 2.9.2
|14 September 2015
|2015051102
| [[Moodle 2.9.2 release notes|Release Notes]]
|
|-
!Moodle 2.9.3
|9 November 2015
|2015051103
| [[Moodle 2.9.3 release notes|Release Notes]]
|
|-
! Moodle 2.9.4
|11 January 2016
|2015051104
|[[Moodle 2.9.4 release notes|Release Notes]]
|
|-
!Moodle 2.9.5
|14 March 2016
|2015051105
|[[Moodle 2.9.5 release notes|Release Notes]]
|
|-
!Moodle 2.9.6
|9 May 2016
|2015051106
|[[Moodle 2.9.6 release notes|Release Notes]]
|
|-
!Moodle 2.9.7
|11 July 2016
|2015051107
|[[Moodle 2.9.7 release notes|Release Notes]]
|
|-
!Moodle 2.9.8
|12 September 2016
|2015051108
|[[Moodle 2.9.8 release notes|Release Notes]]
|
|-
! Moodle 2.9.9
|14 November 2016
|2015051109
|[[Moodle 2.9.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.9.x ended 9 May 2016 (12 months).
Bug fixes for security issues in 2.9.x ended 14 November 2016 (18 months).
==Moodle 2.8==
{| class="wikitable"
|-
!Moodle 2.8
|10 November 2014
|2014111000
| [[Moodle 2.8 release notes|Release Notes]]
|[https://docs.moodle.org/28/en/Upgrading_to_Moodle_2.8 Upgrading to 2.8]
|-
!Moodle 2.8.1
|13 November 2014
|2014111001
| [[Moodle 2.8.1 release notes|Release Notes]]
|
|-
!Moodle 2.8.2
|12 January 2015
|2014111002
| [[Moodle 2.8.2 release notes|Release Notes]]
|
|-
!Moodle 2.8.3
|2 February 2015
|2014111003
|[[Moodle 2.8.3 release notes|Release Notes]]
|
|-
!Moodle 2.8.4
|9 March 2015
|2014111004
|[[Moodle 2.8.4 release notes|Release Notes]]
|
|-
!Moodle 2.8.5
|10 March 2015
|2014111005
|[[Moodle 2.8.5 release notes|Release Notes]]
|
|-
!Moodle 2.8.6
|11 May 2015
|2014111006
|[[Moodle 2.8.6 release notes|Release Notes]]
|
|-
! Moodle 2.8.7
|6 July 2015
|2014111007
|[[Moodle 2.8.7 release notes|Release Notes]]
|
|-
!Moodle 2.8.8
|14 September 2015
|2014111008
| [[Moodle 2.8.8 release notes|Release Notes]]
|
|-
!Moodle 2.8.9
|9 November 2015
|2014111009
|[[Moodle 2.8.9 release notes|Release Notes]]
|
|-
!Moodle 2.8.10
|11 January 2016
|2014111010
|[[Moodle 2.8.10 release notes|Release Notes]]
|
|-
!Moodle 2.8.11
|14 March 2016
|2014111011
|[[Moodle 2.8.11 release notes|Release Notes]]
|
|-
!Moodle 2.8.12
|9 May 2016
|2014111012
| [[Moodle 2.8.12 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.8.x ended 9 November 2015 (12 months).
Bug fixes for security issues in 2.8.x ended 9 May 2016 (18 months).
==Moodle 2.7 (LTS)==
{| class="wikitable"
|-
!Moodle 2.7
| 12 May 2014
|2014051200
|[[Moodle 2.7 release notes|Release Notes]]
|[https://docs.moodle.org/27/en/Upgrading_to_Moodle_2.7 Upgrading to 2.7]
|-
! Moodle 2.7.1
|14 July 2014
|2014051201
|[[Moodle 2.7.1 release notes|Release Notes]]
|
|-
!Moodle 2.7.2
|8 September 2014
|2014051202
|[[Moodle 2.7.2 release notes|Release Notes]]
|
|-
!Moodle 2.7.3
|10 November 2014
|2014051203
| [[Moodle 2.7.3 release notes|Release Notes]]
|
|-
!Moodle 2.7.4
|12 January 2015
|2014051204
| [[Moodle 2.7.4 release notes|Release Notes]]
|
|-
!Moodle 2.7.5
|2 February 2015
|2014051205
|[[Moodle 2.7.5 release notes|Release Notes]]
|
|-
!Moodle 2.7.6
|9 March 2015
|2014051206
|[[Moodle 2.7.6 release notes|Release Notes]]
|
|-
!Moodle 2.7.7
|10 March 2015
|2014051207
|[[Moodle 2.7.7 release notes|Release Notes]]
|
|-
!Moodle 2.7.8
|11 May 2015
|2014051208
|[[Moodle 2.7.8 release notes|Release Notes]]
|
|-
!Moodle 2.7.9
|6 July 2015
|2014051209
|[[Moodle 2.7.9 release notes|Release Notes]]
|
|-
!Moodle 2.7.10
| 14 September 2015
|2014051210
|[[Moodle 2.7.10 release notes|Release Notes]]
|
|-
!Moodle 2.7.11
|9 November 2015
|2014051211
|[[Moodle 2.7.11 release notes|Release Notes]]
|
|-
!Moodle 2.7.12
|11 January 2016
|2014051212
|[[Moodle 2.7.12 release notes|Release Notes]]
|
|-
!Moodle 2.7.13
|14 March 2016
|2014051213
|[[Moodle 2.7.13 release notes|Release Notes]]
|
|-
!Moodle 2.7.14
|9 May 2016
|2014051214
| [[Moodle 2.7.14 release notes|Release Notes]]
|
|-
!Moodle 2.7.15
|11 July 2016
|2014051215
|[[Moodle 2.7.15 release notes|Release Notes]]
|
|-
!Moodle 2.7.16
|12 September 2016
|2014051216
|[[Moodle 2.7.16 release notes|Release Notes]]
|
|-
!Moodle 2.7.17
|14 November 2016
|2014051217
|[[Moodle 2.7.17 release notes|Release Notes]]
|
|-
!Moodle 2.7.18
|9 January 2017
|2014051218
|[[Moodle 2.7.18 release notes|Release Notes]]
|
|-
!Moodle 2.7.19
|13 March 2017
|2014051219
|[[Moodle 2.7.19 release notes|Release Notes]]
|
|-
!Moodle 2.7.20
|8 May 2017
|2014051220
| [[Moodle 2.7.20 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.7.x ended 11 May 2015 (12 months).
Bug fixes for security issues in 2.7.x ended 8 May 2017 (36 months).
==Moodle 2.6==
{| class="wikitable"
|-
!Moodle 2.6
|18 November 2013
|2013111800
|[[Moodle 2.6 release notes|Release Notes]]
|[https://docs.moodle.org/26/en/Upgrading_to_Moodle_2.6 Upgrading to 2.6]
|-
!Moodle 2.6.1
|13 January 2014
| 2013111801
| [[Moodle 2.6.1 release notes|Release Notes]]
|
|-
!Moodle 2.6.2
|10 March 2014
|2013111802
|[[Moodle 2.6.2 release notes|Release Notes]]
|
|-
!Moodle 2.6.3
|12 May 2014
|2013111803
|[[Moodle 2.6.3 release notes|Release Notes]]
|
|-
!Moodle 2.6.4
|14 July 2014
|2013111804
|[[Moodle 2.6.4 release notes|Release Notes]]
|
|-
!Moodle 2.6.5
|8 September 2014
|2013111805
|[[Moodle 2.6.5 release notes|Release Notes]]
|
|-
!Moodle 2.6.6
|10 November 2014
|2013111806
|[[Moodle 2.6.6 release notes|Release Notes]]
|
|-
!Moodle 2.6.7
|12 January 2015
|2013111807
|[[Moodle 2.6.7 release notes|Release Notes]]
|
|-
! Moodle 2.6.8
|2 February 2015
|2013111808
|[[Moodle 2.6.8 release notes|Release Notes]]
|
|-
! Moodle 2.6.9
|9 March 2015
|2013111809
|[[Moodle 2.6.9 release notes|Release Notes]]
|
|-
!Moodle 2.6.10
|10 March 2015
|2013111810
| [[Moodle 2.6.10 release notes|Release Notes]]
|
|-
!Moodle 2.6.11
|11 May 2015
|2013111811
|[[Moodle 2.6.11 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 2.6.x ended 10 November 2014 (12 months).
Bug fixes for security issues in 2.6.x ended 11 May 2015 (18 months).
==Moodle 2.5==
{| class="wikitable"
|-
!Moodle 2.5
| 14 May 2013
|2013051400
|[[Moodle 2.5 release notes|Release Notes]]
| [https://docs.moodle.org/25/en/Upgrading_to_Moodle_2.5 Upgrading to 2.5]
|-
! Moodle 2.5.1
|8 July 2013
|2013051401
|[[Moodle 2.5.1 release notes|Release Notes]]
|
|-
!Moodle 2.5.2
|9 September 2013
|2013051402
|[[Moodle 2.5.2 release notes|Release Notes]]
|
|-
!Moodle 2.5.3
|11 November 2013
|2013051403
|[[Moodle 2.5.3 release notes|Release Notes]]
|
|-
!Moodle 2.5.4
|13 January 2014
| 2013051404
| [[Moodle 2.5.4 release notes|Release Notes]]
|
|-
!Moodle 2.5.5
|10 March 2014
|2013051405
|[[Moodle 2.5.5 release notes|Release Notes]]
|
|-
!Moodle 2.5.6
|12 May 2014
|2013051406
|[[Moodle 2.5.6 release notes|Release Notes]]
|
|-
!Moodle 2.5.7
|14 July 2014
|2013051407
|[[Moodle 2.5.7 release notes|Release Notes]]
|
|-
!Moodle 2.5.8
|8 September 2014
|2013051408
|[[Moodle 2.5.8 release notes|Release Notes]]
|
|-
! Moodle 2.5.9
| 10 November 2014
|2013051409
|[[Moodle 2.5.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.5.x ended May 2014 (12 months).
Bug fixes for security issues in 2.5.x ended 10 November 2014 (18 months).
==Moodle 2.4==
{| class="wikitable"
|-
! Moodle 2.4
|3 December 2012
|2012120300
|[[Moodle 2.4 release notes|Release Notes]]
|[https://docs.moodle.org/24/en/Upgrading_to_Moodle_2.4 Upgrading to 2.4]
|-
! Moodle 2.4.1
|14 January 2013
|2012120301
|[[Moodle 2.4.1 release notes|Release Notes]]
|
|-
!Moodle 2.4.2
|11 March 2013
|2012120302
|[[Moodle 2.4.2 release notes|Release Notes]]
|
|-
!Moodle 2.4.3
|18 March 2013
|2012120303
|[[Moodle 2.4.3 release notes|Release Notes]]
|
|-
!Moodle 2.4.4
|14 May 2013
|2012120304
|[[Moodle 2.4.4 release notes|Release Notes]]
|
|-
!Moodle 2.4.5
|8 July 2013
|2012120305
|[[Moodle 2.4.5 release notes|Release Notes]]
|
|-
!Moodle 2.4.6
|9 September 2013
|2012120306
|[[Moodle 2.4.6 release notes|Release Notes]]
|
|-
!Moodle 2.4.7
|11 November 2013
|2012120307
| [[Moodle 2.4.7 release notes|Release Notes]]
|
|-
! Moodle 2.4.8
|13 January 2014
|2012120308
|[[Moodle 2.4.8 release notes|Release Notes]]
|
|-
!Moodle 2.4.9
|10 March 2014
|2012120309
|[[Moodle 2.4.9 release notes|Release Notes]]
|
|-
!Moodle 2.4.10
|12 May 2014
|2012120310
| [[Moodle 2.4.10 release notes|Release Notes]]
|
|-
!Moodle 2.4.11
|14 July 2014
|2012120311
|[[Moodle 2.4.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.4.x ended December 2013 (12 months).
Bug fixes for security issues in 2.4.x ended June 2014 (18 months).
==Moodle 2.3==
{| class="wikitable"
|-
!Moodle 2.3
|25 June 2012
|2012062500
|[[Moodle 2.3 release notes|Release Notes]]
| [https://docs.moodle.org/23/en/Upgrading_to_Moodle_2.3 Upgrading to 2.3]
|-
!Moodle 2.3.1
|9 July 2012
|2012062501
|[[Moodle 2.3.1 release notes|Release Notes]]
|
|-
! Moodle 2.3.2
|10 September 2012
|2012062502
|[[Moodle 2.3.2 release notes|Release Notes]]
|
|-
!Moodle 2.3.3
|12 November 2012
|2012062503
|[[Moodle 2.3.3 release notes|Release Notes]]
|
|-
! Moodle 2.3.4
|14 January 2013
|2012062504
|[[Moodle 2.3.4 release notes|Release Notes]]
|
|-
!Moodle 2.3.5
|11 March 2013
|2012062505
|[[Moodle 2.3.5 release notes|Release Notes]]
|
|-
!Moodle 2.3.6
|18 March 2013
|2012062506
|[[Moodle 2.3.6 release notes|Release Notes]]
|
|-
!Moodle 2.3.7
|14 May 2013
|2012062507
|[[Moodle 2.3.7 release notes|Release Notes]]
|
|-
!Moodle 2.3.8
|8 July 2013
|2012062508
|[[Moodle 2.3.8 release notes|Release Notes]]
|
|-
!Moodle 2.3.9
|9 September 2013
|2012062509
|[[Moodle 2.3.9 release notes|Release Notes]]
|
|-
! Moodle 2.3.10
|11 November 2013
|2012062510
|[[Moodle 2.3.10 release notes|Release Notes]]
|
|-
!Moodle 2.3.11
|13 January 2014
|2012062511
|[[Moodle 2.3.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.3.x ended June 2013 (12 months).
Bug fixes for security issues in 2.3.x ended December 2013 (18 months).
==Moodle 2.2==
{| class="wikitable"
|-
! Moodle 2.2
|5 December 2011
|2011120500
|[[Moodle 2.2 release notes|Release Notes]]
|[https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 Upgrading to 2.2]
|-
!Moodle 2.2.1
|9 January 2012
|2011120501
|[[Moodle 2.2.1 release notes|Release Notes]]
|
|-
!Moodle 2.2.2
|12 March 2012
|2011120502
|[[Moodle 2.2.2 release notes|Release Notes]]
|
|-
!Moodle 2.2.3
|14 May 2012
|2011120503
|[[Moodle 2.2.3 release notes|Release Notes]]
|
|-
! Moodle 2.2.4
|9 July 2012
|2011120504
|[[Moodle 2.2.4 release notes|Release Notes]]
|
|-
!Moodle 2.2.5
|10 September 2012
|2011120505
|[[Moodle 2.2.5 release notes|Release Notes]]
|
|-
!Moodle 2.2.6
|12 November 2012
|2011120506
| [[Moodle 2.2.6 release notes|Release Notes]]
|
|-
! Moodle 2.2.7
|14 January 2013
|2011120507
|[[Moodle 2.2.7 release notes|Release Notes]]
|
|-
!Moodle 2.2.8
|11 March 2013
|2011120508
|[[Moodle 2.2.8 release notes|Release Notes]]
|
|-
!Moodle 2.2.9
|18 March 2013
|2011120509
|[[Moodle 2.2.9 release notes|Release Notes]]
|
|-
!Moodle 2.2.10
|14 May 2013
| 2011120510
|[[Moodle 2.2.10 release notes|Release Notes]]
|
|-
!Moodle 2.2.11
|8 July 2013
|2011120511
|[[Moodle 2.2.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.2.x ended December 2012 (12 months).
Bug fixes for security issues in 2.2.x ended June 2013 (18 months).
==Moodle 2.1==
{| class="wikitable"
|-
!Moodle 2.1
| 1 July 2011
|2011070100
|[[Moodle 2.1 release notes|Release Notes]]
|[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to 2.1]
|-
! Moodle 2.1.1
|1 August 2011
|2011070101
| [[Moodle 2.1.1 release notes|Release Notes]]
|
|-
!Moodle 2.1.2
|10 October 2011
|2011070102
|[[Moodle 2.1.2 release notes|Release Notes]]
|
|-
!Moodle 2.1.3
|28 November 2011
|2011070103
|[[Moodle 2.1.3 release notes|Release Notes]]
|
|-
!Moodle 2.1.4
|9 January 2012
|2011070104
|[[Moodle 2.1.4 release notes|Release Notes]]
|
|-
!Moodle 2.1.5
|12 March 2012
|2011070105
|[[Moodle 2.1.5 release notes|Release Notes]]
|
|-
!Moodle 2.1.6
|14 May 2012
|2011070106
|[[Moodle 2.1.6 release notes|Release Notes]]
|
|-
! Moodle 2.1.7
|9 July 2012
|2011070107
|[[Moodle 2.1.7 release notes|Release Notes]]
|
|-
!Moodle 2.1.8
|10 September 2012
|2011070108
|[[Moodle 2.1.8 release notes|Release Notes]]
|
|-
!Moodle 2.1.9
|12 November 2012
|2011070109
|[[Moodle 2.1.9 release notes|Release Notes]]
|
|-
!Moodle 2.1.10
|14 January 2013
|2011070110
|[[Moodle 2.1.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.1.x ended June 2012 (12 months).
Bug fixes for security issues in 2.1.x ended December 2012 (18 months).
==Moodle 2.0==
{| class="wikitable"
|-
!Moodle 2.0
|24 November 2010
|2010112400
| [[Moodle 2.0 release notes|Release Notes]]
|[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to 2.0]
|-
!Moodle 2.0.1
|25 December 2010
|2010122500
|[[Moodle 2.0.1 release notes|Release Notes]]
|
|-
!Moodle 2.0.2
|21 February 2011
|2011022100
|[[Moodle 2.0.2 release notes|Release Notes]]
|
|-
!Moodle 2.0.3
|5 May 2011
|2011033003
|[[Moodle 2.0.3 release notes|Release Notes]]
|
|-
! Moodle 2.0.4
|1 August 2011
|2011033004
| [[Moodle 2.0.4 release notes|Release Notes]]
|
|-
!Moodle 2.0.5
|10 October 2011
|2011033005
|[[Moodle 2.0.5 release notes|Release Notes]]
|
|-
!Moodle 2.0.6
|28 November 2011
|2011033006
|[[Moodle 2.0.6 release notes|Release Notes]]
|
|-
!Moodle 2.0.7
|9 January 2012
|2011033007
|[[Moodle 2.0.7 release notes|Release Notes]]
|
|-
!Moodle 2.0.8
|12 March 2012
|2011033008
|[[Moodle 2.0.8 release notes|Release Notes]]
|
|-
!Moodle 2.0.9
|14 May 2012
|2011033009
|[[Moodle 2.0.9 release notes|Release Notes]]
|
|-
!Moodle 2.0.10
|9 July 2012
|2011033010
|[[Moodle 2.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.0.x ended December 2011 (12 months).
Bug fixes for security issues in 2.0.x ended June 2012 (18 months).
==Moodle 1.9==
{| class="wikitable"
|-
!Moodle 1.9
|3 March 2008
|2007101509
|[[Moodle 1.9 release notes|Release Notes]]
|[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to 1.9]
|-
!Moodle 1.9.1
|15 May 2008
| 2007101512
|[[Moodle 1.9.1 release notes|Release Notes]]
|
|-
! Moodle 1.9.2
|11 July 2008
|2007101520
|[[Moodle 1.9.2 release notes|Release Notes]]
|
|-
!Moodle 1.9.3
|15 October 2008
|2007101530
|[[Moodle 1.9.3 release notes|Release Notes]]
|
|-
!Moodle 1.9.4
|28 January 2009
|2007101540
|[[Moodle 1.9.4 release notes|Release Notes]]
|
|-
!Moodle 1.9.5
|13 May 2009
|2007101550
|[[Moodle 1.9.5 release notes|Release Notes]]
|
|-
!Moodle 1.9.6
|21 October 2009
|2007101560
|[[Moodle 1.9.6 release notes|Release Notes]]
|
|-
!Moodle 1.9.7
|25 November 2009
|2007101570
|[[Moodle 1.9.7 release notes|Release Notes]]
|
|-
!Moodle 1.9.8
|25 March 2010
|2007101580.00
|[[Moodle 1.9.8 release notes|Release Notes]]
|
|-
! Moodle 1.9.9
| 8 June 2010
| 2007101590.00
| [[Moodle 1.9.9 release notes|Release Notes]]
|
|-
!Moodle 1.9.10
|25 October 2010
|2007101591.00
|
[[Moodle 1.9.10 release notes|Release Notes]]
|
|-
!Moodle 1.9.11
|21 February 2011
|2007101591.02
|[[Moodle 1.9.11 release notes|Release Notes]]
|
|-
! Moodle 1.9.12
|10 May 2011
|2007101591.03
|[[Moodle 1.9.12 release notes|Release Notes]]
|
|-
!Moodle 1.9.13
|1 August 2011
|2007101591.04
|[[Moodle 1.9.13 release notes|Release Notes]]
|
|-
!Moodle 1.9.14
|10 October 2011
|2007101591.06
|
[[Moodle 1.9.14 release notes|Release Notes]]
|
|-
!Moodle 1.9.15
|28 November 2011
| 2007101591.07
| [[Moodle 1.9.15 release notes|Release Notes]]
|
|-
!Moodle 1.9.16
|9 January 2012
|2007101591.10
|[[Moodle 1.9.16 release notes|Release Notes]]
|
|-
! Moodle 1.9.17
|12 March 2012
|2007101591.12
|[[Moodle 1.9.17 release notes|Release Notes]]
|
|-
!Moodle 1.9.18
|14 May 2012
|2007101591.16
|[[Moodle 1.9.18 release notes|Release Notes]]
|
|-
! Moodle 1.9.19
|9 July 2012
|2007101592.00
|[[Moodle 1.9.19 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 1.9.x has ended June 2011 (3.5 years).
Bug fixes for security issues in 1.9.x by Moodle HQ ended June 2012 (4.5 years).
Bug fixes for security issues in 1.9.19+ branch by [http://catalyst.net.nz Catalyst IT] ended [http://moodle.org/mod/forum/discuss.php?d=199706 Dec 2013] (6 years).
==Moodle 1.8 ==
*[[Moodle 1.8 release notes|Moodle 1.8]] - 30 March 2007
*[[Moodle 1.8.1 release notes|Moodle 1.8.1]] - 14 June 2007
*[[Moodle 1.8.2 release notes|Moodle 1.8.2]] - 8 July 2007
*[[Moodle 1.8.3 release notes|Moodle 1.8.3]] - 11 October 2007
*[[Moodle 1.8.4 release notes|Moodle 1.8.4]] - 11 January 2008
*[[Moodle 1.8.5 release notes|Moodle 1.8.5]] - 8 April 2008
*[[Moodle 1.8.6 release notes|Moodle 1.8.6]] - 11 July 2008
*[[Moodle 1.8.7 release notes|Moodle 1.8.7]] - 15 October 2008
*[[Moodle 1.8.8 release notes|Moodle 1.8.8]] - 28 January 2009
*[[Moodle 1.8.9 release notes|Moodle 1.8.9]] - 15 May 2009
*[[Moodle 1.8.10 release notes|Moodle 1.8.10]] - 26 October 2009
*[[Moodle 1.8.11 release notes|Moodle 1.8.11]] - 25 November 2009
*[[Moodle 1.8.12 release notes|Moodle 1.8.12]] - 27 March 2010
*[[Moodle 1.8.13 release notes|Moodle 1.8.13]] - 8 June 2010
*[[Moodle 1.8.14 release notes|Moodle 1.8.14]] - 3 December 2010
*Support has ended

==Moodle 1.7==
*[[Moodle 1.7 release notes|Moodle 1.7]] - 7 November 2006
*[[Moodle 1.7.1 release notes|Moodle 1.7.1]] - 17 January 2007
*[[Moodle 1.7.2 release notes|Moodle 1.7.2]] - 30 March 2007
*[[Moodle 1.7.3 release notes|Moodle 1.7.3]] - 11 October 2007
*[[Moodle 1.7.4 release notes|Moodle 1.7.4]] - 11 January 2008
*[[Moodle 1.7.5 release notes|Moodle 1.7.5]] - 11 July 2008
*[[Moodle 1.7.6 release notes|Moodle 1.7.6]] - 15 October 2008
*[[Moodle 1.7.7 release notes|Moodle 1.7.7]] - 28 January 2009
*Support has ended
==Moodle 1.6==
*[[Moodle 1.6 release notes|Moodle 1.6]] - 20 June 2006
*[[Moodle 1.6.1 release notes|Moodle 1.6.1]] - 20 July 2006
*[[Moodle 1.6.2 release notes|Moodle 1.6.2]] - 12 September 2006
*[[Moodle 1.6.3 release notes|Moodle 1.6.3]] - 10 October 2006
*[[Moodle 1.6.4 release notes|Moodle 1.6.4]] - 17 January 2007
*[[Moodle 1.6.5 release notes|Moodle 1.6.5]] - 30 March 2007
*Moodle 1.6.6 - 11 January 2008
*Moodle 1.6.7 - 11 July 2008
*[[Moodle 1.6.8 release notes|Moodle 1.6.8]] - 15 October 2008
*[[Moodle 1.6.9 release notes|Moodle 1.6.9]] - 28 January 2009
* Support has ended
==Moodle 1.5==
*[[Moodle 1.5 release notes|Moodle 1.5]] - 5 June 2005
*[[Moodle 1.5.1 release notes|Moodle 1.5.1]] - 8 July 2005
*[[Moodle 1.5.2 release notes|Moodle 1.5.2]] - 16 July 2005
*[[Moodle 1.5.3 release notes|Moodle 1.5.3]] - 11 November 2005
*[[Moodle 1.5.4 release notes|Moodle 1.5.4]] - 21 May 2006
*Support has ended
==Moodle 1.4==
*Moodle 1.4 - 31 August 2004
*Moodle 1.4.1 - 12 September 2004
*Moodle 1.4.2 - 5 November 2004
*Moodle 1.4.3 - 21 December 2004
*Moodle 1.4.4 - 7 March 2005
*[[Moodle 1.4.5 release notes|Moodle 1.4.5]] - 7 May 2005
*Support has ended
==Moodle 1.3==
*Moodle 1.3 - 25 May 2004
* Moodle 1.3.1 - 4 June 2004
*Moodle 1.3.2 - 9 July 2004
*Moodle 1.3.3 - 16 July 2004
* Moodle 1.3.4 - 11 August 2004
*Moodle 1.3.5 - 9 September 2004
*Support has ended
==Moodle 1.2==
*Moodle 1.2 - 20 March 2004
*Moodle 1.2.1 - 25 March 2004
*Support has ended
==Moodle 1.1==
*Moodle 1.1 - 29 August 2003
*Moodle 1.1.1 - 11 September 2003
*Support has ended
== Moodle 1.0==
*Moodle 1.0 - 20 August 2002
*Moodle 1.0.1 - 26 August 2002
*Moodle 1.0.2 - 2 September 2002
*Moodle 1.0.3 - 5 September 2002
*Moodle 1.0.4 - 10 September 2002
*Moodle 1.0.5 - 27 September 2002
* Moodle 1.0.6 - 26 October 2002
::1.0.6.1 - 6 November 2002
::1.0.6.2 - 11 November 2002
::1.0.6.3 - 14 November 2002
::1.0.6.4 - 25 November 2002
*Moodle 1.0.7 - 9 December 2002
*Moodle 1.0.8 - 7 January 2003
*Moodle 1.0.9 - 30 May 2003
*Support has ended
==See also==
*[[Roadmap]] - future versions
*[[Moodle versions]] - an explanation of how our versions work plus version numbers for each release (for $plugin->requires)
[[Category:Release notes]]
[[Category:Core development]]
[[fr:Historique des versions]]
[[es:dev/Historia de las versiones]]
[[de:Versionshistorie]]

File:401 release graph.png

2022-05-09T01:27:26Z

Abgreeve: A graph that shows the 4.0.1 release. Details about this can be found in a table.

== Summary ==
A graph that shows the 4.0.1 release. Details about this can be found in a table.

Setting up Sublime2

2022-04-28T03:17:09Z

Abgreeve: Marking this document as obsolete

{{obsolete}}

According Wikipedia ''Sublime Text is a cross-platform text and source code editor, with a Python API. The chrome was inspired by Vim. Its functionality is also extendable with sublime-packages; Sublime Text is not open source software nor free software, but some of the extending packages have free-software licenses and are community-built and maintained.''

== Sublime Settings ==

For Moodle Development:

Preferences -> Settings (default or user)

Tab size and spaces:

"tab_size": 4,

// Set to true to insert spaces when tab is pressed
"translate_tabs_to_spaces": true,

"rulers":
[
132
],

== Sublime plugins for PHP and Moodle Development ==

For installing new plugins in Sublime2, the best way is to use the Sublime Package Control, see [http://wbond.net/sublime_packages/package_control/installation installation instructions]

=== SublimeMoodle ===

By [https://moodle.org/user/view.php?id=1451616&course=5 Frédéric Massart]

* Auto completion for functions, classes and constants.
* Helper to write testing instructions (Command palette > Moodle: Write testing instructions)
* Open a tracker issue based on user input (Command palette > Moodle: Open a tracker issue)
* Open a tracker issue based on text selection or current branch (Command palette > Moodle: Resolve and open tracker issue)

You need to install it manually or add a new Package Control repository

https://github.com/FMCorz/SublimeMoodle

=== Trailing Spaces ===

A Sublime Text 2 and 3 plugin that allows you to highlight trailing spaces and delete them in a flash!

https://github.com/SublimeText/TrailingSpaces

=== Sublime PHP CS ===

PHP CodeSniffer, PHP Coding Standard Fixer, Linter, Mess Detector and Facebook Scheck Support for Sublime Text

I recommend to enable only the Linter and the PHP Coding Standard Fixer. Mess Detector and Scheck may help a lot but they not fit well with some Moodle coding rules.

The PHP Coding Standard Fixer check the code using the PEAR standard, for installing the Moodle standard you can install using PEAR or manually install it.

'''Install using pear installer'''

1. Install PHP CS using PEAR installer following steps described in https://docs.moodle.org/dev/CodeSniffer#Installing_PHP_CS

2. Edit the settings for the PHP CodeSniffer package, change this:
<syntaxhighlight lang="php">
"phpcs_additional_args": {
"--standard": "moodle",
"-n": ""
},
</syntaxhighlight>

You can delete the -n option if you want to see also Warnings

<syntaxhighlight lang="php">
// This display warnings also.
"phpcs_additional_args": {
"--standard": "moodle"
},
</syntaxhighlight>
You can put the previous directories in a different directory and change the --standard value to point to that directory

'''Manually install (to avoid dependencies issues)'''

1 Download the phpcs.phar bundle from the author web page: https://github.com/squizlabs/PHP_CodeSniffer/releases/download/3.5.8/phpcs.phar (remember to chmod +x the phpcs.phar file)

2 Clone the https://github.com/moodlehq/moodle-local_codechecker repo into a local directory

3 Edit the settings for the PHP CodeSniffer package, change this:

"phpcs_executable_path": "/path/to/phpcs.phar",

"phpcs_additional_args": {
"--standard": "/path/to/moodle-local_codechecker/moodle",
"-n": ""
},

=== DockBlockr ===

Simplifies writing DocBlock comments in Javascript, PHP, CoffeeScript, Actionscript, C & C++

Just type /** and tab ... It will preload the fool dock skel (tab between vars for quick editing)

https://github.com/spadgos/sublime-jsdocs

=== Sidebar Enhancements ===

Enhancements to Sublime Text sidebar. Files and folders.

https://github.com/titoBouzout/SideBarEnhancements

=== Bracket Highlighter ===

Bracket and tag highlighter for Sublime Text 2

https://github.com/facelessuser/BracketHighlighter

=== Sublime CodeIntel ===

Full-featured code intelligence and smart autocomplete engine

Avoid to index XML files (it will crash with Moodle), Shift + Click for jumping to function definitions

I recomend you to index only the Moodle lib/ folder (include the folder in your project in order to allo CodeIntel to index it)

http://github.com/Kronuz/SublimeCodeIntel

[[Category:Developer tools|Sublime]]

Moodle 4.0 developer update

2022-03-31T06:55:02Z

Abgreeve: Removed unnecessary 4.0 tag

This page highlights the important changes that are coming in Moodle 4.0 for developers. Including how the UX improvements impact custom themes, relevant API changes, and what you can do as developer to prepare for the 4.0 release.
== Navigation changes ==
The core Navigation API has been left mostly untouched. The callbacks to all navigation callbacks remains unchanged and will be called as part of the regular 'navigation' and 'settingsnav' initialisation. Some new core classes have been created and exist within a new namespace 'core/navigation' and serves as conduit to rearrange, cherry-pick existing navigation nodes from the navigation/settingsnav trees and display within the respective navigation type. As such, it is highly recommended to provide unique keys for custom navigation nodes as this helps in the cherry-picking / rearranging process within the new classes.
=== Primary navigation ===
The primary navigation(the navbar) apart from the existing content will now display links to the Dashboard, My Courses, Site Admin and Course search, by default. You can still add items to the navbar via the 'custom menu' option. This will be displayed within the 'More' menu. We have transitioned the menus to be rendered via templates - refer user_menu.mustache. The lang menu has been moved to reside within the user menu.
==== Customising the primary navigation ====
Not yet implemented but we are looking at allowing the full addition and removal of any of the primary navigation tabs in the boost theme config file.
=== Secondary navigation ===
The main content area shows tabs for secondary navigation with a maximum of 5 items being rendered in this ‘more’ menu. A new UI component has been created to render menus like this. Files:
/lib/templates/moremenu.mustache
==== Adding items to the navigation ====
The secondary navigation pulls information mainly from the settings navigation node from each context. Any plugin that implements the existing navigation hooks will have their items added to the secondary navigation.
Existing navigation hooks:
* {module}_extend_navigation
* {local}_extend_navigation
* {report}_report_extend_navigation
* {plugin}_extend_navigation_course
* {plugin}_extend_navigation_category_settings
==== Changing the order of tabs ====
Apart from the previously mentioned functions, you can also create a custom secondary class as mentioned earlier. This will automatically be picked by getter and used to render the secondary nav within the activity. E.g. mod_assign/local/views/secondary. Note: This is currently only possible on an activity and block level.
=== Tertiary navigation ===
We've moved action buttons to the top of the page. We would encourage you to do the same.
If you have any buttons on an activity page that go to another page, or open a form (or similar), then we encourage you to move them from the body of your activity page to the top. All of the core activities have been updated to follow this pattern. Please take a look to see how you can format your activity in a similar fashion. There is no API here. You are welcome to create the buttons and display them as you wish in this top area.
=== New API functions ===
==== Page API ====
* Magic getters to fetch the primary and secondary navs and the primary output.
* The secondarynav magic getter also checks whether a custom secondary class has been defined within the module's local\views directory. Use this if you want to deviate from the standard secondary nav structure/order.

* set_secondarynav - Force override the secondary navigation class

* set_secondary_navigation - Sets the ‘_hassecondarynavigation’ and optionally the ‘_hastablistsecondarynavigation’ to indicate whether a page should render the secondary navigation, and if the secondary navigation should be rendered and behave with a tablist ARIA role (as opposed to its default which is being rendered with a menubar ARIA role).
==== Navigationlib ====
* set_show_in_secondary_navigation - whether or not a node should be displayed in the secondary nav. Accepts a single boolean argument
* set_force_into_more_menu- whether or not to force a node into the 'More' menu. Accepts a single boolean argument
==== The activity header class ====
There is a new activity header class that handles the display of information common to activities. 3rd party activities are not required to explicitly output this information as part of rendering individual pages.

The common information that are currently handled by the class are:
* title
* description
* completion information

As part of the update it was required that the initial information to be displayed by the class be toggable at a theme and layout level. Taking this into account the following theme level configurable exists:
* activityheaderconfig => An array that currently only enforces 'notitle' but can be expanded in the future NOTE: Boost has this set as true by default 'options'
The following layout level options that can be defined:
* noactivityheader - to remove the header in this specific layout.
* activityheader - An array that enforces the following options:
** notitle
** nocompletion
** nodescription
The class has a page level getter which you can use to fetch the current version of the class. The base state is initialised within the constructor with the completion information only fetched when data is exported for the template.

The class has setters for the following variables which can be leveraged to modify the header for a particular page in the format set_{variable_name}:
* hidecompletion
* description
* title
Alternately, bulk operations can also be done by passing the above variables in an array to 'set_attrs' which in turn calls the setters.<blockquote>'''Note: Any updates to the activityheader needs to be performed before the call to $OUTPUT->header'''</blockquote>
===== Theme updates: =====
With the changes in boost to incorporate the primary and secondary navigation, 3rd party themes would need to account for the following in their templates:
* To leverage the activity_header, it's data needs to be exported and included into the base template :<syntaxhighlight lang="html">
{{#headercontent}}
{{> core/activity_header}}
{{#headercontent}}
</syntaxhighlight>** headercontent being the array element that contains the exported activity_header data
* It is recommended to transition towards the secondary/tertiary navigation hierarchy to reduce user cognitive load and with a logical separation of components
** Secondary navigation can be added to the templates by following the example https://github.com/moodle/moodle/blob/master/theme/boost/templates/columns2.mustache#L64-L68 This leverages the secondary navigation class to generate it's content.
* Flat navigation classes have been marked for deprecation. Themes that leverage the flat_navigation will need to make the following changes in their plugins in order to use it
** Account for the additional changes [[Moodle 4.0 developer update#Theme changes]]
** Indicate that they do not implement secondary navigation via the page's "set_secondary_navigation" function. It is recommended to set this within the root layout file e.g. columns2
** Initialise the flat navigation by introducing the following in the root layout file(if not existent)<syntaxhighlight lang="php">
$nav = $PAGE->flatnav;
$templatecontext['firstcollectionlabel'] = $nav->get_collectionlabel();
</syntaxhighlight>
* In order to reintroduce the settings cog in the templates, you can introduce the following: <syntaxhighlight>
<div id="region-main-settings-menu" class="d-print-none {{#hasblocks}}has-blocks{{/hasblocks}}">
<div> {{{ output.region_main_settings_menu }}} </div>
</div>
</syntaxhighlight>
===== Accessibility notes: =====
The jump to ‘maincontent’ div is now rendered within the activity header when within an activity context
== Component library ==
Each Moodle installation now ships with a Moodle User Interface (UI) Component library, a documentation system used to describe all the Bootstrap components and the custom Moodle components. The component Library is a helper tool for developers when creating user interfaces, a testing tool for theme developers and a documentation tool for core developers. The ultimate goal of having a component library is to encourage developers to create consistent user interfaces to improve Moodle’s overall user experience.

The library contains pages with documentation about User Interface components. It contains details on how to use the component, what variations are available and the JavaScript events / options are associated with the component.

When writing on these pages it is possible to render core mustache templates using some custom syntax like this:
<nowiki>{{< mustache template="core/notification_error" >}}</nowiki>
<nowiki>{{< /mustache >}}</nowiki>
You can also call core JavaScript or use HTML examples where the html code and the rendered result are visible in the Component Library. For more info visit the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-templates/ Moodle templates] page or the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-javascript/ Moodle JavaScript] page.

Each page in the library uses the current css from the default theme in your Moodle installation, if you have multiple themes installed and enabled the setting "Allow theme changes on url", the component library will have a theme selector option.

A hosted version of the Component Library can be found here. http://componentlibrary.moodle.com
=== Enabling the Component Library ===
Component library pages are written in the markdown language. These pages need to be compiled to HTML pages before the Component Library is visible. To compile the pages the server running Moodle needs to have the [[Javascript Modules#Install%20NVM%20and%20Node|JavaScript developer tools installed]] (nodeJs and Grunt)

If your server meets all requirements you can enable the library running
$ npm install
$ grunt componentlibrary
Further installation instructions can be found in the Component Library itself.
=== Documenting new UI Components ===
There are no set rules for adding new pages in the component library yet. These rules will need to be written and adopted in the integration process for Moodle code.

As a guideline for making this rules consideration are:

The component library is not about single use components, for example the Moodle grade book (a huge component with many custom features). Or about very common components like buttons, these are already covered by the Bootstrap section of the component library.

New features should be build keeping in mind the UI part needs to be customisable and if possible (and making sense) reusable. And example would be the new page drawers that we are introducing for the Navigation project. Or the custom primary navigation menus where overflowing items are pushed into a More section.
== Theme changes ==
=== Edit switch ===
On theme boost the “Turn editing on” and “Customise this page” buttons have been replaced by an edit switch in the top navbar. Theme Classic will keep using the old buttons. Child themes can choose to use the edit switch if the theme config.php is using this variable
$THEME->haseditswitch = true;
The languague menu, which used to be rendered in place of the custom menu has moved to the user dropdown when the user is logged in. If not logged in it will be placed next to the search / notification / messaging icon in the top navbar.
=== Login page ===
The login page has been redesigned and allows the admin to configure a background image for the login page only in the theme settings page. This change is available in both Boost and Classic. The login page still has all the features with an improved layout.
=== The page footer ===
In large screens, the page footer button is only visible when clicking a help button at the bottom right of the screen.
=== User initials as profile picture placeholder ===
If users do not upload a profile picture the user initials are displayed on a rounded gray background as a placeholder picture in the top navbar or any other page using a placeholder image. This change will be available in both Boost and Classic.

With the introduction of this placeholder image the full username will no longer be displayed in the top navbar.
=== Removal of back to top link ===
The "back to top" link will be removed for theme boost since the new course index reduced the dependence on page scrolling. Also, the new footer is positioned where this component used to be.
=== Styling changes ===
By default rounded edges will be used for UI components, for the page header and main content area the borders will be removed.
=== New layout page ===
Theme boost now uses the drawers.php layout for the course index and blocks.
== Question bank changes ==
There was a big project to deliver [[Question bank improvements for Moodle 4.0]] which added a new plugin type for adding features to the question banks, tracking the version history for each question as it is edited (question table has been split into <code>question</code>, <code>question_versions</code> and <code>question_bank_entries</code>), and tracking where each question is going to be used, with new tables <code>question_references</code> and <code>question_set_references</code>. This work was done in Epic MDL-70329 if you want to track down the details of any of the core changes.
=== Question type plugins ===
Amazingly, we (Safat and colleagues at Catalyst AU) managed to implement this without breaking most question type plugins.

However, the changes to the question bank, and the other Moodle 4.0 changes, probably broke the Behat tests for your plugin. To help with fixing that, MDL-74130 adds navigation to key question type pages (Preview and Edit for a question, and standard question bank pages like the bank itself, import and export) which should let you fix your test efficiently, and in a way that will work in all Moodle versions since 3.9.

The 'most' in the first paragraph here is becuase more advance question types may require more effort to fix. (For example qtype_combined which creates multi-part qusetions like the core qtype_multianswer; or qtype_pmatch or qtype_stack, which store additional data - questions tests - alongside the question itseld. How should that work with versionning?) But, if you have not done weird things like that, you are probably safe. If you find anything else that causes problems, please list it here.

The same thing should apply to question behaviour and question import/export format plugings: no significant changes required (probably just fixing the Behat tests because of the navigation changes).
=== New plugin type: qbank plugins ===
This is not something that will cause problems for people upgrading from 3.x. Rather, it is an exciting possibility you can explore once you have survived process of upgrading to 4.0. There is a whole new plugin type which you can create to add new features to the question bank. For example extra columns, new actions and bulk actions, and so on. See [[Question_bank_plugins]].
=== Activities that use questions ===
The probable bad news is if you have an activity module which uses questions. So far, the only activity which has been fixed is mod_quiz in Moodle core, so we don't yet have a good picture of what fixes will be necessary in other activities. Work is about to start fixing [https://github.com/studentquiz/moodle-mod_studentquiz mod_studentquiz], so watching that should give more clues. As we do that, we will try to update this section of this page. Other help writing the information required here would also be greatly appreciated.
== The course format system ==
Most of the logic for rendering and editing a course has been moved to a new subsystem called courseformat. The subsystem is located in "course/format" folder so it includes all the format plugins inside. The methods and modules which are distributed between the course and the course/format folders are now rearranged or refactored to be aligned with the current Moodle coding style.
=== Mandatory renderer in course formats ===
Now format plugins renderer is not optional anymore. Legacy formats without a renderer will get a deprecation message but it will continue working however, they should create a new renderer as soon as possible. The section-based format can do it by extending the provided core_courseformat\output\section_renderer class which includes all the necessary methods.
=== New format base class ===
The old base_format class (which all plugins extend) is now renamed as core_courseformat\base. The new class provides all the functionally of the previous base_format but it has been refactored to be used as a centralized source of truth for the course rendering. Legacy formats should extend the new class to avoid the deprecation message.

Now, the plugin format class provides information such as:
* If the page is displaying a single or multiple section
* Give access to other related format objects like the modinfo, the course record, maximum number of sections...
* If the format is compatible with features like course index, reactive components, ajax...
* Other format specifics like the page title, the default section name, default blocks...

The format instance is now the main object output components will use to render a course (see next section for more information).
=== New course output classes and mustache files ===
Traditionally, section-based course formats uses print_single_section_page and print_multiple_section_page to render the course content. In Moodle 4.0 most of the course rendering methods are migrated to output components and mustache templates. The old methods will get deprecation messages if they use the old renderer methods.

This is an example of a format rendering a course:<syntaxhighlight lang="php-brief">
// Get the course format instance.
$format = course_get_format($course);

// Get the specific format renderer.
$renderer = $format->get_renderer($PAGE);

if (!empty($displaysection)) {
// Setup the format instance to display a single section.
$format->set_section_number($displaysection);
}

// Create the ouptut instance and render it.
$outputclass = $format->get_output_classname('content');
$widget = new $outputclass($format);

echo $renderer->render($widget);
</syntaxhighlight>Format plugins are free to use its own output classes to render a course, or they could override the existing output classes by providing their own implementation. For example, the default output for "content" (as in the previous example) is "core_courseformat\output\local\|content", however, if the plugin has a "format_XXX\output\courseformat\content" class, the $format->class the get_output_class will return the overridden one.
Another important update on course rendering is that now all course structure is rendered using mustache templates instead of the original html_writer methods. Now themes are able to override the course format by providing alternative versions of the mustache files. All core course templates are located in "course/format/templates".

All course format output classes implements the new named_templatable interface, which allows the class to define its own template path using the "get_template_name" method. This new interface in combination with [[Templates#Blocks|mustache blocks]] allows the format plugins to provide alternative templates to render the course.

All the new output classes and a guide on how to migrate the current third-party plugins will be available soon.
=== Course editor javascript modules and frontend components ===
The majority of the javascript logic related to the course editing is replaced by AMD modules. Because this is a major change in the way courses are edited and rendered, by default format plugins will continue using the previous YUI modules for now. However, formats can start using the new libraries overriding the "$format->supports_components()" method.

Some Moodle 4.0 new features are only available for courses using the new editor library:
* Edit the course via the course index
* Creating sections without reloading the course page
* The new move section/activity modal
* Native browser drag&drop implementation
The new course editor uses a component-based reactive pattern to keep track of the course changes. The pattern highlights are:
* The main AMD module "core_crouseformat\courseeditor" maintains a data structure called state.
* Each UI element is implemented as a Component that observes the course state data and reacts to any data change
* When any reactive component needs to modify the course, it asks the course editor to execute a mutation. Mutations encapsulate all web services calls and alter the course state data.

The reactive library documentation, as well as the format plugin migration guide, will be available soon.
=== Other course related 4.0 changes ===
Two new web services have been added:
* core_courseformat_get_state: user by the new javascript course editor to get the current course state data (containing the list of sections, activities, and other course-related data)
* core_courseformat_update_course: to alter the current course content. Each call returns the parts of the course state altered by the action
== Behat changes ==
=== New steps ===
Moodle 4.0 introduces some new behat steps.

Sometimes you want to create a bulk number of activities. In that case you can use:<syntaxhighlight lang="gherkin">
:count :entitytype exist with the following data:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
Given 100 "mod_lti > tool types" exist with the following data:
|name |Test tool [count] |
|description |Example description [count] |
|baseurl |https://www.example.com/tool[count]|
</syntaxhighlight>

Dynamic (AJAX) tabs is a new feature contributed to Moodle 4.0 by the Workplace team (MDL-71943). You can use the following step to navigate between the tabs.<syntaxhighlight lang="gherkin">
And I click on the "tab title" dynamic tab
</syntaxhighlight>

To make sure that edit mode is (or is not) available on the current page, the following steps can be used.<syntaxhighlight lang="gherkin">
And edit mode should be available on the current page
And edit mode should not be available on the current page
</syntaxhighlight>

There are new aliases for the existing steps <code>I turn editing mode on</code> and <code>I turn editing mode off</code>.<syntaxhighlight lang="gherkin">
And I switch editing mode on
And I switch editing mode off
</syntaxhighlight>

In addition to the existing step to go to a course with editing mode on, we now have the following step to do the same but with editing mode being off.<syntaxhighlight lang="gherkin">
And I am on "course full name" course homepage with editing mode off
</syntaxhighlight>

The following step is similar to the old <code>following "link string" should download between "min bytes" and "max bytes" bytes</code> step, with more flexibility.<syntaxhighlight lang="gherkin">
And following "element string" "element type" in the "container string" "container type" should download between "min bytes" and "max bytes" bytes
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And following "Download" "link" in the "Starter" "table_row" should download between "0" and "5000" bytes
</syntaxhighlight>

The following step can be used to hover the mouse over the trigger area.<syntaxhighlight lang="gherkin">
And I hover over the "element string" "element type" in the "container string" "container type"
</syntaxhighlight>

The following step enables an installed plugin.<syntaxhighlight lang="gherkin">
And I enable "plugin name" "plugin type" plugin
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I enable "course_summary" "block" plugin
</syntaxhighlight>

The following is a special variation of 'I click on "<page name>" "link" in the "page" "region"'. It first checks to see if we are on the given page via the breadcrumb. If not we then attempt to follow the link name given.<syntaxhighlight lang="gherkin">
And I follow the breadcrumb "page name"
</syntaxhighlight>

You can use the following step to ensure a node is active in the navbar.<syntaxhighlight lang="gherkin">
And I should see "Node" is active in navigation
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I should see "My courses" is active in navigation
</syntaxhighlight>

The following step can be used to navigate to a given node in the primary navigation.<syntaxhighlight lang="gherkin">
And I select "Node" from primary navigation
</syntaxhighlight>

The following steps are to check whether an item exists in the user menu or not.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the user menu
And "item text" "selector type" should not exist in the user menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "Language" "link" should exist in the user menu
</syntaxhighlight>

The following steps are to check if a submenu of the user menu is shown, and if an item exists or does not exist in a given user submenu.<syntaxhighlight lang="gherkin">
And I should see "submenu name" user submenu
And "item text" "selector type" should exist in the "submenu name" user submenu
And "item text" "selector type" should not exist in the "submenu name" user submenu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I follow "Language" in the user menu
Then I should see "Language selector" user submenu
And "English &lrm;(en)&lrm;" "link" should exist in the "Language selector" user submenu
And "English (pirate) &lrm;(en_ar)&lrm;" "link" should not exist in the "Language selector" user submenu
</syntaxhighlight>

To add enrolment methods to courses you can use the following new step. The data that you provide in the next lines are used to fill the enrolment method form.<syntaxhighlight lang="gherkin">
And I add "enrolment method" in "course identifier" with:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I add "Self enrolment" enrolment method in "Course 1" with:
| Custom instance name | Test student enrolment |
| Enrolment key | moodle_rules |
| Use group enrolment keys | Yes |
</syntaxhighlight>

There are 3 new steps specific to the calendar component. These steps can be used to hover over a day in the mini-calendar or the full calendar.<syntaxhighlight lang="gherkin">
And I hover over day "day of month" of this month in the full calendar page
And I hover over day "day of month" of this month in the mini-calendar block
And I hover over today in the mini-calendar block
</syntaxhighlight>

Some new steps are added to question bank to be able to add comment to questions, verify the existence of a comment, and deleting comments form questions. Please note that the steps for adding comments only write the comment text in the comment field. You still need to click on the "Add comment" button to save the comment.<syntaxhighlight lang="gherkin">
And I add "comment text" comment to question
And I add "comment text" comment to question preview
And I delete "comment text" comment from question
And I delete "comment text" comment from question preview
And I should see "number of comments" on the comments column
And I click "number of comments" on the row on the comments column

</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "Question bank" in current page administration
And I should see "0" on the comments column
And I click "0" on the row on the comments column
And I add "test comment 01" comment to question
And I click on "Add comment" "button" in the ".modal-dialog" "css_element"
And I click on "Close" "button" in the ".modal-dialog" "css_element"
And I should see "1" on the comments column
And I click "1" on the row on the comments column
And I delete "test comment 01" comment from question
</syntaxhighlight>

Similar to the steps for comments, the following steps are to verify the number of a question's usage and to click on it in order to open the question usage modal.<syntaxhighlight lang="gherkin">
And I should see "usage count" on the usage column
And I click "usage count" on the usage column
</syntaxhighlight>

The following new steps are related to bulk actions in the question bank UI.<syntaxhighlight lang="gherkin">
And I click on question bulk action "action"
And I should see question bulk action "action"
And I should not see question bulk action "action"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I click on "First question" "checkbox"
And I click on "Second question" "checkbox"
And I click on "With selected" "button"
And I should see question bulk action "deleteselected"
And I click on question bulk action "deleteselected"
And I click on "Delete" "button" in the "Confirm" "dialogue"
</syntaxhighlight>

[https://docs.moodle.org/en/Report_builder Report builder] is a new feature contributed to Moodle 4.0 by the Workplace team. The following new step is added to Moodle 4.0 to select an action from the action menu in the list of custom reports table.<syntaxhighlight lang="gherkin">
And I press "action" action in the "report name" report row
</syntaxhighlight>

There's another step related to the report builder to set a column's aggregation in the report editor.<syntaxhighlight lang="gherkin">
And I set the "column title" column aggregation to "aggregation method"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I set the "First name" column aggregation to "Comma separated values"
</syntaxhighlight>

The following step needs to be used in scenarios that involve testing BigBlueButton. For this to work, you need to have a [https://github.com/moodlehq/bigbluebutton_mock BigBlueButton Mock API Server] and set <code>TEST_MOD_BIGBLUEBUTTONBN_MOCK_SERVER</code> to point to that in config.php.<syntaxhighlight lang="gherkin">
And a BigBlueButton mock server is configured
</syntaxhighlight>

The following step replicates receiving a callback from the BigBlueButton server indicating the recordings for meetings are ready for viewing.<syntaxhighlight lang="gherkin">
And the BigBlueButtonBN server has sent recording ready notifications
</syntaxhighlight>

The following steps are specific to the lesson activity. Note that in 4.0, some links (such as the "edit" and the "grade essays" links) are replaced by buttons, so you need to update your old steps with the new ones.<syntaxhighlight lang="gherkin">
And I edit the lesson
</syntaxhighlight>A new step is added to be used in lesson activities to edit them. This step navigates the user to the lesson edit page.
<syntaxhighlight lang="gherkin">
And I grade lesson essays
</syntaxhighlight>It's a new step to go to the "Grade essays" page of the lesson we are currently in.
<syntaxhighlight lang="gherkin">
And I select edit type "edit type"
</syntaxhighlight>Select the lesson edit type when we are in the the lesson's edit page. "edit type" can either be "Collapsed" or "Expanded".

The following new step can be used to navigate to the exports page in the course gradebook and select the specified export type from the grade exports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "export option" export page in the course gradebook
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "XML file" export page in the course gradebook
</syntaxhighlight>

Similarly, there's a new step to navigate to the imports page in the course gradebook and select the specified import type from the grade imports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "import option" import page in the course gradebook
</syntaxhighlight>
=== Boost steps ===
In addition to the steps listed in the previous section, there are also some Boost specific steps coming with Moodle 4.0. These steps only work in Boost or Boost child themes, so you need to make sure they are not used in scenarios that may be run by non-Boost themes.

The following step checks whether a node is active in the secondary navigation.<syntaxhighlight lang="gherkin">
And I should see :name is active in secondary navigation
</syntaxhighlight>

The Boost theme shows the language selector menu in the primary navigation when not logged in, and within the user menu when logged in. The following steps are to check if the primary navigation includes the language selector menu.<syntaxhighlight lang="gherkin">
And language selector menu should exist in the navbar
And language selector menu should not exist in the navbar
</syntaxhighlight>

And the following steps can be used to check whether an item exists in the language selector menu in the Boost theme.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the language selector menu
And "item text" "selector type" should not exist in the language selector menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "English &lrm;(en)&lrm;" "link" should exist in the language selector menu
</syntaxhighlight>
=== Modified steps ===
The step <code>I change the (window|viewport) size to "size"</code> now supports 2 new values for the size argument. The size argument now accepts <code>mobile</code> and <code>tablet</code> values in addition to <code>small</code>, <code>medium</code> and <code>large</code>.
=== Removed steps ===
Some behat steps are removed or replaced with new steps.

As a result of some design changes, hidden or restricted activities are no longer dimmed. Therefore the step<syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be dimmed
</syntaxhighlight>is now removed.
Depending on what you were using that step for, you may be able to use these steps:<syntaxhighlight lang="gherkin">
And "Label name" label should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And I should see "Activity or resource name"
And "Activity or resource name" "link" should not exist in the "region-main" "region"
</syntaxhighlight>
=== Other things to consider ===
To make behat tests more readable and easy to maintain, it is recommended to use the most direct steps to get what the test needs. It is highly recommended to use
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
instead of navigating to the activity via
I am on "Course" course homepage
I follow "Activity name"
Now that [https://docs.moodle.org/dev/Prototypes#Course_creation_improvements Course index] is integrated these behat steps
I am on "Course" course homepage
I follow "Activity name"
will fail using Boost theme.

The reason for it is that the drawer used in Boost is hiding the course index. So when the test is trying to follow an "Activity name" link, it finds two different links:
* one in the course index
* another one in the course main content.
But the first one, the one in the course index, is hidden by the drawer, and the test fails.

However the recommended behat steps
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
Old behat steps that may now fail can be updated to the new steps.
For example:
And I am on the "Test assignment name" "assign activity" page logged in as teacher1
instead of:
When I log in as "teacher1"
And I am on "Course" course homepage
And I follow "Test assignment name"
Or for settings, instead of:
<syntaxhighlight lang="gherkin">And I follow "Test choice name"
And I navigate to "Edit settings" in current page administration</syntaxhighlight>
Use:
<syntaxhighlight lang="gherkin">And I am on the "Test choice name" "choice activity editing" page</syntaxhighlight>

There are also similar stream-lined navigation steps for accessing question bank pages. See MDL-74130.
== Other ==
=== Core plugins review ===
A few plugins from core Moodle LMS which are no longer or hardly used have been removed and, if appropriate, added to the Moodle plugins directory.

More information about this project, the list of plugins to be removed and the process to follow for keeping them before upgrading to 4.0 can be found in the [[Core plugins review]] page.
=== Core blocks cleanup ===
In the "Add a block" menu, the list of blocks was really long. A few changes have been done to reduce this list.

More information about this project can be found in the [[Add a block cleanup]] page.
=== Site admin presets plugin ===
The third-party plugin [https://moodle.org/plugins/block_admin_presets Admin presets], created by David Monllaó and maintained by developers from [https://pimenko.com/ Pimenko] has been adapted and integrated into Moodle 4.0. It stores settings and plugins status (enabled/disabled) in what's called "presets" to let admins quickly switch between different configurations.

More information about this project can be found in the [[Site admin presets|Site admin presets plugin]] page.
=== JavaScript browser support changes ===
From Moodle 4.0, Internet Explorer is no longer supported. See MDL-73915 and MDLSITE-6109 for further information on this change.

This change means that changes built on 4.0 onwards (including the master branch) will be different to older versions of Moodle.

For plugin developers supporting multiple versions of Moodle using a single plugin version, the compiled javascript files are backwards compatible and will _work_ on all supported versions, however if you run the `grunt` command on multiple versions you will see unbuilt changes. Running grunt on all versions of Moodle is not necessary and this check can be safely disabled for Moodle versions 3.9 - 4.0, as long as only at least you run `grunt` against at least one version of Moodle.

If you need to support Internet Explorer and do not wish to fork your plugin for Moodle 4.0 onwards, then it is recommended that you run `grunt` on an older version of Moodle.
=== The course index element ===
The new course index feature can be themed using a set of scss variables. Use them to change the look and feel instead of adding custom css
/theme/boost/scss/moodle/courseindex.scss
With the introduction of the course index component, the previous and next links shown underneath each activity are no longer needed and they will be removed.
=== Activity icons ===
The icons used for activities have been redesigned and updated for all core moodle activities.

When viewing the new icons in a file manager, for example for the quiz activity, you will see a simple black monochrome icon with a transparent background.

On the course page, or in the activity chooser, the icon will display as a white icon on a coloured background. Styling of the icons on the coursepage is controlled by the css in theme/boost/scss/moodle/icons.scss.

The background colour for activity icons is set using a new variable in function [modname]_supports(). The quiz activity is of type assessment, so in function quiz_supports() there is a new line defining the purpose:
case FEATURE_MOD_PURPOSE: return MOD_PURPOSE_ASSESSMENT;
Available purposes are:
* MOD_PURPOSE_COMMUNICATION
* MOD_PURPOSE_ASSESSMENT
* MOD_PURPOSE_COLLABORATION
* MOD_PURPOSE_CONTENT
* MOD_PURPOSE_ADMINISTRATION
* MOD_PURPOSE_INTERFACE
The background colours linked to these purposes are set in theme/boost/scss/moodle/variables.scss
$activity-icon-colors: map-merge(
(
"administration": #5d63f6,
"assessment": #eb66a2,
"collaboration": #f7634d,
"communication": #11a676,
"content": #399be2,
"interface": #a378ff
),
$activity-icon-colors
);
If activity plugins do not define FEATURE_MOD_PURPOSE the activity icon will be rendered against a light grey background. There is no requirement to define the purpose of activity plugins, it will only affect the icon styling.

Plugins implementing the variable FEATURE_MOD_PURPOSE are only supported on Moodle 4.0 and newer.

Customising the activity icon can be done in an alternative way. For example using the styles.css in mod/[pluginname/styles.css

In the example below the activity plugin developer chooses to keep the coloured icon for the activity and render it as large as the coloured background on the core activities
.modicon_subcourse.activityiconcontainer {
background-color: transparent;
padding: 0;
}

.modicon_subcourse.activityiconcontainer img {
width: 50px;
height: 50px;
}
To customize all icon colours use this scss array and add it to the ‘Raw initial SCSS’ in the theme Boost advanced settings page. The complete array of icon background colours can be overridden using the ‘Raw initial SCSS’ in the theme settings page. The example below changes the colours of each activity type.
$activity-icon-colors: (
"administration": #5D63F6,
"assessment": #11A676,
"collaboration": #EB66A2,
"communication": #F7634D,
"content": #399BE2,
"interface": #A378FF
)
== I'm a developer, what do I need to know? ==
This section is a quick checklist of the areas in this document that you should consult when updating your plugin.
=== Modules ===
If you are a module developer (activity / resources) then you need to review the following updates and changes:
* If using settings, reformat to work with the secondary navigation. We have significantly changed the way that settings are shown. Settings added to the course and activity administration branch of the navigation are now by default shown in the secondary navigation. You will most likely find them in the more section of the secondary navigation. Please avoid creating settings in containers (a parent navigation node with children). These settings will still be shown, but this goes against the pattern that we are trying to establish for navigation around the site. If you have a lot of settings, consider creating a specific page to handle your additional settings.
** The order of the items in the secondary navigation may not be to your liking. This can be changed. See [[Moodle_4.0_developer_update#Changing_the_order_of_tabs|changing the order of tabs]]
* Update my behat tests to use new steps for site navigation. See [[Moodle_4.0_developer_update#Behat_changes|new behat steps]].
* Update my module to use the new activity_header API. See [[Moodle_4.0_developer_update#The_activity_header_class|the activity header]].
* Update my pages to make it work with the general format of the tertiary navigation. See [[Moodle_4.0_developer_update#Tertiary_navigation|the tertiary navigation]].
* Update my activity icon to use the API and set a purpose. See [[Moodle_4.0_developer_update#Activity_icons|activity icons]].
=== Themes ===
If you are a theme developer then you may want to consider the following:
* Take a look at the [[Moodle_4.0_developer_update#Navigation_changes|new navigation]] and decide if you want to incorporate this into your theme.
** A new layout ([[Moodle_4.0_developer_update#New_layout_page|drawers]])
** An [[Moodle_4.0_developer_update#Edit_switch|edit switch]]
** The [[Moodle_4.0_developer_update#The_course_index_element|course index]]
* Use of the flat nav
* New Site administration page and layout
* Course settings and how they are displayed
=== Course format ===
There have been a lot of changes made to the course format. Most in the process of moving the course format away from using the old rendering system and towards templates.
We recommend the following sections be read carefully:
# [[Moodle_4.0_developer_update#The_course_format_system|The course format]]. There have been a lot of deprecations and reading this section is critical in understanding the changes made.
# Consider moving the rendering of your content over to the [[Templates|template system]].
=== Other plugins ===
# Are you adding settings? See the [[Moodle_4.0_developer_update#Adding_items_to_the_navigation|secondary nav]] for adding items to this navigation bar.
# Have a look at [[Moodle_4.0_developer_update#Secondary_navigation|secondary]] and [[Moodle_4.0_developer_update#Tertiary_navigation|tertiary]] navigation changes in general if you have a plugin that has multiple pages to navigate around.
# Do you have behat tests? Check the new [[Moodle_4.0_developer_update#Behat_changes|behat changes]].

Moodle 4.0 developer update

2022-03-16T02:43:12Z

Abgreeve: Other plugins developer update

{{Moodle 4.0}}This page highlights the important changes that are coming in Moodle 4.0 for developers. Including how the UX improvements impact custom themes, relevant API changes, and what you can do as developer to prepare for the 4.0 release.
== Navigation changes ==
The core Navigation API has been left mostly untouched. The callbacks to all navigation callbacks remains unchanged and will be called as part of the regular 'navigation' and 'settingsnav' initialisation. Some new core classes have been created and exist within a new namespace 'core/navigation' and serves as conduit to rearrange, cherry-pick existing navigation nodes from the navigation/settingsnav trees and display within the respective navigation type. As such, it is highly recommended to provide unique keys for custom navigation nodes as this helps in the cherry-picking / rearranging process within the new classes.
=== Primary navigation ===
The primary navigation(the navbar) apart from the existing content will now display links to the Dashboard, My Courses, Site Admin and Course search, by default. You can still add items to the navbar via the 'custom menu' option. This will be displayed within the 'More' menu. We have transitioned the menus to be rendered via templates - refer user_menu.mustache. The lang menu has been moved to reside within the user menu.
==== Customising the primary navigation ====
Not yet implemented but we are looking at allowing the full addition and removal of any of the primary navigation tabs in the boost theme config file.
=== Secondary navigation ===
The main content area shows tabs for secondary navigation with a maximum of 5 items being rendered in this ‘more’ menu. A new UI component has been created to render menus like this. Files:
/lib/templates/moremenu.mustache

==== Adding items to the navigation ====
The secondary navigation pulls information mainly from the settings navigation node from each context. Any plugin that implements the existing navigation hooks will have their items added to the secondary navigation.
Existing navigation hooks:
* {module}_extend_navigation
* {local}_extend_navigation
* {report}_report_extend_navigation
* {plugin}_extend_navigation_course
* {plugin}_extend_navigation_category_settings

==== Changing the order of tabs ====
Apart from the previously mentioned functions, you can also create a custom secondary class as mentioned earlier. This will automatically be picked by getter and used to render the secondary nav within the activity. E.g. mod_assign/local/views/secondary. Note: This is currently only possible on an activity and block level.

=== Tertiary navigation ===
We've moved action buttons to the top of the page. We would encourage you to do the same.
If you have any buttons on an activity page that go to another page, or open a form (or similar), then we encourage you to move them from the body of your activity page to the top. All of the core activities have been updated to follow this pattern. Please take a look to see how you can format your activity in a similar fashion. There is no API here. You are welcome to create the buttons and display them as you wish in this top area.
=== New API functions ===
==== Page API ====
* Magic getters to fetch the primary and secondary navs and the primary output.
* The secondarynav magic getter also checks whether a custom secondary class has been defined within the module's local\views directory. Use this if you want to deviate from the standard secondary nav structure/order.

* set_secondary_nav - Force override the secondary navigation class

* has_secondary_navigation_setter - Sets the ‘_hassecondarynavigation’ to indicate whether a page should render the secondary navigation
==== Navigationlib ====
* set_show_in_secondary_navigation - whether or not a node should be displayed in the secondary nav. Accepts a single boolean argument
* set_force_into_more_menu- whether or not to force a node into the 'More' menu. Accepts a single boolean argument
==== The activity header class ====
There is a new activity header class that handles the display of information common to activities. 3rd party activities are not required to explicitly output this information as part of rendering individual pages.

The common information that are currently handled by the class are:
* title
* description
* completion information

As part of the update it was required that the initial information to be displayed by the class be toggable at a theme and layout level. Taking this into account the following theme level configurable exists:
* activityheaderconfig => An array that currently only enforces 'notitle' but can be expanded in the future NOTE: Boost has this set as true by default 'options'
The following layout level options that can be defined:
* noactivityheader - to remove the header in this specific layout.
* activityheader - An array that enforces the following options:
** notitle
** nocompletion
** nodescription
The class has a page level getter which you can use to fetch the current version of the class. The base state is initialised within the constructor with the completion information only fetched when data is exported for the template.

The class has setters for the following variables which can be leveraged to modify the header for a particular page in the format set_{variable_name}:
* hidecompletion
* description
* title
Alternately, bulk operations can also be done by passing the above variables in an array to 'set_attrs' which in turn calls the setters.<blockquote>'''Note: Any updates to the activityheader needs to be performed before the call to $OUTPUT->header'''</blockquote>
===== Theme updates: =====
In order for 3rd party themes to use the class they need to export the activity_header and include the following into their base template :<syntaxhighlight lang="html">
{{#headercontent}}
{{> core/activity_header}}
{{#headercontent}}
</syntaxhighlight>** headercontent being the array element that contains the exported activity_header data
===== Accessibility notes: =====
The jump to ‘maincontent’ div is now rendered within the activity header when within an activity context
== Component library ==
Each Moodle installation now ships with a Moodle User Interface (UI) Component library, a documentation system used to describe all the Bootstrap components and the custom Moodle components. The component Library is a helper tool for developers when creating user interfaces, a testing tool for theme developers and a documentation tool for core developers. The ultimate goal of having a component library is to encourage developers to create consistent user interfaces to improve Moodle’s overall user experience.

The library contains pages with documentation about User Interface components. It contains details on how to use the component, what variations are available and the JavaScript events / options are associated with the component.

When writing on these pages it is possible to render core mustache templates using some custom syntax like this:
<nowiki>{{< mustache template="core/notification_error" >}}</nowiki>
<nowiki>{{< /mustache >}}</nowiki>
You can also call core JavaScript or use HTML examples where the html code and the rendered result are visible in the Component Library. For more info visit the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-templates/ Moodle templates] page or the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-javascript/ Moodle JavaScript] page.

Each page in the library uses the current css from the default theme in your Moodle installation, if you have multiple themes installed and enabled the setting "Allow theme changes on url", the component library will have a theme selector option.

A hosted version of the Component Library can be found here. http://componentlibrary.moodle.com
=== Enabling the Component Library ===
Component library pages are written in the markdown language. These pages need to be compiled to HTML pages before the Component Library is visible. To compile the pages the server running Moodle needs to have the [[Javascript Modules#Install%20NVM%20and%20Node|JavaScript developer tools installed]] (nodeJs and Grunt)

If your server meets all requirements you can enable the library running
$ npm install
$ grunt componentlibrary
Further installation instructions can be found in the Component Library itself.
=== Documenting new UI Components ===
There are no set rules for adding new pages in the component library yet. These rules will need to be written and adopted in the integration process for Moodle code.

As a guideline for making this rules consideration are:

The component library is not about single use components, for example the Moodle grade book (a huge component with many custom features). Or about very common components like buttons, these are already covered by the Bootstrap section of the component library.

New features should be build keeping in mind the UI part needs to be customisable and if possible (and making sense) reusable. And example would be the new page drawers that we are introducing for the Navigation project. Or the custom primary navigation menus where overflowing items are pushed into a More section.
== Theme changes ==
=== Edit switch ===
On theme boost the “Turn editing on” and “Customise this page” buttons have been replaced by an edit switch in the top navbar. Theme Classic will keep using the old buttons. Child themes can choose to use the edit switch if the theme config.php is using this variable
$THEME->haseditswitch = true;
The languague menu, which used to be rendered in place of the custom menu has moved to the user dropdown when the user is logged in. If not logged in it will be placed next to the search / notification / messaging icon in the top navbar.
=== Login page ===
The login page has been redesigned and allows the admin to configure a background image for the login page only in the theme settings page. This change is available in both Boost and Classic. The login page still has all the features with an improved layout.
=== The page footer ===
In large screens, the page footer button is only visible when clicking a help button at the bottom right of the screen.
=== User initials as profile picture placeholder ===
If users do not upload a profile picture the user initials are displayed on a rounded gray background as a placeholder picture in the top navbar or any other page using a placeholder image. This change will be available in both Boost and Classic.

With the introduction of this placeholder image the full username will no longer be displayed in the top navbar.
=== Removal of back to top link ===
The "back to top" link will be removed for theme boost since the new course index reduced the dependence on page scrolling. Also, the new footer is positioned where this component used to be.
=== Styling changes ===
By default rounded edges will be used for UI components, for the page header and main content area the borders will be removed.
=== New layout page ===
Theme boost now uses the drawers.php layout for the course index and blocks.
== Question bank changes ==
There was a big project to deliver [[Question bank improvements for Moodle 4.0]] which added a new plugin type for adding features to the question banks, tracking the version history for each question as it is edited (question table has been split into <code>question</code>, <code>question_versions</code> and <code>question_bank_entries</code>), and tracking where each question is going to be used, with new tables <code>question_references</code> and <code>question_set_references</code>. This work was done in Epic MDL-70329 if you want to track down the details of any of the core changes.
=== Question type plugins ===
Amazingly, we (Safat and colleagues at Catalyst AU) managed to implement this without breaking most question type plugins.

However, the changes to the question bank, and the other Moodle 4.0 changes, probably broke the Behat tests for your plugin. To help with fixing that, MDL-74130 adds navigation to key question type pages (Preview and Edit for a question, and standard question bank pages like the bank itself, import and export) which should let you fix your test efficiently, and in a way that will work in all Moodle versions since 3.9.

The 'most' in the first paragraph here is becuase more advance question types may require more effort to fix. (For example qtype_combined which creates multi-part qusetions like the core qtype_multianswer; or qtype_pmatch or qtype_stack, which store additional data - questions tests - alongside the question itseld. How should that work with versionning?) But, if you have not done weird things like that, you are probably safe. If you find anything else that causes problems, please list it here.

The same thing should apply to question behaviour and question import/export format plugings: no significant changes required (probably just fixing the Behat tests because of the navigation changes).
=== New plugin type: qbank plugins ===
This is not something that will cause problems for people upgrading from 3.x. Rather, it is an exciting possibility you can explore once you have survived process of upgrading to 4.0. There is a whole new plugin type which you can create to add new features to the question bank. For example extra columns, new actions and bulk actions, and so on. See [[Question_bank_plugins]].
=== Activities that use questions ===
The probable bad news is if you have an activity module which uses questions. So far, the only activity which has been fixed is mod_quiz in Moodle core, so we don't yet have a good picture of what fixes will be necessary in other activities. Work is about to start fixing [https://github.com/studentquiz/moodle-mod_studentquiz mod_studentquiz], so watching that should give more clues. As we do that, we will try to update this section of this page. Other help writing the information required here would also be greatly appreciated.
== The course format system ==
Most of the logic for rendering and editing a course has been moved to a new subsystem called courseformat. The subsystem is located in "course/format" folder so it includes all the format plugins inside. The methods and modules which are distributed between the course and the course/format folders are now rearranged or refactored to be aligned with the current Moodle coding style.
=== Mandatory renderer in course formats ===
Now format plugins renderer is not optional anymore. Legacy formats without a renderer will get a deprecation message but it will continue working however, they should create a new renderer as soon as possible. The section-based format can do it by extending the provided core_courseformat\output\section_renderer class which includes all the necessary methods.
=== New format base class ===
The old base_format class (which all plugins extend) is now renamed as core_courseformat\base. The new class provides all the functionally of the previous base_format but it has been refactored to be used as a centralized source of truth for the course rendering. Legacy formats should extend the new class to avoid the deprecation message.

Now, the plugin format class provides information such as:
* If the page is displaying a single or multiple section
* Give access to other related format objects like the modinfo, the course record, maximum number of sections...
* If the format is compatible with features like course index, reactive components, ajax...
* Other format specifics like the page title, the default section name, default blocks...

The format instance is now the main object output components will use to render a course (see next section for more information).
=== New course output classes and mustache files ===
Traditionally, section-based course formats uses print_single_section_page and print_multiple_section_page to render the course content. In Moodle 4.0 most of the course rendering methods are migrated to output components and mustache templates. The old methods will get deprecation messages if they use the old renderer methods.

This is an example of a format rendering a course:<syntaxhighlight lang="php-brief">
// Get the course format instance.
$format = course_get_format($course);

// Get the specific format renderer.
$renderer = $format->get_renderer($PAGE);

if (!empty($displaysection)) {
// Setup the format instance to display a single section.
$format->set_section_number($displaysection);
}

// Create the ouptut instance and render it.
$outputclass = $format->get_output_classname('content');
$widget = new $outputclass($format);

echo $renderer->render($widget);
</syntaxhighlight>Format plugins are free to use its own output classes to render a course, or they could override the existing output classes by providing their own implementation. For example, the default output for "content" (as in the previous example) is "core_courseformat\output\local\|content", however, if the plugin has a "format_XXX\output\courseformat\content" class, the $format->class the get_output_class will return the overridden one.
Another important update on course rendering is that now all course structure is rendered using mustache templates instead of the original html_writer methods. Now themes are able to override the course format by providing alternative versions of the mustache files. All core course templates are located in "course/format/templates".

All the new output classes and a guide on how to migrate the current third-party plugins will be available soon.
=== Course editor javascript modules and frontend components ===
The majority of the javascript logic related to the course editing is replaced by AMD modules. Because this is a major change in the way courses are edited and rendered, by default format plugins will continue using the previous YUI modules for now. However, formats can start using the new libraries overriding the "$format->supports_components()" method.

Some Moodle 4.0 new features are only available for courses using the new editor library:
* Edit the course via the course index
* Creating sections without reloading the course page
* The new move section/activity modal
* Native browser drag&drop implementation
The new course editor uses a component-based reactive pattern to keep track of the course changes. The pattern highlights are:
* The main AMD module "core_crouseformat\courseeditor" maintains a data structure called state.
* Each UI element is implemented as a Component that observes the course state data and reacts to any data change
* When any reactive component needs to modify the course, it asks the course editor to execute a mutation. Mutations encapsulate all web services calls and alter the course state data.

The reactive library documentation, as well as the format plugin migration guide, will be available soon.
=== Other course related 4.0 changes ===
Two new web services have been added:
* core_courseformat_get_state: user by the new javascript course editor to get the current course state data (containing the list of sections, activities, and other course-related data)
* core_courseformat_update_course: to alter the current course content. Each call returns the parts of the course state altered by the action
== Behat changes ==
=== New steps ===
Moodle 4.0 introduces some new behat steps.

Sometimes you want to create a bulk number of activities. In that case you can use:<syntaxhighlight lang="gherkin">
:count :entitytype exist with the following data:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
Given 100 "mod_lti > tool types" exist with the following data:
|name |Test tool [count] |
|description |Example description [count] |
|baseurl |https://www.example.com/tool[count]|
</syntaxhighlight>

Dynamic (AJAX) tabs is a new feature contributed to Moodle 4.0 by the Workplace team (MDL-71943). You can use the following step to navigate between the tabs.<syntaxhighlight lang="gherkin">
And I click on the "tab title" dynamic tab
</syntaxhighlight>

To make sure that edit mode is (or is not) available on the current page, the following steps can be used.<syntaxhighlight lang="gherkin">
And edit mode should be available on the current page
And edit mode should not be available on the current page
</syntaxhighlight>

There are new aliases for the existing steps <code>I turn editing mode on</code> and <code>I turn editing mode off</code>.<syntaxhighlight lang="gherkin">
And I switch editing mode on
And I switch editing mode off
</syntaxhighlight>

In addition to the existing step to go to a course with editing mode on, we now have the following step to do the same but with editing mode being off.<syntaxhighlight lang="gherkin">
And I am on "course full name" course homepage with editing mode off
</syntaxhighlight>

The following step is similar to the old <code>following "link string" should download between "min bytes" and "max bytes" bytes</code> step, with more flexibility.<syntaxhighlight lang="gherkin">
And following "element string" "element type" in the "container string" "container type" should download between "min bytes" and "max bytes" bytes
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And following "Download" "link" in the "Starter" "table_row" should download between "0" and "5000" bytes
</syntaxhighlight>

The following step can be used to hover the mouse over the trigger area.<syntaxhighlight lang="gherkin">
And I hover over the "element string" "element type" in the "container string" "container type"
</syntaxhighlight>

The following step enables an installed plugin.<syntaxhighlight lang="gherkin">
And I enable "plugin name" "plugin type" plugin
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I enable "course_summary" "block" plugin
</syntaxhighlight>

The following is a special variation of 'I click on "<page name>" "link" in the "page" "region"'. It first checks to see if we are on the given page via the breadcrumb. If not we then attempt to follow the link name given.<syntaxhighlight lang="gherkin">
And I follow the breadcrumb "page name"
</syntaxhighlight>

You can use the following step to ensure a node is active in the navbar.<syntaxhighlight lang="gherkin">
And I should see "Node" is active in navigation
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I should see "My courses" is active in navigation
</syntaxhighlight>

The following step can be used to navigate to a given node in the primary navigation.<syntaxhighlight lang="gherkin">
And I select "Node" from primary navigation
</syntaxhighlight>

The following steps are to check whether an item exists in the user menu or not.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the user menu
And "item text" "selector type" should not exist in the user menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "Language" "link" should exist in the user menu
</syntaxhighlight>

The following steps are to check if a submenu of the user menu is shown, and if an item exists or does not exist in a given user submenu.<syntaxhighlight lang="gherkin">
And I should see "submenu name" user submenu
And "item text" "selector type" should exist in the "submenu name" user submenu
And "item text" "selector type" should not exist in the "submenu name" user submenu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I follow "Language" in the user menu
Then I should see "Language selector" user submenu
And "English &lrm;(en)&lrm;" "link" should exist in the "Language selector" user submenu
And "English (pirate) &lrm;(en_ar)&lrm;" "link" should not exist in the "Language selector" user submenu
</syntaxhighlight>

To add enrolment methods to courses you can use the following new step. The data that you provide in the next lines are used to fill the enrolment method form.<syntaxhighlight lang="gherkin">
And I add "enrolment method" in "course identifier" with:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I add "Self enrolment" enrolment method in "Course 1" with:
| Custom instance name | Test student enrolment |
| Enrolment key | moodle_rules |
| Use group enrolment keys | Yes |
</syntaxhighlight>

There are 3 new steps specific to the calendar component. These steps can be used to hover over a day in the mini-calendar or the full calendar.<syntaxhighlight lang="gherkin">
And I hover over day "day of month" of this month in the full calendar page
And I hover over day "day of month" of this month in the mini-calendar block
And I hover over today in the mini-calendar block
</syntaxhighlight>

Some new steps are added to question bank to be able to add comment to questions, verify the existence of a comment, and deleting comments form questions. Please note that the steps for adding comments only write the comment text in the comment field. You still need to click on the "Add comment" button to save the comment.<syntaxhighlight lang="gherkin">
And I add "comment text" comment to question
And I add "comment text" comment to question preview
And I delete "comment text" comment from question
And I delete "comment text" comment from question preview
And I should see "number of comments" on the comments column
And I click "number of comments" on the row on the comments column

</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "Question bank" in current page administration
And I should see "0" on the comments column
And I click "0" on the row on the comments column
And I add "test comment 01" comment to question
And I click on "Add comment" "button" in the ".modal-dialog" "css_element"
And I click on "Close" "button" in the ".modal-dialog" "css_element"
And I should see "1" on the comments column
And I click "1" on the row on the comments column
And I delete "test comment 01" comment from question
</syntaxhighlight>

Similar to the steps for comments, the following steps are to verify the number of a question's usage and to click on it in order to open the question usage modal.<syntaxhighlight lang="gherkin">
And I should see "usage count" on the usage column
And I click "usage count" on the usage column
</syntaxhighlight>

The following new steps are related to bulk actions in the question bank UI.<syntaxhighlight lang="gherkin">
And I click on question bulk action "action"
And I should see question bulk action "action"
And I should not see question bulk action "action"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I click on "First question" "checkbox"
And I click on "Second question" "checkbox"
And I click on "With selected" "button"
And I should see question bulk action "deleteselected"
And I click on question bulk action "deleteselected"
And I click on "Delete" "button" in the "Confirm" "dialogue"
</syntaxhighlight>

[https://docs.moodle.org/en/Report_builder Report builder] is a new feature contributed to Moodle 4.0 by the Workplace team. The following new step is added to Moodle 4.0 to select an action from the action menu in the list of custom reports table.<syntaxhighlight lang="gherkin">
And I press "action" action in the "report name" report row
</syntaxhighlight>

There's another step related to the report builder to set a column's aggregation in the report editor.<syntaxhighlight lang="gherkin">
And I set the "column title" column aggregation to "aggregation method"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I set the "First name" column aggregation to "Comma separated values"
</syntaxhighlight>

The following step needs to be used in scenarios that involve testing BigBlueButton. For this to work, you need to have a [https://github.com/moodlehq/bigbluebutton_mock BigBlueButton Mock API Server] and set <code>TEST_MOD_BIGBLUEBUTTONBN_MOCK_SERVER</code> to point to that in config.php.<syntaxhighlight lang="gherkin">
And a BigBlueButton mock server is configured
</syntaxhighlight>

The following step replicates receiving a callback from the BigBlueButton server indicating the recordings for meetings are ready for viewing.<syntaxhighlight lang="gherkin">
And the BigBlueButtonBN server has sent recording ready notifications
</syntaxhighlight>

The following steps are specific to the lesson activity. Note that in 4.0, some links (such as the "edit" and the "grade essays" links) are replaced by buttons, so you need to update your old steps with the new ones.<syntaxhighlight lang="gherkin">
And I edit the lesson
</syntaxhighlight>A new step is added to be used in lesson activities to edit them. This step navigates the user to the lesson edit page.
<syntaxhighlight lang="gherkin">
And I grade lesson essays
</syntaxhighlight>It's a new step to go to the "Grade essays" page of the lesson we are currently in.
<syntaxhighlight lang="gherkin">
And I select edit type "edit type"
</syntaxhighlight>Select the lesson edit type when we are in the the lesson's edit page. "edit type" can either be "Collapsed" or "Expanded".

The following new step can be used to navigate to the exports page in the course gradebook and select the specified export type from the grade exports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "export option" export page in the course gradebook
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "XML file" export page in the course gradebook
</syntaxhighlight>

Similarly, there's a new step to navigate to the imports page in the course gradebook and select the specified import type from the grade imports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "import option" import page in the course gradebook
</syntaxhighlight>
=== Boost steps ===
In addition to the steps listed in the previous section, there are also some Boost specific steps coming with Moodle 4.0. These steps only work in Boost or Boost child themes, so you need to make sure they are not used in scenarios that may be run by non-Boost themes.

The following step checks whether a node is active in the secondary navigation.<syntaxhighlight lang="gherkin">
And I should see :name is active in secondary navigation
</syntaxhighlight>

The Boost theme shows the language selector menu in the primary navigation when not logged in, and within the user menu when logged in. The following steps are to check if the primary navigation includes the language selector menu.<syntaxhighlight lang="gherkin">
And language selector menu should exist in the navbar
And language selector menu should not exist in the navbar
</syntaxhighlight>

And the following steps can be used to check whether an item exists in the language selector menu in the Boost theme.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the language selector menu
And "item text" "selector type" should not exist in the language selector menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "English &lrm;(en)&lrm;" "link" should exist in the language selector menu
</syntaxhighlight>
=== Modified steps ===
The step <code>I change the (window|viewport) size to "size"</code> now supports 2 new values for the size argument. The size argument now accepts <code>mobile</code> and <code>tablet</code> values in addition to <code>small</code>, <code>medium</code> and <code>large</code>.

=== Removed steps ===
Some behat steps are removed or replaced with new steps.

As a result of some design changes, hidden or restricted activities are no longer dimmed. Therefore the step<syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be dimmed
</syntaxhighlight>is now removed.
Depending on what you were using that step for, you may be able to use these steps:<syntaxhighlight lang="gherkin">
And "Label name" label should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And I should see "Activity or resource name"
And "Activity or resource name" "link" should not exist in the "region-main" "region"
</syntaxhighlight>
=== Other things to consider ===
To make behat tests more readable and easy to maintain, it is recommended to use the most direct steps to get what the test needs. It is highly recommended to use
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
instead of navigating to the activity via
I am on "Course" course homepage
I follow "Activity name"
Now that [https://docs.moodle.org/dev/Prototypes#Course_creation_improvements Course index] is integrated these behat steps
I am on "Course" course homepage
I follow "Activity name"
will fail using Boost theme.

The reason for it is that the drawer used in Boost is hiding the course index. So when the test is trying to follow an "Activity name" link, it finds two different links:
* one in the course index
* another one in the course main content.
But the first one, the one in the course index, is hidden by the drawer, and the test fails.

However the recommended behat steps
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
Old behat steps that may now fail can be updated to the new steps.
For example:
And I am on the "Test assignment name" "assign activity" page logged in as teacher1
instead of:
When I log in as "teacher1"
And I am on "Course" course homepage
And I follow "Test assignment name"

Or for settings, instead of:
<syntaxhighlight lang="gherkin">And I follow "Test choice name"
And I navigate to "Edit settings" in current page administration</syntaxhighlight>
Use:
<syntaxhighlight lang="gherkin">And I am on the "Test choice name" "choice activity editing" page</syntaxhighlight>

There are also similar stream-lined navigation steps for accessing question bank pages. See MDL-74130.

== Other ==
=== Core plugins review ===
A few plugins from core Moodle LMS which are no longer or hardly used have been removed and, if appropriate, added to the Moodle plugins directory.

More information about this project, the list of plugins to be removed and the process to follow for keeping them before upgrading to 4.0 can be found in the [[Core plugins review]] page.
=== Site admin presets plugin ===
The third-party plugin [https://moodle.org/plugins/block_admin_presets Admin presets], created by David Monllaó and maintained by developers from [https://pimenko.com/ Pimenko] has been adapted and integrated into Moodle 4.0. It stores settings and plugins status (enabled/disabled) in what's called "presets" to let admins quickly switch between different configurations.

More information about this project can be found in the [[Site admin presets|Site admin presets plugin]] page.
=== JavaScript browser support changes ===
From Moodle 4.0, Internet Explorer is no longer supported. See MDL-73915 and MDLSITE-6109 for further information on this change.

This change means that changes built on 4.0 onwards (including the master branch) will be different to older versions of Moodle.

For plugin developers supporting multiple versions of Moodle using a single plugin version, the compiled javascript files are backwards compatible and will _work_ on all supported versions, however if you run the `grunt` command on multiple versions you will see unbuilt changes. Running grunt on all versions of Moodle is not necessary and this check can be safely disabled for Moodle versions 3.9 - 4.0, as long as only at least you run `grunt` against at least one version of Moodle.

If you need to support Internet Explorer and do not wish to fork your plugin for Moodle 4.0 onwards, then it is recommended that you run `grunt` on an older version of Moodle.
=== The course index element ===
The new course index feature can be themed using a set of scss variables. Use them to change the look and feel instead of adding custom css
/theme/boost/scss/moodle/courseindex.scss
With the introduction of the course index component, the previous and next links shown underneath each activity are no longer needed and they will be removed.
=== Activity icons ===
The icons used for activities have been redesigned and updated for all core moodle activities.

When viewing the new icons in a file manager, for example for the quiz activity, you will see a simple black monochrome icon with a transparent background.

On the course page, or in the activity chooser, the icon will display as a white icon on a coloured background. Styling of the icons on the coursepage is controlled by the css in theme/boost/scss/moodle/icons.scss.

The background colour for activity icons is set using a new variable in function [modname]_supports(). The quiz activity is of type assessment, so in function quiz_supports() there is a new line defining the purpose:
case FEATURE_MOD_PURPOSE: return MOD_PURPOSE_ASSESSMENT;
Available purposes are:
* MOD_PURPOSE_COMMUNICATION
* MOD_PURPOSE_ASSESSMENT
* MOD_PURPOSE_COLLABORATION
* MOD_PURPOSE_CONTENT
* MOD_PURPOSE_ADMINISTRATION
* MOD_PURPOSE_INTERFACE
The background colours linked to these purposes are set in theme/boost/scss/moodle/variables.scss
$activity-icon-colors: map-merge(
(
"administration": #5d63f6,
"assessment": #eb66a2,
"collaboration": #f7634d,
"communication": #11a676,
"content": #399be2,
"interface": #a378ff
),
$activity-icon-colors
);
If activity plugins do not define FEATURE_MOD_PURPOSE the activity icon will be rendered against a light grey background. There is no requirement to define the purpose of activity plugins, it will only affect the icon styling.

Plugins implementing the variable FEATURE_MOD_PURPOSE are only supported on Moodle 4.0 and newer.

Customising the activity icon can be done in an alternative way. For example using the styles.css in mod/[pluginname/styles.css

In the example below the activity plugin developer chooses to keep the coloured icon for the activity and render it as large as the coloured background on the core activities
.modicon_subcourse.activityiconcontainer {
background-color: transparent;
padding: 0;
}

.modicon_subcourse.activityiconcontainer img {
width: 50px;
height: 50px;
}
To customize all icon colours use this scss array and add it to the ‘Raw initial SCSS’ in the theme Boost advanced settings page. The complete array of icon background colours can be overridden using the ‘Raw initial SCSS’ in the theme settings page. The example below changes the colours of each activity type.
$activity-icon-colors: (
"administration": #5D63F6,
"assessment": #11A676,
"collaboration": #EB66A2,
"communication": #F7634D,
"content": #399BE2,
"interface": #A378FF
)
== I'm a developer, what do I need to know? ==
This section is a quick checklist of the areas in this document that you should consult when updating your plugin.
=== Modules ===
If you are a module developer (activity / resources) then you need to review the following updates and changes:
* If using settings, reformat to work with the secondary navigation. We have significantly changed the way that settings are shown. Settings added to the course and activity administration branch of the navigation are now by default shown in the secondary navigation. You will most likely find them in the more section of the secondary navigation. Please avoid creating settings in containers (a parent navigation node with children). These settings will still be shown, but this goes against the pattern that we are trying to establish for navigation around the site. If you have a lot of settings, consider creating a specific page to handle your additional settings.
** The order of the items in the secondary navigation may not be to your liking. This can be changed. See [[Moodle_4.0_developer_update#Changing_the_order_of_tabs|changing the order of tabs]]
* Update my behat tests to use new steps for site navigation. See [[Moodle_4.0_developer_update#Behat_changes|new behat steps]].
* Update my module to use the new activity_header API. See [[Moodle_4.0_developer_update#The_activity_header_class|the activity header]].
* Update my pages to make it work with the general format of the tertiary navigation. See [[Moodle_4.0_developer_update#Tertiary_navigation|the tertiary navigation]].
* Update my activity icon to use the API and set a purpose. See [[Moodle_4.0_developer_update#Activity_icons|activity icons]].
=== Themes ===
If you are a theme developer then you may want to consider the following:
* Take a look at the [[Moodle_4.0_developer_update#Navigation_changes|new navigation]] and decide if you want to incorporate this into your theme.
** A new layout ([[Moodle_4.0_developer_update#New_layout_page|drawers]])
** An [[Moodle_4.0_developer_update#Edit_switch|edit switch]]
** The [[Moodle_4.0_developer_update#The_course_index_element|course index]]
* Use of the flat nav
* New Site administration page and layout
* Course settings and how they are displayed

=== Course format ===
There have been a lot of changes made to the course format. Most in the process of moving the course format away from using the old rendering system and towards templates.
We recommend the following sections be read carefully:
# [[Moodle_4.0_developer_update#The_course_format_system|The course format]]. There have been a lot of deprecations and reading this section is critical in understanding the changes made.
# Consider moving the rendering of your content over to the [[Templates|template system]].

=== Other plugins ===
# Are you adding settings? See the [[Moodle_4.0_developer_update#Adding_items_to_the_navigation|secondary nav]] for adding items to this navigation bar.
# Have a look at [[Moodle_4.0_developer_update#Secondary_navigation|secondary]] and [[Moodle_4.0_developer_update#Tertiary_navigation|tertiary]] navigation changes in general if you have a plugin that has multiple pages to navigate around.
# Do you have behat tests? Check the new [[Moodle_4.0_developer_update#Behat_changes|behat changes]].

Moodle 4.0 developer update

2022-03-16T02:40:16Z

Abgreeve: /* Secondary navigation -- adding items to the navigation */

Moodle 4.0 developer update

2022-03-16T02:27:11Z

Abgreeve: Added the course format section for plugin developers

{{Moodle 4.0}}This page highlights the important changes that are coming in Moodle 4.0 for developers. Including how the UX improvements impact custom themes, relevant API changes, and what you can do as developer to prepare for the 4.0 release.
== Navigation changes ==
The core Navigation API has been left mostly untouched. The callbacks to all navigation callbacks remains unchanged and will be called as part of the regular 'navigation' and 'settingsnav' initialisation. Some new core classes have been created and exist within a new namespace 'core/navigation' and serves as conduit to rearrange, cherry-pick existing navigation nodes from the navigation/settingsnav trees and display within the respective navigation type. As such, it is highly recommended to provide unique keys for custom navigation nodes as this helps in the cherry-picking / rearranging process within the new classes.
=== Primary navigation ===
The primary navigation(the navbar) apart from the existing content will now display links to the Dashboard, My Courses, Site Admin and Course search, by default. You can still add items to the navbar via the 'custom menu' option. This will be displayed within the 'More' menu. We have transitioned the menus to be rendered via templates - refer user_menu.mustache. The lang menu has been moved to reside within the user menu.
==== Customising the primary navigation ====
Not yet implemented but we are looking at allowing the full addition and removal of any of the primary navigation tabs in the boost theme config file.
=== Secondary navigation ===
The main content area shows tabs for secondary navigation with a maximum of 5 items being rendered in this ‘more’ menu. A new UI component has been created to render menus like this. Files:
/lib/templates/moremenu.mustache
==== Changing the order of tabs ====
Apart from the previously mentioned functions, you can also create a custom secondary class as mentioned earlier. This will automatically be picked by getter and used to render the secondary nav within the activity. E.g. mod_assign/local/views/secondary. Note: This is currently only possible on an activity and block level.
=== Tertiary navigation ===
We've moved action buttons to the top of the page. We would encourage you to do the same.
If you have any buttons on an activity page that go to another page, or open a form (or similar), then we encourage you to move them from the body of your activity page to the top. All of the core activities have been updated to follow this pattern. Please take a look to see how you can format your activity in a similar fashion. There is no API here. You are welcome to create the buttons and display them as you wish in this top area.
=== New API functions ===
==== Page API ====
* Magic getters to fetch the primary and secondary navs and the primary output.
* The secondarynav magic getter also checks whether a custom secondary class has been defined within the module's local\views directory. Use this if you want to deviate from the standard secondary nav structure/order.

* set_secondary_nav - Force override the secondary navigation class

* has_secondary_navigation_setter - Sets the ‘_hassecondarynavigation’ to indicate whether a page should render the secondary navigation
==== Navigationlib ====
* set_show_in_secondary_navigation - whether or not a node should be displayed in the secondary nav. Accepts a single boolean argument
* set_force_into_more_menu- whether or not to force a node into the 'More' menu. Accepts a single boolean argument
==== The activity header class ====
There is a new activity header class that handles the display of information common to activities. 3rd party activities are not required to explicitly output this information as part of rendering individual pages.

The common information that are currently handled by the class are:
* title
* description
* completion information

As part of the update it was required that the initial information to be displayed by the class be toggable at a theme and layout level. Taking this into account the following theme level configurable exists:
* activityheaderconfig => An array that currently only enforces 'notitle' but can be expanded in the future NOTE: Boost has this set as true by default 'options'
The following layout level options that can be defined:
* noactivityheader - to remove the header in this specific layout.
* activityheader - An array that enforces the following options:
** notitle
** nocompletion
** nodescription
The class has a page level getter which you can use to fetch the current version of the class. The base state is initialised within the constructor with the completion information only fetched when data is exported for the template.

The class has setters for the following variables which can be leveraged to modify the header for a particular page in the format set_{variable_name}:
* hidecompletion
* description
* title
Alternately, bulk operations can also be done by passing the above variables in an array to 'set_attrs' which in turn calls the setters.<blockquote>'''Note: Any updates to the activityheader needs to be performed before the call to $OUTPUT->header'''</blockquote>
===== Theme updates: =====
In order for 3rd party themes to use the class they need to export the activity_header and include the following into their base template :<syntaxhighlight lang="html">
{{#headercontent}}
{{> core/activity_header}}
{{#headercontent}}
</syntaxhighlight>** headercontent being the array element that contains the exported activity_header data
===== Accessibility notes: =====
The jump to ‘maincontent’ div is now rendered within the activity header when within an activity context
== Component library ==
Each Moodle installation now ships with a Moodle User Interface (UI) Component library, a documentation system used to describe all the Bootstrap components and the custom Moodle components. The component Library is a helper tool for developers when creating user interfaces, a testing tool for theme developers and a documentation tool for core developers. The ultimate goal of having a component library is to encourage developers to create consistent user interfaces to improve Moodle’s overall user experience.

The library contains pages with documentation about User Interface components. It contains details on how to use the component, what variations are available and the JavaScript events / options are associated with the component.

When writing on these pages it is possible to render core mustache templates using some custom syntax like this:
<nowiki>{{< mustache template="core/notification_error" >}}</nowiki>
<nowiki>{{< /mustache >}}</nowiki>
You can also call core JavaScript or use HTML examples where the html code and the rendered result are visible in the Component Library. For more info visit the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-templates/ Moodle templates] page or the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-javascript/ Moodle JavaScript] page.

Each page in the library uses the current css from the default theme in your Moodle installation, if you have multiple themes installed and enabled the setting "Allow theme changes on url", the component library will have a theme selector option.

A hosted version of the Component Library can be found here. http://componentlibrary.moodle.com
=== Enabling the Component Library ===
Component library pages are written in the markdown language. These pages need to be compiled to HTML pages before the Component Library is visible. To compile the pages the server running Moodle needs to have the [[Javascript Modules#Install%20NVM%20and%20Node|JavaScript developer tools installed]] (nodeJs and Grunt)

If your server meets all requirements you can enable the library running
$ npm install
$ grunt componentlibrary
Further installation instructions can be found in the Component Library itself.
=== Documenting new UI Components ===
There are no set rules for adding new pages in the component library yet. These rules will need to be written and adopted in the integration process for Moodle code.

As a guideline for making this rules consideration are:

The component library is not about single use components, for example the Moodle grade book (a huge component with many custom features). Or about very common components like buttons, these are already covered by the Bootstrap section of the component library.

New features should be build keeping in mind the UI part needs to be customisable and if possible (and making sense) reusable. And example would be the new page drawers that we are introducing for the Navigation project. Or the custom primary navigation menus where overflowing items are pushed into a More section.
== Theme changes ==
=== Edit switch ===
On theme boost the “Turn editing on” and “Customise this page” buttons have been replaced by an edit switch in the top navbar. Theme Classic will keep using the old buttons. Child themes can choose to use the edit switch if the theme config.php is using this variable
$THEME->haseditswitch = true;
The languague menu, which used to be rendered in place of the custom menu has moved to the user dropdown when the user is logged in. If not logged in it will be placed next to the search / notification / messaging icon in the top navbar.
=== Login page ===
The login page has been redesigned and allows the admin to configure a background image for the login page only in the theme settings page. This change is available in both Boost and Classic. The login page still has all the features with an improved layout.
=== The page footer ===
In large screens, the page footer button is only visible when clicking a help button at the bottom right of the screen.
=== User initials as profile picture placeholder ===
If users do not upload a profile picture the user initials are displayed on a rounded gray background as a placeholder picture in the top navbar or any other page using a placeholder image. This change will be available in both Boost and Classic.

With the introduction of this placeholder image the full username will no longer be displayed in the top navbar.
=== Removal of back to top link ===
The "back to top" link will be removed for theme boost since the new course index reduced the dependence on page scrolling. Also, the new footer is positioned where this component used to be.
=== Styling changes ===
By default rounded edges will be used for UI components, for the page header and main content area the borders will be removed.
=== New layout page ===
Theme boost now uses the drawers.php layout for the course index and blocks.
== Question bank changes ==
There was a big project to deliver [[Question bank improvements for Moodle 4.0]] which added a new plugin type for adding features to the question banks, tracking the version history for each question as it is edited (question table has been split into <code>question</code>, <code>question_versions</code> and <code>question_bank_entries</code>), and tracking where each question is going to be used, with new tables <code>question_references</code> and <code>question_set_references</code>. This work was done in Epic MDL-70329 if you want to track down the details of any of the core changes.
=== Question type plugins ===
Amazingly, we (Safat and colleagues at Catalyst AU) managed to implement this without breaking most question type plugins.

However, the changes to the question bank, and the other Moodle 4.0 changes, probably broke the Behat tests for your plugin. To help with fixing that, MDL-74130 adds navigation to key question type pages (Preview and Edit for a question, and standard question bank pages like the bank itself, import and export) which should let you fix your test efficiently, and in a way that will work in all Moodle versions since 3.9.

The 'most' in the first paragraph here is becuase more advance question types may require more effort to fix. (For example qtype_combined which creates multi-part qusetions like the core qtype_multianswer; or qtype_pmatch or qtype_stack, which store additional data - questions tests - alongside the question itseld. How should that work with versionning?) But, if you have not done weird things like that, you are probably safe. If you find anything else that causes problems, please list it here.

The same thing should apply to question behaviour and question import/export format plugings: no significant changes required (probably just fixing the Behat tests because of the navigation changes).
=== New plugin type: qbank plugins ===
This is not something that will cause problems for people upgrading from 3.x. Rather, it is an exciting possibility you can explore once you have survived process of upgrading to 4.0. There is a whole new plugin type which you can create to add new features to the question bank. For example extra columns, new actions and bulk actions, and so on. See [[Question_bank_plugins]].
=== Activities that use questions ===
The probable bad news is if you have an activity module which uses questions. So far, the only activity which has been fixed is mod_quiz in Moodle core, so we don't yet have a good picture of what fixes will be necessary in other activities. Work is about to start fixing [https://github.com/studentquiz/moodle-mod_studentquiz mod_studentquiz], so watching that should give more clues. As we do that, we will try to update this section of this page. Other help writing the information required here would also be greatly appreciated.
== The course format system ==
Most of the logic for rendering and editing a course has been moved to a new subsystem called courseformat. The subsystem is located in "course/format" folder so it includes all the format plugins inside. The methods and modules which are distributed between the course and the course/format folders are now rearranged or refactored to be aligned with the current Moodle coding style.
=== Mandatory renderer in course formats ===
Now format plugins renderer is not optional anymore. Legacy formats without a renderer will get a deprecation message but it will continue working however, they should create a new renderer as soon as possible. The section-based format can do it by extending the provided core_courseformat\output\section_renderer class which includes all the necessary methods.
=== New format base class ===
The old base_format class (which all plugins extend) is now renamed as core_courseformat\base. The new class provides all the functionally of the previous base_format but it has been refactored to be used as a centralized source of truth for the course rendering. Legacy formats should extend the new class to avoid the deprecation message.

Now, the plugin format class provides information such as:
* If the page is displaying a single or multiple section
* Give access to other related format objects like the modinfo, the course record, maximum number of sections...
* If the format is compatible with features like course index, reactive components, ajax...
* Other format specifics like the page title, the default section name, default blocks...

The format instance is now the main object output components will use to render a course (see next section for more information).
=== New course output classes and mustache files ===
Traditionally, section-based course formats uses print_single_section_page and print_multiple_section_page to render the course content. In Moodle 4.0 most of the course rendering methods are migrated to output components and mustache templates. The old methods will get deprecation messages if they use the old renderer methods.

This is an example of a format rendering a course:<syntaxhighlight lang="php-brief">
// Get the course format instance.
$format = course_get_format($course);

// Get the specific format renderer.
$renderer = $format->get_renderer($PAGE);

if (!empty($displaysection)) {
// Setup the format instance to display a single section.
$format->set_section_number($displaysection);
}

// Create the ouptut instance and render it.
$outputclass = $format->get_output_classname('content');
$widget = new $outputclass($format);

echo $renderer->render($widget);
</syntaxhighlight>Format plugins are free to use its own output classes to render a course, or they could override the existing output classes by providing their own implementation. For example, the default output for "content" (as in the previous example) is "core_courseformat\output\local\|content", however, if the plugin has a "format_XXX\output\courseformat\content" class, the $format->class the get_output_class will return the overridden one.
Another important update on course rendering is that now all course structure is rendered using mustache templates instead of the original html_writer methods. Now themes are able to override the course format by providing alternative versions of the mustache files. All core course templates are located in "course/format/templates".

All the new output classes and a guide on how to migrate the current third-party plugins will be available soon.
=== Course editor javascript modules and frontend components ===
The majority of the javascript logic related to the course editing is replaced by AMD modules. Because this is a major change in the way courses are edited and rendered, by default format plugins will continue using the previous YUI modules for now. However, formats can start using the new libraries overriding the "$format->supports_components()" method.

Some Moodle 4.0 new features are only available for courses using the new editor library:
* Edit the course via the course index
* Creating sections without reloading the course page
* The new move section/activity modal
* Native browser drag&drop implementation
The new course editor uses a component-based reactive pattern to keep track of the course changes. The pattern highlights are:
* The main AMD module "core_crouseformat\courseeditor" maintains a data structure called state.
* Each UI element is implemented as a Component that observes the course state data and reacts to any data change
* When any reactive component needs to modify the course, it asks the course editor to execute a mutation. Mutations encapsulate all web services calls and alter the course state data.

The reactive library documentation, as well as the format plugin migration guide, will be available soon.
=== Other course related 4.0 changes ===
Two new web services have been added:
* core_courseformat_get_state: user by the new javascript course editor to get the current course state data (containing the list of sections, activities, and other course-related data)
* core_courseformat_update_course: to alter the current course content. Each call returns the parts of the course state altered by the action
== Behat changes ==
=== New steps ===
Moodle 4.0 introduces some new behat steps.

Sometimes you want to create a bulk number of activities. In that case you can use:<syntaxhighlight lang="gherkin">
:count :entitytype exist with the following data:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
Given 100 "mod_lti > tool types" exist with the following data:
|name |Test tool [count] |
|description |Example description [count] |
|baseurl |https://www.example.com/tool[count]|
</syntaxhighlight>

Dynamic (AJAX) tabs is a new feature contributed to Moodle 4.0 by the Workplace team (MDL-71943). You can use the following step to navigate between the tabs.<syntaxhighlight lang="gherkin">
And I click on the "tab title" dynamic tab
</syntaxhighlight>

To make sure that edit mode is (or is not) available on the current page, the following steps can be used.<syntaxhighlight lang="gherkin">
And edit mode should be available on the current page
And edit mode should not be available on the current page
</syntaxhighlight>

There are new aliases for the existing steps <code>I turn editing mode on</code> and <code>I turn editing mode off</code>.<syntaxhighlight lang="gherkin">
And I switch editing mode on
And I switch editing mode off
</syntaxhighlight>

In addition to the existing step to go to a course with editing mode on, we now have the following step to do the same but with editing mode being off.<syntaxhighlight lang="gherkin">
And I am on "course full name" course homepage with editing mode off
</syntaxhighlight>

The following step is similar to the old <code>following "link string" should download between "min bytes" and "max bytes" bytes</code> step, with more flexibility.<syntaxhighlight lang="gherkin">
And following "element string" "element type" in the "container string" "container type" should download between "min bytes" and "max bytes" bytes
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And following "Download" "link" in the "Starter" "table_row" should download between "0" and "5000" bytes
</syntaxhighlight>

The following step can be used to hover the mouse over the trigger area.<syntaxhighlight lang="gherkin">
And I hover over the "element string" "element type" in the "container string" "container type"
</syntaxhighlight>

The following step enables an installed plugin.<syntaxhighlight lang="gherkin">
And I enable "plugin name" "plugin type" plugin
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I enable "course_summary" "block" plugin
</syntaxhighlight>

The following is a special variation of 'I click on "<page name>" "link" in the "page" "region"'. It first checks to see if we are on the given page via the breadcrumb. If not we then attempt to follow the link name given.<syntaxhighlight lang="gherkin">
And I follow the breadcrumb "page name"
</syntaxhighlight>

You can use the following step to ensure a node is active in the navbar.<syntaxhighlight lang="gherkin">
And I should see "Node" is active in navigation
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I should see "My courses" is active in navigation
</syntaxhighlight>

The following step can be used to navigate to a given node in the primary navigation.<syntaxhighlight lang="gherkin">
And I select "Node" from primary navigation
</syntaxhighlight>

The following steps are to check whether an item exists in the user menu or not.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the user menu
And "item text" "selector type" should not exist in the user menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "Language" "link" should exist in the user menu
</syntaxhighlight>

The following steps are to check if a submenu of the user menu is shown, and if an item exists or does not exist in a given user submenu.<syntaxhighlight lang="gherkin">
And I should see "submenu name" user submenu
And "item text" "selector type" should exist in the "submenu name" user submenu
And "item text" "selector type" should not exist in the "submenu name" user submenu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I follow "Language" in the user menu
Then I should see "Language selector" user submenu
And "English &lrm;(en)&lrm;" "link" should exist in the "Language selector" user submenu
And "English (pirate) &lrm;(en_ar)&lrm;" "link" should not exist in the "Language selector" user submenu
</syntaxhighlight>

To add enrolment methods to courses you can use the following new step. The data that you provide in the next lines are used to fill the enrolment method form.<syntaxhighlight lang="gherkin">
And I add "enrolment method" in "course identifier" with:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I add "Self enrolment" enrolment method in "Course 1" with:
| Custom instance name | Test student enrolment |
| Enrolment key | moodle_rules |
| Use group enrolment keys | Yes |
</syntaxhighlight>

There are 3 new steps specific to the calendar component. These steps can be used to hover over a day in the mini-calendar or the full calendar.<syntaxhighlight lang="gherkin">
And I hover over day "day of month" of this month in the full calendar page
And I hover over day "day of month" of this month in the mini-calendar block
And I hover over today in the mini-calendar block
</syntaxhighlight>

Some new steps are added to question bank to be able to add comment to questions, verify the existence of a comment, and deleting comments form questions. Please note that the steps for adding comments only write the comment text in the comment field. You still need to click on the "Add comment" button to save the comment.<syntaxhighlight lang="gherkin">
And I add "comment text" comment to question
And I add "comment text" comment to question preview
And I delete "comment text" comment from question
And I delete "comment text" comment from question preview
And I should see "number of comments" on the comments column
And I click "number of comments" on the row on the comments column

</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "Question bank" in current page administration
And I should see "0" on the comments column
And I click "0" on the row on the comments column
And I add "test comment 01" comment to question
And I click on "Add comment" "button" in the ".modal-dialog" "css_element"
And I click on "Close" "button" in the ".modal-dialog" "css_element"
And I should see "1" on the comments column
And I click "1" on the row on the comments column
And I delete "test comment 01" comment from question
</syntaxhighlight>

Similar to the steps for comments, the following steps are to verify the number of a question's usage and to click on it in order to open the question usage modal.<syntaxhighlight lang="gherkin">
And I should see "usage count" on the usage column
And I click "usage count" on the usage column
</syntaxhighlight>

The following new steps are related to bulk actions in the question bank UI.<syntaxhighlight lang="gherkin">
And I click on question bulk action "action"
And I should see question bulk action "action"
And I should not see question bulk action "action"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I click on "First question" "checkbox"
And I click on "Second question" "checkbox"
And I click on "With selected" "button"
And I should see question bulk action "deleteselected"
And I click on question bulk action "deleteselected"
And I click on "Delete" "button" in the "Confirm" "dialogue"
</syntaxhighlight>

[https://docs.moodle.org/en/Report_builder Report builder] is a new feature contributed to Moodle 4.0 by the Workplace team. The following new step is added to Moodle 4.0 to select an action from the action menu in the list of custom reports table.<syntaxhighlight lang="gherkin">
And I press "action" action in the "report name" report row
</syntaxhighlight>

There's another step related to the report builder to set a column's aggregation in the report editor.<syntaxhighlight lang="gherkin">
And I set the "column title" column aggregation to "aggregation method"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I set the "First name" column aggregation to "Comma separated values"
</syntaxhighlight>

The following step needs to be used in scenarios that involve testing BigBlueButton. For this to work, you need to have a [https://github.com/moodlehq/bigbluebutton_mock BigBlueButton Mock API Server] and set <code>TEST_MOD_BIGBLUEBUTTONBN_MOCK_SERVER</code> to point to that in config.php.<syntaxhighlight lang="gherkin">
And a BigBlueButton mock server is configured
</syntaxhighlight>

The following step replicates receiving a callback from the BigBlueButton server indicating the recordings for meetings are ready for viewing.<syntaxhighlight lang="gherkin">
And the BigBlueButtonBN server has sent recording ready notifications
</syntaxhighlight>

The following steps are specific to the lesson activity. Note that in 4.0, some links (such as the "edit" and the "grade essays" links) are replaced by buttons, so you need to update your old steps with the new ones.<syntaxhighlight lang="gherkin">
And I edit the lesson
</syntaxhighlight>A new step is added to be used in lesson activities to edit them. This step navigates the user to the lesson edit page.
<syntaxhighlight lang="gherkin">
And I grade lesson essays
</syntaxhighlight>It's a new step to go to the "Grade essays" page of the lesson we are currently in.
<syntaxhighlight lang="gherkin">
And I select edit type "edit type"
</syntaxhighlight>Select the lesson edit type when we are in the the lesson's edit page. "edit type" can either be "Collapsed" or "Expanded".

The following new step can be used to navigate to the exports page in the course gradebook and select the specified export type from the grade exports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "export option" export page in the course gradebook
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "XML file" export page in the course gradebook
</syntaxhighlight>

Similarly, there's a new step to navigate to the imports page in the course gradebook and select the specified import type from the grade imports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "import option" import page in the course gradebook
</syntaxhighlight>
=== Boost steps ===
In addition to the steps listed in the previous section, there are also some Boost specific steps coming with Moodle 4.0. These steps only work in Boost or Boost child themes, so you need to make sure they are not used in scenarios that may be run by non-Boost themes.

The following step checks whether a node is active in the secondary navigation.<syntaxhighlight lang="gherkin">
And I should see :name is active in secondary navigation
</syntaxhighlight>

The Boost theme shows the language selector menu in the primary navigation when not logged in, and within the user menu when logged in. The following steps are to check if the primary navigation includes the language selector menu.<syntaxhighlight lang="gherkin">
And language selector menu should exist in the navbar
And language selector menu should not exist in the navbar
</syntaxhighlight>

And the following steps can be used to check whether an item exists in the language selector menu in the Boost theme.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the language selector menu
And "item text" "selector type" should not exist in the language selector menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "English &lrm;(en)&lrm;" "link" should exist in the language selector menu
</syntaxhighlight>
=== Modified steps ===
The step <code>I change the (window|viewport) size to "size"</code> now supports 2 new values for the size argument. The size argument now accepts <code>mobile</code> and <code>tablet</code> values in addition to <code>small</code>, <code>medium</code> and <code>large</code>.

=== Removed steps ===
Some behat steps are removed or replaced with new steps.

As a result of some design changes, hidden or restricted activities are no longer dimmed. Therefore the step<syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be dimmed
</syntaxhighlight>is now removed.
Depending on what you were using that step for, you may be able to use these steps:<syntaxhighlight lang="gherkin">
And "Label name" label should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And I should see "Activity or resource name"
And "Activity or resource name" "link" should not exist in the "region-main" "region"
</syntaxhighlight>
=== Other things to consider ===
To make behat tests more readable and easy to maintain, it is recommended to use the most direct steps to get what the test needs. It is highly recommended to use
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
instead of navigating to the activity via
I am on "Course" course homepage
I follow "Activity name"
Now that [https://docs.moodle.org/dev/Prototypes#Course_creation_improvements Course index] is integrated these behat steps
I am on "Course" course homepage
I follow "Activity name"
will fail using Boost theme.

The reason for it is that the drawer used in Boost is hiding the course index. So when the test is trying to follow an "Activity name" link, it finds two different links:
* one in the course index
* another one in the course main content.
But the first one, the one in the course index, is hidden by the drawer, and the test fails.

However the recommended behat steps
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
Old behat steps that may now fail can be updated to the new steps.
For example:
And I am on the "Test assignment name" "assign activity" page logged in as teacher1
instead of:
When I log in as "teacher1"
And I am on "Course" course homepage
And I follow "Test assignment name"

Or for settings, instead of:
<syntaxhighlight lang="gherkin">And I follow "Test choice name"
And I navigate to "Edit settings" in current page administration</syntaxhighlight>
Use:
<syntaxhighlight lang="gherkin">And I am on the "Test choice name" "choice activity editing" page</syntaxhighlight>

There are also similar stream-lined navigation steps for accessing question bank pages. See MDL-74130.

== Other ==
=== Core plugins review ===
A few plugins from core Moodle LMS which are no longer or hardly used have been removed and, if appropriate, added to the Moodle plugins directory.

More information about this project, the list of plugins to be removed and the process to follow for keeping them before upgrading to 4.0 can be found in the [[Core plugins review]] page.
=== Site admin presets plugin ===
The third-party plugin [https://moodle.org/plugins/block_admin_presets Admin presets], created by David Monllaó and maintained by developers from [https://pimenko.com/ Pimenko] has been adapted and integrated into Moodle 4.0. It stores settings and plugins status (enabled/disabled) in what's called "presets" to let admins quickly switch between different configurations.

More information about this project can be found in the [[Site admin presets|Site admin presets plugin]] page.
=== JavaScript browser support changes ===
From Moodle 4.0, Internet Explorer is no longer supported. See MDL-73915 and MDLSITE-6109 for further information on this change.

This change means that changes built on 4.0 onwards (including the master branch) will be different to older versions of Moodle.

For plugin developers supporting multiple versions of Moodle using a single plugin version, the compiled javascript files are backwards compatible and will _work_ on all supported versions, however if you run the `grunt` command on multiple versions you will see unbuilt changes. Running grunt on all versions of Moodle is not necessary and this check can be safely disabled for Moodle versions 3.9 - 4.0, as long as only at least you run `grunt` against at least one version of Moodle.

If you need to support Internet Explorer and do not wish to fork your plugin for Moodle 4.0 onwards, then it is recommended that you run `grunt` on an older version of Moodle.
=== The course index element ===
The new course index feature can be themed using a set of scss variables. Use them to change the look and feel instead of adding custom css
/theme/boost/scss/moodle/courseindex.scss
With the introduction of the course index component, the previous and next links shown underneath each activity are no longer needed and they will be removed.
=== Activity icons ===
The icons used for activities have been redesigned and updated for all core moodle activities.

When viewing the new icons in a file manager, for example for the quiz activity, you will see a simple black monochrome icon with a transparent background.

On the course page, or in the activity chooser, the icon will display as a white icon on a coloured background. Styling of the icons on the coursepage is controlled by the css in theme/boost/scss/moodle/icons.scss.

The background colour for activity icons is set using a new variable in function [modname]_supports(). The quiz activity is of type assessment, so in function quiz_supports() there is a new line defining the purpose:
case FEATURE_MOD_PURPOSE: return MOD_PURPOSE_ASSESSMENT;
Available purposes are:
* MOD_PURPOSE_COMMUNICATION
* MOD_PURPOSE_ASSESSMENT
* MOD_PURPOSE_COLLABORATION
* MOD_PURPOSE_CONTENT
* MOD_PURPOSE_ADMINISTRATION
* MOD_PURPOSE_INTERFACE
The background colours linked to these purposes are set in theme/boost/scss/moodle/variables.scss
$activity-icon-colors: map-merge(
(
"administration": #5d63f6,
"assessment": #eb66a2,
"collaboration": #f7634d,
"communication": #11a676,
"content": #399be2,
"interface": #a378ff
),
$activity-icon-colors
);
If activity plugins do not define FEATURE_MOD_PURPOSE the activity icon will be rendered against a light grey background. There is no requirement to define the purpose of activity plugins, it will only affect the icon styling.

Plugins implementing the variable FEATURE_MOD_PURPOSE are only supported on Moodle 4.0 and newer.

Customising the activity icon can be done in an alternative way. For example using the styles.css in mod/[pluginname/styles.css

In the example below the activity plugin developer chooses to keep the coloured icon for the activity and render it as large as the coloured background on the core activities
.modicon_subcourse.activityiconcontainer {
background-color: transparent;
padding: 0;
}

.modicon_subcourse.activityiconcontainer img {
width: 50px;
height: 50px;
}
To customize all icon colours use this scss array and add it to the ‘Raw initial SCSS’ in the theme Boost advanced settings page. The complete array of icon background colours can be overridden using the ‘Raw initial SCSS’ in the theme settings page. The example below changes the colours of each activity type.
$activity-icon-colors: (
"administration": #5D63F6,
"assessment": #11A676,
"collaboration": #EB66A2,
"communication": #F7634D,
"content": #399BE2,
"interface": #A378FF
)
== I'm a developer, what do I need to know? ==
This section is a quick checklist of the areas in this document that you should consult when updating your plugin.
=== Modules ===
If you are a module developer (activity / resources) then you need to review the following updates and changes:
* If using settings, reformat to work with the secondary navigation. We have significantly changed the way that settings are shown. Settings added to the course and activity administration branch of the navigation are now by default shown in the secondary navigation. You will most likely find them in the more section of the secondary navigation. Please avoid creating settings in containers (a parent navigation node with children). These settings will still be shown, but this goes against the pattern that we are trying to establish for navigation around the site. If you have a lot of settings, consider creating a specific page to handle your additional settings.
** The order of the items in the secondary navigation may not be to your liking. This can be changed. See [[Moodle_4.0_developer_update#Changing_the_order_of_tabs|changing the order of tabs]]
* Update my behat tests to use new steps for site navigation. See [[Moodle_4.0_developer_update#Behat_changes|new behat steps]].
* Update my module to use the new activity_header API. See [[Moodle_4.0_developer_update#The_activity_header_class|the activity header]].
* Update my pages to make it work with the general format of the tertiary navigation. See [[Moodle_4.0_developer_update#Tertiary_navigation|the tertiary navigation]].
* Update my activity icon to use the API and set a purpose. See [[Moodle_4.0_developer_update#Activity_icons|activity icons]].
=== Themes ===
If you are a theme developer then you may want to consider the following:
* Take a look at the [[Moodle_4.0_developer_update#Navigation_changes|new navigation]] and decide if you want to incorporate this into your theme.
** A new layout ([[Moodle_4.0_developer_update#New_layout_page|drawers]])
** An [[Moodle_4.0_developer_update#Edit_switch|edit switch]]
** The [[Moodle_4.0_developer_update#The_course_index_element|course index]]
* Use of the flat nav
* New Site administration page and layout
* Course settings and how they are displayed

=== Course format ===
There have been a lot of changes made to the course format. Most in the process of moving the course format away from using the old rendering system and towards templates.
We recommend the following sections be read carefully:
# [[Moodle_4.0_developer_update#The_course_format_system|The course format]]. There have been a lot of deprecations and reading this section is critical in understanding the changes made.
# Consider moving the rendering of your content over to the [[Templates|template system]].

Moodle 4.0 developer update

2022-03-14T07:58:39Z

Abgreeve: /* I'm a developer, what do I need to know? - description */

{{Moodle 4.0}}This page highlights the important changes that are coming in Moodle 4.0 for developers. Including how the UX improvements impact custom themes, relevant API changes, and what you can do as developer to prepare for the 4.0 release.
== Navigation changes ==
The core Navigation API has been left mostly untouched. The callbacks to all navigation callbacks remains unchanged and will be called as part of the regular 'navigation' and 'settingsnav' initialisation. Some new core classes have been created and exist within a new namespace 'core/navigation' and serves as conduit to rearrange, cherry-pick existing navigation nodes from the navigation/settingsnav trees and display within the respective navigation type. As such, it is highly recommended to provide unique keys for custom navigation nodes as this helps in the cherry-picking / rearranging process within the new classes.
=== Primary navigation ===
The primary navigation(the navbar) apart from the existing content will now display links to the Dashboard, My Courses, Site Admin and Course search, by default. You can still add items to the navbar via the 'custom menu' option. This will be displayed within the 'More' menu. We have transitioned the menus to be rendered via templates - refer user_menu.mustache. The lang menu has been moved to reside within the user menu.
==== Customising the primary navigation ====
Not yet implemented but we are looking at allowing the full addition and removal of any of the primary navigation tabs in the boost theme config file.
=== Secondary navigation ===
The main content area shows tabs for secondary navigation with a maximum of 5 items being rendered in this ‘more’ menu. A new UI component has been created to render menus like this. Files:
/lib/templates/moremenu.mustache
==== Changing the order of tabs ====
Apart from the previously mentioned functions, you can also create a custom secondary class as mentioned earlier. This will automatically be picked by getter and used to render the secondary nav within the activity. E.g. mod_assign/local/views/secondary. Note: This is currently only possible on an activity and block level.
=== Tertiary navigation ===
We've moved action buttons to the top of the page. We would encourage you to do the same.
If you have any buttons on an activity page that go to another page, or open a form (or similar), then we encourage you to move them from the body of your activity page to the top. All of the core activities have been updated to follow this pattern. Please take a look to see how you can format your activity in a similar fashion. There is no API here. You are welcome to create the buttons and display them as you wish in this top area.
=== New API functions ===
==== Page API ====
* Magic getters to fetch the primary and secondary navs and the primary output.
* The secondarynav magic getter also checks whether a custom secondary class has been defined within the module's local\views directory. Use this if you want to deviate from the standard secondary nav structure/order.

* set_secondary_nav - Force override the secondary navigation class

* has_secondary_navigation_setter - Sets the ‘_hassecondarynavigation’ to indicate whether a page should render the secondary navigation
==== Navigationlib ====
* set_show_in_secondary_navigation - whether or not a node should be displayed in the secondary nav. Accepts a single boolean argument
* set_force_into_more_menu- whether or not to force a node into the 'More' menu. Accepts a single boolean argument
==== The activity header class ====
There is a new activity header class that handles the display of information common to activities. 3rd party activities are not required to explicitly output this information as part of rendering individual pages.

The common information that are currently handled by the class are:
* title
* description
* completion information

As part of the update it was required that the initial information to be displayed by the class be toggable at a theme and layout level. Taking this into account the following theme level configurable exists:
* activityheaderconfig => An array that currently only enforces 'notitle' but can be expanded in the future NOTE: Boost has this set as true by default 'options'
The following layout level options that can be defined:
* noactivityheader - to remove the header in this specific layout.
* activityheader - An array that enforces the following options:
** notitle
** nocompletion
** nodescription
The class has a page level getter which you can use to fetch the current version of the class. The base state is initialised within the constructor with the completion information only fetched when data is exported for the template.

The class has setters for the following variables which can be leveraged to modify the header for a particular page in the format set_{variable_name}:
* hidecompletion
* description
* title
Alternately, bulk operations can also be done by passing the above variables in an array to 'set_attrs' which in turn calls the setters.<blockquote>'''Note: Any updates to the activityheader needs to be performed before the call to $OUTPUT->header'''</blockquote>
===== Theme updates: =====
In order for 3rd party themes to use the class they need to export the activity_header and include the following into their base template :<syntaxhighlight lang="html">
{{#headercontent}}
{{> core/activity_header}}
{{#headercontent}}
</syntaxhighlight>** headercontent being the array element that contains the exported activity_header data
===== Accessibility notes: =====
The jump to ‘maincontent’ div is now rendered within the activity header when within an activity context
== Component library ==
Each Moodle installation now ships with a Moodle User Interface (UI) Component library, a documentation system used to describe all the Bootstrap components and the custom Moodle components. The component Library is a helper tool for developers when creating user interfaces, a testing tool for theme developers and a documentation tool for core developers. The ultimate goal of having a component library is to encourage developers to create consistent user interfaces to improve Moodle’s overall user experience.

The library contains pages with documentation about User Interface components. It contains details on how to use the component, what variations are available and the JavaScript events / options are associated with the component.

When writing on these pages it is possible to render core mustache templates using some custom syntax like this:
<nowiki>{{< mustache template="core/notification_error" >}}</nowiki>
<nowiki>{{< /mustache >}}</nowiki>
You can also call core JavaScript or use HTML examples where the html code and the rendered result are visible in the Component Library. For more info visit the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-templates/ Moodle templates] page or the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-javascript/ Moodle JavaScript] page.

Each page in the library uses the current css from the default theme in your Moodle installation, if you have multiple themes installed and enabled the setting "Allow theme changes on url", the component library will have a theme selector option.

A hosted version of the Component Library can be found here. http://componentlibrary.moodle.com
=== Enabling the Component Library ===
Component library pages are written in the markdown language. These pages need to be compiled to HTML pages before the Component Library is visible. To compile the pages the server running Moodle needs to have the [[Javascript Modules#Install%20NVM%20and%20Node|JavaScript developer tools installed]] (nodeJs and Grunt)

If your server meets all requirements you can enable the library running
$ npm install
$ grunt componentlibrary
Further installation instructions can be found in the Component Library itself.
=== Documenting new UI Components ===
There are no set rules for adding new pages in the component library yet. These rules will need to be written and adopted in the integration process for Moodle code.

As a guideline for making this rules consideration are:

The component library is not about single use components, for example the Moodle grade book (a huge component with many custom features). Or about very common components like buttons, these are already covered by the Bootstrap section of the component library.

New features should be build keeping in mind the UI part needs to be customisable and if possible (and making sense) reusable. And example would be the new page drawers that we are introducing for the Navigation project. Or the custom primary navigation menus where overflowing items are pushed into a More section.
== Theme changes ==
=== Edit switch ===
On theme boost the “Turn editing on” and “Customise this page” buttons have been replaced by an edit switch in the top navbar. Theme Classic will keep using the old buttons. Child themes can choose to use the edit switch if the theme config.php is using this variable
$THEME->haseditswitch = true;
The languague menu, which used to be rendered in place of the custom menu has moved to the user dropdown when the user is logged in. If not logged in it will be placed next to the search / notification / messaging icon in the top navbar.
=== Login page ===
The login page has been redesigned and allows the admin to configure a background image for the login page only in the theme settings page. This change is available in both Boost and Classic. The login page still has all the features with an improved layout.
=== The page footer ===
In large screens, the page footer button is only visible when clicking a help button at the bottom right of the screen.
=== User initials as profile picture placeholder ===
If users do not upload a profile picture the user initials are displayed on a rounded gray background as a placeholder picture in the top navbar or any other page using a placeholder image. This change will be available in both Boost and Classic.

With the introduction of this placeholder image the full username will no longer be displayed in the top navbar.
=== Removal of back to top link ===
The "back to top" link will be removed for theme boost since the new course index reduced the dependence on page scrolling. Also, the new footer is positioned where this component used to be.
=== Styling changes ===
By default rounded edges will be used for UI components, for the page header and main content area the borders will be removed.
=== New layout page ===
Theme boost now uses the drawers.php layout for the course index and blocks.
== Question bank changes ==
There was a big project to deliver [[Question bank improvements for Moodle 4.0]] which added a new plugin type for adding features to the question banks, tracking the version history for each question as it is edited (question table has been split into <code>question</code>, <code>question_versions</code> and <code>question_bank_entries</code>), and tracking where each question is going to be used, with new tables <code>question_references</code> and <code>question_set_references</code>. This work was done in Epic MDL-70329 if you want to track down the details of any of the core changes.
=== Question type plugins ===
Amazingly, we (Safat and colleagues at Catalyst AU) managed to implement this without breaking most question type plugins.

However, the changes to the question bank, and the other Moodle 4.0 changes, probably broke the Behat tests for your plugin. To help with fixing that, MDL-74130 adds navigation to key question type pages (Preview and Edit for a question, and standard question bank pages like the bank itself, import and export) which should let you fix your test efficiently, and in a way that will work in all Moodle versions since 3.9.

The 'most' in the first paragraph here is becuase more advance question types may require more effort to fix. (For example qtype_combined which creates multi-part qusetions like the core qtype_multianswer; or qtype_pmatch or qtype_stack, which store additional data - questions tests - alongside the question itseld. How should that work with versionning?) But, if you have not done weird things like that, you are probably safe. If you find anything else that causes problems, please list it here.

The same thing should apply to question behaviour and question import/export format plugings: no significant changes required (probably just fixing the Behat tests because of the navigation changes).
=== New plugin type: qbank plugins ===
This is not something that will cause problems for people upgrading from 3.x. Rather, it is an exciting possibility you can explore once you have survived process of upgrading to 4.0. There is a whole new plugin type which you can create to add new features to the question bank. For example extra columns, new actions and bulk actions, and so on. See [[Question_bank_plugins]].
=== Activities that use questions ===
The probable bad news is if you have an activity module which uses questions. So far, the only activity which has been fixed is mod_quiz in Moodle core, so we don't yet have a good picture of what fixes will be necessary in other activities. Work is about to start fixing [https://github.com/studentquiz/moodle-mod_studentquiz mod_studentquiz], so watching that should give more clues. As we do that, we will try to update this section of this page. Other help writing the information required here would also be greatly appreciated.
== The course format system ==
Most of the logic for rendering and editing a course has been moved to a new subsystem called courseformat. The subsystem is located in "course/format" folder so it includes all the format plugins inside. The methods and modules which are distributed between the course and the course/format folders are now rearranged or refactored to be aligned with the current Moodle coding style.
=== Mandatory renderer in course formats ===
Now format plugins renderer is not optional anymore. Legacy formats without a renderer will get a deprecation message but it will continue working however, they should create a new renderer as soon as possible. The section-based format can do it by extending the provided core_courseformat\output\section_renderer class which includes all the necessary methods.
=== New format base class ===
The old base_format class (which all plugins extend) is now renamed as core_courseformat\base. The new class provides all the functionally of the previous base_format but it has been refactored to be used as a centralized source of truth for the course rendering. Legacy formats should extend the new class to avoid the deprecation message.

Now, the plugin format class provides information such as:
* If the page is displaying a single or multiple section
* Give access to other related format objects like the modinfo, the course record, maximum number of sections...
* If the format is compatible with features like course index, reactive components, ajax...
* Other format specifics like the page title, the default section name, default blocks...

The format instance is now the main object output components will use to render a course (see next section for more information).
=== New course output classes and mustache files ===
Traditionally, section-based course formats uses print_single_section_page and print_multiple_section_page to render the course content. In Moodle 4.0 most of the course rendering methods are migrated to output components and mustache templates. The old methods will get deprecation messages if they use the old renderer methods.

This is an example of a format rendering a course:<syntaxhighlight lang="php-brief">
// Get the course format instance.
$format = course_get_format($course);

// Get the specific format renderer.
$renderer = $format->get_renderer($PAGE);

if (!empty($displaysection)) {
// Setup the format instance to display a single section.
$format->set_section_number($displaysection);
}

// Create the ouptut instance and render it.
$outputclass = $format->get_output_classname('content');
$widget = new $outputclass($format);

echo $renderer->render($widget);
</syntaxhighlight>Format plugins are free to use its own output classes to render a course, or they could override the existing output classes by providing their own implementation. For example, the default output for "content" (as in the previous example) is "core_courseformat\output\local\|content", however, if the plugin has a "format_XXX\output\courseformat\content" class, the $format->class the get_output_class will return the overridden one.
Another important update on course rendering is that now all course structure is rendered using mustache templates instead of the original html_writer methods. Now themes are able to override the course format by providing alternative versions of the mustache files. All core course templates are located in "course/format/templates".

All the new output classes and a guide on how to migrate the current third-party plugins will be available soon.
=== Course editor javascript modules and frontend components ===
The majority of the javascript logic related to the course editing is replaced by AMD modules. Because this is a major change in the way courses are edited and rendered, by default format plugins will continue using the previous YUI modules for now. However, formats can start using the new libraries overriding the "$format->supports_components()" method.

Some Moodle 4.0 new features are only available for courses using the new editor library:
* Edit the course via the course index
* Creating sections without reloading the course page
* The new move section/activity modal
* Native browser drag&drop implementation
The new course editor uses a component-based reactive pattern to keep track of the course changes. The pattern highlights are:
* The main AMD module "core_crouseformat\courseeditor" maintains a data structure called state.
* Each UI element is implemented as a Component that observes the course state data and reacts to any data change
* When any reactive component needs to modify the course, it asks the course editor to execute a mutation. Mutations encapsulate all web services calls and alter the course state data.

The reactive library documentation, as well as the format plugin migration guide, will be available soon.
=== Other course related 4.0 changes ===
Two new web services have been added:
* core_courseformat_get_state: user by the new javascript course editor to get the current course state data (containing the list of sections, activities, and other course-related data)
* core_courseformat_update_course: to alter the current course content. Each call returns the parts of the course state altered by the action
== Behat changes ==
=== New steps ===
Moodle 4.0 introduces some new behat steps.

Sometimes you want to create a bulk number of activities. In that case you can use:<syntaxhighlight lang="gherkin">
:count :entitytype exist with the following data:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
Given 100 "mod_lti > tool types" exist with the following data:
|name |Test tool [count] |
|description |Example description [count] |
|baseurl |https://www.example.com/tool[count]|
</syntaxhighlight>

Dynamic (AJAX) tabs is a new feature contributed to Moodle 4.0 by the Workplace team (MDL-71943). You can use the following step to navigate between the tabs.<syntaxhighlight lang="gherkin">
And I click on the "tab title" dynamic tab
</syntaxhighlight>

To make sure that edit mode is (or is not) available on the current page, the following steps can be used.<syntaxhighlight lang="gherkin">
And edit mode should be available on the current page
And edit mode should not be available on the current page
</syntaxhighlight>

There are new aliases for the existing steps <code>I turn editing mode on</code> and <code>I turn editing mode off</code>.<syntaxhighlight lang="gherkin">
And I switch editing mode on
And I switch editing mode off
</syntaxhighlight>

In addition to the existing step to go to a course with editing mode on, we now have the following step to do the same but with editing mode being off.<syntaxhighlight lang="gherkin">
And I am on "course full name" course homepage with editing mode off
</syntaxhighlight>

The following step is similar to the old <code>following "link string" should download between "min bytes" and "max bytes" bytes</code> step, with more flexibility.<syntaxhighlight lang="gherkin">
And following "element string" "element type" in the "container string" "container type" should download between "min bytes" and "max bytes" bytes
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And following "Download" "link" in the "Starter" "table_row" should download between "0" and "5000" bytes
</syntaxhighlight>

The following step can be used to hover the mouse over the trigger area.<syntaxhighlight lang="gherkin">
And I hover over the "element string" "element type" in the "container string" "container type"
</syntaxhighlight>

The following step enables an installed plugin.<syntaxhighlight lang="gherkin">
And I enable "plugin name" "plugin type" plugin
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I enable "course_summary" "block" plugin
</syntaxhighlight>

The following is a special variation of 'I click on "<page name>" "link" in the "page" "region"'. It first checks to see if we are on the given page via the breadcrumb. If not we then attempt to follow the link name given.<syntaxhighlight lang="gherkin">
And I follow the breadcrumb "page name"
</syntaxhighlight>

You can use the following step to ensure a node is active in the navbar.<syntaxhighlight lang="gherkin">
And I should see "Node" is active in navigation
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I should see "My courses" is active in navigation
</syntaxhighlight>

The following step can be used to navigate to a given node in the primary navigation.<syntaxhighlight lang="gherkin">
And I select "Node" from primary navigation
</syntaxhighlight>

The following steps are to check whether an item exists in the user menu or not.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the user menu
And "item text" "selector type" should not exist in the user menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "Language" "link" should exist in the user menu
</syntaxhighlight>

The following steps are to check if a submenu of the user menu is shown, and if an item exists or does not exist in a given user submenu.<syntaxhighlight lang="gherkin">
And I should see "submenu name" user submenu
And "item text" "selector type" should exist in the "submenu name" user submenu
And "item text" "selector type" should not exist in the "submenu name" user submenu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I follow "Language" in the user menu
Then I should see "Language selector" user submenu
And "English &lrm;(en)&lrm;" "link" should exist in the "Language selector" user submenu
And "English (pirate) &lrm;(en_ar)&lrm;" "link" should not exist in the "Language selector" user submenu
</syntaxhighlight>

To add enrolment methods to courses you can use the following new step. The data that you provide in the next lines are used to fill the enrolment method form.<syntaxhighlight lang="gherkin">
And I add "enrolment method" in "course identifier" with:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I add "Self enrolment" enrolment method in "Course 1" with:
| Custom instance name | Test student enrolment |
| Enrolment key | moodle_rules |
| Use group enrolment keys | Yes |
</syntaxhighlight>

There are 3 new steps specific to the calendar component. These steps can be used to hover over a day in the mini-calendar or the full calendar.<syntaxhighlight lang="gherkin">
And I hover over day "day of month" of this month in the full calendar page
And I hover over day "day of month" of this month in the mini-calendar block
And I hover over today in the mini-calendar block
</syntaxhighlight>

Some new steps are added to question bank to be able to add comment to questions, verify the existence of a comment, and deleting comments form questions. Please note that the steps for adding comments only write the comment text in the comment field. You still need to click on the "Add comment" button to save the comment.<syntaxhighlight lang="gherkin">
And I add "comment text" comment to question
And I add "comment text" comment to question preview
And I delete "comment text" comment from question
And I delete "comment text" comment from question preview
And I should see "number of comments" on the comments column
And I click "number of comments" on the row on the comments column

</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "Question bank" in current page administration
And I should see "0" on the comments column
And I click "0" on the row on the comments column
And I add "test comment 01" comment to question
And I click on "Add comment" "button" in the ".modal-dialog" "css_element"
And I click on "Close" "button" in the ".modal-dialog" "css_element"
And I should see "1" on the comments column
And I click "1" on the row on the comments column
And I delete "test comment 01" comment from question
</syntaxhighlight>

Similar to the steps for comments, the following steps are to verify the number of a question's usage and to click on it in order to open the question usage modal.<syntaxhighlight lang="gherkin">
And I should see "usage count" on the usage column
And I click "usage count" on the usage column
</syntaxhighlight>

The following new steps are related to bulk actions in the question bank UI.<syntaxhighlight lang="gherkin">
And I click on question bulk action "action"
And I should see question bulk action "action"
And I should not see question bulk action "action"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I click on "First question" "checkbox"
And I click on "Second question" "checkbox"
And I click on "With selected" "button"
And I should see question bulk action "deleteselected"
And I click on question bulk action "deleteselected"
And I click on "Delete" "button" in the "Confirm" "dialogue"
</syntaxhighlight>

[https://docs.moodle.org/en/Report_builder Report builder] is a new feature contributed to Moodle 4.0 by the Workplace team. The following new step is added to Moodle 4.0 to select an action from the action menu in the list of custom reports table.<syntaxhighlight lang="gherkin">
And I press "action" action in the "report name" report row
</syntaxhighlight>

There's another step related to the report builder to set a column's aggregation in the report editor.<syntaxhighlight lang="gherkin">
And I set the "column title" column aggregation to "aggregation method"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I set the "First name" column aggregation to "Comma separated values"
</syntaxhighlight>

The following step needs to be used in scenarios that involve testing BigBlueButton. For this to work, you need to have a [https://github.com/moodlehq/bigbluebutton_mock BigBlueButton Mock API Server] and set <code>TEST_MOD_BIGBLUEBUTTONBN_MOCK_SERVER</code> to point to that in config.php.<syntaxhighlight lang="gherkin">
And a BigBlueButton mock server is configured
</syntaxhighlight>

The following step replicates receiving a callback from the BigBlueButton server indicating the recordings for meetings are ready for viewing.<syntaxhighlight lang="gherkin">
And the BigBlueButtonBN server has sent recording ready notifications
</syntaxhighlight>

The following steps are specific to the lesson activity. Note that in 4.0, some links (such as the "edit" and the "grade essays" links) are replaced by buttons, so you need to update your old steps with the new ones.<syntaxhighlight lang="gherkin">
And I edit the lesson
</syntaxhighlight>A new step is added to be used in lesson activities to edit them. This step navigates the user to the lesson edit page.
<syntaxhighlight lang="gherkin">
And I grade lesson essays
</syntaxhighlight>It's a new step to go to the "Grade essays" page of the lesson we are currently in.
<syntaxhighlight lang="gherkin">
And I select edit type "edit type"
</syntaxhighlight>Select the lesson edit type when we are in the the lesson's edit page. "edit type" can either be "Collapsed" or "Expanded".

The following new step can be used to navigate to the exports page in the course gradebook and select the specified export type from the grade exports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "export option" export page in the course gradebook
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "XML file" export page in the course gradebook
</syntaxhighlight>

Similarly, there's a new step to navigate to the imports page in the course gradebook and select the specified import type from the grade imports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "import option" import page in the course gradebook
</syntaxhighlight>
=== Boost steps ===
In addition to the steps listed in the previous section, there are also some Boost specific steps coming with Moodle 4.0. These steps only work in Boost or Boost child themes, so you need to make sure they are not used in scenarios that may be run by non-Boost themes.

The following step checks whether a node is active in the secondary navigation.<syntaxhighlight lang="gherkin">
And I should see :name is active in secondary navigation
</syntaxhighlight>

The Boost theme shows the language selector menu in the primary navigation when not logged in, and within the user menu when logged in. The following steps are to check if the primary navigation includes the language selector menu.<syntaxhighlight lang="gherkin">
And language selector menu should exist in the navbar
And language selector menu should not exist in the navbar
</syntaxhighlight>

And the following steps can be used to check whether an item exists in the language selector menu in the Boost theme.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the language selector menu
And "item text" "selector type" should not exist in the language selector menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "English &lrm;(en)&lrm;" "link" should exist in the language selector menu
</syntaxhighlight>
=== Modified steps ===
The step <code>I change the (window|viewport) size to "size"</code> now supports 2 new values for the size argument. The size argument now accepts <code>mobile</code> and <code>tablet</code> values in addition to <code>small</code>, <code>medium</code> and <code>large</code>.
=== Removed steps ===
Some behat steps are removed or replaced with new steps.

As a result of some design changes, hidden or restricted activities are no longer dimmed. Therefore the step<syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be dimmed
</syntaxhighlight>is now removed.
Depending on what you were using that step for, you may be able to use these steps:<syntaxhighlight lang="gherkin">
And "Label name" label should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And I should see "Activity or resource name"
And "Activity or resource name" "link" should not exist in the "region-main" "region"
</syntaxhighlight>
=== Other things to consider ===
To make behat tests more readable and easy to maintain, it is recommended to use the most direct steps to get what the test needs. It is highly recommended to use
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
instead of navigating to the activity via
I am on "Course" course homepage
I follow "Activity name"
Now that [https://docs.moodle.org/dev/Prototypes#Course_creation_improvements Course index] is integrated these behat steps
I am on "Course" course homepage
I follow "Activity name"
will fail using Boost theme.

The reason for it is that the drawer used in Boost is hiding the course index. So when the test is trying to follow an "Activity name" link, it finds two different links:
* one in the course index
* another one in the course main content.
But the first one, the one in the course index, is hidden by the drawer, and the test fails.

However the recommended behat steps
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
Old behat steps that may now fail can be updated to the new steps.
For example:
And I am on the "Test assignment name" "assign activity" page logged in as teacher1
instead of:
When I log in as "teacher1"
And I am on "Course" course homepage
And I follow "Test assignment name"
There are also similar stream-lined navigation steps for accessing question bank pages. See MDL-74130.
== Other ==
=== Core plugins review ===
A few plugins from core Moodle LMS which are no longer or hardly used have been removed and, if appropriate, added to the Moodle plugins directory.

More information about this project, the list of plugins to be removed and the process to follow for keeping them before upgrading to 4.0 can be found in the [[Core plugins review]] page.
=== Site admin presets plugin ===
The third-party plugin [https://moodle.org/plugins/block_admin_presets Admin presets], created by David Monllaó and maintained by developers from [https://pimenko.com/ Pimenko] has been adapted and integrated into Moodle 4.0. It stores settings and plugins status (enabled/disabled) in what's called "presets" to let admins quickly switch between different configurations.

More information about this project can be found in the [[Site admin presets|Site admin presets plugin]] page.
=== JavaScript browser support changes ===
From Moodle 4.0, Internet Explorer is no longer supported. See MDL-73915 and MDLSITE-6109 for further information on this change.

This change means that changes built on 4.0 onwards (including the master branch) will be different to older versions of Moodle.

For plugin developers supporting multiple versions of Moodle using a single plugin version, the compiled javascript files are backwards compatible and will _work_ on all supported versions, however if you run the `grunt` command on multiple versions you will see unbuilt changes. Running grunt on all versions of Moodle is not necessary and this check can be safely disabled for Moodle versions 3.9 - 4.0, as long as only at least you run `grunt` against at least one version of Moodle.

If you need to support Internet Explorer and do not wish to fork your plugin for Moodle 4.0 onwards, then it is recommended that you run `grunt` on an older version of Moodle.
=== The course index element ===
The new course index feature can be themed using a set of scss variables. Use them to change the look and feel instead of adding custom css
/theme/boost/scss/moodle/courseindex.scss
With the introduction of the course index component, the previous and next links shown underneath each activity are no longer needed and they will be removed.
=== Activity icons ===
The icons used for activities have been redesigned and updated for all core moodle activities.

When viewing the new icons in a file manager, for example for the quiz activity, you will see a simple black monochrome icon with a transparent background.

On the course page, or in the activity chooser, the icon will display as a white icon on a coloured background. Styling of the icons on the coursepage is controlled by the css in theme/boost/scss/moodle/icons.scss.

The background colour for activity icons is set using a new variable in function [modname]_supports(). The quiz activity is of type assessment, so in function quiz_supports() there is a new line defining the purpose:
case FEATURE_MOD_PURPOSE: return MOD_PURPOSE_ASSESSMENT;
Available purposes are:
* MOD_PURPOSE_COMMUNICATION
* MOD_PURPOSE_ASSESSMENT
* MOD_PURPOSE_COLLABORATION
* MOD_PURPOSE_CONTENT
* MOD_PURPOSE_ADMINISTRATION
* MOD_PURPOSE_INTERFACE
The background colours linked to these purposes are set in theme/boost/scss/moodle/variables.scss
$activity-icon-colors: map-merge(
(
"administration": #5d63f6,
"assessment": #eb66a2,
"collaboration": #f7634d,
"communication": #11a676,
"content": #399be2,
"interface": #a378ff
),
$activity-icon-colors
);
If activity plugins do not define FEATURE_MOD_PURPOSE the activity icon will be rendered against a light grey background. There is no requirement to define the purpose of activity plugins, it will only affect the icon styling.

Plugins implementing the variable FEATURE_MOD_PURPOSE are only supported on Moodle 4.0 and newer.

Customising the activity icon can be done in an alternative way. For example using the styles.css in mod/[pluginname/styles.css

In the example below the activity plugin developer chooses to keep the coloured icon for the activity and render it as large as the coloured background on the core activities
.modicon_subcourse.activityiconcontainer {
background-color: transparent;
padding: 0;
}

.modicon_subcourse.activityiconcontainer img {
width: 50px;
height: 50px;
}
To customize all icon colours use this scss array and add it to the ‘Raw initial SCSS’ in the theme Boost advanced settings page. The complete array of icon background colours can be overridden using the ‘Raw initial SCSS’ in the theme settings page. The example below changes the colours of each activity type.
$activity-icon-colors: (
"administration": #5D63F6,
"assessment": #11A676,
"collaboration": #EB66A2,
"communication": #F7634D,
"content": #399BE2,
"interface": #A378FF
)
== I'm a developer, what do I need to know? ==
This section is a quick checklist of the areas in this document that you should consult when updating your plugin.
=== Modules ===
If you are a module developer (activity / resources) then you need to review the following updates and changes:
* If using settings, reformat to work with the secondary navigation. We have significantly changed the way that settings are shown. Settings added to the course and activity administration branch of the navigation are now by default shown in the secondary navigation. You will most likely find them in the more section of the secondary navigation. Please avoid creating settings in containers (a parent navigation node with children). These settings will still be shown, but this goes against the pattern that we are trying to establish for navigation around the site. If you have a lot of settings, consider creating a specific page to handle your additional settings.
** The order of the items in the secondary navigation may not be to your liking. This can be changed. See [[Moodle_4.0_developer_update#Changing_the_order_of_tabs|changing the order of tabs]]
* Update my behat tests to use new steps for site navigation. See [[Moodle_4.0_developer_update#Behat_changes|new behat steps]].
* Update my module to use the new activity_header API. See [[Moodle_4.0_developer_update#The_activity_header_class|the activity header]].
* Update my pages to make it work with the general format of the tertiary navigation. See [[Moodle_4.0_developer_update#Tertiary_navigation|the tertiary navigation]].
* Update my activity icon to use the API and set a purpose. See [[Moodle_4.0_developer_update#Activity_icons|activity icons]].
=== Themes ===
If you are a theme developer then you may want to consider the following:
* Take a look at the [[Moodle_4.0_developer_update#Navigation_changes|new navigation]] and decide if you want to incorporate this into your theme.
** A new layout ([[Moodle_4.0_developer_update#New_layout_page|drawers]])
** An [[Moodle_4.0_developer_update#Edit_switch|edit switch]]
** The [[Moodle_4.0_developer_update#The_course_index_element|course index]]
* Use of the flat nav
* New Site administration page and layout
* Course settings and how they are displayed

Releases

2022-03-14T07:49:08Z

Abgreeve: /* Moodle 3.9 (LTS) update to 3.9.13 */

This page lists all official releases of Moodle, grouped by branch in reverse chronological order.
==Version support==
From Moodle 2.6 onwards, the end of support, both general and security, happens the second Monday of May and November, observing the 12, 18... month periods, no matter if the major release date was moved or not.

The most recent [https://en.wikipedia.org/wiki/Long-term_support long-term support release (LTS)] version is Moodle 3.9.
{| class="wikitable" border="1px solid #dee2e6;"
|-
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Version
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Release status
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Initial release
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:rgba(0, 0, 0, 0.05);" | General support ends
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Security support ends
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.9 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 15 June 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 10 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 November 2023 (ext 6M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.10
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 9 November 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 8 November 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 9 May 2022
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.11
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 17 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 14 Nov 2022 (ext 6M)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 Nov 2023 (ext 12M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |4.0
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |April 2022
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |May 2023
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |November 2023
|-
|4.1 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
|November 2022
|November 2023
|November 2025
|}
[[Image:releasescurrent.png|alt=Release graph]]

Release graph key:
{| class="wikitable" border="1px solid #dee2e6;"
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Currently supported stable releases.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | Current release of versions still receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Future point releases receiving bug fixes, as well as security updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#316d5e; color:white; adding: .3rem 0.5rem 0.3rem 0.5rem;" |Future security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Future point releases receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#686566; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Previously released versions containing bug fixes, as well as security updates. Updating to a currently supported version is recommended.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#282828; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Previously released versions containing security updates only. Updating to a currently supported version is recommended.
|}
==General release calendar==
These are the target dates for releases. These dates may vary slightly due to unforeseen circumstances.
{| class="wikitable"
|-
!Release type
!Frequency
!Months
|-
|[[Process#Major_release_cycles|Major]] (eg. 3.x)
|6 monthly
|Second Monday of May and November
|-
|[[Process#Stable_maintenance_cycles|Minor]] (Point) (eg. 3.x.y)
| 2 monthly
|Second Monday of July, September, November, March and May.
Third Monday of January.
|}
All releases are preceded by a one week warning. Upcoming release dates can be found in the [https://www.google.com/calendar/ical/moodle.com_p4c2oe7hsb77ltaro5qtihb5d4%40group.calendar.google.com/public/basic.ics Moodle development calendar] (Note, this is an iCAL link that will try to add the dates to your personal calendar. If you just want to browse the dates online, use [https://calendar.google.com/calendar/embed?src=moodle.com_p4c2oe7hsb77ltaro5qtihb5d4@group.calendar.google.com&pli=1 this link].).
==Moodle 3.11==
{| class="wikitable"
|-
!Moodle 3.11
|17 May 2021
|2021051700
|[[Moodle 3.11 release notes|Release Notes]]
|[https://docs.moodle.org/311/en/Upgrading Upgrading to 3.11]
|-
!Moodle 3.11.1
|12 July 2021
|2021051701
|[[Moodle 3.11.1 release notes|Release Notes]]
|
|-
!Moodle 3.11.2
|29 July 2021
|2021051702
|[[Moodle 3.11.2 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.11.3
|13 September 2021
|2021051703
|[[Moodle 3.11.3 release notes|Release Notes]]
|
|-
! Moodle 3.11.4
|8 November 2021
|2021051704
|[[Moodle 3.11.4 release notes|Release Notes]]
|
|-
! Moodle 3.11.5
|17 January 2022
|2021051705
|[[Moodle 3.11.5 release notes|Release Notes]]
|-
! Moodle 3.11.6
|14 March 2022
|2021051706
|[[Moodle 3.11.6 release notes|Release Notes]]
|}
Bug fixes for general core bugs in 3.11.x will end 14 Nov 2022 (12 months plus 6 months extension).
Bug fixes for security issues in 3.11.x will end 13 Nov 2023 (18 months plus 12 months extension).

==Moodle 3.10==
{| class="wikitable"
|-
! Moodle 3.10
|9 November 2020
|2020110900
|
[[Moodle 3.10 release notes|Release Notes]]
|[https://docs.moodle.org/310/en/Upgrading Upgrading to 3.10]
|-
!Moodle 3.10.1
|18 January 2021
|2020110901
| [[Moodle 3.10.1 release notes|Release Notes]]
|
|-
!Moodle 3.10.2
|8 March 2021
|2020110902
|[[Moodle 3.10.2 release notes|Release Notes]]
|
|-
! Moodle 3.10.3
|25 March 2021
|2020110903
|[[Moodle 3.10.3 release notes|Release Notes]]
|
|-
!Moodle 3.10.4
|10 May 2021
|2020110904
|[[Moodle 3.10.4 release notes|Release Notes]]
|
|-
!Moodle 3.10.5
|12 July 2021
|2020110905
|[[Moodle 3.10.5 release notes|Release Notes]]
|
|-
!Moodle 3.10.6
|29 July 2021
|2020110906
|[[Moodle 3.10.6 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.10.7
|13 September 2021
|2020110907
|[[Moodle 3.10.7 release notes|Release Notes]]
|
|-
!Moodle 3.10.8
|8 November 2021
|2020110908
|[[Moodle 3.10.8 release notes|Release Notes]]
|
|-
!Moodle 3.10.9
|17 January 2022
|2020110909
|[[Moodle 3.10.9 release notes|Release Notes]]
|-
!Moodle 3.10.10
|14 March 2022
|2020110910
|[[Moodle 3.10.10 release notes|Release Notes]]
|}
Bug fixes for general core bugs in 3.10.x ended 8 November 2021 (12 months).
Bug fixes for security issues in 3.10.x will end 9 May 2022 (18 months).

==Moodle 3.9 (LTS)==
{| class="wikitable"
|-
! Moodle 3.9
|15 June 2020
|2020061500
|[[Moodle 3.9 release notes|Release Notes]]
|
[https://docs.moodle.org/39/en/Upgrading Upgrading to 3.9]
|-
!Moodle 3.9.1
|13 July 2020
|2020061501
|[[Moodle 3.9.1 release notes|Release Notes]]
|
|-
!Moodle 3.9.2
|14 September 2020
|2020061502
| [[Moodle 3.9.2 release notes|Release Notes]]
|
|-
!Moodle 3.9.3
|9 November 2020
|2020061503
| [[Moodle 3.9.3 release notes|Release Notes]]
|
|-
!Moodle 3.9.4
|18 January 2021
|2020061504
|[[Moodle 3.9.4 release notes|Release Notes]]
|
|-
!Moodle 3.9.5
|8 March 2021
|2020061505
|[[Moodle 3.9.5 release notes|Release Notes]]
|
|-
!Moodle 3.9.6
|25 March 2021
|2020061506
|[[Moodle 3.9.6 release notes|Release Notes]]
|
|-
!Moodle 3.9.7
|10 May 2021
|2020061507
|[[Moodle 3.9.7 release notes|Release Notes]]
|
|-
! Moodle 3.9.8
|12 July 2021
|2020061508
|[[Moodle 3.9.8 release notes|Release Notes]]
|
|-
!Moodle 3.9.9
|29 July 2021
|2020061509
|[[Moodle 3.9.9 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.9.10
|13 September 2021
|2020061510
|[[Moodle 3.9.10 release notes|Release Notes]]
|
|-
!Moodle 3.9.11
| 8 November 2021
|2020061511
|[[Moodle 3.9.11 release notes|Release Notes]]
|
|-
!Moodle 3.9.12
| 17 January 2022
|2020061512
|[[Moodle 3.9.12 release notes|Release Notes]]
|-
!Moodle 3.9.13
| 14 March 2022
|2020061513
|[[Moodle 3.9.13 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.9.x ended 10 May 2021 (12 months).
Bug fixes for security issues in 3.9.x will end 13 Nov 2023 (36 months plus 6 months extension).

==Moodle 3.8==
{| class="wikitable"
|-
!Moodle 3.8
|18 November 2019
|2019111800
|[[Moodle 3.8 release notes|Release Notes]]
|
[https://docs.moodle.org/38/en/Upgrading Upgrading to 3.8]
|-
!Moodle 3.8.1
|13 January 2020
|2019111801
|[[Moodle 3.8.1 release notes|Release Notes]]
|
|-
!Moodle 3.8.2
|9 March 2020
|2019111802
|[[Moodle 3.8.2 release notes|Release Notes]]
|
|-
!Moodle 3.8.3
|11 May 2020
|2019111803
|[[Moodle 3.8.3 release notes|Release Notes]]
|
|-
!Moodle 3.8.4
|13 July 2020
|2019111804
|[[Moodle 3.8.4 release notes|Release Notes]]
|
|-
!Moodle 3.8.5
|14 September 2020
|2019111805
| [[Moodle 3.8.5 release notes|Release Notes]]
|
|-
!Moodle 3.8.6
|9 November 2020
|2019111806
| [[Moodle 3.8.6 release notes|Release Notes]]
|
|-
!Moodle 3.8.7
|18 January 2021
|2019111807
|[[Moodle 3.8.7 release notes|Release Notes]]
|
|-
!Moodle 3.8.8
|8 March 2021
|2019111808
|[[Moodle 3.8.8 release notes|Release Notes]]
|
|-
!Moodle 3.8.9
|10 May 2021
|2019111809
|[[Moodle 3.8.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.8.x ended 9 November 2020 (12 months).
Bug fixes for security issues in 3.8.x ended 10 May 2021 (18 months).
==Moodle 3.7==
{| class="wikitable"
|-
!Moodle 3.7
|20 May 2019
|2019052000
|[[Moodle 3.7 release notes|Release Notes]]
|[https://docs.moodle.org/37/en/Upgrading Upgrading to 3.7]
|-
!Moodle 3.7.1
|8 July 2019
|2019052001
|[[Moodle 3.7.1 release notes|Release Notes]]
|
|-
!Moodle 3.7.2
|9 September 2019
|2019052002
|[[Moodle 3.7.2 release notes|Release Notes]]
|
|-
!Moodle 3.7.3
|11 November 2019
|2019052003
| [[Moodle 3.7.3 release notes|Release Notes]]
|
|-
!Moodle 3.7.4
|13 January 2020
|2019052004
|[[Moodle 3.7.4 release notes|Release Notes]]
|
|-
!Moodle 3.7.5
|9 March 2020
|2019052005
|[[Moodle 3.7.5 release notes|Release Notes]]
|
|-
!Moodle 3.7.6
|11 May 2020
|2019052006
|[[Moodle 3.7.6 release notes|Release Notes]]
|
|-
!Moodle 3.7.7
|13 July 2020
|2019052007
|[[Moodle 3.7.7 release notes|Release Notes]]
|
|-
!Moodle 3.7.8
|14 September 2020
|2019052008
| [[Moodle 3.7.8 release notes|Release Notes]]
|
|-
!Moodle 3.7.9
|9 November 2020
|2019052009
|[[Moodle 3.7.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.7.x ended 11 May 2020 (12 months).
Bug fixes for security issues in 3.7.x ended 9 November 2020 (18 months).
==Moodle 3.6==
{| class="wikitable"
|-
!Moodle 3.6
| 3 December 2018
|2018120300
|[[Moodle 3.6 release notes|Release Notes]]
|
[https://docs.moodle.org/36/en/Upgrading Upgrading to 3.6]
|-
!Moodle 3.6.1
|5 December 2018
|2018120301
| [[Moodle 3.6.1 release notes|Release Notes]]
|
|-
! Moodle 3.6.2
|14 January 2019
|2018120302
|[[Moodle 3.6.2 release notes|Release Notes]]
|
|-
!Moodle 3.6.3
|11 March 2019
|2018120303
|[[Moodle 3.6.3 release notes|Release Notes]]
|
|-
!Moodle 3.6.4
|13 May 2019
|2018120304
|[[Moodle 3.6.4 release notes|Release Notes]]
|
|-
!Moodle 3.6.5
|8th July 2019
|2018120305
|[[Moodle 3.6.5 release notes|Release Notes]]
|
|-
!Moodle 3.6.6
|9th September 2019
|2018120306
|[[Moodle 3.6.6 release notes|Release Notes]]
|
|-
!Moodle 3.6.7
| 11th November 2019
|2018120307
|[[Moodle 3.6.7 release notes|Release Notes]]
|
|-
!Moodle 3.6.8
|13th January 2020
|2018120308
|[[Moodle 3.6.8 release notes|Release Notes]]
|
|-
!Moodle 3.6.9
|9th March 2020
|2018120309
| [[Moodle 3.6.9 release notes|Release Notes]]
|
|-
!Moodle 3.6.10
|11th May 2020
|2018120310
|[[Moodle 3.6.10 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.6.x ended 11 November 2019 (12 months).
Bug fixes for security issues in 3.6.x ended 11 May 2020 (18 months).
==Moodle 3.5 (LTS)==
{| class="wikitable"
|-
!Moodle 3.5
|17 May 2018
|2018051700
|[[Moodle 3.5 release notes|Release Notes]]
|[https://docs.moodle.org/35/en/Upgrading Upgrading to 3.5]
|-
! Moodle 3.5.1
|9 July 2018
|2018051701
|[[Moodle 3.5.1 release notes|Release Notes]]
|
|-
!Moodle 3.5.2
|10 September 2018
|2018051702
|[[Moodle 3.5.2 release notes|Release Notes]]
|
|-
!Moodle 3.5.3
|12 November 2018
|2018051703
| [[Moodle 3.5.3 release notes|Release Notes]]
|
|-
! Moodle 3.5.4
|14 January 2019
|2018051704
|[[Moodle 3.5.4 release notes|Release Notes]]
|
|-
!Moodle 3.5.5
|11 March 2019
|2018051705
|[[Moodle 3.5.5 release notes|Release Notes]]
|
|-
!Moodle 3.5.6
|13 May 2019
|2018051706
|[[Moodle 3.5.6 release notes|Release Notes]]
|
|-
!Moodle 3.5.7
|8 July 2019
|2018051707
|[[Moodle 3.5.7 release notes|Release Notes]]
|
|-
!Moodle 3.5.8
|9 September 2019
|2018051708
|[[Moodle 3.5.8 release notes|Release Notes]]
|
|-
!Moodle 3.5.9
|11 November 2019
|2018051709
|[[Moodle 3.5.9 release notes|Release Notes]]
|
|-
!Moodle 3.5.10
|13 January 2020
|2018051710
| [[Moodle 3.5.10 release notes|Release Notes]]
|
|-
!Moodle 3.5.11
|9 March 2020
|2018051711
|[[Moodle 3.5.11 release notes|Release Notes]]
|
|-
!Moodle 3.5.12
|11 May 2020
|2018051712
| [[Moodle 3.5.12 release notes|Release Notes]]
|
|-
!Moodle 3.5.13
|13 July 2020
|2018051713
|[[Moodle 3.5.13 release notes|Release Notes]]
|
|-
!Moodle 3.5.14
| 14 September 2020
|2018051714
|[[Moodle 3.5.14 release notes|Release Notes]]
|
|-
!Moodle 3.5.15
|9 November 2020
|2018051715
|[[Moodle 3.5.15 release notes|Release Notes]]
|
|-
!Moodle 3.5.16
|18 January 2021
|2018051716
| [[Moodle 3.5.16 release notes|Release Notes]]
|
|-
!Moodle 3.5.17
|8 March 2021
| 2018051717
|[[Moodle 3.5.17 release notes|Release Notes]]
|
|-
!Moodle 3.5.18
| 10 May 2021
| 2018051718
|[[Moodle 3.5.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.5.x ended May 2019 (12 months).
Bug fixes for security issues in 3.5.x ended 10 May 2021 (36 months).
==Moodle 3.4==
{| class="wikitable"
|-
!Moodle 3.4
|13 November 2017
|2017111300
|[[Moodle 3.4 release notes|Release Notes]]
|
[https://docs.moodle.org/34/en/Upgrading Upgrading to 3.4]
|-
! Moodle 3.4.1
|15 January 2018
|2017111301
|[[Moodle 3.4.1 release notes|Release Notes]]
|
|-
!Moodle 3.4.2
|19 March 2018
|2017111302
|[[Moodle 3.4.2 release notes|Release Notes]]
|
|-
!Moodle 3.4.3
|17 May 2018
|2017111303
|[[Moodle 3.4.3 release notes|Release Notes]]
|
|-
! Moodle 3.4.4
|9 July 2018
|2017111304
|[[Moodle 3.4.4 release notes|Release Notes]]
|
|-
!Moodle 3.4.5
|10 September 2018
|2017111305
|[[Moodle 3.4.5 release notes|Release Notes]]
|
|-
!Moodle 3.4.6
|12 November 2018
|2017111306
| [[Moodle 3.4.6 release notes|Release Notes]]
|
|-
! Moodle 3.4.7
|14 January 2019
|2017111307
|[[Moodle 3.4.7 release notes|Release Notes]]
|
|-
!Moodle 3.4.8
|11 March 2019
|2017111308
|[[Moodle 3.4.8 release notes|Release Notes]]
|
|-
!Moodle 3.4.9
|13 May 2019
|2017111309
| [[Moodle 3.4.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.4.x ended 12 November 2018 (12 months).
Bug fixes for security issues in 3.4.x ended 13 May 2019 (18 months).
==Moodle 3.3==
{| class="wikitable"
|-
!Moodle 3.3
|15 May 2017
|2017051500
|[[Moodle 3.3 release notes|Release Notes]]
|
[https://docs.moodle.org/33/en/Upgrading Upgrading to 3.3]
|-
!Moodle 3.3.1
|10 July 2017
|2017051501
|[[Moodle 3.3.1 release notes|Release Notes]]
|
|-
!Moodle 3.3.2
|11 September 2017
|2017051502
|[[Moodle 3.3.2 release notes|Release Notes]]
|
|-
!Moodle 3.3.3
|13 November 2017
|2017051503
| [[Moodle 3.3.3 release notes|Release Notes]]
|
|-
! Moodle 3.3.4
|15 January 2018
|2017051504
|[[Moodle 3.3.4 release notes|Release Notes]]
|
|-
!Moodle 3.3.5
|19 March 2018
|2017051505
|[[Moodle 3.3.5 release notes|Release Notes]]
|
|-
!Moodle 3.3.6
|17 May 2018
|2017051506
|[[Moodle 3.3.6 release notes|Release Notes]]
|
|-
! Moodle 3.3.7
|9 July 2018
|2017051507
|[[Moodle 3.3.7 release notes|Release Notes]]
|
|-
!Moodle 3.3.8
|10 September 2018
|2017051508
|[[Moodle 3.3.8 release notes|Release Notes]]
|
|-
! Moodle 3.3.9
|12 November 2018
|2017051509
|[[Moodle 3.3.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.3.x ended 17 May 2018 (12 months).
Bug fixes for security issues in 3.3.x ended 12 November 2018 (18 months).
==Moodle 3.2==
{| class="wikitable"
|-
!Moodle 3.2
| 5 December 2016
|2016120500
|[[Moodle 3.2 release notes|Release Notes]]
|[https://docs.moodle.org/32/en/Upgrading Upgrading to 3.2]
|-
!Moodle 3.2.1
|9 January 2017
|2016120501
|[[Moodle 3.2.1 release notes|Release Notes]]
|
|-
!Moodle 3.2.2
|13 March 2017
|2016120502
|[[Moodle 3.2.2 release notes|Release Notes]]
|
|-
!Moodle 3.2.3
|8 May 2017
|2016120503
|[[Moodle 3.2.3 release notes|Release Notes]]
|
|-
!Moodle 3.2.4
|10 July 2017
|2016120504
|[[Moodle 3.2.4 release notes|Release Notes]]
|
|-
!Moodle 3.2.5
|11 September 2017
|2016120505
|[[Moodle 3.2.5 release notes|Release Notes]]
|
|-
!Moodle 3.2.6
|13 November 2017
|2016120506
| [[Moodle 3.2.6 release notes|Release Notes]]
|
|-
! Moodle 3.2.7
|15 January 2018
|2016120507
|[[Moodle 3.2.7 release notes|Release Notes]]
|
|-
!Moodle 3.2.8
|19 March 2018
|2016120508
|[[Moodle 3.2.8 release notes|Release Notes]]
|
|-
!Moodle 3.2.9
|17 May 2018
|2016120509
| [[Moodle 3.2.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.2.x ended 13 November 2017 (12 months).
Bug fixes for security issues in 3.2.x ended 17 May 2018 (18 months).
==Moodle 3.1 (LTS)==
{| class="wikitable"
|-
!Moodle 3.1
|23 May 2016
|2016052300
|[[Moodle 3.1 release notes|Release Notes]]
|
[https://docs.moodle.org/31/en/Upgrading Upgrading to 3.1]
|-
!Moodle 3.1.1
|11 July 2016
|2016052301
|[[Moodle 3.1.1 release notes|Release Notes]]
|
|-
!Moodle 3.1.2
|12 September 2016
|2016052302
|[[Moodle 3.1.2 release notes|Release Notes]]
|
|-
!Moodle 3.1.3
|14 November 2016
|2016052303
|[[Moodle 3.1.3 release notes|Release Notes]]
|
|-
!Moodle 3.1.4
|9 January 2017
|2016052304
|[[Moodle 3.1.4 release notes|Release Notes]]
|
|-
!Moodle 3.1.5
|13 March 2017
|2016052305
|[[Moodle 3.1.5 release notes|Release Notes]]
|
|-
!Moodle 3.1.6
|8 May 2017
|2016052306
|[[Moodle 3.1.6 release notes|Release Notes]]
|
|-
!Moodle 3.1.7
|10 July 2017
|2016052307
|[[Moodle 3.1.7 release notes|Release Notes]]
|
|-
!Moodle 3.1.8
|11 September 2017
|2016052308
|[[Moodle 3.1.8 release notes|Release Notes]]
|
|-
!Moodle 3.1.9
|13 November 2017
|2016052309
|[[Moodle 3.1.9 release notes|Release Notes]]
|
|-
!Moodle 3.1.10
|15 January 2018
|2016052310
|[[Moodle 3.1.10 release notes|Release Notes]]
|
|-
! Moodle 3.1.11
|19 March 2018
|2016052311
|[[Moodle 3.1.11 release notes|Release Notes]]
|
|-
!Moodle 3.1.12
|17 May 2018
|2016052312
|[[Moodle 3.1.12 release notes|Release Notes]]
|
|-
!Moodle 3.1.13
|9 July 2018
|2016052313
|[[Moodle 3.1.13 release notes|Release Notes]]
|
|-
!Moodle 3.1.14
|10 September 2018
|2016052314
|[[Moodle 3.1.14 release notes|Release Notes]]
|
|-
! Moodle 3.1.15
|12 November 2018
|2016052315
|[[Moodle 3.1.15 release notes|Release Notes]]
|
|-
!Moodle 3.1.16
|14 January 2019
|2016052316
|[[Moodle 3.1.16 release notes|Release Notes]]
|
|-
! Moodle 3.1.17
|11 March 2019
| 2016052317
|[[Moodle 3.1.17 release notes|Release Notes]]
|
|-
!Moodle 3.1.18
|13 May 2019
|2016052318
|[[Moodle 3.1.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.1.x ended 8 May 2017 (12 months).
Bug fixes for security issues in 3.1.x ended 13 May 2019 (36 months).
==Moodle 3.0==
{| class="wikitable"
|-
!Moodle 3.0
|16 November 2015
|2015111600
|[[Moodle 3.0 release notes|Release Notes]]
|[https://docs.moodle.org/30/en/Upgrading Upgrading to 3.0]
|-
!Moodle 3.0.1
|21 December 2015
|2015111601
| [[Moodle 3.0.1 release notes|Release Notes]]
|
|-
! Moodle 3.0.2
|11 January 2016
|2015111602
|[[Moodle 3.0.2 release notes|Release Notes]]
|
|-
!Moodle 3.0.3
|14 March 2016
|2015111603
|[[Moodle 3.0.3 release notes|Release Notes]]
|
|-
!Moodle 3.0.4
|9 May 2016
|2015111604
|[[Moodle 3.0.4 release notes|Release Notes]]
|
|-
!Moodle 3.0.5
|11 July 2016
|2015111605
|[[Moodle 3.0.5 release notes|Release Notes]]
|
|-
!Moodle 3.0.6
|12 September 2016
|2015111606
|[[Moodle 3.0.6 release notes|Release Notes]]
|
|-
!Moodle 3.0.7
|14 November 2016
|2015111607
|[[Moodle 3.0.7 release notes|Release Notes]]
|
|-
!Moodle 3.0.8
|9 January 2017
|2015111608
|[[Moodle 3.0.8 release notes|Release Notes]]
|
|-
!Moodle 3.0.9
|13 March 2017
|2015111609
|[[Moodle 3.0.9 release notes|Release Notes]]
|
|-
!Moodle 3.0.10
|8 May 2017
|2015111610
|[[Moodle 3.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.0.x ended 14 November 2016 (12 months).
Bug fixes for security issues in 3.0.x ended 8 May 2017 (18 months).
==Moodle 2.9==
{| class="wikitable"
|-
!Moodle 2.9
| 11 May 2015
|2015051100
|[[Moodle 2.9 release notes|Release Notes]]
| [https://docs.moodle.org/29/en/Upgrading_to_Moodle_2.9 Upgrading to 2.9]
|-
! Moodle 2.9.1
|6 July 2015
|2015051101
|[[Moodle 2.9.1 release notes|Release Notes]]
|
|-
!Moodle 2.9.2
|14 September 2015
|2015051102
| [[Moodle 2.9.2 release notes|Release Notes]]
|
|-
!Moodle 2.9.3
|9 November 2015
|2015051103
| [[Moodle 2.9.3 release notes|Release Notes]]
|
|-
! Moodle 2.9.4
|11 January 2016
|2015051104
|[[Moodle 2.9.4 release notes|Release Notes]]
|
|-
!Moodle 2.9.5
|14 March 2016
|2015051105
|[[Moodle 2.9.5 release notes|Release Notes]]
|
|-
!Moodle 2.9.6
|9 May 2016
|2015051106
|[[Moodle 2.9.6 release notes|Release Notes]]
|
|-
!Moodle 2.9.7
|11 July 2016
|2015051107
|[[Moodle 2.9.7 release notes|Release Notes]]
|
|-
!Moodle 2.9.8
|12 September 2016
|2015051108
|[[Moodle 2.9.8 release notes|Release Notes]]
|
|-
! Moodle 2.9.9
|14 November 2016
|2015051109
|[[Moodle 2.9.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.9.x ended 9 May 2016 (12 months).
Bug fixes for security issues in 2.9.x ended 14 November 2016 (18 months).
==Moodle 2.8==
{| class="wikitable"
|-
!Moodle 2.8
|10 November 2014
|2014111000
| [[Moodle 2.8 release notes|Release Notes]]
|[https://docs.moodle.org/28/en/Upgrading_to_Moodle_2.8 Upgrading to 2.8]
|-
!Moodle 2.8.1
|13 November 2014
|2014111001
| [[Moodle 2.8.1 release notes|Release Notes]]
|
|-
!Moodle 2.8.2
|12 January 2015
|2014111002
| [[Moodle 2.8.2 release notes|Release Notes]]
|
|-
!Moodle 2.8.3
|2 February 2015
|2014111003
|[[Moodle 2.8.3 release notes|Release Notes]]
|
|-
!Moodle 2.8.4
|9 March 2015
|2014111004
|[[Moodle 2.8.4 release notes|Release Notes]]
|
|-
!Moodle 2.8.5
|10 March 2015
|2014111005
|[[Moodle 2.8.5 release notes|Release Notes]]
|
|-
!Moodle 2.8.6
|11 May 2015
|2014111006
|[[Moodle 2.8.6 release notes|Release Notes]]
|
|-
! Moodle 2.8.7
|6 July 2015
|2014111007
|[[Moodle 2.8.7 release notes|Release Notes]]
|
|-
!Moodle 2.8.8
|14 September 2015
|2014111008
| [[Moodle 2.8.8 release notes|Release Notes]]
|
|-
!Moodle 2.8.9
|9 November 2015
|2014111009
|[[Moodle 2.8.9 release notes|Release Notes]]
|
|-
!Moodle 2.8.10
|11 January 2016
|2014111010
|[[Moodle 2.8.10 release notes|Release Notes]]
|
|-
!Moodle 2.8.11
|14 March 2016
|2014111011
|[[Moodle 2.8.11 release notes|Release Notes]]
|
|-
!Moodle 2.8.12
|9 May 2016
|2014111012
| [[Moodle 2.8.12 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.8.x ended 9 November 2015 (12 months).
Bug fixes for security issues in 2.8.x ended 9 May 2016 (18 months).
==Moodle 2.7 (LTS)==
{| class="wikitable"
|-
!Moodle 2.7
| 12 May 2014
|2014051200
|[[Moodle 2.7 release notes|Release Notes]]
|[https://docs.moodle.org/27/en/Upgrading_to_Moodle_2.7 Upgrading to 2.7]
|-
! Moodle 2.7.1
|14 July 2014
|2014051201
|[[Moodle 2.7.1 release notes|Release Notes]]
|
|-
!Moodle 2.7.2
|8 September 2014
|2014051202
|[[Moodle 2.7.2 release notes|Release Notes]]
|
|-
!Moodle 2.7.3
|10 November 2014
|2014051203
| [[Moodle 2.7.3 release notes|Release Notes]]
|
|-
!Moodle 2.7.4
|12 January 2015
|2014051204
| [[Moodle 2.7.4 release notes|Release Notes]]
|
|-
!Moodle 2.7.5
|2 February 2015
|2014051205
|[[Moodle 2.7.5 release notes|Release Notes]]
|
|-
!Moodle 2.7.6
|9 March 2015
|2014051206
|[[Moodle 2.7.6 release notes|Release Notes]]
|
|-
!Moodle 2.7.7
|10 March 2015
|2014051207
|[[Moodle 2.7.7 release notes|Release Notes]]
|
|-
!Moodle 2.7.8
|11 May 2015
|2014051208
|[[Moodle 2.7.8 release notes|Release Notes]]
|
|-
!Moodle 2.7.9
|6 July 2015
|2014051209
|[[Moodle 2.7.9 release notes|Release Notes]]
|
|-
!Moodle 2.7.10
| 14 September 2015
|2014051210
|[[Moodle 2.7.10 release notes|Release Notes]]
|
|-
!Moodle 2.7.11
|9 November 2015
|2014051211
|[[Moodle 2.7.11 release notes|Release Notes]]
|
|-
!Moodle 2.7.12
|11 January 2016
|2014051212
|[[Moodle 2.7.12 release notes|Release Notes]]
|
|-
!Moodle 2.7.13
|14 March 2016
|2014051213
|[[Moodle 2.7.13 release notes|Release Notes]]
|
|-
!Moodle 2.7.14
|9 May 2016
|2014051214
| [[Moodle 2.7.14 release notes|Release Notes]]
|
|-
!Moodle 2.7.15
|11 July 2016
|2014051215
|[[Moodle 2.7.15 release notes|Release Notes]]
|
|-
!Moodle 2.7.16
|12 September 2016
|2014051216
|[[Moodle 2.7.16 release notes|Release Notes]]
|
|-
!Moodle 2.7.17
|14 November 2016
|2014051217
|[[Moodle 2.7.17 release notes|Release Notes]]
|
|-
!Moodle 2.7.18
|9 January 2017
|2014051218
|[[Moodle 2.7.18 release notes|Release Notes]]
|
|-
!Moodle 2.7.19
|13 March 2017
|2014051219
|[[Moodle 2.7.19 release notes|Release Notes]]
|
|-
!Moodle 2.7.20
|8 May 2017
|2014051220
| [[Moodle 2.7.20 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.7.x ended 11 May 2015 (12 months).
Bug fixes for security issues in 2.7.x ended 8 May 2017 (36 months).
==Moodle 2.6==
{| class="wikitable"
|-
!Moodle 2.6
|18 November 2013
|2013111800
|[[Moodle 2.6 release notes|Release Notes]]
|[https://docs.moodle.org/26/en/Upgrading_to_Moodle_2.6 Upgrading to 2.6]
|-
!Moodle 2.6.1
|13 January 2014
| 2013111801
| [[Moodle 2.6.1 release notes|Release Notes]]
|
|-
!Moodle 2.6.2
|10 March 2014
|2013111802
|[[Moodle 2.6.2 release notes|Release Notes]]
|
|-
!Moodle 2.6.3
|12 May 2014
|2013111803
|[[Moodle 2.6.3 release notes|Release Notes]]
|
|-
!Moodle 2.6.4
|14 July 2014
|2013111804
|[[Moodle 2.6.4 release notes|Release Notes]]
|
|-
!Moodle 2.6.5
|8 September 2014
|2013111805
|[[Moodle 2.6.5 release notes|Release Notes]]
|
|-
!Moodle 2.6.6
|10 November 2014
|2013111806
|[[Moodle 2.6.6 release notes|Release Notes]]
|
|-
!Moodle 2.6.7
|12 January 2015
|2013111807
|[[Moodle 2.6.7 release notes|Release Notes]]
|
|-
! Moodle 2.6.8
|2 February 2015
|2013111808
|[[Moodle 2.6.8 release notes|Release Notes]]
|
|-
! Moodle 2.6.9
|9 March 2015
|2013111809
|[[Moodle 2.6.9 release notes|Release Notes]]
|
|-
!Moodle 2.6.10
|10 March 2015
|2013111810
| [[Moodle 2.6.10 release notes|Release Notes]]
|
|-
!Moodle 2.6.11
|11 May 2015
|2013111811
|[[Moodle 2.6.11 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 2.6.x ended 10 November 2014 (12 months).
Bug fixes for security issues in 2.6.x ended 11 May 2015 (18 months).
==Moodle 2.5==
{| class="wikitable"
|-
!Moodle 2.5
| 14 May 2013
|2013051400
|[[Moodle 2.5 release notes|Release Notes]]
| [https://docs.moodle.org/25/en/Upgrading_to_Moodle_2.5 Upgrading to 2.5]
|-
! Moodle 2.5.1
|8 July 2013
|2013051401
|[[Moodle 2.5.1 release notes|Release Notes]]
|
|-
!Moodle 2.5.2
|9 September 2013
|2013051402
|[[Moodle 2.5.2 release notes|Release Notes]]
|
|-
!Moodle 2.5.3
|11 November 2013
|2013051403
|[[Moodle 2.5.3 release notes|Release Notes]]
|
|-
!Moodle 2.5.4
|13 January 2014
| 2013051404
| [[Moodle 2.5.4 release notes|Release Notes]]
|
|-
!Moodle 2.5.5
|10 March 2014
|2013051405
|[[Moodle 2.5.5 release notes|Release Notes]]
|
|-
!Moodle 2.5.6
|12 May 2014
|2013051406
|[[Moodle 2.5.6 release notes|Release Notes]]
|
|-
!Moodle 2.5.7
|14 July 2014
|2013051407
|[[Moodle 2.5.7 release notes|Release Notes]]
|
|-
!Moodle 2.5.8
|8 September 2014
|2013051408
|[[Moodle 2.5.8 release notes|Release Notes]]
|
|-
! Moodle 2.5.9
| 10 November 2014
|2013051409
|[[Moodle 2.5.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.5.x ended May 2014 (12 months).
Bug fixes for security issues in 2.5.x ended 10 November 2014 (18 months).
==Moodle 2.4==
{| class="wikitable"
|-
! Moodle 2.4
|3 December 2012
|2012120300
|[[Moodle 2.4 release notes|Release Notes]]
|[https://docs.moodle.org/24/en/Upgrading_to_Moodle_2.4 Upgrading to 2.4]
|-
! Moodle 2.4.1
|14 January 2013
|2012120301
|[[Moodle 2.4.1 release notes|Release Notes]]
|
|-
!Moodle 2.4.2
|11 March 2013
|2012120302
|[[Moodle 2.4.2 release notes|Release Notes]]
|
|-
!Moodle 2.4.3
|18 March 2013
|2012120303
|[[Moodle 2.4.3 release notes|Release Notes]]
|
|-
!Moodle 2.4.4
|14 May 2013
|2012120304
|[[Moodle 2.4.4 release notes|Release Notes]]
|
|-
!Moodle 2.4.5
|8 July 2013
|2012120305
|[[Moodle 2.4.5 release notes|Release Notes]]
|
|-
!Moodle 2.4.6
|9 September 2013
|2012120306
|[[Moodle 2.4.6 release notes|Release Notes]]
|
|-
!Moodle 2.4.7
|11 November 2013
|2012120307
| [[Moodle 2.4.7 release notes|Release Notes]]
|
|-
! Moodle 2.4.8
|13 January 2014
|2012120308
|[[Moodle 2.4.8 release notes|Release Notes]]
|
|-
!Moodle 2.4.9
|10 March 2014
|2012120309
|[[Moodle 2.4.9 release notes|Release Notes]]
|
|-
!Moodle 2.4.10
|12 May 2014
|2012120310
| [[Moodle 2.4.10 release notes|Release Notes]]
|
|-
!Moodle 2.4.11
|14 July 2014
|2012120311
|[[Moodle 2.4.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.4.x ended December 2013 (12 months).
Bug fixes for security issues in 2.4.x ended June 2014 (18 months).
==Moodle 2.3==
{| class="wikitable"
|-
!Moodle 2.3
|25 June 2012
|2012062500
|[[Moodle 2.3 release notes|Release Notes]]
| [https://docs.moodle.org/23/en/Upgrading_to_Moodle_2.3 Upgrading to 2.3]
|-
!Moodle 2.3.1
|9 July 2012
|2012062501
|[[Moodle 2.3.1 release notes|Release Notes]]
|
|-
! Moodle 2.3.2
|10 September 2012
|2012062502
|[[Moodle 2.3.2 release notes|Release Notes]]
|
|-
!Moodle 2.3.3
|12 November 2012
|2012062503
|[[Moodle 2.3.3 release notes|Release Notes]]
|
|-
! Moodle 2.3.4
|14 January 2013
|2012062504
|[[Moodle 2.3.4 release notes|Release Notes]]
|
|-
!Moodle 2.3.5
|11 March 2013
|2012062505
|[[Moodle 2.3.5 release notes|Release Notes]]
|
|-
!Moodle 2.3.6
|18 March 2013
|2012062506
|[[Moodle 2.3.6 release notes|Release Notes]]
|
|-
!Moodle 2.3.7
|14 May 2013
|2012062507
|[[Moodle 2.3.7 release notes|Release Notes]]
|
|-
!Moodle 2.3.8
|8 July 2013
|2012062508
|[[Moodle 2.3.8 release notes|Release Notes]]
|
|-
!Moodle 2.3.9
|9 September 2013
|2012062509
|[[Moodle 2.3.9 release notes|Release Notes]]
|
|-
! Moodle 2.3.10
|11 November 2013
|2012062510
|[[Moodle 2.3.10 release notes|Release Notes]]
|
|-
!Moodle 2.3.11
|13 January 2014
|2012062511
|[[Moodle 2.3.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.3.x ended June 2013 (12 months).
Bug fixes for security issues in 2.3.x ended December 2013 (18 months).
==Moodle 2.2==
{| class="wikitable"
|-
! Moodle 2.2
|5 December 2011
|2011120500
|[[Moodle 2.2 release notes|Release Notes]]
|[https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 Upgrading to 2.2]
|-
!Moodle 2.2.1
|9 January 2012
|2011120501
|[[Moodle 2.2.1 release notes|Release Notes]]
|
|-
!Moodle 2.2.2
|12 March 2012
|2011120502
|[[Moodle 2.2.2 release notes|Release Notes]]
|
|-
!Moodle 2.2.3
|14 May 2012
|2011120503
|[[Moodle 2.2.3 release notes|Release Notes]]
|
|-
! Moodle 2.2.4
|9 July 2012
|2011120504
|[[Moodle 2.2.4 release notes|Release Notes]]
|
|-
!Moodle 2.2.5
|10 September 2012
|2011120505
|[[Moodle 2.2.5 release notes|Release Notes]]
|
|-
!Moodle 2.2.6
|12 November 2012
|2011120506
| [[Moodle 2.2.6 release notes|Release Notes]]
|
|-
! Moodle 2.2.7
|14 January 2013
|2011120507
|[[Moodle 2.2.7 release notes|Release Notes]]
|
|-
!Moodle 2.2.8
|11 March 2013
|2011120508
|[[Moodle 2.2.8 release notes|Release Notes]]
|
|-
!Moodle 2.2.9
|18 March 2013
|2011120509
|[[Moodle 2.2.9 release notes|Release Notes]]
|
|-
!Moodle 2.2.10
|14 May 2013
| 2011120510
|[[Moodle 2.2.10 release notes|Release Notes]]
|
|-
!Moodle 2.2.11
|8 July 2013
|2011120511
|[[Moodle 2.2.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.2.x ended December 2012 (12 months).
Bug fixes for security issues in 2.2.x ended June 2013 (18 months).
==Moodle 2.1==
{| class="wikitable"
|-
!Moodle 2.1
| 1 July 2011
|2011070100
|[[Moodle 2.1 release notes|Release Notes]]
|[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to 2.1]
|-
! Moodle 2.1.1
|1 August 2011
|2011070101
| [[Moodle 2.1.1 release notes|Release Notes]]
|
|-
!Moodle 2.1.2
|10 October 2011
|2011070102
|[[Moodle 2.1.2 release notes|Release Notes]]
|
|-
!Moodle 2.1.3
|28 November 2011
|2011070103
|[[Moodle 2.1.3 release notes|Release Notes]]
|
|-
!Moodle 2.1.4
|9 January 2012
|2011070104
|[[Moodle 2.1.4 release notes|Release Notes]]
|
|-
!Moodle 2.1.5
|12 March 2012
|2011070105
|[[Moodle 2.1.5 release notes|Release Notes]]
|
|-
!Moodle 2.1.6
|14 May 2012
|2011070106
|[[Moodle 2.1.6 release notes|Release Notes]]
|
|-
! Moodle 2.1.7
|9 July 2012
|2011070107
|[[Moodle 2.1.7 release notes|Release Notes]]
|
|-
!Moodle 2.1.8
|10 September 2012
|2011070108
|[[Moodle 2.1.8 release notes|Release Notes]]
|
|-
!Moodle 2.1.9
|12 November 2012
|2011070109
|[[Moodle 2.1.9 release notes|Release Notes]]
|
|-
!Moodle 2.1.10
|14 January 2013
|2011070110
|[[Moodle 2.1.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.1.x ended June 2012 (12 months).
Bug fixes for security issues in 2.1.x ended December 2012 (18 months).
==Moodle 2.0==
{| class="wikitable"
|-
!Moodle 2.0
|24 November 2010
|2010112400
| [[Moodle 2.0 release notes|Release Notes]]
|[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to 2.0]
|-
!Moodle 2.0.1
|25 December 2010
|2010122500
|[[Moodle 2.0.1 release notes|Release Notes]]
|
|-
!Moodle 2.0.2
|21 February 2011
|2011022100
|[[Moodle 2.0.2 release notes|Release Notes]]
|
|-
!Moodle 2.0.3
|5 May 2011
|2011033003
|[[Moodle 2.0.3 release notes|Release Notes]]
|
|-
! Moodle 2.0.4
|1 August 2011
|2011033004
| [[Moodle 2.0.4 release notes|Release Notes]]
|
|-
!Moodle 2.0.5
|10 October 2011
|2011033005
|[[Moodle 2.0.5 release notes|Release Notes]]
|
|-
!Moodle 2.0.6
|28 November 2011
|2011033006
|[[Moodle 2.0.6 release notes|Release Notes]]
|
|-
!Moodle 2.0.7
|9 January 2012
|2011033007
|[[Moodle 2.0.7 release notes|Release Notes]]
|
|-
!Moodle 2.0.8
|12 March 2012
|2011033008
|[[Moodle 2.0.8 release notes|Release Notes]]
|
|-
!Moodle 2.0.9
|14 May 2012
|2011033009
|[[Moodle 2.0.9 release notes|Release Notes]]
|
|-
!Moodle 2.0.10
|9 July 2012
|2011033010
|[[Moodle 2.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.0.x ended December 2011 (12 months).
Bug fixes for security issues in 2.0.x ended June 2012 (18 months).
==Moodle 1.9==
{| class="wikitable"
|-
!Moodle 1.9
|3 March 2008
|2007101509
|[[Moodle 1.9 release notes|Release Notes]]
|[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to 1.9]
|-
!Moodle 1.9.1
|15 May 2008
| 2007101512
|[[Moodle 1.9.1 release notes|Release Notes]]
|
|-
! Moodle 1.9.2
|11 July 2008
|2007101520
|[[Moodle 1.9.2 release notes|Release Notes]]
|
|-
!Moodle 1.9.3
|15 October 2008
|2007101530
|[[Moodle 1.9.3 release notes|Release Notes]]
|
|-
!Moodle 1.9.4
|28 January 2009
|2007101540
|[[Moodle 1.9.4 release notes|Release Notes]]
|
|-
!Moodle 1.9.5
|13 May 2009
|2007101550
|[[Moodle 1.9.5 release notes|Release Notes]]
|
|-
!Moodle 1.9.6
|21 October 2009
|2007101560
|[[Moodle 1.9.6 release notes|Release Notes]]
|
|-
!Moodle 1.9.7
|25 November 2009
|2007101570
|[[Moodle 1.9.7 release notes|Release Notes]]
|
|-
!Moodle 1.9.8
|25 March 2010
|2007101580.00
|[[Moodle 1.9.8 release notes|Release Notes]]
|
|-
! Moodle 1.9.9
| 8 June 2010
| 2007101590.00
| [[Moodle 1.9.9 release notes|Release Notes]]
|
|-
!Moodle 1.9.10
|25 October 2010
|2007101591.00
|
[[Moodle 1.9.10 release notes|Release Notes]]
|
|-
!Moodle 1.9.11
|21 February 2011
|2007101591.02
|[[Moodle 1.9.11 release notes|Release Notes]]
|
|-
! Moodle 1.9.12
|10 May 2011
|2007101591.03
|[[Moodle 1.9.12 release notes|Release Notes]]
|
|-
!Moodle 1.9.13
|1 August 2011
|2007101591.04
|[[Moodle 1.9.13 release notes|Release Notes]]
|
|-
!Moodle 1.9.14
|10 October 2011
|2007101591.06
|
[[Moodle 1.9.14 release notes|Release Notes]]
|
|-
!Moodle 1.9.15
|28 November 2011
| 2007101591.07
| [[Moodle 1.9.15 release notes|Release Notes]]
|
|-
!Moodle 1.9.16
|9 January 2012
|2007101591.10
|[[Moodle 1.9.16 release notes|Release Notes]]
|
|-
! Moodle 1.9.17
|12 March 2012
|2007101591.12
|[[Moodle 1.9.17 release notes|Release Notes]]
|
|-
!Moodle 1.9.18
|14 May 2012
|2007101591.16
|[[Moodle 1.9.18 release notes|Release Notes]]
|
|-
! Moodle 1.9.19
|9 July 2012
|2007101592.00
|[[Moodle 1.9.19 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 1.9.x has ended June 2011 (3.5 years).
Bug fixes for security issues in 1.9.x by Moodle HQ ended June 2012 (4.5 years).
Bug fixes for security issues in 1.9.19+ branch by [http://catalyst.net.nz Catalyst IT] ended [http://moodle.org/mod/forum/discuss.php?d=199706 Dec 2013] (6 years).
==Moodle 1.8 ==
*[[Moodle 1.8 release notes|Moodle 1.8]] - 30 March 2007
*[[Moodle 1.8.1 release notes|Moodle 1.8.1]] - 14 June 2007
*[[Moodle 1.8.2 release notes|Moodle 1.8.2]] - 8 July 2007
*[[Moodle 1.8.3 release notes|Moodle 1.8.3]] - 11 October 2007
*[[Moodle 1.8.4 release notes|Moodle 1.8.4]] - 11 January 2008
*[[Moodle 1.8.5 release notes|Moodle 1.8.5]] - 8 April 2008
*[[Moodle 1.8.6 release notes|Moodle 1.8.6]] - 11 July 2008
*[[Moodle 1.8.7 release notes|Moodle 1.8.7]] - 15 October 2008
*[[Moodle 1.8.8 release notes|Moodle 1.8.8]] - 28 January 2009
*[[Moodle 1.8.9 release notes|Moodle 1.8.9]] - 15 May 2009
*[[Moodle 1.8.10 release notes|Moodle 1.8.10]] - 26 October 2009
*[[Moodle 1.8.11 release notes|Moodle 1.8.11]] - 25 November 2009
*[[Moodle 1.8.12 release notes|Moodle 1.8.12]] - 27 March 2010
*[[Moodle 1.8.13 release notes|Moodle 1.8.13]] - 8 June 2010
*[[Moodle 1.8.14 release notes|Moodle 1.8.14]] - 3 December 2010
*Support has ended

==Moodle 1.7==
*[[Moodle 1.7 release notes|Moodle 1.7]] - 7 November 2006
*[[Moodle 1.7.1 release notes|Moodle 1.7.1]] - 17 January 2007
*[[Moodle 1.7.2 release notes|Moodle 1.7.2]] - 30 March 2007
*[[Moodle 1.7.3 release notes|Moodle 1.7.3]] - 11 October 2007
*[[Moodle 1.7.4 release notes|Moodle 1.7.4]] - 11 January 2008
*[[Moodle 1.7.5 release notes|Moodle 1.7.5]] - 11 July 2008
*[[Moodle 1.7.6 release notes|Moodle 1.7.6]] - 15 October 2008
*[[Moodle 1.7.7 release notes|Moodle 1.7.7]] - 28 January 2009
*Support has ended
==Moodle 1.6==
*[[Moodle 1.6 release notes|Moodle 1.6]] - 20 June 2006
*[[Moodle 1.6.1 release notes|Moodle 1.6.1]] - 20 July 2006
*[[Moodle 1.6.2 release notes|Moodle 1.6.2]] - 12 September 2006
*[[Moodle 1.6.3 release notes|Moodle 1.6.3]] - 10 October 2006
*[[Moodle 1.6.4 release notes|Moodle 1.6.4]] - 17 January 2007
*[[Moodle 1.6.5 release notes|Moodle 1.6.5]] - 30 March 2007
*Moodle 1.6.6 - 11 January 2008
*Moodle 1.6.7 - 11 July 2008
*[[Moodle 1.6.8 release notes|Moodle 1.6.8]] - 15 October 2008
*[[Moodle 1.6.9 release notes|Moodle 1.6.9]] - 28 January 2009
* Support has ended
==Moodle 1.5==
*[[Moodle 1.5 release notes|Moodle 1.5]] - 5 June 2005
*[[Moodle 1.5.1 release notes|Moodle 1.5.1]] - 8 July 2005
*[[Moodle 1.5.2 release notes|Moodle 1.5.2]] - 16 July 2005
*[[Moodle 1.5.3 release notes|Moodle 1.5.3]] - 11 November 2005
*[[Moodle 1.5.4 release notes|Moodle 1.5.4]] - 21 May 2006
*Support has ended
==Moodle 1.4==
*Moodle 1.4 - 31 August 2004
*Moodle 1.4.1 - 12 September 2004
*Moodle 1.4.2 - 5 November 2004
*Moodle 1.4.3 - 21 December 2004
*Moodle 1.4.4 - 7 March 2005
*[[Moodle 1.4.5 release notes|Moodle 1.4.5]] - 7 May 2005
*Support has ended
==Moodle 1.3==
*Moodle 1.3 - 25 May 2004
* Moodle 1.3.1 - 4 June 2004
*Moodle 1.3.2 - 9 July 2004
*Moodle 1.3.3 - 16 July 2004
* Moodle 1.3.4 - 11 August 2004
*Moodle 1.3.5 - 9 September 2004
*Support has ended
==Moodle 1.2==
*Moodle 1.2 - 20 March 2004
*Moodle 1.2.1 - 25 March 2004
*Support has ended
==Moodle 1.1==
*Moodle 1.1 - 29 August 2003
*Moodle 1.1.1 - 11 September 2003
*Support has ended
== Moodle 1.0==
*Moodle 1.0 - 20 August 2002
*Moodle 1.0.1 - 26 August 2002
*Moodle 1.0.2 - 2 September 2002
*Moodle 1.0.3 - 5 September 2002
*Moodle 1.0.4 - 10 September 2002
*Moodle 1.0.5 - 27 September 2002
* Moodle 1.0.6 - 26 October 2002
::1.0.6.1 - 6 November 2002
::1.0.6.2 - 11 November 2002
::1.0.6.3 - 14 November 2002
::1.0.6.4 - 25 November 2002
*Moodle 1.0.7 - 9 December 2002
*Moodle 1.0.8 - 7 January 2003
*Moodle 1.0.9 - 30 May 2003
*Support has ended
==See also==
*[[Roadmap]] - future versions
*[[Moodle versions]] - an explanation of how our versions work plus version numbers for each release (for $plugin->requires)
[[Category:Release notes]]
[[Category:Core development]]
[[fr:Historique des versions]]
[[es:dev/Historia de las versiones]]
[[de:Versionshistorie]]

Releases

2022-03-14T07:46:41Z

Abgreeve: /* Moodle 3.10.10 detail update */

This page lists all official releases of Moodle, grouped by branch in reverse chronological order.
==Version support==
From Moodle 2.6 onwards, the end of support, both general and security, happens the second Monday of May and November, observing the 12, 18... month periods, no matter if the major release date was moved or not.

The most recent [https://en.wikipedia.org/wiki/Long-term_support long-term support release (LTS)] version is Moodle 3.9.
{| class="wikitable" border="1px solid #dee2e6;"
|-
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Version
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Release status
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Initial release
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:rgba(0, 0, 0, 0.05);" | General support ends
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Security support ends
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.9 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 15 June 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 10 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 November 2023 (ext 6M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.10
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 9 November 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 8 November 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 9 May 2022
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.11
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 17 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 14 Nov 2022 (ext 6M)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 Nov 2023 (ext 12M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |4.0
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |April 2022
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |May 2023
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |November 2023
|-
|4.1 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
|November 2022
|November 2023
|November 2025
|}
[[Image:releasescurrent.png|alt=Release graph]]

Release graph key:
{| class="wikitable" border="1px solid #dee2e6;"
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Currently supported stable releases.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | Current release of versions still receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Future point releases receiving bug fixes, as well as security updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#316d5e; color:white; adding: .3rem 0.5rem 0.3rem 0.5rem;" |Future security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Future point releases receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#686566; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Previously released versions containing bug fixes, as well as security updates. Updating to a currently supported version is recommended.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#282828; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Previously released versions containing security updates only. Updating to a currently supported version is recommended.
|}
==General release calendar==
These are the target dates for releases. These dates may vary slightly due to unforeseen circumstances.
{| class="wikitable"
|-
!Release type
!Frequency
!Months
|-
|[[Process#Major_release_cycles|Major]] (eg. 3.x)
|6 monthly
|Second Monday of May and November
|-
|[[Process#Stable_maintenance_cycles|Minor]] (Point) (eg. 3.x.y)
| 2 monthly
|Second Monday of July, September, November, March and May.
Third Monday of January.
|}
All releases are preceded by a one week warning. Upcoming release dates can be found in the [https://www.google.com/calendar/ical/moodle.com_p4c2oe7hsb77ltaro5qtihb5d4%40group.calendar.google.com/public/basic.ics Moodle development calendar] (Note, this is an iCAL link that will try to add the dates to your personal calendar. If you just want to browse the dates online, use [https://calendar.google.com/calendar/embed?src=moodle.com_p4c2oe7hsb77ltaro5qtihb5d4@group.calendar.google.com&pli=1 this link].).
==Moodle 3.11==
{| class="wikitable"
|-
!Moodle 3.11
|17 May 2021
|2021051700
|[[Moodle 3.11 release notes|Release Notes]]
|[https://docs.moodle.org/311/en/Upgrading Upgrading to 3.11]
|-
!Moodle 3.11.1
|12 July 2021
|2021051701
|[[Moodle 3.11.1 release notes|Release Notes]]
|
|-
!Moodle 3.11.2
|29 July 2021
|2021051702
|[[Moodle 3.11.2 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.11.3
|13 September 2021
|2021051703
|[[Moodle 3.11.3 release notes|Release Notes]]
|
|-
! Moodle 3.11.4
|8 November 2021
|2021051704
|[[Moodle 3.11.4 release notes|Release Notes]]
|
|-
! Moodle 3.11.5
|17 January 2022
|2021051705
|[[Moodle 3.11.5 release notes|Release Notes]]
|-
! Moodle 3.11.6
|14 March 2022
|2021051706
|[[Moodle 3.11.6 release notes|Release Notes]]
|}
Bug fixes for general core bugs in 3.11.x will end 14 Nov 2022 (12 months plus 6 months extension).
Bug fixes for security issues in 3.11.x will end 13 Nov 2023 (18 months plus 12 months extension).

==Moodle 3.10==
{| class="wikitable"
|-
! Moodle 3.10
|9 November 2020
|2020110900
|
[[Moodle 3.10 release notes|Release Notes]]
|[https://docs.moodle.org/310/en/Upgrading Upgrading to 3.10]
|-
!Moodle 3.10.1
|18 January 2021
|2020110901
| [[Moodle 3.10.1 release notes|Release Notes]]
|
|-
!Moodle 3.10.2
|8 March 2021
|2020110902
|[[Moodle 3.10.2 release notes|Release Notes]]
|
|-
! Moodle 3.10.3
|25 March 2021
|2020110903
|[[Moodle 3.10.3 release notes|Release Notes]]
|
|-
!Moodle 3.10.4
|10 May 2021
|2020110904
|[[Moodle 3.10.4 release notes|Release Notes]]
|
|-
!Moodle 3.10.5
|12 July 2021
|2020110905
|[[Moodle 3.10.5 release notes|Release Notes]]
|
|-
!Moodle 3.10.6
|29 July 2021
|2020110906
|[[Moodle 3.10.6 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.10.7
|13 September 2021
|2020110907
|[[Moodle 3.10.7 release notes|Release Notes]]
|
|-
!Moodle 3.10.8
|8 November 2021
|2020110908
|[[Moodle 3.10.8 release notes|Release Notes]]
|
|-
!Moodle 3.10.9
|17 January 2022
|2020110909
|[[Moodle 3.10.9 release notes|Release Notes]]
|-
!Moodle 3.10.10
|14 March 2022
|2020110910
|[[Moodle 3.10.10 release notes|Release Notes]]
|}
Bug fixes for general core bugs in 3.10.x ended 8 November 2021 (12 months).
Bug fixes for security issues in 3.10.x will end 9 May 2022 (18 months).

==Moodle 3.9 (LTS)==
{| class="wikitable"
|-
! Moodle 3.9
|15 June 2020
|2020061500
|[[Moodle 3.9 release notes|Release Notes]]
|
[https://docs.moodle.org/39/en/Upgrading Upgrading to 3.9]
|-
!Moodle 3.9.1
|13 July 2020
|2020061501
|[[Moodle 3.9.1 release notes|Release Notes]]
|
|-
!Moodle 3.9.2
|14 September 2020
|2020061502
| [[Moodle 3.9.2 release notes|Release Notes]]
|
|-
!Moodle 3.9.3
|9 November 2020
|2020061503
| [[Moodle 3.9.3 release notes|Release Notes]]
|
|-
!Moodle 3.9.4
|18 January 2021
|2020061504
|[[Moodle 3.9.4 release notes|Release Notes]]
|
|-
!Moodle 3.9.5
|8 March 2021
|2020061505
|[[Moodle 3.9.5 release notes|Release Notes]]
|
|-
!Moodle 3.9.6
|25 March 2021
|2020061506
|[[Moodle 3.9.6 release notes|Release Notes]]
|
|-
!Moodle 3.9.7
|10 May 2021
|2020061507
|[[Moodle 3.9.7 release notes|Release Notes]]
|
|-
! Moodle 3.9.8
|12 July 2021
|2020061508
|[[Moodle 3.9.8 release notes|Release Notes]]
|
|-
!Moodle 3.9.9
|29 July 2021
|2020061509
|[[Moodle 3.9.9 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.9.10
|13 September 2021
|2020061510
|[[Moodle 3.9.10 release notes|Release Notes]]
|
|-
!Moodle 3.9.11
| 8 November 2021
|2020061511
|[[Moodle 3.9.11 release notes|Release Notes]]
|
|-
!Moodle 3.9.12
| 17 January 2022
|2020061512
|[[Moodle 3.9.12 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.9.x ended 10 May 2021 (12 months).
Bug fixes for security issues in 3.9.x will end 13 Nov 2023 (36 months plus 6 months extension).
==Moodle 3.8==
{| class="wikitable"
|-
!Moodle 3.8
|18 November 2019
|2019111800
|[[Moodle 3.8 release notes|Release Notes]]
|
[https://docs.moodle.org/38/en/Upgrading Upgrading to 3.8]
|-
!Moodle 3.8.1
|13 January 2020
|2019111801
|[[Moodle 3.8.1 release notes|Release Notes]]
|
|-
!Moodle 3.8.2
|9 March 2020
|2019111802
|[[Moodle 3.8.2 release notes|Release Notes]]
|
|-
!Moodle 3.8.3
|11 May 2020
|2019111803
|[[Moodle 3.8.3 release notes|Release Notes]]
|
|-
!Moodle 3.8.4
|13 July 2020
|2019111804
|[[Moodle 3.8.4 release notes|Release Notes]]
|
|-
!Moodle 3.8.5
|14 September 2020
|2019111805
| [[Moodle 3.8.5 release notes|Release Notes]]
|
|-
!Moodle 3.8.6
|9 November 2020
|2019111806
| [[Moodle 3.8.6 release notes|Release Notes]]
|
|-
!Moodle 3.8.7
|18 January 2021
|2019111807
|[[Moodle 3.8.7 release notes|Release Notes]]
|
|-
!Moodle 3.8.8
|8 March 2021
|2019111808
|[[Moodle 3.8.8 release notes|Release Notes]]
|
|-
!Moodle 3.8.9
|10 May 2021
|2019111809
|[[Moodle 3.8.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.8.x ended 9 November 2020 (12 months).
Bug fixes for security issues in 3.8.x ended 10 May 2021 (18 months).
==Moodle 3.7==
{| class="wikitable"
|-
!Moodle 3.7
|20 May 2019
|2019052000
|[[Moodle 3.7 release notes|Release Notes]]
|[https://docs.moodle.org/37/en/Upgrading Upgrading to 3.7]
|-
!Moodle 3.7.1
|8 July 2019
|2019052001
|[[Moodle 3.7.1 release notes|Release Notes]]
|
|-
!Moodle 3.7.2
|9 September 2019
|2019052002
|[[Moodle 3.7.2 release notes|Release Notes]]
|
|-
!Moodle 3.7.3
|11 November 2019
|2019052003
| [[Moodle 3.7.3 release notes|Release Notes]]
|
|-
!Moodle 3.7.4
|13 January 2020
|2019052004
|[[Moodle 3.7.4 release notes|Release Notes]]
|
|-
!Moodle 3.7.5
|9 March 2020
|2019052005
|[[Moodle 3.7.5 release notes|Release Notes]]
|
|-
!Moodle 3.7.6
|11 May 2020
|2019052006
|[[Moodle 3.7.6 release notes|Release Notes]]
|
|-
!Moodle 3.7.7
|13 July 2020
|2019052007
|[[Moodle 3.7.7 release notes|Release Notes]]
|
|-
!Moodle 3.7.8
|14 September 2020
|2019052008
| [[Moodle 3.7.8 release notes|Release Notes]]
|
|-
!Moodle 3.7.9
|9 November 2020
|2019052009
|[[Moodle 3.7.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.7.x ended 11 May 2020 (12 months).
Bug fixes for security issues in 3.7.x ended 9 November 2020 (18 months).
==Moodle 3.6==
{| class="wikitable"
|-
!Moodle 3.6
| 3 December 2018
|2018120300
|[[Moodle 3.6 release notes|Release Notes]]
|
[https://docs.moodle.org/36/en/Upgrading Upgrading to 3.6]
|-
!Moodle 3.6.1
|5 December 2018
|2018120301
| [[Moodle 3.6.1 release notes|Release Notes]]
|
|-
! Moodle 3.6.2
|14 January 2019
|2018120302
|[[Moodle 3.6.2 release notes|Release Notes]]
|
|-
!Moodle 3.6.3
|11 March 2019
|2018120303
|[[Moodle 3.6.3 release notes|Release Notes]]
|
|-
!Moodle 3.6.4
|13 May 2019
|2018120304
|[[Moodle 3.6.4 release notes|Release Notes]]
|
|-
!Moodle 3.6.5
|8th July 2019
|2018120305
|[[Moodle 3.6.5 release notes|Release Notes]]
|
|-
!Moodle 3.6.6
|9th September 2019
|2018120306
|[[Moodle 3.6.6 release notes|Release Notes]]
|
|-
!Moodle 3.6.7
| 11th November 2019
|2018120307
|[[Moodle 3.6.7 release notes|Release Notes]]
|
|-
!Moodle 3.6.8
|13th January 2020
|2018120308
|[[Moodle 3.6.8 release notes|Release Notes]]
|
|-
!Moodle 3.6.9
|9th March 2020
|2018120309
| [[Moodle 3.6.9 release notes|Release Notes]]
|
|-
!Moodle 3.6.10
|11th May 2020
|2018120310
|[[Moodle 3.6.10 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.6.x ended 11 November 2019 (12 months).
Bug fixes for security issues in 3.6.x ended 11 May 2020 (18 months).
==Moodle 3.5 (LTS)==
{| class="wikitable"
|-
!Moodle 3.5
|17 May 2018
|2018051700
|[[Moodle 3.5 release notes|Release Notes]]
|[https://docs.moodle.org/35/en/Upgrading Upgrading to 3.5]
|-
! Moodle 3.5.1
|9 July 2018
|2018051701
|[[Moodle 3.5.1 release notes|Release Notes]]
|
|-
!Moodle 3.5.2
|10 September 2018
|2018051702
|[[Moodle 3.5.2 release notes|Release Notes]]
|
|-
!Moodle 3.5.3
|12 November 2018
|2018051703
| [[Moodle 3.5.3 release notes|Release Notes]]
|
|-
! Moodle 3.5.4
|14 January 2019
|2018051704
|[[Moodle 3.5.4 release notes|Release Notes]]
|
|-
!Moodle 3.5.5
|11 March 2019
|2018051705
|[[Moodle 3.5.5 release notes|Release Notes]]
|
|-
!Moodle 3.5.6
|13 May 2019
|2018051706
|[[Moodle 3.5.6 release notes|Release Notes]]
|
|-
!Moodle 3.5.7
|8 July 2019
|2018051707
|[[Moodle 3.5.7 release notes|Release Notes]]
|
|-
!Moodle 3.5.8
|9 September 2019
|2018051708
|[[Moodle 3.5.8 release notes|Release Notes]]
|
|-
!Moodle 3.5.9
|11 November 2019
|2018051709
|[[Moodle 3.5.9 release notes|Release Notes]]
|
|-
!Moodle 3.5.10
|13 January 2020
|2018051710
| [[Moodle 3.5.10 release notes|Release Notes]]
|
|-
!Moodle 3.5.11
|9 March 2020
|2018051711
|[[Moodle 3.5.11 release notes|Release Notes]]
|
|-
!Moodle 3.5.12
|11 May 2020
|2018051712
| [[Moodle 3.5.12 release notes|Release Notes]]
|
|-
!Moodle 3.5.13
|13 July 2020
|2018051713
|[[Moodle 3.5.13 release notes|Release Notes]]
|
|-
!Moodle 3.5.14
| 14 September 2020
|2018051714
|[[Moodle 3.5.14 release notes|Release Notes]]
|
|-
!Moodle 3.5.15
|9 November 2020
|2018051715
|[[Moodle 3.5.15 release notes|Release Notes]]
|
|-
!Moodle 3.5.16
|18 January 2021
|2018051716
| [[Moodle 3.5.16 release notes|Release Notes]]
|
|-
!Moodle 3.5.17
|8 March 2021
| 2018051717
|[[Moodle 3.5.17 release notes|Release Notes]]
|
|-
!Moodle 3.5.18
| 10 May 2021
| 2018051718
|[[Moodle 3.5.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.5.x ended May 2019 (12 months).
Bug fixes for security issues in 3.5.x ended 10 May 2021 (36 months).
==Moodle 3.4==
{| class="wikitable"
|-
!Moodle 3.4
|13 November 2017
|2017111300
|[[Moodle 3.4 release notes|Release Notes]]
|
[https://docs.moodle.org/34/en/Upgrading Upgrading to 3.4]
|-
! Moodle 3.4.1
|15 January 2018
|2017111301
|[[Moodle 3.4.1 release notes|Release Notes]]
|
|-
!Moodle 3.4.2
|19 March 2018
|2017111302
|[[Moodle 3.4.2 release notes|Release Notes]]
|
|-
!Moodle 3.4.3
|17 May 2018
|2017111303
|[[Moodle 3.4.3 release notes|Release Notes]]
|
|-
! Moodle 3.4.4
|9 July 2018
|2017111304
|[[Moodle 3.4.4 release notes|Release Notes]]
|
|-
!Moodle 3.4.5
|10 September 2018
|2017111305
|[[Moodle 3.4.5 release notes|Release Notes]]
|
|-
!Moodle 3.4.6
|12 November 2018
|2017111306
| [[Moodle 3.4.6 release notes|Release Notes]]
|
|-
! Moodle 3.4.7
|14 January 2019
|2017111307
|[[Moodle 3.4.7 release notes|Release Notes]]
|
|-
!Moodle 3.4.8
|11 March 2019
|2017111308
|[[Moodle 3.4.8 release notes|Release Notes]]
|
|-
!Moodle 3.4.9
|13 May 2019
|2017111309
| [[Moodle 3.4.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.4.x ended 12 November 2018 (12 months).
Bug fixes for security issues in 3.4.x ended 13 May 2019 (18 months).
==Moodle 3.3==
{| class="wikitable"
|-
!Moodle 3.3
|15 May 2017
|2017051500
|[[Moodle 3.3 release notes|Release Notes]]
|
[https://docs.moodle.org/33/en/Upgrading Upgrading to 3.3]
|-
!Moodle 3.3.1
|10 July 2017
|2017051501
|[[Moodle 3.3.1 release notes|Release Notes]]
|
|-
!Moodle 3.3.2
|11 September 2017
|2017051502
|[[Moodle 3.3.2 release notes|Release Notes]]
|
|-
!Moodle 3.3.3
|13 November 2017
|2017051503
| [[Moodle 3.3.3 release notes|Release Notes]]
|
|-
! Moodle 3.3.4
|15 January 2018
|2017051504
|[[Moodle 3.3.4 release notes|Release Notes]]
|
|-
!Moodle 3.3.5
|19 March 2018
|2017051505
|[[Moodle 3.3.5 release notes|Release Notes]]
|
|-
!Moodle 3.3.6
|17 May 2018
|2017051506
|[[Moodle 3.3.6 release notes|Release Notes]]
|
|-
! Moodle 3.3.7
|9 July 2018
|2017051507
|[[Moodle 3.3.7 release notes|Release Notes]]
|
|-
!Moodle 3.3.8
|10 September 2018
|2017051508
|[[Moodle 3.3.8 release notes|Release Notes]]
|
|-
! Moodle 3.3.9
|12 November 2018
|2017051509
|[[Moodle 3.3.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.3.x ended 17 May 2018 (12 months).
Bug fixes for security issues in 3.3.x ended 12 November 2018 (18 months).
==Moodle 3.2==
{| class="wikitable"
|-
!Moodle 3.2
| 5 December 2016
|2016120500
|[[Moodle 3.2 release notes|Release Notes]]
|[https://docs.moodle.org/32/en/Upgrading Upgrading to 3.2]
|-
!Moodle 3.2.1
|9 January 2017
|2016120501
|[[Moodle 3.2.1 release notes|Release Notes]]
|
|-
!Moodle 3.2.2
|13 March 2017
|2016120502
|[[Moodle 3.2.2 release notes|Release Notes]]
|
|-
!Moodle 3.2.3
|8 May 2017
|2016120503
|[[Moodle 3.2.3 release notes|Release Notes]]
|
|-
!Moodle 3.2.4
|10 July 2017
|2016120504
|[[Moodle 3.2.4 release notes|Release Notes]]
|
|-
!Moodle 3.2.5
|11 September 2017
|2016120505
|[[Moodle 3.2.5 release notes|Release Notes]]
|
|-
!Moodle 3.2.6
|13 November 2017
|2016120506
| [[Moodle 3.2.6 release notes|Release Notes]]
|
|-
! Moodle 3.2.7
|15 January 2018
|2016120507
|[[Moodle 3.2.7 release notes|Release Notes]]
|
|-
!Moodle 3.2.8
|19 March 2018
|2016120508
|[[Moodle 3.2.8 release notes|Release Notes]]
|
|-
!Moodle 3.2.9
|17 May 2018
|2016120509
| [[Moodle 3.2.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.2.x ended 13 November 2017 (12 months).
Bug fixes for security issues in 3.2.x ended 17 May 2018 (18 months).
==Moodle 3.1 (LTS)==
{| class="wikitable"
|-
!Moodle 3.1
|23 May 2016
|2016052300
|[[Moodle 3.1 release notes|Release Notes]]
|
[https://docs.moodle.org/31/en/Upgrading Upgrading to 3.1]
|-
!Moodle 3.1.1
|11 July 2016
|2016052301
|[[Moodle 3.1.1 release notes|Release Notes]]
|
|-
!Moodle 3.1.2
|12 September 2016
|2016052302
|[[Moodle 3.1.2 release notes|Release Notes]]
|
|-
!Moodle 3.1.3
|14 November 2016
|2016052303
|[[Moodle 3.1.3 release notes|Release Notes]]
|
|-
!Moodle 3.1.4
|9 January 2017
|2016052304
|[[Moodle 3.1.4 release notes|Release Notes]]
|
|-
!Moodle 3.1.5
|13 March 2017
|2016052305
|[[Moodle 3.1.5 release notes|Release Notes]]
|
|-
!Moodle 3.1.6
|8 May 2017
|2016052306
|[[Moodle 3.1.6 release notes|Release Notes]]
|
|-
!Moodle 3.1.7
|10 July 2017
|2016052307
|[[Moodle 3.1.7 release notes|Release Notes]]
|
|-
!Moodle 3.1.8
|11 September 2017
|2016052308
|[[Moodle 3.1.8 release notes|Release Notes]]
|
|-
!Moodle 3.1.9
|13 November 2017
|2016052309
|[[Moodle 3.1.9 release notes|Release Notes]]
|
|-
!Moodle 3.1.10
|15 January 2018
|2016052310
|[[Moodle 3.1.10 release notes|Release Notes]]
|
|-
! Moodle 3.1.11
|19 March 2018
|2016052311
|[[Moodle 3.1.11 release notes|Release Notes]]
|
|-
!Moodle 3.1.12
|17 May 2018
|2016052312
|[[Moodle 3.1.12 release notes|Release Notes]]
|
|-
!Moodle 3.1.13
|9 July 2018
|2016052313
|[[Moodle 3.1.13 release notes|Release Notes]]
|
|-
!Moodle 3.1.14
|10 September 2018
|2016052314
|[[Moodle 3.1.14 release notes|Release Notes]]
|
|-
! Moodle 3.1.15
|12 November 2018
|2016052315
|[[Moodle 3.1.15 release notes|Release Notes]]
|
|-
!Moodle 3.1.16
|14 January 2019
|2016052316
|[[Moodle 3.1.16 release notes|Release Notes]]
|
|-
! Moodle 3.1.17
|11 March 2019
| 2016052317
|[[Moodle 3.1.17 release notes|Release Notes]]
|
|-
!Moodle 3.1.18
|13 May 2019
|2016052318
|[[Moodle 3.1.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.1.x ended 8 May 2017 (12 months).
Bug fixes for security issues in 3.1.x ended 13 May 2019 (36 months).
==Moodle 3.0==
{| class="wikitable"
|-
!Moodle 3.0
|16 November 2015
|2015111600
|[[Moodle 3.0 release notes|Release Notes]]
|[https://docs.moodle.org/30/en/Upgrading Upgrading to 3.0]
|-
!Moodle 3.0.1
|21 December 2015
|2015111601
| [[Moodle 3.0.1 release notes|Release Notes]]
|
|-
! Moodle 3.0.2
|11 January 2016
|2015111602
|[[Moodle 3.0.2 release notes|Release Notes]]
|
|-
!Moodle 3.0.3
|14 March 2016
|2015111603
|[[Moodle 3.0.3 release notes|Release Notes]]
|
|-
!Moodle 3.0.4
|9 May 2016
|2015111604
|[[Moodle 3.0.4 release notes|Release Notes]]
|
|-
!Moodle 3.0.5
|11 July 2016
|2015111605
|[[Moodle 3.0.5 release notes|Release Notes]]
|
|-
!Moodle 3.0.6
|12 September 2016
|2015111606
|[[Moodle 3.0.6 release notes|Release Notes]]
|
|-
!Moodle 3.0.7
|14 November 2016
|2015111607
|[[Moodle 3.0.7 release notes|Release Notes]]
|
|-
!Moodle 3.0.8
|9 January 2017
|2015111608
|[[Moodle 3.0.8 release notes|Release Notes]]
|
|-
!Moodle 3.0.9
|13 March 2017
|2015111609
|[[Moodle 3.0.9 release notes|Release Notes]]
|
|-
!Moodle 3.0.10
|8 May 2017
|2015111610
|[[Moodle 3.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.0.x ended 14 November 2016 (12 months).
Bug fixes for security issues in 3.0.x ended 8 May 2017 (18 months).
==Moodle 2.9==
{| class="wikitable"
|-
!Moodle 2.9
| 11 May 2015
|2015051100
|[[Moodle 2.9 release notes|Release Notes]]
| [https://docs.moodle.org/29/en/Upgrading_to_Moodle_2.9 Upgrading to 2.9]
|-
! Moodle 2.9.1
|6 July 2015
|2015051101
|[[Moodle 2.9.1 release notes|Release Notes]]
|
|-
!Moodle 2.9.2
|14 September 2015
|2015051102
| [[Moodle 2.9.2 release notes|Release Notes]]
|
|-
!Moodle 2.9.3
|9 November 2015
|2015051103
| [[Moodle 2.9.3 release notes|Release Notes]]
|
|-
! Moodle 2.9.4
|11 January 2016
|2015051104
|[[Moodle 2.9.4 release notes|Release Notes]]
|
|-
!Moodle 2.9.5
|14 March 2016
|2015051105
|[[Moodle 2.9.5 release notes|Release Notes]]
|
|-
!Moodle 2.9.6
|9 May 2016
|2015051106
|[[Moodle 2.9.6 release notes|Release Notes]]
|
|-
!Moodle 2.9.7
|11 July 2016
|2015051107
|[[Moodle 2.9.7 release notes|Release Notes]]
|
|-
!Moodle 2.9.8
|12 September 2016
|2015051108
|[[Moodle 2.9.8 release notes|Release Notes]]
|
|-
! Moodle 2.9.9
|14 November 2016
|2015051109
|[[Moodle 2.9.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.9.x ended 9 May 2016 (12 months).
Bug fixes for security issues in 2.9.x ended 14 November 2016 (18 months).
==Moodle 2.8==
{| class="wikitable"
|-
!Moodle 2.8
|10 November 2014
|2014111000
| [[Moodle 2.8 release notes|Release Notes]]
|[https://docs.moodle.org/28/en/Upgrading_to_Moodle_2.8 Upgrading to 2.8]
|-
!Moodle 2.8.1
|13 November 2014
|2014111001
| [[Moodle 2.8.1 release notes|Release Notes]]
|
|-
!Moodle 2.8.2
|12 January 2015
|2014111002
| [[Moodle 2.8.2 release notes|Release Notes]]
|
|-
!Moodle 2.8.3
|2 February 2015
|2014111003
|[[Moodle 2.8.3 release notes|Release Notes]]
|
|-
!Moodle 2.8.4
|9 March 2015
|2014111004
|[[Moodle 2.8.4 release notes|Release Notes]]
|
|-
!Moodle 2.8.5
|10 March 2015
|2014111005
|[[Moodle 2.8.5 release notes|Release Notes]]
|
|-
!Moodle 2.8.6
|11 May 2015
|2014111006
|[[Moodle 2.8.6 release notes|Release Notes]]
|
|-
! Moodle 2.8.7
|6 July 2015
|2014111007
|[[Moodle 2.8.7 release notes|Release Notes]]
|
|-
!Moodle 2.8.8
|14 September 2015
|2014111008
| [[Moodle 2.8.8 release notes|Release Notes]]
|
|-
!Moodle 2.8.9
|9 November 2015
|2014111009
|[[Moodle 2.8.9 release notes|Release Notes]]
|
|-
!Moodle 2.8.10
|11 January 2016
|2014111010
|[[Moodle 2.8.10 release notes|Release Notes]]
|
|-
!Moodle 2.8.11
|14 March 2016
|2014111011
|[[Moodle 2.8.11 release notes|Release Notes]]
|
|-
!Moodle 2.8.12
|9 May 2016
|2014111012
| [[Moodle 2.8.12 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.8.x ended 9 November 2015 (12 months).
Bug fixes for security issues in 2.8.x ended 9 May 2016 (18 months).
==Moodle 2.7 (LTS)==
{| class="wikitable"
|-
!Moodle 2.7
| 12 May 2014
|2014051200
|[[Moodle 2.7 release notes|Release Notes]]
|[https://docs.moodle.org/27/en/Upgrading_to_Moodle_2.7 Upgrading to 2.7]
|-
! Moodle 2.7.1
|14 July 2014
|2014051201
|[[Moodle 2.7.1 release notes|Release Notes]]
|
|-
!Moodle 2.7.2
|8 September 2014
|2014051202
|[[Moodle 2.7.2 release notes|Release Notes]]
|
|-
!Moodle 2.7.3
|10 November 2014
|2014051203
| [[Moodle 2.7.3 release notes|Release Notes]]
|
|-
!Moodle 2.7.4
|12 January 2015
|2014051204
| [[Moodle 2.7.4 release notes|Release Notes]]
|
|-
!Moodle 2.7.5
|2 February 2015
|2014051205
|[[Moodle 2.7.5 release notes|Release Notes]]
|
|-
!Moodle 2.7.6
|9 March 2015
|2014051206
|[[Moodle 2.7.6 release notes|Release Notes]]
|
|-
!Moodle 2.7.7
|10 March 2015
|2014051207
|[[Moodle 2.7.7 release notes|Release Notes]]
|
|-
!Moodle 2.7.8
|11 May 2015
|2014051208
|[[Moodle 2.7.8 release notes|Release Notes]]
|
|-
!Moodle 2.7.9
|6 July 2015
|2014051209
|[[Moodle 2.7.9 release notes|Release Notes]]
|
|-
!Moodle 2.7.10
| 14 September 2015
|2014051210
|[[Moodle 2.7.10 release notes|Release Notes]]
|
|-
!Moodle 2.7.11
|9 November 2015
|2014051211
|[[Moodle 2.7.11 release notes|Release Notes]]
|
|-
!Moodle 2.7.12
|11 January 2016
|2014051212
|[[Moodle 2.7.12 release notes|Release Notes]]
|
|-
!Moodle 2.7.13
|14 March 2016
|2014051213
|[[Moodle 2.7.13 release notes|Release Notes]]
|
|-
!Moodle 2.7.14
|9 May 2016
|2014051214
| [[Moodle 2.7.14 release notes|Release Notes]]
|
|-
!Moodle 2.7.15
|11 July 2016
|2014051215
|[[Moodle 2.7.15 release notes|Release Notes]]
|
|-
!Moodle 2.7.16
|12 September 2016
|2014051216
|[[Moodle 2.7.16 release notes|Release Notes]]
|
|-
!Moodle 2.7.17
|14 November 2016
|2014051217
|[[Moodle 2.7.17 release notes|Release Notes]]
|
|-
!Moodle 2.7.18
|9 January 2017
|2014051218
|[[Moodle 2.7.18 release notes|Release Notes]]
|
|-
!Moodle 2.7.19
|13 March 2017
|2014051219
|[[Moodle 2.7.19 release notes|Release Notes]]
|
|-
!Moodle 2.7.20
|8 May 2017
|2014051220
| [[Moodle 2.7.20 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.7.x ended 11 May 2015 (12 months).
Bug fixes for security issues in 2.7.x ended 8 May 2017 (36 months).
==Moodle 2.6==
{| class="wikitable"
|-
!Moodle 2.6
|18 November 2013
|2013111800
|[[Moodle 2.6 release notes|Release Notes]]
|[https://docs.moodle.org/26/en/Upgrading_to_Moodle_2.6 Upgrading to 2.6]
|-
!Moodle 2.6.1
|13 January 2014
| 2013111801
| [[Moodle 2.6.1 release notes|Release Notes]]
|
|-
!Moodle 2.6.2
|10 March 2014
|2013111802
|[[Moodle 2.6.2 release notes|Release Notes]]
|
|-
!Moodle 2.6.3
|12 May 2014
|2013111803
|[[Moodle 2.6.3 release notes|Release Notes]]
|
|-
!Moodle 2.6.4
|14 July 2014
|2013111804
|[[Moodle 2.6.4 release notes|Release Notes]]
|
|-
!Moodle 2.6.5
|8 September 2014
|2013111805
|[[Moodle 2.6.5 release notes|Release Notes]]
|
|-
!Moodle 2.6.6
|10 November 2014
|2013111806
|[[Moodle 2.6.6 release notes|Release Notes]]
|
|-
!Moodle 2.6.7
|12 January 2015
|2013111807
|[[Moodle 2.6.7 release notes|Release Notes]]
|
|-
! Moodle 2.6.8
|2 February 2015
|2013111808
|[[Moodle 2.6.8 release notes|Release Notes]]
|
|-
! Moodle 2.6.9
|9 March 2015
|2013111809
|[[Moodle 2.6.9 release notes|Release Notes]]
|
|-
!Moodle 2.6.10
|10 March 2015
|2013111810
| [[Moodle 2.6.10 release notes|Release Notes]]
|
|-
!Moodle 2.6.11
|11 May 2015
|2013111811
|[[Moodle 2.6.11 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 2.6.x ended 10 November 2014 (12 months).
Bug fixes for security issues in 2.6.x ended 11 May 2015 (18 months).
==Moodle 2.5==
{| class="wikitable"
|-
!Moodle 2.5
| 14 May 2013
|2013051400
|[[Moodle 2.5 release notes|Release Notes]]
| [https://docs.moodle.org/25/en/Upgrading_to_Moodle_2.5 Upgrading to 2.5]
|-
! Moodle 2.5.1
|8 July 2013
|2013051401
|[[Moodle 2.5.1 release notes|Release Notes]]
|
|-
!Moodle 2.5.2
|9 September 2013
|2013051402
|[[Moodle 2.5.2 release notes|Release Notes]]
|
|-
!Moodle 2.5.3
|11 November 2013
|2013051403
|[[Moodle 2.5.3 release notes|Release Notes]]
|
|-
!Moodle 2.5.4
|13 January 2014
| 2013051404
| [[Moodle 2.5.4 release notes|Release Notes]]
|
|-
!Moodle 2.5.5
|10 March 2014
|2013051405
|[[Moodle 2.5.5 release notes|Release Notes]]
|
|-
!Moodle 2.5.6
|12 May 2014
|2013051406
|[[Moodle 2.5.6 release notes|Release Notes]]
|
|-
!Moodle 2.5.7
|14 July 2014
|2013051407
|[[Moodle 2.5.7 release notes|Release Notes]]
|
|-
!Moodle 2.5.8
|8 September 2014
|2013051408
|[[Moodle 2.5.8 release notes|Release Notes]]
|
|-
! Moodle 2.5.9
| 10 November 2014
|2013051409
|[[Moodle 2.5.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.5.x ended May 2014 (12 months).
Bug fixes for security issues in 2.5.x ended 10 November 2014 (18 months).
==Moodle 2.4==
{| class="wikitable"
|-
! Moodle 2.4
|3 December 2012
|2012120300
|[[Moodle 2.4 release notes|Release Notes]]
|[https://docs.moodle.org/24/en/Upgrading_to_Moodle_2.4 Upgrading to 2.4]
|-
! Moodle 2.4.1
|14 January 2013
|2012120301
|[[Moodle 2.4.1 release notes|Release Notes]]
|
|-
!Moodle 2.4.2
|11 March 2013
|2012120302
|[[Moodle 2.4.2 release notes|Release Notes]]
|
|-
!Moodle 2.4.3
|18 March 2013
|2012120303
|[[Moodle 2.4.3 release notes|Release Notes]]
|
|-
!Moodle 2.4.4
|14 May 2013
|2012120304
|[[Moodle 2.4.4 release notes|Release Notes]]
|
|-
!Moodle 2.4.5
|8 July 2013
|2012120305
|[[Moodle 2.4.5 release notes|Release Notes]]
|
|-
!Moodle 2.4.6
|9 September 2013
|2012120306
|[[Moodle 2.4.6 release notes|Release Notes]]
|
|-
!Moodle 2.4.7
|11 November 2013
|2012120307
| [[Moodle 2.4.7 release notes|Release Notes]]
|
|-
! Moodle 2.4.8
|13 January 2014
|2012120308
|[[Moodle 2.4.8 release notes|Release Notes]]
|
|-
!Moodle 2.4.9
|10 March 2014
|2012120309
|[[Moodle 2.4.9 release notes|Release Notes]]
|
|-
!Moodle 2.4.10
|12 May 2014
|2012120310
| [[Moodle 2.4.10 release notes|Release Notes]]
|
|-
!Moodle 2.4.11
|14 July 2014
|2012120311
|[[Moodle 2.4.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.4.x ended December 2013 (12 months).
Bug fixes for security issues in 2.4.x ended June 2014 (18 months).
==Moodle 2.3==
{| class="wikitable"
|-
!Moodle 2.3
|25 June 2012
|2012062500
|[[Moodle 2.3 release notes|Release Notes]]
| [https://docs.moodle.org/23/en/Upgrading_to_Moodle_2.3 Upgrading to 2.3]
|-
!Moodle 2.3.1
|9 July 2012
|2012062501
|[[Moodle 2.3.1 release notes|Release Notes]]
|
|-
! Moodle 2.3.2
|10 September 2012
|2012062502
|[[Moodle 2.3.2 release notes|Release Notes]]
|
|-
!Moodle 2.3.3
|12 November 2012
|2012062503
|[[Moodle 2.3.3 release notes|Release Notes]]
|
|-
! Moodle 2.3.4
|14 January 2013
|2012062504
|[[Moodle 2.3.4 release notes|Release Notes]]
|
|-
!Moodle 2.3.5
|11 March 2013
|2012062505
|[[Moodle 2.3.5 release notes|Release Notes]]
|
|-
!Moodle 2.3.6
|18 March 2013
|2012062506
|[[Moodle 2.3.6 release notes|Release Notes]]
|
|-
!Moodle 2.3.7
|14 May 2013
|2012062507
|[[Moodle 2.3.7 release notes|Release Notes]]
|
|-
!Moodle 2.3.8
|8 July 2013
|2012062508
|[[Moodle 2.3.8 release notes|Release Notes]]
|
|-
!Moodle 2.3.9
|9 September 2013
|2012062509
|[[Moodle 2.3.9 release notes|Release Notes]]
|
|-
! Moodle 2.3.10
|11 November 2013
|2012062510
|[[Moodle 2.3.10 release notes|Release Notes]]
|
|-
!Moodle 2.3.11
|13 January 2014
|2012062511
|[[Moodle 2.3.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.3.x ended June 2013 (12 months).
Bug fixes for security issues in 2.3.x ended December 2013 (18 months).
==Moodle 2.2==
{| class="wikitable"
|-
! Moodle 2.2
|5 December 2011
|2011120500
|[[Moodle 2.2 release notes|Release Notes]]
|[https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 Upgrading to 2.2]
|-
!Moodle 2.2.1
|9 January 2012
|2011120501
|[[Moodle 2.2.1 release notes|Release Notes]]
|
|-
!Moodle 2.2.2
|12 March 2012
|2011120502
|[[Moodle 2.2.2 release notes|Release Notes]]
|
|-
!Moodle 2.2.3
|14 May 2012
|2011120503
|[[Moodle 2.2.3 release notes|Release Notes]]
|
|-
! Moodle 2.2.4
|9 July 2012
|2011120504
|[[Moodle 2.2.4 release notes|Release Notes]]
|
|-
!Moodle 2.2.5
|10 September 2012
|2011120505
|[[Moodle 2.2.5 release notes|Release Notes]]
|
|-
!Moodle 2.2.6
|12 November 2012
|2011120506
| [[Moodle 2.2.6 release notes|Release Notes]]
|
|-
! Moodle 2.2.7
|14 January 2013
|2011120507
|[[Moodle 2.2.7 release notes|Release Notes]]
|
|-
!Moodle 2.2.8
|11 March 2013
|2011120508
|[[Moodle 2.2.8 release notes|Release Notes]]
|
|-
!Moodle 2.2.9
|18 March 2013
|2011120509
|[[Moodle 2.2.9 release notes|Release Notes]]
|
|-
!Moodle 2.2.10
|14 May 2013
| 2011120510
|[[Moodle 2.2.10 release notes|Release Notes]]
|
|-
!Moodle 2.2.11
|8 July 2013
|2011120511
|[[Moodle 2.2.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.2.x ended December 2012 (12 months).
Bug fixes for security issues in 2.2.x ended June 2013 (18 months).
==Moodle 2.1==
{| class="wikitable"
|-
!Moodle 2.1
| 1 July 2011
|2011070100
|[[Moodle 2.1 release notes|Release Notes]]
|[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to 2.1]
|-
! Moodle 2.1.1
|1 August 2011
|2011070101
| [[Moodle 2.1.1 release notes|Release Notes]]
|
|-
!Moodle 2.1.2
|10 October 2011
|2011070102
|[[Moodle 2.1.2 release notes|Release Notes]]
|
|-
!Moodle 2.1.3
|28 November 2011
|2011070103
|[[Moodle 2.1.3 release notes|Release Notes]]
|
|-
!Moodle 2.1.4
|9 January 2012
|2011070104
|[[Moodle 2.1.4 release notes|Release Notes]]
|
|-
!Moodle 2.1.5
|12 March 2012
|2011070105
|[[Moodle 2.1.5 release notes|Release Notes]]
|
|-
!Moodle 2.1.6
|14 May 2012
|2011070106
|[[Moodle 2.1.6 release notes|Release Notes]]
|
|-
! Moodle 2.1.7
|9 July 2012
|2011070107
|[[Moodle 2.1.7 release notes|Release Notes]]
|
|-
!Moodle 2.1.8
|10 September 2012
|2011070108
|[[Moodle 2.1.8 release notes|Release Notes]]
|
|-
!Moodle 2.1.9
|12 November 2012
|2011070109
|[[Moodle 2.1.9 release notes|Release Notes]]
|
|-
!Moodle 2.1.10
|14 January 2013
|2011070110
|[[Moodle 2.1.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.1.x ended June 2012 (12 months).
Bug fixes for security issues in 2.1.x ended December 2012 (18 months).
==Moodle 2.0==
{| class="wikitable"
|-
!Moodle 2.0
|24 November 2010
|2010112400
| [[Moodle 2.0 release notes|Release Notes]]
|[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to 2.0]
|-
!Moodle 2.0.1
|25 December 2010
|2010122500
|[[Moodle 2.0.1 release notes|Release Notes]]
|
|-
!Moodle 2.0.2
|21 February 2011
|2011022100
|[[Moodle 2.0.2 release notes|Release Notes]]
|
|-
!Moodle 2.0.3
|5 May 2011
|2011033003
|[[Moodle 2.0.3 release notes|Release Notes]]
|
|-
! Moodle 2.0.4
|1 August 2011
|2011033004
| [[Moodle 2.0.4 release notes|Release Notes]]
|
|-
!Moodle 2.0.5
|10 October 2011
|2011033005
|[[Moodle 2.0.5 release notes|Release Notes]]
|
|-
!Moodle 2.0.6
|28 November 2011
|2011033006
|[[Moodle 2.0.6 release notes|Release Notes]]
|
|-
!Moodle 2.0.7
|9 January 2012
|2011033007
|[[Moodle 2.0.7 release notes|Release Notes]]
|
|-
!Moodle 2.0.8
|12 March 2012
|2011033008
|[[Moodle 2.0.8 release notes|Release Notes]]
|
|-
!Moodle 2.0.9
|14 May 2012
|2011033009
|[[Moodle 2.0.9 release notes|Release Notes]]
|
|-
!Moodle 2.0.10
|9 July 2012
|2011033010
|[[Moodle 2.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.0.x ended December 2011 (12 months).
Bug fixes for security issues in 2.0.x ended June 2012 (18 months).
==Moodle 1.9==
{| class="wikitable"
|-
!Moodle 1.9
|3 March 2008
|2007101509
|[[Moodle 1.9 release notes|Release Notes]]
|[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to 1.9]
|-
!Moodle 1.9.1
|15 May 2008
| 2007101512
|[[Moodle 1.9.1 release notes|Release Notes]]
|
|-
! Moodle 1.9.2
|11 July 2008
|2007101520
|[[Moodle 1.9.2 release notes|Release Notes]]
|
|-
!Moodle 1.9.3
|15 October 2008
|2007101530
|[[Moodle 1.9.3 release notes|Release Notes]]
|
|-
!Moodle 1.9.4
|28 January 2009
|2007101540
|[[Moodle 1.9.4 release notes|Release Notes]]
|
|-
!Moodle 1.9.5
|13 May 2009
|2007101550
|[[Moodle 1.9.5 release notes|Release Notes]]
|
|-
!Moodle 1.9.6
|21 October 2009
|2007101560
|[[Moodle 1.9.6 release notes|Release Notes]]
|
|-
!Moodle 1.9.7
|25 November 2009
|2007101570
|[[Moodle 1.9.7 release notes|Release Notes]]
|
|-
!Moodle 1.9.8
|25 March 2010
|2007101580.00
|[[Moodle 1.9.8 release notes|Release Notes]]
|
|-
! Moodle 1.9.9
| 8 June 2010
| 2007101590.00
| [[Moodle 1.9.9 release notes|Release Notes]]
|
|-
!Moodle 1.9.10
|25 October 2010
|2007101591.00
|
[[Moodle 1.9.10 release notes|Release Notes]]
|
|-
!Moodle 1.9.11
|21 February 2011
|2007101591.02
|[[Moodle 1.9.11 release notes|Release Notes]]
|
|-
! Moodle 1.9.12
|10 May 2011
|2007101591.03
|[[Moodle 1.9.12 release notes|Release Notes]]
|
|-
!Moodle 1.9.13
|1 August 2011
|2007101591.04
|[[Moodle 1.9.13 release notes|Release Notes]]
|
|-
!Moodle 1.9.14
|10 October 2011
|2007101591.06
|
[[Moodle 1.9.14 release notes|Release Notes]]
|
|-
!Moodle 1.9.15
|28 November 2011
| 2007101591.07
| [[Moodle 1.9.15 release notes|Release Notes]]
|
|-
!Moodle 1.9.16
|9 January 2012
|2007101591.10
|[[Moodle 1.9.16 release notes|Release Notes]]
|
|-
! Moodle 1.9.17
|12 March 2012
|2007101591.12
|[[Moodle 1.9.17 release notes|Release Notes]]
|
|-
!Moodle 1.9.18
|14 May 2012
|2007101591.16
|[[Moodle 1.9.18 release notes|Release Notes]]
|
|-
! Moodle 1.9.19
|9 July 2012
|2007101592.00
|[[Moodle 1.9.19 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 1.9.x has ended June 2011 (3.5 years).
Bug fixes for security issues in 1.9.x by Moodle HQ ended June 2012 (4.5 years).
Bug fixes for security issues in 1.9.19+ branch by [http://catalyst.net.nz Catalyst IT] ended [http://moodle.org/mod/forum/discuss.php?d=199706 Dec 2013] (6 years).
==Moodle 1.8 ==
*[[Moodle 1.8 release notes|Moodle 1.8]] - 30 March 2007
*[[Moodle 1.8.1 release notes|Moodle 1.8.1]] - 14 June 2007
*[[Moodle 1.8.2 release notes|Moodle 1.8.2]] - 8 July 2007
*[[Moodle 1.8.3 release notes|Moodle 1.8.3]] - 11 October 2007
*[[Moodle 1.8.4 release notes|Moodle 1.8.4]] - 11 January 2008
*[[Moodle 1.8.5 release notes|Moodle 1.8.5]] - 8 April 2008
*[[Moodle 1.8.6 release notes|Moodle 1.8.6]] - 11 July 2008
*[[Moodle 1.8.7 release notes|Moodle 1.8.7]] - 15 October 2008
*[[Moodle 1.8.8 release notes|Moodle 1.8.8]] - 28 January 2009
*[[Moodle 1.8.9 release notes|Moodle 1.8.9]] - 15 May 2009
*[[Moodle 1.8.10 release notes|Moodle 1.8.10]] - 26 October 2009
*[[Moodle 1.8.11 release notes|Moodle 1.8.11]] - 25 November 2009
*[[Moodle 1.8.12 release notes|Moodle 1.8.12]] - 27 March 2010
*[[Moodle 1.8.13 release notes|Moodle 1.8.13]] - 8 June 2010
*[[Moodle 1.8.14 release notes|Moodle 1.8.14]] - 3 December 2010
*Support has ended

==Moodle 1.7==
*[[Moodle 1.7 release notes|Moodle 1.7]] - 7 November 2006
*[[Moodle 1.7.1 release notes|Moodle 1.7.1]] - 17 January 2007
*[[Moodle 1.7.2 release notes|Moodle 1.7.2]] - 30 March 2007
*[[Moodle 1.7.3 release notes|Moodle 1.7.3]] - 11 October 2007
*[[Moodle 1.7.4 release notes|Moodle 1.7.4]] - 11 January 2008
*[[Moodle 1.7.5 release notes|Moodle 1.7.5]] - 11 July 2008
*[[Moodle 1.7.6 release notes|Moodle 1.7.6]] - 15 October 2008
*[[Moodle 1.7.7 release notes|Moodle 1.7.7]] - 28 January 2009
*Support has ended
==Moodle 1.6==
*[[Moodle 1.6 release notes|Moodle 1.6]] - 20 June 2006
*[[Moodle 1.6.1 release notes|Moodle 1.6.1]] - 20 July 2006
*[[Moodle 1.6.2 release notes|Moodle 1.6.2]] - 12 September 2006
*[[Moodle 1.6.3 release notes|Moodle 1.6.3]] - 10 October 2006
*[[Moodle 1.6.4 release notes|Moodle 1.6.4]] - 17 January 2007
*[[Moodle 1.6.5 release notes|Moodle 1.6.5]] - 30 March 2007
*Moodle 1.6.6 - 11 January 2008
*Moodle 1.6.7 - 11 July 2008
*[[Moodle 1.6.8 release notes|Moodle 1.6.8]] - 15 October 2008
*[[Moodle 1.6.9 release notes|Moodle 1.6.9]] - 28 January 2009
* Support has ended
==Moodle 1.5==
*[[Moodle 1.5 release notes|Moodle 1.5]] - 5 June 2005
*[[Moodle 1.5.1 release notes|Moodle 1.5.1]] - 8 July 2005
*[[Moodle 1.5.2 release notes|Moodle 1.5.2]] - 16 July 2005
*[[Moodle 1.5.3 release notes|Moodle 1.5.3]] - 11 November 2005
*[[Moodle 1.5.4 release notes|Moodle 1.5.4]] - 21 May 2006
*Support has ended
==Moodle 1.4==
*Moodle 1.4 - 31 August 2004
*Moodle 1.4.1 - 12 September 2004
*Moodle 1.4.2 - 5 November 2004
*Moodle 1.4.3 - 21 December 2004
*Moodle 1.4.4 - 7 March 2005
*[[Moodle 1.4.5 release notes|Moodle 1.4.5]] - 7 May 2005
*Support has ended
==Moodle 1.3==
*Moodle 1.3 - 25 May 2004
* Moodle 1.3.1 - 4 June 2004
*Moodle 1.3.2 - 9 July 2004
*Moodle 1.3.3 - 16 July 2004
* Moodle 1.3.4 - 11 August 2004
*Moodle 1.3.5 - 9 September 2004
*Support has ended
==Moodle 1.2==
*Moodle 1.2 - 20 March 2004
*Moodle 1.2.1 - 25 March 2004
*Support has ended
==Moodle 1.1==
*Moodle 1.1 - 29 August 2003
*Moodle 1.1.1 - 11 September 2003
*Support has ended
== Moodle 1.0==
*Moodle 1.0 - 20 August 2002
*Moodle 1.0.1 - 26 August 2002
*Moodle 1.0.2 - 2 September 2002
*Moodle 1.0.3 - 5 September 2002
*Moodle 1.0.4 - 10 September 2002
*Moodle 1.0.5 - 27 September 2002
* Moodle 1.0.6 - 26 October 2002
::1.0.6.1 - 6 November 2002
::1.0.6.2 - 11 November 2002
::1.0.6.3 - 14 November 2002
::1.0.6.4 - 25 November 2002
*Moodle 1.0.7 - 9 December 2002
*Moodle 1.0.8 - 7 January 2003
*Moodle 1.0.9 - 30 May 2003
*Support has ended
==See also==
*[[Roadmap]] - future versions
*[[Moodle versions]] - an explanation of how our versions work plus version numbers for each release (for $plugin->requires)
[[Category:Release notes]]
[[Category:Core development]]
[[fr:Historique des versions]]
[[es:dev/Historia de las versiones]]
[[de:Versionshistorie]]

Releases

2022-03-14T07:43:49Z

Abgreeve: /* Moodle 3.11.6 update */

This page lists all official releases of Moodle, grouped by branch in reverse chronological order.
==Version support==
From Moodle 2.6 onwards, the end of support, both general and security, happens the second Monday of May and November, observing the 12, 18... month periods, no matter if the major release date was moved or not.

The most recent [https://en.wikipedia.org/wiki/Long-term_support long-term support release (LTS)] version is Moodle 3.9.
{| class="wikitable" border="1px solid #dee2e6;"
|-
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Version
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Release status
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Initial release
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:rgba(0, 0, 0, 0.05);" | General support ends
! style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" | Security support ends
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.9 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 15 June 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 10 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 November 2023 (ext 6M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.10
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 9 November 2020
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 8 November 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 9 May 2022
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 3.11
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" | Current stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 17 May 2021
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 14 Nov 2022 (ext 6M)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | 13 Nov 2023 (ext 12M)
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |4.0
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |April 2022
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |May 2023
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |November 2023
|-
|4.1 (LTS)
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stable
|November 2022
|November 2023
|November 2025
|}
[[Image:releasescurrent.png|alt=Release graph]]

Release graph key:
{| class="wikitable" border="1px solid #dee2e6;"
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#f98012; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Currently supported stable releases.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#239cae; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Current security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" | Current release of versions still receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#9cbd50; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Future stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Future point releases receiving bug fixes, as well as security updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#316d5e; color:white; adding: .3rem 0.5rem 0.3rem 0.5rem;" |Future security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Future point releases receiving security-only updates.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#686566; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past stables
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: rgba(0, 0, 0, 0.05);" |Previously released versions containing bug fixes, as well as security updates. Updating to a currently supported version is recommended.
|-
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color:#282828; color:white; padding: .3rem 0.5rem 0.3rem 0.5rem;" |Past security
| style="vertical-align: top; border-top: 1px solid #dee2e6; background-color: #FFFFFF" |Previously released versions containing security updates only. Updating to a currently supported version is recommended.
|}
==General release calendar==
These are the target dates for releases. These dates may vary slightly due to unforeseen circumstances.
{| class="wikitable"
|-
!Release type
!Frequency
!Months
|-
|[[Process#Major_release_cycles|Major]] (eg. 3.x)
|6 monthly
|Second Monday of May and November
|-
|[[Process#Stable_maintenance_cycles|Minor]] (Point) (eg. 3.x.y)
| 2 monthly
|Second Monday of July, September, November, March and May.
Third Monday of January.
|}
All releases are preceded by a one week warning. Upcoming release dates can be found in the [https://www.google.com/calendar/ical/moodle.com_p4c2oe7hsb77ltaro5qtihb5d4%40group.calendar.google.com/public/basic.ics Moodle development calendar] (Note, this is an iCAL link that will try to add the dates to your personal calendar. If you just want to browse the dates online, use [https://calendar.google.com/calendar/embed?src=moodle.com_p4c2oe7hsb77ltaro5qtihb5d4@group.calendar.google.com&pli=1 this link].).
==Moodle 3.11==
{| class="wikitable"
|-
!Moodle 3.11
|17 May 2021
|2021051700
|[[Moodle 3.11 release notes|Release Notes]]
|[https://docs.moodle.org/311/en/Upgrading Upgrading to 3.11]
|-
!Moodle 3.11.1
|12 July 2021
|2021051701
|[[Moodle 3.11.1 release notes|Release Notes]]
|
|-
!Moodle 3.11.2
|29 July 2021
|2021051702
|[[Moodle 3.11.2 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.11.3
|13 September 2021
|2021051703
|[[Moodle 3.11.3 release notes|Release Notes]]
|
|-
! Moodle 3.11.4
|8 November 2021
|2021051704
|[[Moodle 3.11.4 release notes|Release Notes]]
|
|-
! Moodle 3.11.5
|17 January 2022
|2021051705
|[[Moodle 3.11.5 release notes|Release Notes]]
|-
! Moodle 3.11.6
|14 March 2022
|2021051706
|[[Moodle 3.11.6 release notes|Release Notes]]
|}
Bug fixes for general core bugs in 3.11.x will end 14 Nov 2022 (12 months plus 6 months extension).
Bug fixes for security issues in 3.11.x will end 13 Nov 2023 (18 months plus 12 months extension).

==Moodle 3.10==
{| class="wikitable"
|-
! Moodle 3.10
|9 November 2020
|2020110900
|
[[Moodle 3.10 release notes|Release Notes]]
|[https://docs.moodle.org/310/en/Upgrading Upgrading to 3.10]
|-
!Moodle 3.10.1
|18 January 2021
|2020110901
| [[Moodle 3.10.1 release notes|Release Notes]]
|
|-
!Moodle 3.10.2
|8 March 2021
|2020110902
|[[Moodle 3.10.2 release notes|Release Notes]]
|
|-
! Moodle 3.10.3
|25 March 2021
|2020110903
|[[Moodle 3.10.3 release notes|Release Notes]]
|
|-
!Moodle 3.10.4
|10 May 2021
|2020110904
|[[Moodle 3.10.4 release notes|Release Notes]]
|
|-
!Moodle 3.10.5
|12 July 2021
|2020110905
|[[Moodle 3.10.5 release notes|Release Notes]]
|
|-
!Moodle 3.10.6
|29 July 2021
|2020110906
|[[Moodle 3.10.6 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.10.7
|13 September 2021
|2020110907
|[[Moodle 3.10.7 release notes|Release Notes]]
|
|-
!Moodle 3.10.8
|8 November 2021
|2020110908
|[[Moodle 3.10.8 release notes|Release Notes]]
|
|-
!Moodle 3.10.9
|17 January 2022
|2020110909
|[[Moodle 3.10.9 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.10.x ended 8 November 2021 (12 months).
Bug fixes for security issues in 3.10.x will end 9 May 2022 (18 months).
==Moodle 3.9 (LTS)==
{| class="wikitable"
|-
! Moodle 3.9
|15 June 2020
|2020061500
|[[Moodle 3.9 release notes|Release Notes]]
|
[https://docs.moodle.org/39/en/Upgrading Upgrading to 3.9]
|-
!Moodle 3.9.1
|13 July 2020
|2020061501
|[[Moodle 3.9.1 release notes|Release Notes]]
|
|-
!Moodle 3.9.2
|14 September 2020
|2020061502
| [[Moodle 3.9.2 release notes|Release Notes]]
|
|-
!Moodle 3.9.3
|9 November 2020
|2020061503
| [[Moodle 3.9.3 release notes|Release Notes]]
|
|-
!Moodle 3.9.4
|18 January 2021
|2020061504
|[[Moodle 3.9.4 release notes|Release Notes]]
|
|-
!Moodle 3.9.5
|8 March 2021
|2020061505
|[[Moodle 3.9.5 release notes|Release Notes]]
|
|-
!Moodle 3.9.6
|25 March 2021
|2020061506
|[[Moodle 3.9.6 release notes|Release Notes]]
|
|-
!Moodle 3.9.7
|10 May 2021
|2020061507
|[[Moodle 3.9.7 release notes|Release Notes]]
|
|-
! Moodle 3.9.8
|12 July 2021
|2020061508
|[[Moodle 3.9.8 release notes|Release Notes]]
|
|-
!Moodle 3.9.9
|29 July 2021
|2020061509
|[[Moodle 3.9.9 release notes|Release Notes]]
|Emergency minor release
|-
! Moodle 3.9.10
|13 September 2021
|2020061510
|[[Moodle 3.9.10 release notes|Release Notes]]
|
|-
!Moodle 3.9.11
| 8 November 2021
|2020061511
|[[Moodle 3.9.11 release notes|Release Notes]]
|
|-
!Moodle 3.9.12
| 17 January 2022
|2020061512
|[[Moodle 3.9.12 release notes|Release Notes]]
|
|}
Bug fixes for general core bugs in 3.9.x ended 10 May 2021 (12 months).
Bug fixes for security issues in 3.9.x will end 13 Nov 2023 (36 months plus 6 months extension).
==Moodle 3.8==
{| class="wikitable"
|-
!Moodle 3.8
|18 November 2019
|2019111800
|[[Moodle 3.8 release notes|Release Notes]]
|
[https://docs.moodle.org/38/en/Upgrading Upgrading to 3.8]
|-
!Moodle 3.8.1
|13 January 2020
|2019111801
|[[Moodle 3.8.1 release notes|Release Notes]]
|
|-
!Moodle 3.8.2
|9 March 2020
|2019111802
|[[Moodle 3.8.2 release notes|Release Notes]]
|
|-
!Moodle 3.8.3
|11 May 2020
|2019111803
|[[Moodle 3.8.3 release notes|Release Notes]]
|
|-
!Moodle 3.8.4
|13 July 2020
|2019111804
|[[Moodle 3.8.4 release notes|Release Notes]]
|
|-
!Moodle 3.8.5
|14 September 2020
|2019111805
| [[Moodle 3.8.5 release notes|Release Notes]]
|
|-
!Moodle 3.8.6
|9 November 2020
|2019111806
| [[Moodle 3.8.6 release notes|Release Notes]]
|
|-
!Moodle 3.8.7
|18 January 2021
|2019111807
|[[Moodle 3.8.7 release notes|Release Notes]]
|
|-
!Moodle 3.8.8
|8 March 2021
|2019111808
|[[Moodle 3.8.8 release notes|Release Notes]]
|
|-
!Moodle 3.8.9
|10 May 2021
|2019111809
|[[Moodle 3.8.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.8.x ended 9 November 2020 (12 months).
Bug fixes for security issues in 3.8.x ended 10 May 2021 (18 months).
==Moodle 3.7==
{| class="wikitable"
|-
!Moodle 3.7
|20 May 2019
|2019052000
|[[Moodle 3.7 release notes|Release Notes]]
|[https://docs.moodle.org/37/en/Upgrading Upgrading to 3.7]
|-
!Moodle 3.7.1
|8 July 2019
|2019052001
|[[Moodle 3.7.1 release notes|Release Notes]]
|
|-
!Moodle 3.7.2
|9 September 2019
|2019052002
|[[Moodle 3.7.2 release notes|Release Notes]]
|
|-
!Moodle 3.7.3
|11 November 2019
|2019052003
| [[Moodle 3.7.3 release notes|Release Notes]]
|
|-
!Moodle 3.7.4
|13 January 2020
|2019052004
|[[Moodle 3.7.4 release notes|Release Notes]]
|
|-
!Moodle 3.7.5
|9 March 2020
|2019052005
|[[Moodle 3.7.5 release notes|Release Notes]]
|
|-
!Moodle 3.7.6
|11 May 2020
|2019052006
|[[Moodle 3.7.6 release notes|Release Notes]]
|
|-
!Moodle 3.7.7
|13 July 2020
|2019052007
|[[Moodle 3.7.7 release notes|Release Notes]]
|
|-
!Moodle 3.7.8
|14 September 2020
|2019052008
| [[Moodle 3.7.8 release notes|Release Notes]]
|
|-
!Moodle 3.7.9
|9 November 2020
|2019052009
|[[Moodle 3.7.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.7.x ended 11 May 2020 (12 months).
Bug fixes for security issues in 3.7.x ended 9 November 2020 (18 months).
==Moodle 3.6==
{| class="wikitable"
|-
!Moodle 3.6
| 3 December 2018
|2018120300
|[[Moodle 3.6 release notes|Release Notes]]
|
[https://docs.moodle.org/36/en/Upgrading Upgrading to 3.6]
|-
!Moodle 3.6.1
|5 December 2018
|2018120301
| [[Moodle 3.6.1 release notes|Release Notes]]
|
|-
! Moodle 3.6.2
|14 January 2019
|2018120302
|[[Moodle 3.6.2 release notes|Release Notes]]
|
|-
!Moodle 3.6.3
|11 March 2019
|2018120303
|[[Moodle 3.6.3 release notes|Release Notes]]
|
|-
!Moodle 3.6.4
|13 May 2019
|2018120304
|[[Moodle 3.6.4 release notes|Release Notes]]
|
|-
!Moodle 3.6.5
|8th July 2019
|2018120305
|[[Moodle 3.6.5 release notes|Release Notes]]
|
|-
!Moodle 3.6.6
|9th September 2019
|2018120306
|[[Moodle 3.6.6 release notes|Release Notes]]
|
|-
!Moodle 3.6.7
| 11th November 2019
|2018120307
|[[Moodle 3.6.7 release notes|Release Notes]]
|
|-
!Moodle 3.6.8
|13th January 2020
|2018120308
|[[Moodle 3.6.8 release notes|Release Notes]]
|
|-
!Moodle 3.6.9
|9th March 2020
|2018120309
| [[Moodle 3.6.9 release notes|Release Notes]]
|
|-
!Moodle 3.6.10
|11th May 2020
|2018120310
|[[Moodle 3.6.10 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.6.x ended 11 November 2019 (12 months).
Bug fixes for security issues in 3.6.x ended 11 May 2020 (18 months).
==Moodle 3.5 (LTS)==
{| class="wikitable"
|-
!Moodle 3.5
|17 May 2018
|2018051700
|[[Moodle 3.5 release notes|Release Notes]]
|[https://docs.moodle.org/35/en/Upgrading Upgrading to 3.5]
|-
! Moodle 3.5.1
|9 July 2018
|2018051701
|[[Moodle 3.5.1 release notes|Release Notes]]
|
|-
!Moodle 3.5.2
|10 September 2018
|2018051702
|[[Moodle 3.5.2 release notes|Release Notes]]
|
|-
!Moodle 3.5.3
|12 November 2018
|2018051703
| [[Moodle 3.5.3 release notes|Release Notes]]
|
|-
! Moodle 3.5.4
|14 January 2019
|2018051704
|[[Moodle 3.5.4 release notes|Release Notes]]
|
|-
!Moodle 3.5.5
|11 March 2019
|2018051705
|[[Moodle 3.5.5 release notes|Release Notes]]
|
|-
!Moodle 3.5.6
|13 May 2019
|2018051706
|[[Moodle 3.5.6 release notes|Release Notes]]
|
|-
!Moodle 3.5.7
|8 July 2019
|2018051707
|[[Moodle 3.5.7 release notes|Release Notes]]
|
|-
!Moodle 3.5.8
|9 September 2019
|2018051708
|[[Moodle 3.5.8 release notes|Release Notes]]
|
|-
!Moodle 3.5.9
|11 November 2019
|2018051709
|[[Moodle 3.5.9 release notes|Release Notes]]
|
|-
!Moodle 3.5.10
|13 January 2020
|2018051710
| [[Moodle 3.5.10 release notes|Release Notes]]
|
|-
!Moodle 3.5.11
|9 March 2020
|2018051711
|[[Moodle 3.5.11 release notes|Release Notes]]
|
|-
!Moodle 3.5.12
|11 May 2020
|2018051712
| [[Moodle 3.5.12 release notes|Release Notes]]
|
|-
!Moodle 3.5.13
|13 July 2020
|2018051713
|[[Moodle 3.5.13 release notes|Release Notes]]
|
|-
!Moodle 3.5.14
| 14 September 2020
|2018051714
|[[Moodle 3.5.14 release notes|Release Notes]]
|
|-
!Moodle 3.5.15
|9 November 2020
|2018051715
|[[Moodle 3.5.15 release notes|Release Notes]]
|
|-
!Moodle 3.5.16
|18 January 2021
|2018051716
| [[Moodle 3.5.16 release notes|Release Notes]]
|
|-
!Moodle 3.5.17
|8 March 2021
| 2018051717
|[[Moodle 3.5.17 release notes|Release Notes]]
|
|-
!Moodle 3.5.18
| 10 May 2021
| 2018051718
|[[Moodle 3.5.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.5.x ended May 2019 (12 months).
Bug fixes for security issues in 3.5.x ended 10 May 2021 (36 months).
==Moodle 3.4==
{| class="wikitable"
|-
!Moodle 3.4
|13 November 2017
|2017111300
|[[Moodle 3.4 release notes|Release Notes]]
|
[https://docs.moodle.org/34/en/Upgrading Upgrading to 3.4]
|-
! Moodle 3.4.1
|15 January 2018
|2017111301
|[[Moodle 3.4.1 release notes|Release Notes]]
|
|-
!Moodle 3.4.2
|19 March 2018
|2017111302
|[[Moodle 3.4.2 release notes|Release Notes]]
|
|-
!Moodle 3.4.3
|17 May 2018
|2017111303
|[[Moodle 3.4.3 release notes|Release Notes]]
|
|-
! Moodle 3.4.4
|9 July 2018
|2017111304
|[[Moodle 3.4.4 release notes|Release Notes]]
|
|-
!Moodle 3.4.5
|10 September 2018
|2017111305
|[[Moodle 3.4.5 release notes|Release Notes]]
|
|-
!Moodle 3.4.6
|12 November 2018
|2017111306
| [[Moodle 3.4.6 release notes|Release Notes]]
|
|-
! Moodle 3.4.7
|14 January 2019
|2017111307
|[[Moodle 3.4.7 release notes|Release Notes]]
|
|-
!Moodle 3.4.8
|11 March 2019
|2017111308
|[[Moodle 3.4.8 release notes|Release Notes]]
|
|-
!Moodle 3.4.9
|13 May 2019
|2017111309
| [[Moodle 3.4.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.4.x ended 12 November 2018 (12 months).
Bug fixes for security issues in 3.4.x ended 13 May 2019 (18 months).
==Moodle 3.3==
{| class="wikitable"
|-
!Moodle 3.3
|15 May 2017
|2017051500
|[[Moodle 3.3 release notes|Release Notes]]
|
[https://docs.moodle.org/33/en/Upgrading Upgrading to 3.3]
|-
!Moodle 3.3.1
|10 July 2017
|2017051501
|[[Moodle 3.3.1 release notes|Release Notes]]
|
|-
!Moodle 3.3.2
|11 September 2017
|2017051502
|[[Moodle 3.3.2 release notes|Release Notes]]
|
|-
!Moodle 3.3.3
|13 November 2017
|2017051503
| [[Moodle 3.3.3 release notes|Release Notes]]
|
|-
! Moodle 3.3.4
|15 January 2018
|2017051504
|[[Moodle 3.3.4 release notes|Release Notes]]
|
|-
!Moodle 3.3.5
|19 March 2018
|2017051505
|[[Moodle 3.3.5 release notes|Release Notes]]
|
|-
!Moodle 3.3.6
|17 May 2018
|2017051506
|[[Moodle 3.3.6 release notes|Release Notes]]
|
|-
! Moodle 3.3.7
|9 July 2018
|2017051507
|[[Moodle 3.3.7 release notes|Release Notes]]
|
|-
!Moodle 3.3.8
|10 September 2018
|2017051508
|[[Moodle 3.3.8 release notes|Release Notes]]
|
|-
! Moodle 3.3.9
|12 November 2018
|2017051509
|[[Moodle 3.3.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.3.x ended 17 May 2018 (12 months).
Bug fixes for security issues in 3.3.x ended 12 November 2018 (18 months).
==Moodle 3.2==
{| class="wikitable"
|-
!Moodle 3.2
| 5 December 2016
|2016120500
|[[Moodle 3.2 release notes|Release Notes]]
|[https://docs.moodle.org/32/en/Upgrading Upgrading to 3.2]
|-
!Moodle 3.2.1
|9 January 2017
|2016120501
|[[Moodle 3.2.1 release notes|Release Notes]]
|
|-
!Moodle 3.2.2
|13 March 2017
|2016120502
|[[Moodle 3.2.2 release notes|Release Notes]]
|
|-
!Moodle 3.2.3
|8 May 2017
|2016120503
|[[Moodle 3.2.3 release notes|Release Notes]]
|
|-
!Moodle 3.2.4
|10 July 2017
|2016120504
|[[Moodle 3.2.4 release notes|Release Notes]]
|
|-
!Moodle 3.2.5
|11 September 2017
|2016120505
|[[Moodle 3.2.5 release notes|Release Notes]]
|
|-
!Moodle 3.2.6
|13 November 2017
|2016120506
| [[Moodle 3.2.6 release notes|Release Notes]]
|
|-
! Moodle 3.2.7
|15 January 2018
|2016120507
|[[Moodle 3.2.7 release notes|Release Notes]]
|
|-
!Moodle 3.2.8
|19 March 2018
|2016120508
|[[Moodle 3.2.8 release notes|Release Notes]]
|
|-
!Moodle 3.2.9
|17 May 2018
|2016120509
| [[Moodle 3.2.9 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 3.2.x ended 13 November 2017 (12 months).
Bug fixes for security issues in 3.2.x ended 17 May 2018 (18 months).
==Moodle 3.1 (LTS)==
{| class="wikitable"
|-
!Moodle 3.1
|23 May 2016
|2016052300
|[[Moodle 3.1 release notes|Release Notes]]
|
[https://docs.moodle.org/31/en/Upgrading Upgrading to 3.1]
|-
!Moodle 3.1.1
|11 July 2016
|2016052301
|[[Moodle 3.1.1 release notes|Release Notes]]
|
|-
!Moodle 3.1.2
|12 September 2016
|2016052302
|[[Moodle 3.1.2 release notes|Release Notes]]
|
|-
!Moodle 3.1.3
|14 November 2016
|2016052303
|[[Moodle 3.1.3 release notes|Release Notes]]
|
|-
!Moodle 3.1.4
|9 January 2017
|2016052304
|[[Moodle 3.1.4 release notes|Release Notes]]
|
|-
!Moodle 3.1.5
|13 March 2017
|2016052305
|[[Moodle 3.1.5 release notes|Release Notes]]
|
|-
!Moodle 3.1.6
|8 May 2017
|2016052306
|[[Moodle 3.1.6 release notes|Release Notes]]
|
|-
!Moodle 3.1.7
|10 July 2017
|2016052307
|[[Moodle 3.1.7 release notes|Release Notes]]
|
|-
!Moodle 3.1.8
|11 September 2017
|2016052308
|[[Moodle 3.1.8 release notes|Release Notes]]
|
|-
!Moodle 3.1.9
|13 November 2017
|2016052309
|[[Moodle 3.1.9 release notes|Release Notes]]
|
|-
!Moodle 3.1.10
|15 January 2018
|2016052310
|[[Moodle 3.1.10 release notes|Release Notes]]
|
|-
! Moodle 3.1.11
|19 March 2018
|2016052311
|[[Moodle 3.1.11 release notes|Release Notes]]
|
|-
!Moodle 3.1.12
|17 May 2018
|2016052312
|[[Moodle 3.1.12 release notes|Release Notes]]
|
|-
!Moodle 3.1.13
|9 July 2018
|2016052313
|[[Moodle 3.1.13 release notes|Release Notes]]
|
|-
!Moodle 3.1.14
|10 September 2018
|2016052314
|[[Moodle 3.1.14 release notes|Release Notes]]
|
|-
! Moodle 3.1.15
|12 November 2018
|2016052315
|[[Moodle 3.1.15 release notes|Release Notes]]
|
|-
!Moodle 3.1.16
|14 January 2019
|2016052316
|[[Moodle 3.1.16 release notes|Release Notes]]
|
|-
! Moodle 3.1.17
|11 March 2019
| 2016052317
|[[Moodle 3.1.17 release notes|Release Notes]]
|
|-
!Moodle 3.1.18
|13 May 2019
|2016052318
|[[Moodle 3.1.18 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.1.x ended 8 May 2017 (12 months).
Bug fixes for security issues in 3.1.x ended 13 May 2019 (36 months).
==Moodle 3.0==
{| class="wikitable"
|-
!Moodle 3.0
|16 November 2015
|2015111600
|[[Moodle 3.0 release notes|Release Notes]]
|[https://docs.moodle.org/30/en/Upgrading Upgrading to 3.0]
|-
!Moodle 3.0.1
|21 December 2015
|2015111601
| [[Moodle 3.0.1 release notes|Release Notes]]
|
|-
! Moodle 3.0.2
|11 January 2016
|2015111602
|[[Moodle 3.0.2 release notes|Release Notes]]
|
|-
!Moodle 3.0.3
|14 March 2016
|2015111603
|[[Moodle 3.0.3 release notes|Release Notes]]
|
|-
!Moodle 3.0.4
|9 May 2016
|2015111604
|[[Moodle 3.0.4 release notes|Release Notes]]
|
|-
!Moodle 3.0.5
|11 July 2016
|2015111605
|[[Moodle 3.0.5 release notes|Release Notes]]
|
|-
!Moodle 3.0.6
|12 September 2016
|2015111606
|[[Moodle 3.0.6 release notes|Release Notes]]
|
|-
!Moodle 3.0.7
|14 November 2016
|2015111607
|[[Moodle 3.0.7 release notes|Release Notes]]
|
|-
!Moodle 3.0.8
|9 January 2017
|2015111608
|[[Moodle 3.0.8 release notes|Release Notes]]
|
|-
!Moodle 3.0.9
|13 March 2017
|2015111609
|[[Moodle 3.0.9 release notes|Release Notes]]
|
|-
!Moodle 3.0.10
|8 May 2017
|2015111610
|[[Moodle 3.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 3.0.x ended 14 November 2016 (12 months).
Bug fixes for security issues in 3.0.x ended 8 May 2017 (18 months).
==Moodle 2.9==
{| class="wikitable"
|-
!Moodle 2.9
| 11 May 2015
|2015051100
|[[Moodle 2.9 release notes|Release Notes]]
| [https://docs.moodle.org/29/en/Upgrading_to_Moodle_2.9 Upgrading to 2.9]
|-
! Moodle 2.9.1
|6 July 2015
|2015051101
|[[Moodle 2.9.1 release notes|Release Notes]]
|
|-
!Moodle 2.9.2
|14 September 2015
|2015051102
| [[Moodle 2.9.2 release notes|Release Notes]]
|
|-
!Moodle 2.9.3
|9 November 2015
|2015051103
| [[Moodle 2.9.3 release notes|Release Notes]]
|
|-
! Moodle 2.9.4
|11 January 2016
|2015051104
|[[Moodle 2.9.4 release notes|Release Notes]]
|
|-
!Moodle 2.9.5
|14 March 2016
|2015051105
|[[Moodle 2.9.5 release notes|Release Notes]]
|
|-
!Moodle 2.9.6
|9 May 2016
|2015051106
|[[Moodle 2.9.6 release notes|Release Notes]]
|
|-
!Moodle 2.9.7
|11 July 2016
|2015051107
|[[Moodle 2.9.7 release notes|Release Notes]]
|
|-
!Moodle 2.9.8
|12 September 2016
|2015051108
|[[Moodle 2.9.8 release notes|Release Notes]]
|
|-
! Moodle 2.9.9
|14 November 2016
|2015051109
|[[Moodle 2.9.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.9.x ended 9 May 2016 (12 months).
Bug fixes for security issues in 2.9.x ended 14 November 2016 (18 months).
==Moodle 2.8==
{| class="wikitable"
|-
!Moodle 2.8
|10 November 2014
|2014111000
| [[Moodle 2.8 release notes|Release Notes]]
|[https://docs.moodle.org/28/en/Upgrading_to_Moodle_2.8 Upgrading to 2.8]
|-
!Moodle 2.8.1
|13 November 2014
|2014111001
| [[Moodle 2.8.1 release notes|Release Notes]]
|
|-
!Moodle 2.8.2
|12 January 2015
|2014111002
| [[Moodle 2.8.2 release notes|Release Notes]]
|
|-
!Moodle 2.8.3
|2 February 2015
|2014111003
|[[Moodle 2.8.3 release notes|Release Notes]]
|
|-
!Moodle 2.8.4
|9 March 2015
|2014111004
|[[Moodle 2.8.4 release notes|Release Notes]]
|
|-
!Moodle 2.8.5
|10 March 2015
|2014111005
|[[Moodle 2.8.5 release notes|Release Notes]]
|
|-
!Moodle 2.8.6
|11 May 2015
|2014111006
|[[Moodle 2.8.6 release notes|Release Notes]]
|
|-
! Moodle 2.8.7
|6 July 2015
|2014111007
|[[Moodle 2.8.7 release notes|Release Notes]]
|
|-
!Moodle 2.8.8
|14 September 2015
|2014111008
| [[Moodle 2.8.8 release notes|Release Notes]]
|
|-
!Moodle 2.8.9
|9 November 2015
|2014111009
|[[Moodle 2.8.9 release notes|Release Notes]]
|
|-
!Moodle 2.8.10
|11 January 2016
|2014111010
|[[Moodle 2.8.10 release notes|Release Notes]]
|
|-
!Moodle 2.8.11
|14 March 2016
|2014111011
|[[Moodle 2.8.11 release notes|Release Notes]]
|
|-
!Moodle 2.8.12
|9 May 2016
|2014111012
| [[Moodle 2.8.12 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.8.x ended 9 November 2015 (12 months).
Bug fixes for security issues in 2.8.x ended 9 May 2016 (18 months).
==Moodle 2.7 (LTS)==
{| class="wikitable"
|-
!Moodle 2.7
| 12 May 2014
|2014051200
|[[Moodle 2.7 release notes|Release Notes]]
|[https://docs.moodle.org/27/en/Upgrading_to_Moodle_2.7 Upgrading to 2.7]
|-
! Moodle 2.7.1
|14 July 2014
|2014051201
|[[Moodle 2.7.1 release notes|Release Notes]]
|
|-
!Moodle 2.7.2
|8 September 2014
|2014051202
|[[Moodle 2.7.2 release notes|Release Notes]]
|
|-
!Moodle 2.7.3
|10 November 2014
|2014051203
| [[Moodle 2.7.3 release notes|Release Notes]]
|
|-
!Moodle 2.7.4
|12 January 2015
|2014051204
| [[Moodle 2.7.4 release notes|Release Notes]]
|
|-
!Moodle 2.7.5
|2 February 2015
|2014051205
|[[Moodle 2.7.5 release notes|Release Notes]]
|
|-
!Moodle 2.7.6
|9 March 2015
|2014051206
|[[Moodle 2.7.6 release notes|Release Notes]]
|
|-
!Moodle 2.7.7
|10 March 2015
|2014051207
|[[Moodle 2.7.7 release notes|Release Notes]]
|
|-
!Moodle 2.7.8
|11 May 2015
|2014051208
|[[Moodle 2.7.8 release notes|Release Notes]]
|
|-
!Moodle 2.7.9
|6 July 2015
|2014051209
|[[Moodle 2.7.9 release notes|Release Notes]]
|
|-
!Moodle 2.7.10
| 14 September 2015
|2014051210
|[[Moodle 2.7.10 release notes|Release Notes]]
|
|-
!Moodle 2.7.11
|9 November 2015
|2014051211
|[[Moodle 2.7.11 release notes|Release Notes]]
|
|-
!Moodle 2.7.12
|11 January 2016
|2014051212
|[[Moodle 2.7.12 release notes|Release Notes]]
|
|-
!Moodle 2.7.13
|14 March 2016
|2014051213
|[[Moodle 2.7.13 release notes|Release Notes]]
|
|-
!Moodle 2.7.14
|9 May 2016
|2014051214
| [[Moodle 2.7.14 release notes|Release Notes]]
|
|-
!Moodle 2.7.15
|11 July 2016
|2014051215
|[[Moodle 2.7.15 release notes|Release Notes]]
|
|-
!Moodle 2.7.16
|12 September 2016
|2014051216
|[[Moodle 2.7.16 release notes|Release Notes]]
|
|-
!Moodle 2.7.17
|14 November 2016
|2014051217
|[[Moodle 2.7.17 release notes|Release Notes]]
|
|-
!Moodle 2.7.18
|9 January 2017
|2014051218
|[[Moodle 2.7.18 release notes|Release Notes]]
|
|-
!Moodle 2.7.19
|13 March 2017
|2014051219
|[[Moodle 2.7.19 release notes|Release Notes]]
|
|-
!Moodle 2.7.20
|8 May 2017
|2014051220
| [[Moodle 2.7.20 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.7.x ended 11 May 2015 (12 months).
Bug fixes for security issues in 2.7.x ended 8 May 2017 (36 months).
==Moodle 2.6==
{| class="wikitable"
|-
!Moodle 2.6
|18 November 2013
|2013111800
|[[Moodle 2.6 release notes|Release Notes]]
|[https://docs.moodle.org/26/en/Upgrading_to_Moodle_2.6 Upgrading to 2.6]
|-
!Moodle 2.6.1
|13 January 2014
| 2013111801
| [[Moodle 2.6.1 release notes|Release Notes]]
|
|-
!Moodle 2.6.2
|10 March 2014
|2013111802
|[[Moodle 2.6.2 release notes|Release Notes]]
|
|-
!Moodle 2.6.3
|12 May 2014
|2013111803
|[[Moodle 2.6.3 release notes|Release Notes]]
|
|-
!Moodle 2.6.4
|14 July 2014
|2013111804
|[[Moodle 2.6.4 release notes|Release Notes]]
|
|-
!Moodle 2.6.5
|8 September 2014
|2013111805
|[[Moodle 2.6.5 release notes|Release Notes]]
|
|-
!Moodle 2.6.6
|10 November 2014
|2013111806
|[[Moodle 2.6.6 release notes|Release Notes]]
|
|-
!Moodle 2.6.7
|12 January 2015
|2013111807
|[[Moodle 2.6.7 release notes|Release Notes]]
|
|-
! Moodle 2.6.8
|2 February 2015
|2013111808
|[[Moodle 2.6.8 release notes|Release Notes]]
|
|-
! Moodle 2.6.9
|9 March 2015
|2013111809
|[[Moodle 2.6.9 release notes|Release Notes]]
|
|-
!Moodle 2.6.10
|10 March 2015
|2013111810
| [[Moodle 2.6.10 release notes|Release Notes]]
|
|-
!Moodle 2.6.11
|11 May 2015
|2013111811
|[[Moodle 2.6.11 release notes|Release Notes]]
| Support has ended
|}
Bug fixes for general core bugs in 2.6.x ended 10 November 2014 (12 months).
Bug fixes for security issues in 2.6.x ended 11 May 2015 (18 months).
==Moodle 2.5==
{| class="wikitable"
|-
!Moodle 2.5
| 14 May 2013
|2013051400
|[[Moodle 2.5 release notes|Release Notes]]
| [https://docs.moodle.org/25/en/Upgrading_to_Moodle_2.5 Upgrading to 2.5]
|-
! Moodle 2.5.1
|8 July 2013
|2013051401
|[[Moodle 2.5.1 release notes|Release Notes]]
|
|-
!Moodle 2.5.2
|9 September 2013
|2013051402
|[[Moodle 2.5.2 release notes|Release Notes]]
|
|-
!Moodle 2.5.3
|11 November 2013
|2013051403
|[[Moodle 2.5.3 release notes|Release Notes]]
|
|-
!Moodle 2.5.4
|13 January 2014
| 2013051404
| [[Moodle 2.5.4 release notes|Release Notes]]
|
|-
!Moodle 2.5.5
|10 March 2014
|2013051405
|[[Moodle 2.5.5 release notes|Release Notes]]
|
|-
!Moodle 2.5.6
|12 May 2014
|2013051406
|[[Moodle 2.5.6 release notes|Release Notes]]
|
|-
!Moodle 2.5.7
|14 July 2014
|2013051407
|[[Moodle 2.5.7 release notes|Release Notes]]
|
|-
!Moodle 2.5.8
|8 September 2014
|2013051408
|[[Moodle 2.5.8 release notes|Release Notes]]
|
|-
! Moodle 2.5.9
| 10 November 2014
|2013051409
|[[Moodle 2.5.9 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.5.x ended May 2014 (12 months).
Bug fixes for security issues in 2.5.x ended 10 November 2014 (18 months).
==Moodle 2.4==
{| class="wikitable"
|-
! Moodle 2.4
|3 December 2012
|2012120300
|[[Moodle 2.4 release notes|Release Notes]]
|[https://docs.moodle.org/24/en/Upgrading_to_Moodle_2.4 Upgrading to 2.4]
|-
! Moodle 2.4.1
|14 January 2013
|2012120301
|[[Moodle 2.4.1 release notes|Release Notes]]
|
|-
!Moodle 2.4.2
|11 March 2013
|2012120302
|[[Moodle 2.4.2 release notes|Release Notes]]
|
|-
!Moodle 2.4.3
|18 March 2013
|2012120303
|[[Moodle 2.4.3 release notes|Release Notes]]
|
|-
!Moodle 2.4.4
|14 May 2013
|2012120304
|[[Moodle 2.4.4 release notes|Release Notes]]
|
|-
!Moodle 2.4.5
|8 July 2013
|2012120305
|[[Moodle 2.4.5 release notes|Release Notes]]
|
|-
!Moodle 2.4.6
|9 September 2013
|2012120306
|[[Moodle 2.4.6 release notes|Release Notes]]
|
|-
!Moodle 2.4.7
|11 November 2013
|2012120307
| [[Moodle 2.4.7 release notes|Release Notes]]
|
|-
! Moodle 2.4.8
|13 January 2014
|2012120308
|[[Moodle 2.4.8 release notes|Release Notes]]
|
|-
!Moodle 2.4.9
|10 March 2014
|2012120309
|[[Moodle 2.4.9 release notes|Release Notes]]
|
|-
!Moodle 2.4.10
|12 May 2014
|2012120310
| [[Moodle 2.4.10 release notes|Release Notes]]
|
|-
!Moodle 2.4.11
|14 July 2014
|2012120311
|[[Moodle 2.4.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.4.x ended December 2013 (12 months).
Bug fixes for security issues in 2.4.x ended June 2014 (18 months).
==Moodle 2.3==
{| class="wikitable"
|-
!Moodle 2.3
|25 June 2012
|2012062500
|[[Moodle 2.3 release notes|Release Notes]]
| [https://docs.moodle.org/23/en/Upgrading_to_Moodle_2.3 Upgrading to 2.3]
|-
!Moodle 2.3.1
|9 July 2012
|2012062501
|[[Moodle 2.3.1 release notes|Release Notes]]
|
|-
! Moodle 2.3.2
|10 September 2012
|2012062502
|[[Moodle 2.3.2 release notes|Release Notes]]
|
|-
!Moodle 2.3.3
|12 November 2012
|2012062503
|[[Moodle 2.3.3 release notes|Release Notes]]
|
|-
! Moodle 2.3.4
|14 January 2013
|2012062504
|[[Moodle 2.3.4 release notes|Release Notes]]
|
|-
!Moodle 2.3.5
|11 March 2013
|2012062505
|[[Moodle 2.3.5 release notes|Release Notes]]
|
|-
!Moodle 2.3.6
|18 March 2013
|2012062506
|[[Moodle 2.3.6 release notes|Release Notes]]
|
|-
!Moodle 2.3.7
|14 May 2013
|2012062507
|[[Moodle 2.3.7 release notes|Release Notes]]
|
|-
!Moodle 2.3.8
|8 July 2013
|2012062508
|[[Moodle 2.3.8 release notes|Release Notes]]
|
|-
!Moodle 2.3.9
|9 September 2013
|2012062509
|[[Moodle 2.3.9 release notes|Release Notes]]
|
|-
! Moodle 2.3.10
|11 November 2013
|2012062510
|[[Moodle 2.3.10 release notes|Release Notes]]
|
|-
!Moodle 2.3.11
|13 January 2014
|2012062511
|[[Moodle 2.3.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.3.x ended June 2013 (12 months).
Bug fixes for security issues in 2.3.x ended December 2013 (18 months).
==Moodle 2.2==
{| class="wikitable"
|-
! Moodle 2.2
|5 December 2011
|2011120500
|[[Moodle 2.2 release notes|Release Notes]]
|[https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 Upgrading to 2.2]
|-
!Moodle 2.2.1
|9 January 2012
|2011120501
|[[Moodle 2.2.1 release notes|Release Notes]]
|
|-
!Moodle 2.2.2
|12 March 2012
|2011120502
|[[Moodle 2.2.2 release notes|Release Notes]]
|
|-
!Moodle 2.2.3
|14 May 2012
|2011120503
|[[Moodle 2.2.3 release notes|Release Notes]]
|
|-
! Moodle 2.2.4
|9 July 2012
|2011120504
|[[Moodle 2.2.4 release notes|Release Notes]]
|
|-
!Moodle 2.2.5
|10 September 2012
|2011120505
|[[Moodle 2.2.5 release notes|Release Notes]]
|
|-
!Moodle 2.2.6
|12 November 2012
|2011120506
| [[Moodle 2.2.6 release notes|Release Notes]]
|
|-
! Moodle 2.2.7
|14 January 2013
|2011120507
|[[Moodle 2.2.7 release notes|Release Notes]]
|
|-
!Moodle 2.2.8
|11 March 2013
|2011120508
|[[Moodle 2.2.8 release notes|Release Notes]]
|
|-
!Moodle 2.2.9
|18 March 2013
|2011120509
|[[Moodle 2.2.9 release notes|Release Notes]]
|
|-
!Moodle 2.2.10
|14 May 2013
| 2011120510
|[[Moodle 2.2.10 release notes|Release Notes]]
|
|-
!Moodle 2.2.11
|8 July 2013
|2011120511
|[[Moodle 2.2.11 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.2.x ended December 2012 (12 months).
Bug fixes for security issues in 2.2.x ended June 2013 (18 months).
==Moodle 2.1==
{| class="wikitable"
|-
!Moodle 2.1
| 1 July 2011
|2011070100
|[[Moodle 2.1 release notes|Release Notes]]
|[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to 2.1]
|-
! Moodle 2.1.1
|1 August 2011
|2011070101
| [[Moodle 2.1.1 release notes|Release Notes]]
|
|-
!Moodle 2.1.2
|10 October 2011
|2011070102
|[[Moodle 2.1.2 release notes|Release Notes]]
|
|-
!Moodle 2.1.3
|28 November 2011
|2011070103
|[[Moodle 2.1.3 release notes|Release Notes]]
|
|-
!Moodle 2.1.4
|9 January 2012
|2011070104
|[[Moodle 2.1.4 release notes|Release Notes]]
|
|-
!Moodle 2.1.5
|12 March 2012
|2011070105
|[[Moodle 2.1.5 release notes|Release Notes]]
|
|-
!Moodle 2.1.6
|14 May 2012
|2011070106
|[[Moodle 2.1.6 release notes|Release Notes]]
|
|-
! Moodle 2.1.7
|9 July 2012
|2011070107
|[[Moodle 2.1.7 release notes|Release Notes]]
|
|-
!Moodle 2.1.8
|10 September 2012
|2011070108
|[[Moodle 2.1.8 release notes|Release Notes]]
|
|-
!Moodle 2.1.9
|12 November 2012
|2011070109
|[[Moodle 2.1.9 release notes|Release Notes]]
|
|-
!Moodle 2.1.10
|14 January 2013
|2011070110
|[[Moodle 2.1.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.1.x ended June 2012 (12 months).
Bug fixes for security issues in 2.1.x ended December 2012 (18 months).
==Moodle 2.0==
{| class="wikitable"
|-
!Moodle 2.0
|24 November 2010
|2010112400
| [[Moodle 2.0 release notes|Release Notes]]
|[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to 2.0]
|-
!Moodle 2.0.1
|25 December 2010
|2010122500
|[[Moodle 2.0.1 release notes|Release Notes]]
|
|-
!Moodle 2.0.2
|21 February 2011
|2011022100
|[[Moodle 2.0.2 release notes|Release Notes]]
|
|-
!Moodle 2.0.3
|5 May 2011
|2011033003
|[[Moodle 2.0.3 release notes|Release Notes]]
|
|-
! Moodle 2.0.4
|1 August 2011
|2011033004
| [[Moodle 2.0.4 release notes|Release Notes]]
|
|-
!Moodle 2.0.5
|10 October 2011
|2011033005
|[[Moodle 2.0.5 release notes|Release Notes]]
|
|-
!Moodle 2.0.6
|28 November 2011
|2011033006
|[[Moodle 2.0.6 release notes|Release Notes]]
|
|-
!Moodle 2.0.7
|9 January 2012
|2011033007
|[[Moodle 2.0.7 release notes|Release Notes]]
|
|-
!Moodle 2.0.8
|12 March 2012
|2011033008
|[[Moodle 2.0.8 release notes|Release Notes]]
|
|-
!Moodle 2.0.9
|14 May 2012
|2011033009
|[[Moodle 2.0.9 release notes|Release Notes]]
|
|-
!Moodle 2.0.10
|9 July 2012
|2011033010
|[[Moodle 2.0.10 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 2.0.x ended December 2011 (12 months).
Bug fixes for security issues in 2.0.x ended June 2012 (18 months).
==Moodle 1.9==
{| class="wikitable"
|-
!Moodle 1.9
|3 March 2008
|2007101509
|[[Moodle 1.9 release notes|Release Notes]]
|[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to 1.9]
|-
!Moodle 1.9.1
|15 May 2008
| 2007101512
|[[Moodle 1.9.1 release notes|Release Notes]]
|
|-
! Moodle 1.9.2
|11 July 2008
|2007101520
|[[Moodle 1.9.2 release notes|Release Notes]]
|
|-
!Moodle 1.9.3
|15 October 2008
|2007101530
|[[Moodle 1.9.3 release notes|Release Notes]]
|
|-
!Moodle 1.9.4
|28 January 2009
|2007101540
|[[Moodle 1.9.4 release notes|Release Notes]]
|
|-
!Moodle 1.9.5
|13 May 2009
|2007101550
|[[Moodle 1.9.5 release notes|Release Notes]]
|
|-
!Moodle 1.9.6
|21 October 2009
|2007101560
|[[Moodle 1.9.6 release notes|Release Notes]]
|
|-
!Moodle 1.9.7
|25 November 2009
|2007101570
|[[Moodle 1.9.7 release notes|Release Notes]]
|
|-
!Moodle 1.9.8
|25 March 2010
|2007101580.00
|[[Moodle 1.9.8 release notes|Release Notes]]
|
|-
! Moodle 1.9.9
| 8 June 2010
| 2007101590.00
| [[Moodle 1.9.9 release notes|Release Notes]]
|
|-
!Moodle 1.9.10
|25 October 2010
|2007101591.00
|
[[Moodle 1.9.10 release notes|Release Notes]]
|
|-
!Moodle 1.9.11
|21 February 2011
|2007101591.02
|[[Moodle 1.9.11 release notes|Release Notes]]
|
|-
! Moodle 1.9.12
|10 May 2011
|2007101591.03
|[[Moodle 1.9.12 release notes|Release Notes]]
|
|-
!Moodle 1.9.13
|1 August 2011
|2007101591.04
|[[Moodle 1.9.13 release notes|Release Notes]]
|
|-
!Moodle 1.9.14
|10 October 2011
|2007101591.06
|
[[Moodle 1.9.14 release notes|Release Notes]]
|
|-
!Moodle 1.9.15
|28 November 2011
| 2007101591.07
| [[Moodle 1.9.15 release notes|Release Notes]]
|
|-
!Moodle 1.9.16
|9 January 2012
|2007101591.10
|[[Moodle 1.9.16 release notes|Release Notes]]
|
|-
! Moodle 1.9.17
|12 March 2012
|2007101591.12
|[[Moodle 1.9.17 release notes|Release Notes]]
|
|-
!Moodle 1.9.18
|14 May 2012
|2007101591.16
|[[Moodle 1.9.18 release notes|Release Notes]]
|
|-
! Moodle 1.9.19
|9 July 2012
|2007101592.00
|[[Moodle 1.9.19 release notes|Release Notes]]
|Support has ended
|}
Bug fixes for general core bugs in 1.9.x has ended June 2011 (3.5 years).
Bug fixes for security issues in 1.9.x by Moodle HQ ended June 2012 (4.5 years).
Bug fixes for security issues in 1.9.19+ branch by [http://catalyst.net.nz Catalyst IT] ended [http://moodle.org/mod/forum/discuss.php?d=199706 Dec 2013] (6 years).
==Moodle 1.8 ==
*[[Moodle 1.8 release notes|Moodle 1.8]] - 30 March 2007
*[[Moodle 1.8.1 release notes|Moodle 1.8.1]] - 14 June 2007
*[[Moodle 1.8.2 release notes|Moodle 1.8.2]] - 8 July 2007
*[[Moodle 1.8.3 release notes|Moodle 1.8.3]] - 11 October 2007
*[[Moodle 1.8.4 release notes|Moodle 1.8.4]] - 11 January 2008
*[[Moodle 1.8.5 release notes|Moodle 1.8.5]] - 8 April 2008
*[[Moodle 1.8.6 release notes|Moodle 1.8.6]] - 11 July 2008
*[[Moodle 1.8.7 release notes|Moodle 1.8.7]] - 15 October 2008
*[[Moodle 1.8.8 release notes|Moodle 1.8.8]] - 28 January 2009
*[[Moodle 1.8.9 release notes|Moodle 1.8.9]] - 15 May 2009
*[[Moodle 1.8.10 release notes|Moodle 1.8.10]] - 26 October 2009
*[[Moodle 1.8.11 release notes|Moodle 1.8.11]] - 25 November 2009
*[[Moodle 1.8.12 release notes|Moodle 1.8.12]] - 27 March 2010
*[[Moodle 1.8.13 release notes|Moodle 1.8.13]] - 8 June 2010
*[[Moodle 1.8.14 release notes|Moodle 1.8.14]] - 3 December 2010
*Support has ended

==Moodle 1.7==
*[[Moodle 1.7 release notes|Moodle 1.7]] - 7 November 2006
*[[Moodle 1.7.1 release notes|Moodle 1.7.1]] - 17 January 2007
*[[Moodle 1.7.2 release notes|Moodle 1.7.2]] - 30 March 2007
*[[Moodle 1.7.3 release notes|Moodle 1.7.3]] - 11 October 2007
*[[Moodle 1.7.4 release notes|Moodle 1.7.4]] - 11 January 2008
*[[Moodle 1.7.5 release notes|Moodle 1.7.5]] - 11 July 2008
*[[Moodle 1.7.6 release notes|Moodle 1.7.6]] - 15 October 2008
*[[Moodle 1.7.7 release notes|Moodle 1.7.7]] - 28 January 2009
*Support has ended
==Moodle 1.6==
*[[Moodle 1.6 release notes|Moodle 1.6]] - 20 June 2006
*[[Moodle 1.6.1 release notes|Moodle 1.6.1]] - 20 July 2006
*[[Moodle 1.6.2 release notes|Moodle 1.6.2]] - 12 September 2006
*[[Moodle 1.6.3 release notes|Moodle 1.6.3]] - 10 October 2006
*[[Moodle 1.6.4 release notes|Moodle 1.6.4]] - 17 January 2007
*[[Moodle 1.6.5 release notes|Moodle 1.6.5]] - 30 March 2007
*Moodle 1.6.6 - 11 January 2008
*Moodle 1.6.7 - 11 July 2008
*[[Moodle 1.6.8 release notes|Moodle 1.6.8]] - 15 October 2008
*[[Moodle 1.6.9 release notes|Moodle 1.6.9]] - 28 January 2009
* Support has ended
==Moodle 1.5==
*[[Moodle 1.5 release notes|Moodle 1.5]] - 5 June 2005
*[[Moodle 1.5.1 release notes|Moodle 1.5.1]] - 8 July 2005
*[[Moodle 1.5.2 release notes|Moodle 1.5.2]] - 16 July 2005
*[[Moodle 1.5.3 release notes|Moodle 1.5.3]] - 11 November 2005
*[[Moodle 1.5.4 release notes|Moodle 1.5.4]] - 21 May 2006
*Support has ended
==Moodle 1.4==
*Moodle 1.4 - 31 August 2004
*Moodle 1.4.1 - 12 September 2004
*Moodle 1.4.2 - 5 November 2004
*Moodle 1.4.3 - 21 December 2004
*Moodle 1.4.4 - 7 March 2005
*[[Moodle 1.4.5 release notes|Moodle 1.4.5]] - 7 May 2005
*Support has ended
==Moodle 1.3==
*Moodle 1.3 - 25 May 2004
* Moodle 1.3.1 - 4 June 2004
*Moodle 1.3.2 - 9 July 2004
*Moodle 1.3.3 - 16 July 2004
* Moodle 1.3.4 - 11 August 2004
*Moodle 1.3.5 - 9 September 2004
*Support has ended
==Moodle 1.2==
*Moodle 1.2 - 20 March 2004
*Moodle 1.2.1 - 25 March 2004
*Support has ended
==Moodle 1.1==
*Moodle 1.1 - 29 August 2003
*Moodle 1.1.1 - 11 September 2003
*Support has ended
== Moodle 1.0==
*Moodle 1.0 - 20 August 2002
*Moodle 1.0.1 - 26 August 2002
*Moodle 1.0.2 - 2 September 2002
*Moodle 1.0.3 - 5 September 2002
*Moodle 1.0.4 - 10 September 2002
*Moodle 1.0.5 - 27 September 2002
* Moodle 1.0.6 - 26 October 2002
::1.0.6.1 - 6 November 2002
::1.0.6.2 - 11 November 2002
::1.0.6.3 - 14 November 2002
::1.0.6.4 - 25 November 2002
*Moodle 1.0.7 - 9 December 2002
*Moodle 1.0.8 - 7 January 2003
*Moodle 1.0.9 - 30 May 2003
*Support has ended
==See also==
*[[Roadmap]] - future versions
*[[Moodle versions]] - an explanation of how our versions work plus version numbers for each release (for $plugin->requires)
[[Category:Release notes]]
[[Category:Core development]]
[[fr:Historique des versions]]
[[es:dev/Historia de las versiones]]
[[de:Versionshistorie]]

Moodle 4.0 developer update

2022-03-14T07:32:27Z

Abgreeve: Removed comments in module plugin section.

{{Moodle 4.0}}This page highlights the important changes that are coming in Moodle 4.0 for developers. Including how the UX improvements impact custom themes, relevant API changes, and what you can do as developer to prepare for the 4.0 release.
== Navigation changes ==
The core Navigation API has been left mostly untouched. The callbacks to all navigation callbacks remains unchanged and will be called as part of the regular 'navigation' and 'settingsnav' initialisation. Some new core classes have been created and exist within a new namespace 'core/navigation' and serves as conduit to rearrange, cherry-pick existing navigation nodes from the navigation/settingsnav trees and display within the respective navigation type. As such, it is highly recommended to provide unique keys for custom navigation nodes as this helps in the cherry-picking / rearranging process within the new classes.
=== Primary navigation ===
The primary navigation(the navbar) apart from the existing content will now display links to the Dashboard, My Courses, Site Admin and Course search, by default. You can still add items to the navbar via the 'custom menu' option. This will be displayed within the 'More' menu. We have transitioned the menus to be rendered via templates - refer user_menu.mustache. The lang menu has been moved to reside within the user menu.
==== Customising the primary navigation ====
Not yet implemented but we are looking at allowing the full addition and removal of any of the primary navigation tabs in the boost theme config file.
=== Secondary navigation ===
The main content area shows tabs for secondary navigation with a maximum of 5 items being rendered in this ‘more’ menu. A new UI component has been created to render menus like this. Files:
/lib/templates/moremenu.mustache
==== Changing the order of tabs ====
Apart from the previously mentioned functions, you can also create a custom secondary class as mentioned earlier. This will automatically be picked by getter and used to render the secondary nav within the activity. E.g. mod_assign/local/views/secondary. Note: This is currently only possible on an activity and block level.
=== Tertiary navigation ===
We've moved action buttons to the top of the page. We would encourage you to do the same.
If you have any buttons on an activity page that go to another page, or open a form (or similar), then we encourage you to move them from the body of your activity page to the top. All of the core activities have been updated to follow this pattern. Please take a look to see how you can format your activity in a similar fashion. There is no API here. You are welcome to create the buttons and display them as you wish in this top area.
=== New API functions ===
==== Page API ====
* Magic getters to fetch the primary and secondary navs and the primary output.
* The secondarynav magic getter also checks whether a custom secondary class has been defined within the module's local\views directory. Use this if you want to deviate from the standard secondary nav structure/order.

* set_secondary_nav - Force override the secondary navigation class

* has_secondary_navigation_setter - Sets the ‘_hassecondarynavigation’ to indicate whether a page should render the secondary navigation
==== Navigationlib ====
* set_show_in_secondary_navigation - whether or not a node should be displayed in the secondary nav. Accepts a single boolean argument
* set_force_into_more_menu- whether or not to force a node into the 'More' menu. Accepts a single boolean argument
==== The activity header class ====
There is a new activity header class that handles the display of information common to activities. 3rd party activities are not required to explicitly output this information as part of rendering individual pages.

The common information that are currently handled by the class are:
* title
* description
* completion information

As part of the update it was required that the initial information to be displayed by the class be toggable at a theme and layout level. Taking this into account the following theme level configurable exists:
* activityheaderconfig => An array that currently only enforces 'notitle' but can be expanded in the future NOTE: Boost has this set as true by default 'options'
The following layout level options that can be defined:
* noactivityheader - to remove the header in this specific layout.
* activityheader - An array that enforces the following options:
** notitle
** nocompletion
** nodescription
The class has a page level getter which you can use to fetch the current version of the class. The base state is initialised within the constructor with the completion information only fetched when data is exported for the template.

The class has setters for the following variables which can be leveraged to modify the header for a particular page in the format set_{variable_name}:
* hidecompletion
* description
* title
Alternately, bulk operations can also be done by passing the above variables in an array to 'set_attrs' which in turn calls the setters.<blockquote>'''Note: Any updates to the activityheader needs to be performed before the call to $OUTPUT->header'''</blockquote>
===== Theme updates: =====
In order for 3rd party themes to use the class they need to export the activity_header and include the following into their base template :<syntaxhighlight lang="html">
{{#headercontent}}
{{> core/activity_header}}
{{#headercontent}}
</syntaxhighlight>** headercontent being the array element that contains the exported activity_header data
===== Accessibility notes: =====
The jump to ‘maincontent’ div is now rendered within the activity header when within an activity context
== Component library ==
Each Moodle installation now ships with a Moodle User Interface (UI) Component library, a documentation system used to describe all the Bootstrap components and the custom Moodle components. The component Library is a helper tool for developers when creating user interfaces, a testing tool for theme developers and a documentation tool for core developers. The ultimate goal of having a component library is to encourage developers to create consistent user interfaces to improve Moodle’s overall user experience.

The library contains pages with documentation about User Interface components. It contains details on how to use the component, what variations are available and the JavaScript events / options are associated with the component.

When writing on these pages it is possible to render core mustache templates using some custom syntax like this:
<nowiki>{{< mustache template="core/notification_error" >}}</nowiki>
<nowiki>{{< /mustache >}}</nowiki>
You can also call core JavaScript or use HTML examples where the html code and the rendered result are visible in the Component Library. For more info visit the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-templates/ Moodle templates] page or the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-javascript/ Moodle JavaScript] page.

Each page in the library uses the current css from the default theme in your Moodle installation, if you have multiple themes installed and enabled the setting "Allow theme changes on url", the component library will have a theme selector option.

A hosted version of the Component Library can be found here. http://componentlibrary.moodle.com
=== Enabling the Component Library ===
Component library pages are written in the markdown language. These pages need to be compiled to HTML pages before the Component Library is visible. To compile the pages the server running Moodle needs to have the [[Javascript Modules#Install%20NVM%20and%20Node|JavaScript developer tools installed]] (nodeJs and Grunt)

If your server meets all requirements you can enable the library running
$ npm install
$ grunt componentlibrary
Further installation instructions can be found in the Component Library itself.
=== Documenting new UI Components ===
There are no set rules for adding new pages in the component library yet. These rules will need to be written and adopted in the integration process for Moodle code.

As a guideline for making this rules consideration are:

The component library is not about single use components, for example the Moodle grade book (a huge component with many custom features). Or about very common components like buttons, these are already covered by the Bootstrap section of the component library.

New features should be build keeping in mind the UI part needs to be customisable and if possible (and making sense) reusable. And example would be the new page drawers that we are introducing for the Navigation project. Or the custom primary navigation menus where overflowing items are pushed into a More section.
== Theme changes ==
=== Edit switch ===
On theme boost the “Turn editing on” and “Customise this page” buttons have been replaced by an edit switch in the top navbar. Theme Classic will keep using the old buttons. Child themes can choose to use the edit switch if the theme config.php is using this variable
$THEME->haseditswitch = true;
The languague menu, which used to be rendered in place of the custom menu has moved to the user dropdown when the user is logged in. If not logged in it will be placed next to the search / notification / messaging icon in the top navbar.
=== Login page ===
The login page has been redesigned and allows the admin to configure a background image for the login page only in the theme settings page. This change is available in both Boost and Classic. The login page still has all the features with an improved layout.
=== The page footer ===
In large screens, the page footer button is only visible when clicking a help button at the bottom right of the screen.
=== User initials as profile picture placeholder ===
If users do not upload a profile picture the user initials are displayed on a rounded gray background as a placeholder picture in the top navbar or any other page using a placeholder image. This change will be available in both Boost and Classic.

With the introduction of this placeholder image the full username will no longer be displayed in the top navbar.
=== Removal of back to top link ===
The "back to top" link will be removed for theme boost since the new course index reduced the dependence on page scrolling. Also, the new footer is positioned where this component used to be.
=== Styling changes ===
By default rounded edges will be used for UI components, for the page header and main content area the borders will be removed.
=== New layout page ===
Theme boost now uses the drawers.php layout for the course index and blocks.
== Question bank changes ==
There was a big project to deliver [[Question bank improvements for Moodle 4.0]] which added a new plugin type for adding features to the question banks, tracking the version history for each question as it is edited (question table has been split into <code>question</code>, <code>question_versions</code> and <code>question_bank_entries</code>), and tracking where each question is going to be used, with new tables <code>question_references</code> and <code>question_set_references</code>. This work was done in Epic MDL-70329 if you want to track down the details of any of the core changes.
=== Question type plugins ===
Amazingly, we (Safat and colleagues at Catalyst AU) managed to implement this without breaking most question type plugins.

However, the changes to the question bank, and the other Moodle 4.0 changes, probably broke the Behat tests for your plugin. To help with fixing that, MDL-74130 adds navigation to key question type pages (Preview and Edit for a question, and standard question bank pages like the bank itself, import and export) which should let you fix your test efficiently, and in a way that will work in all Moodle versions since 3.9.

The 'most' in the first paragraph here is becuase more advance question types may require more effort to fix. (For example qtype_combined which creates multi-part qusetions like the core qtype_multianswer; or qtype_pmatch or qtype_stack, which store additional data - questions tests - alongside the question itseld. How should that work with versionning?) But, if you have not done weird things like that, you are probably safe. If you find anything else that causes problems, please list it here.

The same thing should apply to question behaviour and question import/export format plugings: no significant changes required (probably just fixing the Behat tests because of the navigation changes).
=== New plugin type: qbank plugins ===
This is not something that will cause problems for people upgrading from 3.x. Rather, it is an exciting possibility you can explore once you have survived process of upgrading to 4.0. There is a whole new plugin type which you can create to add new features to the question bank. For example extra columns, new actions and bulk actions, and so on. See [[Question_bank_plugins]].
=== Activities that use questions ===
The probable bad news is if you have an activity module which uses questions. So far, the only activity which has been fixed is mod_quiz in Moodle core, so we don't yet have a good picture of what fixes will be necessary in other activities. Work is about to start fixing [https://github.com/studentquiz/moodle-mod_studentquiz mod_studentquiz], so watching that should give more clues. As we do that, we will try to update this section of this page. Other help writing the information required here would also be greatly appreciated.
== The course format system ==
Most of the logic for rendering and editing a course has been moved to a new subsystem called courseformat. The subsystem is located in "course/format" folder so it includes all the format plugins inside. The methods and modules which are distributed between the course and the course/format folders are now rearranged or refactored to be aligned with the current Moodle coding style.
=== Mandatory renderer in course formats ===
Now format plugins renderer is not optional anymore. Legacy formats without a renderer will get a deprecation message but it will continue working however, they should create a new renderer as soon as possible. The section-based format can do it by extending the provided core_courseformat\output\section_renderer class which includes all the necessary methods.
=== New format base class ===
The old base_format class (which all plugins extend) is now renamed as core_courseformat\base. The new class provides all the functionally of the previous base_format but it has been refactored to be used as a centralized source of truth for the course rendering. Legacy formats should extend the new class to avoid the deprecation message.

Now, the plugin format class provides information such as:
* If the page is displaying a single or multiple section
* Give access to other related format objects like the modinfo, the course record, maximum number of sections...
* If the format is compatible with features like course index, reactive components, ajax...
* Other format specifics like the page title, the default section name, default blocks...

The format instance is now the main object output components will use to render a course (see next section for more information).
=== New course output classes and mustache files ===
Traditionally, section-based course formats uses print_single_section_page and print_multiple_section_page to render the course content. In Moodle 4.0 most of the course rendering methods are migrated to output components and mustache templates. The old methods will get deprecation messages if they use the old renderer methods.

This is an example of a format rendering a course:<syntaxhighlight lang="php-brief">
// Get the course format instance.
$format = course_get_format($course);

// Get the specific format renderer.
$renderer = $format->get_renderer($PAGE);

if (!empty($displaysection)) {
// Setup the format instance to display a single section.
$format->set_section_number($displaysection);
}

// Create the ouptut instance and render it.
$outputclass = $format->get_output_classname('content');
$widget = new $outputclass($format);

echo $renderer->render($widget);
</syntaxhighlight>Format plugins are free to use its own output classes to render a course, or they could override the existing output classes by providing their own implementation. For example, the default output for "content" (as in the previous example) is "core_courseformat\output\local\|content", however, if the plugin has a "format_XXX\output\courseformat\content" class, the $format->class the get_output_class will return the overridden one.
Another important update on course rendering is that now all course structure is rendered using mustache templates instead of the original html_writer methods. Now themes are able to override the course format by providing alternative versions of the mustache files. All core course templates are located in "course/format/templates".

All the new output classes and a guide on how to migrate the current third-party plugins will be available soon.
=== Course editor javascript modules and frontend components ===
The majority of the javascript logic related to the course editing is replaced by AMD modules. Because this is a major change in the way courses are edited and rendered, by default format plugins will continue using the previous YUI modules for now. However, formats can start using the new libraries overriding the "$format->supports_components()" method.

Some Moodle 4.0 new features are only available for courses using the new editor library:
* Edit the course via the course index
* Creating sections without reloading the course page
* The new move section/activity modal
* Native browser drag&drop implementation
The new course editor uses a component-based reactive pattern to keep track of the course changes. The pattern highlights are:
* The main AMD module "core_crouseformat\courseeditor" maintains a data structure called state.
* Each UI element is implemented as a Component that observes the course state data and reacts to any data change
* When any reactive component needs to modify the course, it asks the course editor to execute a mutation. Mutations encapsulate all web services calls and alter the course state data.

The reactive library documentation, as well as the format plugin migration guide, will be available soon.
=== Other course related 4.0 changes ===
Two new web services have been added:
* core_courseformat_get_state: user by the new javascript course editor to get the current course state data (containing the list of sections, activities, and other course-related data)
* core_courseformat_update_course: to alter the current course content. Each call returns the parts of the course state altered by the action
== Behat changes ==
=== New steps ===
Moodle 4.0 introduces some new behat steps.

Sometimes you want to create a bulk number of activities. In that case you can use:<syntaxhighlight lang="gherkin">
:count :entitytype exist with the following data:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
Given 100 "mod_lti > tool types" exist with the following data:
|name |Test tool [count] |
|description |Example description [count] |
|baseurl |https://www.example.com/tool[count]|
</syntaxhighlight>

Dynamic (AJAX) tabs is a new feature contributed to Moodle 4.0 by the Workplace team (MDL-71943). You can use the following step to navigate between the tabs.<syntaxhighlight lang="gherkin">
And I click on the "tab title" dynamic tab
</syntaxhighlight>

To make sure that edit mode is (or is not) available on the current page, the following steps can be used.<syntaxhighlight lang="gherkin">
And edit mode should be available on the current page
And edit mode should not be available on the current page
</syntaxhighlight>

There are new aliases for the existing steps <code>I turn editing mode on</code> and <code>I turn editing mode off</code>.<syntaxhighlight lang="gherkin">
And I switch editing mode on
And I switch editing mode off
</syntaxhighlight>

In addition to the existing step to go to a course with editing mode on, we now have the following step to do the same but with editing mode being off.<syntaxhighlight lang="gherkin">
And I am on "course full name" course homepage with editing mode off
</syntaxhighlight>

The following step is similar to the old <code>following "link string" should download between "min bytes" and "max bytes" bytes</code> step, with more flexibility.<syntaxhighlight lang="gherkin">
And following "element string" "element type" in the "container string" "container type" should download between "min bytes" and "max bytes" bytes
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And following "Download" "link" in the "Starter" "table_row" should download between "0" and "5000" bytes
</syntaxhighlight>

The following step can be used to hover the mouse over the trigger area.<syntaxhighlight lang="gherkin">
And I hover over the "element string" "element type" in the "container string" "container type"
</syntaxhighlight>

The following step enables an installed plugin.<syntaxhighlight lang="gherkin">
And I enable "plugin name" "plugin type" plugin
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I enable "course_summary" "block" plugin
</syntaxhighlight>

The following is a special variation of 'I click on "<page name>" "link" in the "page" "region"'. It first checks to see if we are on the given page via the breadcrumb. If not we then attempt to follow the link name given.<syntaxhighlight lang="gherkin">
And I follow the breadcrumb "page name"
</syntaxhighlight>

You can use the following step to ensure a node is active in the navbar.<syntaxhighlight lang="gherkin">
And I should see "Node" is active in navigation
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I should see "My courses" is active in navigation
</syntaxhighlight>

The following step can be used to navigate to a given node in the primary navigation.<syntaxhighlight lang="gherkin">
And I select "Node" from primary navigation
</syntaxhighlight>

The following steps are to check whether an item exists in the user menu or not.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the user menu
And "item text" "selector type" should not exist in the user menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "Language" "link" should exist in the user menu
</syntaxhighlight>

The following steps are to check if a submenu of the user menu is shown, and if an item exists or does not exist in a given user submenu.<syntaxhighlight lang="gherkin">
And I should see "submenu name" user submenu
And "item text" "selector type" should exist in the "submenu name" user submenu
And "item text" "selector type" should not exist in the "submenu name" user submenu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I follow "Language" in the user menu
Then I should see "Language selector" user submenu
And "English &lrm;(en)&lrm;" "link" should exist in the "Language selector" user submenu
And "English (pirate) &lrm;(en_ar)&lrm;" "link" should not exist in the "Language selector" user submenu
</syntaxhighlight>

To add enrolment methods to courses you can use the following new step. The data that you provide in the next lines are used to fill the enrolment method form.<syntaxhighlight lang="gherkin">
And I add "enrolment method" in "course identifier" with:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I add "Self enrolment" enrolment method in "Course 1" with:
| Custom instance name | Test student enrolment |
| Enrolment key | moodle_rules |
| Use group enrolment keys | Yes |
</syntaxhighlight>

There are 3 new steps specific to the calendar component. These steps can be used to hover over a day in the mini-calendar or the full calendar.<syntaxhighlight lang="gherkin">
And I hover over day "day of month" of this month in the full calendar page
And I hover over day "day of month" of this month in the mini-calendar block
And I hover over today in the mini-calendar block
</syntaxhighlight>

Some new steps are added to question bank to be able to add comment to questions, verify the existence of a comment, and deleting comments form questions. Please note that the steps for adding comments only write the comment text in the comment field. You still need to click on the "Add comment" button to save the comment.<syntaxhighlight lang="gherkin">
And I add "comment text" comment to question
And I add "comment text" comment to question preview
And I delete "comment text" comment from question
And I delete "comment text" comment from question preview
And I should see "number of comments" on the comments column
And I click "number of comments" on the row on the comments column

</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "Question bank" in current page administration
And I should see "0" on the comments column
And I click "0" on the row on the comments column
And I add "test comment 01" comment to question
And I click on "Add comment" "button" in the ".modal-dialog" "css_element"
And I click on "Close" "button" in the ".modal-dialog" "css_element"
And I should see "1" on the comments column
And I click "1" on the row on the comments column
And I delete "test comment 01" comment from question
</syntaxhighlight>

Similar to the steps for comments, the following steps are to verify the number of a question's usage and to click on it in order to open the question usage modal.<syntaxhighlight lang="gherkin">
And I should see "usage count" on the usage column
And I click "usage count" on the usage column
</syntaxhighlight>

The following new steps are related to bulk actions in the question bank UI.<syntaxhighlight lang="gherkin">
And I click on question bulk action "action"
And I should see question bulk action "action"
And I should not see question bulk action "action"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I click on "First question" "checkbox"
And I click on "Second question" "checkbox"
And I click on "With selected" "button"
And I should see question bulk action "deleteselected"
And I click on question bulk action "deleteselected"
And I click on "Delete" "button" in the "Confirm" "dialogue"
</syntaxhighlight>

[https://docs.moodle.org/en/Report_builder Report builder] is a new feature contributed to Moodle 4.0 by the Workplace team. The following new step is added to Moodle 4.0 to select an action from the action menu in the list of custom reports table.<syntaxhighlight lang="gherkin">
And I press "action" action in the "report name" report row
</syntaxhighlight>

There's another step related to the report builder to set a column's aggregation in the report editor.<syntaxhighlight lang="gherkin">
And I set the "column title" column aggregation to "aggregation method"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I set the "First name" column aggregation to "Comma separated values"
</syntaxhighlight>

The following step needs to be used in scenarios that involve testing BigBlueButton. For this to work, you need to have a [https://github.com/moodlehq/bigbluebutton_mock BigBlueButton Mock API Server] and set <code>TEST_MOD_BIGBLUEBUTTONBN_MOCK_SERVER</code> to point to that in config.php.<syntaxhighlight lang="gherkin">
And a BigBlueButton mock server is configured
</syntaxhighlight>

The following step replicates receiving a callback from the BigBlueButton server indicating the recordings for meetings are ready for viewing.<syntaxhighlight lang="gherkin">
And the BigBlueButtonBN server has sent recording ready notifications
</syntaxhighlight>

The following steps are specific to the lesson activity. Note that in 4.0, some links (such as the "edit" and the "grade essays" links) are replaced by buttons, so you need to update your old steps with the new ones.<syntaxhighlight lang="gherkin">
And I edit the lesson
</syntaxhighlight>A new step is added to be used in lesson activities to edit them. This step navigates the user to the lesson edit page.
<syntaxhighlight lang="gherkin">
And I grade lesson essays
</syntaxhighlight>It's a new step to go to the "Grade essays" page of the lesson we are currently in.
<syntaxhighlight lang="gherkin">
And I select edit type "edit type"
</syntaxhighlight>Select the lesson edit type when we are in the the lesson's edit page. "edit type" can either be "Collapsed" or "Expanded".

The following new step can be used to navigate to the exports page in the course gradebook and select the specified export type from the grade exports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "export option" export page in the course gradebook
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "XML file" export page in the course gradebook
</syntaxhighlight>

Similarly, there's a new step to navigate to the imports page in the course gradebook and select the specified import type from the grade imports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "import option" import page in the course gradebook
</syntaxhighlight>
=== Boost steps ===
In addition to the steps listed in the previous section, there are also some Boost specific steps coming with Moodle 4.0. These steps only work in Boost or Boost child themes, so you need to make sure they are not used in scenarios that may be run by non-Boost themes.

The following step checks whether a node is active in the secondary navigation.<syntaxhighlight lang="gherkin">
And I should see :name is active in secondary navigation
</syntaxhighlight>

The Boost theme shows the language selector menu in the primary navigation when not logged in, and within the user menu when logged in. The following steps are to check if the primary navigation includes the language selector menu.<syntaxhighlight lang="gherkin">
And language selector menu should exist in the navbar
And language selector menu should not exist in the navbar
</syntaxhighlight>

And the following steps can be used to check whether an item exists in the language selector menu in the Boost theme.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the language selector menu
And "item text" "selector type" should not exist in the language selector menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "English &lrm;(en)&lrm;" "link" should exist in the language selector menu
</syntaxhighlight>
=== Modified steps ===
The step <code>I change the (window|viewport) size to "size"</code> now supports 2 new values for the size argument. The size argument now accepts <code>mobile</code> and <code>tablet</code> values in addition to <code>small</code>, <code>medium</code> and <code>large</code>.
=== Removed steps ===
Some behat steps are removed or replaced with new steps.

As a result of some design changes, hidden or restricted activities are no longer dimmed. Therefore the step<syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be dimmed
</syntaxhighlight>is now removed.
Depending on what you were using that step for, you may be able to use these steps:<syntaxhighlight lang="gherkin">
And "Label name" label should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And I should see "Activity or resource name"
And "Activity or resource name" "link" should not exist in the "region-main" "region"
</syntaxhighlight>
=== Other things to consider ===
To make behat tests more readable and easy to maintain, it is recommended to use the most direct steps to get what the test needs. It is highly recommended to use
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
instead of navigating to the activity via
I am on "Course" course homepage
I follow "Activity name"
Now that [https://docs.moodle.org/dev/Prototypes#Course_creation_improvements Course index] is integrated these behat steps
I am on "Course" course homepage
I follow "Activity name"
will fail using Boost theme.

The reason for it is that the drawer used in Boost is hiding the course index. So when the test is trying to follow an "Activity name" link, it finds two different links:
* one in the course index
* another one in the course main content.
But the first one, the one in the course index, is hidden by the drawer, and the test fails.

However the recommended behat steps
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
Old behat steps that may now fail can be updated to the new steps.
For example:
And I am on the "Test assignment name" "assign activity" page logged in as teacher1
instead of:
When I log in as "teacher1"
And I am on "Course" course homepage
And I follow "Test assignment name"
There are also similar stream-lined navigation steps for accessing question bank pages. See MDL-74130.
== Other ==
=== Core plugins review ===
A few plugins from core Moodle LMS which are no longer or hardly used have been removed and, if appropriate, added to the Moodle plugins directory.

More information about this project, the list of plugins to be removed and the process to follow for keeping them before upgrading to 4.0 can be found in the [[Core plugins review]] page.
=== Site admin presets plugin ===
The third-party plugin [https://moodle.org/plugins/block_admin_presets Admin presets], created by David Monllaó and maintained by developers from [https://pimenko.com/ Pimenko] has been adapted and integrated into Moodle 4.0. It stores settings and plugins status (enabled/disabled) in what's called "presets" to let admins quickly switch between different configurations.

More information about this project can be found in the [[Site admin presets|Site admin presets plugin]] page.
=== JavaScript browser support changes ===
From Moodle 4.0, Internet Explorer is no longer supported. See MDL-73915 and MDLSITE-6109 for further information on this change.

This change means that changes built on 4.0 onwards (including the master branch) will be different to older versions of Moodle.

For plugin developers supporting multiple versions of Moodle using a single plugin version, the compiled javascript files are backwards compatible and will _work_ on all supported versions, however if you run the `grunt` command on multiple versions you will see unbuilt changes. Running grunt on all versions of Moodle is not necessary and this check can be safely disabled for Moodle versions 3.9 - 4.0, as long as only at least you run `grunt` against at least one version of Moodle.

If you need to support Internet Explorer and do not wish to fork your plugin for Moodle 4.0 onwards, then it is recommended that you run `grunt` on an older version of Moodle.
=== The course index element ===
The new course index feature can be themed using a set of scss variables. Use them to change the look and feel instead of adding custom css
/theme/boost/scss/moodle/courseindex.scss
With the introduction of the course index component, the previous and next links shown underneath each activity are no longer needed and they will be removed.
=== Activity icons ===
The icons used for activities have been redesigned and updated for all core moodle activities.

When viewing the new icons in a file manager, for example for the quiz activity, you will see a simple black monochrome icon with a transparent background.

On the course page, or in the activity chooser, the icon will display as a white icon on a coloured background. Styling of the icons on the coursepage is controlled by the css in theme/boost/scss/moodle/icons.scss.

The background colour for activity icons is set using a new variable in function [modname]_supports(). The quiz activity is of type assessment, so in function quiz_supports() there is a new line defining the purpose:
case FEATURE_MOD_PURPOSE: return MOD_PURPOSE_ASSESSMENT;
Available purposes are:
* MOD_PURPOSE_COMMUNICATION
* MOD_PURPOSE_ASSESSMENT
* MOD_PURPOSE_COLLABORATION
* MOD_PURPOSE_CONTENT
* MOD_PURPOSE_ADMINISTRATION
* MOD_PURPOSE_INTERFACE
The background colours linked to these purposes are set in theme/boost/scss/moodle/variables.scss
$activity-icon-colors: map-merge(
(
"administration": #5d63f6,
"assessment": #eb66a2,
"collaboration": #f7634d,
"communication": #11a676,
"content": #399be2,
"interface": #a378ff
),
$activity-icon-colors
);
If activity plugins do not define FEATURE_MOD_PURPOSE the activity icon will be rendered against a light grey background. There is no requirement to define the purpose of activity plugins, it will only affect the icon styling.

Plugins implementing the variable FEATURE_MOD_PURPOSE are only supported on Moodle 4.0 and newer.

Customising the activity icon can be done in an alternative way. For example using the styles.css in mod/[pluginname/styles.css

In the example below the activity plugin developer chooses to keep the coloured icon for the activity and render it as large as the coloured background on the core activities
.modicon_subcourse.activityiconcontainer {
background-color: transparent;
padding: 0;
}

.modicon_subcourse.activityiconcontainer img {
width: 50px;
height: 50px;
}
To customize all icon colours use this scss array and add it to the ‘Raw initial SCSS’ in the theme Boost advanced settings page. The complete array of icon background colours can be overridden using the ‘Raw initial SCSS’ in the theme settings page. The example below changes the colours of each activity type.
$activity-icon-colors: (
"administration": #5D63F6,
"assessment": #11A676,
"collaboration": #EB66A2,
"communication": #F7634D,
"content": #399BE2,
"interface": #A378FF
)
== I'm a developer, what do I need to know? ==
=== Modules ===
If you are a module developer (activity / resources) then you need to review the following updates and changes:
* If using settings, reformat to work with the secondary navigation. We have significantly changed the way that settings are shown. Settings added to the course and activity administration branch of the navigation are now by default shown in the secondary navigation. You will most likely find them in the more section of the secondary navigation. Please avoid creating settings in containers (a parent navigation node with children). These settings will still be shown, but this goes against the pattern that we are trying to establish for navigation around the site. If you have a lot of settings, consider creating a specific page to handle your additional settings.
** The order of the items in the secondary navigation may not be to your liking. This can be changed. See [[Moodle_4.0_developer_update#Changing_the_order_of_tabs|changing the order of tabs]]
* Update my behat tests to use new steps for site navigation. See [[Moodle_4.0_developer_update#Behat_changes|new behat steps]].
* Update my module to use the new activity_header API. See [[Moodle_4.0_developer_update#The_activity_header_class|the activity header]].
* Update my pages to make it work with the general format of the tertiary navigation. See [[Moodle_4.0_developer_update#Tertiary_navigation|the tertiary navigation]].
* Update my activity icon to use the API and set a purpose. See [[Moodle_4.0_developer_update#Activity_icons|activity icons]].
=== Themes ===
If you are a theme developer then you may want to consider the following:
* Take a look at the [[Moodle_4.0_developer_update#Navigation_changes|new navigation]] and decide if you want to incorporate this into your theme.
** A new layout ([[Moodle_4.0_developer_update#New_layout_page|drawers]])
** An [[Moodle_4.0_developer_update#Edit_switch|edit switch]]
** The [[Moodle_4.0_developer_update#The_course_index_element|course index]]
* Use of the flat nav
* New Site administration page and layout
* Course settings and how they are displayed

Moodle 4.0 developer update

2022-03-14T07:30:36Z

Abgreeve: Change to unordered list

{{Moodle 4.0}}This page highlights the important changes that are coming in Moodle 4.0 for developers. Including how the UX improvements impact custom themes, relevant API changes, and what you can do as developer to prepare for the 4.0 release.
== Navigation changes ==
The core Navigation API has been left mostly untouched. The callbacks to all navigation callbacks remains unchanged and will be called as part of the regular 'navigation' and 'settingsnav' initialisation. Some new core classes have been created and exist within a new namespace 'core/navigation' and serves as conduit to rearrange, cherry-pick existing navigation nodes from the navigation/settingsnav trees and display within the respective navigation type. As such, it is highly recommended to provide unique keys for custom navigation nodes as this helps in the cherry-picking / rearranging process within the new classes.
=== Primary navigation ===
The primary navigation(the navbar) apart from the existing content will now display links to the Dashboard, My Courses, Site Admin and Course search, by default. You can still add items to the navbar via the 'custom menu' option. This will be displayed within the 'More' menu. We have transitioned the menus to be rendered via templates - refer user_menu.mustache. The lang menu has been moved to reside within the user menu.
==== Customising the primary navigation ====
Not yet implemented but we are looking at allowing the full addition and removal of any of the primary navigation tabs in the boost theme config file.
=== Secondary navigation ===
The main content area shows tabs for secondary navigation with a maximum of 5 items being rendered in this ‘more’ menu. A new UI component has been created to render menus like this. Files:
/lib/templates/moremenu.mustache
==== Changing the order of tabs ====
Apart from the previously mentioned functions, you can also create a custom secondary class as mentioned earlier. This will automatically be picked by getter and used to render the secondary nav within the activity. E.g. mod_assign/local/views/secondary. Note: This is currently only possible on an activity and block level.
=== Tertiary navigation ===
We've moved action buttons to the top of the page. We would encourage you to do the same.
If you have any buttons on an activity page that go to another page, or open a form (or similar), then we encourage you to move them from the body of your activity page to the top. All of the core activities have been updated to follow this pattern. Please take a look to see how you can format your activity in a similar fashion. There is no API here. You are welcome to create the buttons and display them as you wish in this top area.

=== New API functions ===
==== Page API ====
* Magic getters to fetch the primary and secondary navs and the primary output.
* The secondarynav magic getter also checks whether a custom secondary class has been defined within the module's local\views directory. Use this if you want to deviate from the standard secondary nav structure/order.

* set_secondary_nav - Force override the secondary navigation class

* has_secondary_navigation_setter - Sets the ‘_hassecondarynavigation’ to indicate whether a page should render the secondary navigation
==== Navigationlib ====
* set_show_in_secondary_navigation - whether or not a node should be displayed in the secondary nav. Accepts a single boolean argument
* set_force_into_more_menu- whether or not to force a node into the 'More' menu. Accepts a single boolean argument
==== The activity header class ====
There is a new activity header class that handles the display of information common to activities. 3rd party activities are not required to explicitly output this information as part of rendering individual pages.

The common information that are currently handled by the class are:
* title
* description
* completion information

As part of the update it was required that the initial information to be displayed by the class be toggable at a theme and layout level. Taking this into account the following theme level configurable exists:
* activityheaderconfig => An array that currently only enforces 'notitle' but can be expanded in the future NOTE: Boost has this set as true by default 'options'
The following layout level options that can be defined:
* noactivityheader - to remove the header in this specific layout.
* activityheader - An array that enforces the following options:
** notitle
** nocompletion
** nodescription
The class has a page level getter which you can use to fetch the current version of the class. The base state is initialised within the constructor with the completion information only fetched when data is exported for the template.

The class has setters for the following variables which can be leveraged to modify the header for a particular page in the format set_{variable_name}:
* hidecompletion
* description
* title
Alternately, bulk operations can also be done by passing the above variables in an array to 'set_attrs' which in turn calls the setters.<blockquote>'''Note: Any updates to the activityheader needs to be performed before the call to $OUTPUT->header'''</blockquote>
===== Theme updates: =====
In order for 3rd party themes to use the class they need to export the activity_header and include the following into their base template :<syntaxhighlight lang="html">
{{#headercontent}}
{{> core/activity_header}}
{{#headercontent}}
</syntaxhighlight>** headercontent being the array element that contains the exported activity_header data
===== Accessibility notes: =====
The jump to ‘maincontent’ div is now rendered within the activity header when within an activity context
== Component library ==
Each Moodle installation now ships with a Moodle User Interface (UI) Component library, a documentation system used to describe all the Bootstrap components and the custom Moodle components. The component Library is a helper tool for developers when creating user interfaces, a testing tool for theme developers and a documentation tool for core developers. The ultimate goal of having a component library is to encourage developers to create consistent user interfaces to improve Moodle’s overall user experience.

The library contains pages with documentation about User Interface components. It contains details on how to use the component, what variations are available and the JavaScript events / options are associated with the component.

When writing on these pages it is possible to render core mustache templates using some custom syntax like this:
<nowiki>{{< mustache template="core/notification_error" >}}</nowiki>
<nowiki>{{< /mustache >}}</nowiki>
You can also call core JavaScript or use HTML examples where the html code and the rendered result are visible in the Component Library. For more info visit the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-templates/ Moodle templates] page or the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-javascript/ Moodle JavaScript] page.

Each page in the library uses the current css from the default theme in your Moodle installation, if you have multiple themes installed and enabled the setting "Allow theme changes on url", the component library will have a theme selector option.

A hosted version of the Component Library can be found here. http://componentlibrary.moodle.com
=== Enabling the Component Library ===
Component library pages are written in the markdown language. These pages need to be compiled to HTML pages before the Component Library is visible. To compile the pages the server running Moodle needs to have the [[Javascript Modules#Install%20NVM%20and%20Node|JavaScript developer tools installed]] (nodeJs and Grunt)

If your server meets all requirements you can enable the library running
$ npm install
$ grunt componentlibrary
Further installation instructions can be found in the Component Library itself.
=== Documenting new UI Components ===
There are no set rules for adding new pages in the component library yet. These rules will need to be written and adopted in the integration process for Moodle code.

As a guideline for making this rules consideration are:

The component library is not about single use components, for example the Moodle grade book (a huge component with many custom features). Or about very common components like buttons, these are already covered by the Bootstrap section of the component library.

New features should be build keeping in mind the UI part needs to be customisable and if possible (and making sense) reusable. And example would be the new page drawers that we are introducing for the Navigation project. Or the custom primary navigation menus where overflowing items are pushed into a More section.
== Theme changes ==
=== Edit switch ===
On theme boost the “Turn editing on” and “Customise this page” buttons have been replaced by an edit switch in the top navbar. Theme Classic will keep using the old buttons. Child themes can choose to use the edit switch if the theme config.php is using this variable
$THEME->haseditswitch = true;
The languague menu, which used to be rendered in place of the custom menu has moved to the user dropdown when the user is logged in. If not logged in it will be placed next to the search / notification / messaging icon in the top navbar.
=== Login page ===
The login page has been redesigned and allows the admin to configure a background image for the login page only in the theme settings page. This change is available in both Boost and Classic. The login page still has all the features with an improved layout.
=== The page footer ===
In large screens, the page footer button is only visible when clicking a help button at the bottom right of the screen.
=== User initials as profile picture placeholder ===
If users do not upload a profile picture the user initials are displayed on a rounded gray background as a placeholder picture in the top navbar or any other page using a placeholder image. This change will be available in both Boost and Classic.

With the introduction of this placeholder image the full username will no longer be displayed in the top navbar.
=== Removal of back to top link ===
The "back to top" link will be removed for theme boost since the new course index reduced the dependence on page scrolling. Also, the new footer is positioned where this component used to be.
=== Styling changes ===
By default rounded edges will be used for UI components, for the page header and main content area the borders will be removed.
=== New layout page ===
Theme boost now uses the drawers.php layout for the course index and blocks.
== Question bank changes ==
There was a big project to deliver [[Question bank improvements for Moodle 4.0]] which added a new plugin type for adding features to the question banks, tracking the version history for each question as it is edited (question table has been split into <code>question</code>, <code>question_versions</code> and <code>question_bank_entries</code>), and tracking where each question is going to be used, with new tables <code>question_references</code> and <code>question_set_references</code>. This work was done in Epic MDL-70329 if you want to track down the details of any of the core changes.
=== Question type plugins ===
Amazingly, we (Safat and colleagues at Catalyst AU) managed to implement this without breaking most question type plugins.

However, the changes to the question bank, and the other Moodle 4.0 changes, probably broke the Behat tests for your plugin. To help with fixing that, MDL-74130 adds navigation to key question type pages (Preview and Edit for a question, and standard question bank pages like the bank itself, import and export) which should let you fix your test efficiently, and in a way that will work in all Moodle versions since 3.9.

The 'most' in the first paragraph here is becuase more advance question types may require more effort to fix. (For example qtype_combined which creates multi-part qusetions like the core qtype_multianswer; or qtype_pmatch or qtype_stack, which store additional data - questions tests - alongside the question itseld. How should that work with versionning?) But, if you have not done weird things like that, you are probably safe. If you find anything else that causes problems, please list it here.

The same thing should apply to question behaviour and question import/export format plugings: no significant changes required (probably just fixing the Behat tests because of the navigation changes).
=== New plugin type: qbank plugins ===
This is not something that will cause problems for people upgrading from 3.x. Rather, it is an exciting possibility you can explore once you have survived process of upgrading to 4.0. There is a whole new plugin type which you can create to add new features to the question bank. For example extra columns, new actions and bulk actions, and so on. See [[Question_bank_plugins]].
=== Activities that use questions ===
The probable bad news is if you have an activity module which uses questions. So far, the only activity which has been fixed is mod_quiz in Moodle core, so we don't yet have a good picture of what fixes will be necessary in other activities. Work is about to start fixing [https://github.com/studentquiz/moodle-mod_studentquiz mod_studentquiz], so watching that should give more clues. As we do that, we will try to update this section of this page. Other help writing the information required here would also be greatly appreciated.
== The course format system ==
Most of the logic for rendering and editing a course has been moved to a new subsystem called courseformat. The subsystem is located in "course/format" folder so it includes all the format plugins inside. The methods and modules which are distributed between the course and the course/format folders are now rearranged or refactored to be aligned with the current Moodle coding style.
=== Mandatory renderer in course formats ===
Now format plugins renderer is not optional anymore. Legacy formats without a renderer will get a deprecation message but it will continue working however, they should create a new renderer as soon as possible. The section-based format can do it by extending the provided core_courseformat\output\section_renderer class which includes all the necessary methods.
=== New format base class ===
The old base_format class (which all plugins extend) is now renamed as core_courseformat\base. The new class provides all the functionally of the previous base_format but it has been refactored to be used as a centralized source of truth for the course rendering. Legacy formats should extend the new class to avoid the deprecation message.

Now, the plugin format class provides information such as:
* If the page is displaying a single or multiple section
* Give access to other related format objects like the modinfo, the course record, maximum number of sections...
* If the format is compatible with features like course index, reactive components, ajax...
* Other format specifics like the page title, the default section name, default blocks...

The format instance is now the main object output components will use to render a course (see next section for more information).
=== New course output classes and mustache files ===
Traditionally, section-based course formats uses print_single_section_page and print_multiple_section_page to render the course content. In Moodle 4.0 most of the course rendering methods are migrated to output components and mustache templates. The old methods will get deprecation messages if they use the old renderer methods.

This is an example of a format rendering a course:<syntaxhighlight lang="php-brief">
// Get the course format instance.
$format = course_get_format($course);

// Get the specific format renderer.
$renderer = $format->get_renderer($PAGE);

if (!empty($displaysection)) {
// Setup the format instance to display a single section.
$format->set_section_number($displaysection);
}

// Create the ouptut instance and render it.
$outputclass = $format->get_output_classname('content');
$widget = new $outputclass($format);

echo $renderer->render($widget);
</syntaxhighlight>Format plugins are free to use its own output classes to render a course, or they could override the existing output classes by providing their own implementation. For example, the default output for "content" (as in the previous example) is "core_courseformat\output\local\|content", however, if the plugin has a "format_XXX\output\courseformat\content" class, the $format->class the get_output_class will return the overridden one.
Another important update on course rendering is that now all course structure is rendered using mustache templates instead of the original html_writer methods. Now themes are able to override the course format by providing alternative versions of the mustache files. All core course templates are located in "course/format/templates".

All the new output classes and a guide on how to migrate the current third-party plugins will be available soon.
=== Course editor javascript modules and frontend components ===
The majority of the javascript logic related to the course editing is replaced by AMD modules. Because this is a major change in the way courses are edited and rendered, by default format plugins will continue using the previous YUI modules for now. However, formats can start using the new libraries overriding the "$format->supports_components()" method.

Some Moodle 4.0 new features are only available for courses using the new editor library:
* Edit the course via the course index
* Creating sections without reloading the course page
* The new move section/activity modal
* Native browser drag&drop implementation
The new course editor uses a component-based reactive pattern to keep track of the course changes. The pattern highlights are:
* The main AMD module "core_crouseformat\courseeditor" maintains a data structure called state.
* Each UI element is implemented as a Component that observes the course state data and reacts to any data change
* When any reactive component needs to modify the course, it asks the course editor to execute a mutation. Mutations encapsulate all web services calls and alter the course state data.

The reactive library documentation, as well as the format plugin migration guide, will be available soon.
=== Other course related 4.0 changes ===
Two new web services have been added:
* core_courseformat_get_state: user by the new javascript course editor to get the current course state data (containing the list of sections, activities, and other course-related data)
* core_courseformat_update_course: to alter the current course content. Each call returns the parts of the course state altered by the action
== Behat changes ==

=== New steps ===
Moodle 4.0 introduces some new behat steps.

Sometimes you want to create a bulk number of activities. In that case you can use:<syntaxhighlight lang="gherkin">
:count :entitytype exist with the following data:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
Given 100 "mod_lti > tool types" exist with the following data:
|name |Test tool [count] |
|description |Example description [count] |
|baseurl |https://www.example.com/tool[count]|
</syntaxhighlight>

Dynamic (AJAX) tabs is a new feature contributed to Moodle 4.0 by the Workplace team (MDL-71943). You can use the following step to navigate between the tabs.<syntaxhighlight lang="gherkin">
And I click on the "tab title" dynamic tab
</syntaxhighlight>

To make sure that edit mode is (or is not) available on the current page, the following steps can be used.<syntaxhighlight lang="gherkin">
And edit mode should be available on the current page
And edit mode should not be available on the current page
</syntaxhighlight>

There are new aliases for the existing steps <code>I turn editing mode on</code> and <code>I turn editing mode off</code>.<syntaxhighlight lang="gherkin">
And I switch editing mode on
And I switch editing mode off
</syntaxhighlight>

In addition to the existing step to go to a course with editing mode on, we now have the following step to do the same but with editing mode being off.<syntaxhighlight lang="gherkin">
And I am on "course full name" course homepage with editing mode off
</syntaxhighlight>

The following step is similar to the old <code>following "link string" should download between "min bytes" and "max bytes" bytes</code> step, with more flexibility.<syntaxhighlight lang="gherkin">
And following "element string" "element type" in the "container string" "container type" should download between "min bytes" and "max bytes" bytes
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And following "Download" "link" in the "Starter" "table_row" should download between "0" and "5000" bytes
</syntaxhighlight>

The following step can be used to hover the mouse over the trigger area.<syntaxhighlight lang="gherkin">
And I hover over the "element string" "element type" in the "container string" "container type"
</syntaxhighlight>

The following step enables an installed plugin.<syntaxhighlight lang="gherkin">
And I enable "plugin name" "plugin type" plugin
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I enable "course_summary" "block" plugin
</syntaxhighlight>

The following is a special variation of 'I click on "<page name>" "link" in the "page" "region"'. It first checks to see if we are on the given page via the breadcrumb. If not we then attempt to follow the link name given.<syntaxhighlight lang="gherkin">
And I follow the breadcrumb "page name"
</syntaxhighlight>

You can use the following step to ensure a node is active in the navbar.<syntaxhighlight lang="gherkin">
And I should see "Node" is active in navigation
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I should see "My courses" is active in navigation
</syntaxhighlight>

The following step can be used to navigate to a given node in the primary navigation.<syntaxhighlight lang="gherkin">
And I select "Node" from primary navigation
</syntaxhighlight>

The following steps are to check whether an item exists in the user menu or not.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the user menu
And "item text" "selector type" should not exist in the user menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "Language" "link" should exist in the user menu
</syntaxhighlight>

The following steps are to check if a submenu of the user menu is shown, and if an item exists or does not exist in a given user submenu.<syntaxhighlight lang="gherkin">
And I should see "submenu name" user submenu
And "item text" "selector type" should exist in the "submenu name" user submenu
And "item text" "selector type" should not exist in the "submenu name" user submenu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I follow "Language" in the user menu
Then I should see "Language selector" user submenu
And "English &lrm;(en)&lrm;" "link" should exist in the "Language selector" user submenu
And "English (pirate) &lrm;(en_ar)&lrm;" "link" should not exist in the "Language selector" user submenu
</syntaxhighlight>

To add enrolment methods to courses you can use the following new step. The data that you provide in the next lines are used to fill the enrolment method form.<syntaxhighlight lang="gherkin">
And I add "enrolment method" in "course identifier" with:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I add "Self enrolment" enrolment method in "Course 1" with:
| Custom instance name | Test student enrolment |
| Enrolment key | moodle_rules |
| Use group enrolment keys | Yes |
</syntaxhighlight>

There are 3 new steps specific to the calendar component. These steps can be used to hover over a day in the mini-calendar or the full calendar.<syntaxhighlight lang="gherkin">
And I hover over day "day of month" of this month in the full calendar page
And I hover over day "day of month" of this month in the mini-calendar block
And I hover over today in the mini-calendar block
</syntaxhighlight>

Some new steps are added to question bank to be able to add comment to questions, verify the existence of a comment, and deleting comments form questions. Please note that the steps for adding comments only write the comment text in the comment field. You still need to click on the "Add comment" button to save the comment.<syntaxhighlight lang="gherkin">
And I add "comment text" comment to question
And I add "comment text" comment to question preview
And I delete "comment text" comment from question
And I delete "comment text" comment from question preview
And I should see "number of comments" on the comments column
And I click "number of comments" on the row on the comments column

</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "Question bank" in current page administration
And I should see "0" on the comments column
And I click "0" on the row on the comments column
And I add "test comment 01" comment to question
And I click on "Add comment" "button" in the ".modal-dialog" "css_element"
And I click on "Close" "button" in the ".modal-dialog" "css_element"
And I should see "1" on the comments column
And I click "1" on the row on the comments column
And I delete "test comment 01" comment from question
</syntaxhighlight>

Similar to the steps for comments, the following steps are to verify the number of a question's usage and to click on it in order to open the question usage modal.<syntaxhighlight lang="gherkin">
And I should see "usage count" on the usage column
And I click "usage count" on the usage column
</syntaxhighlight>

The following new steps are related to bulk actions in the question bank UI.<syntaxhighlight lang="gherkin">
And I click on question bulk action "action"
And I should see question bulk action "action"
And I should not see question bulk action "action"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I click on "First question" "checkbox"
And I click on "Second question" "checkbox"
And I click on "With selected" "button"
And I should see question bulk action "deleteselected"
And I click on question bulk action "deleteselected"
And I click on "Delete" "button" in the "Confirm" "dialogue"
</syntaxhighlight>

[https://docs.moodle.org/en/Report_builder Report builder] is a new feature contributed to Moodle 4.0 by the Workplace team. The following new step is added to Moodle 4.0 to select an action from the action menu in the list of custom reports table.<syntaxhighlight lang="gherkin">
And I press "action" action in the "report name" report row
</syntaxhighlight>

There's another step related to the report builder to set a column's aggregation in the report editor.<syntaxhighlight lang="gherkin">
And I set the "column title" column aggregation to "aggregation method"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I set the "First name" column aggregation to "Comma separated values"
</syntaxhighlight>

The following step needs to be used in scenarios that involve testing BigBlueButton. For this to work, you need to have a [https://github.com/moodlehq/bigbluebutton_mock BigBlueButton Mock API Server] and set <code>TEST_MOD_BIGBLUEBUTTONBN_MOCK_SERVER</code> to point to that in config.php.<syntaxhighlight lang="gherkin">
And a BigBlueButton mock server is configured
</syntaxhighlight>

The following step replicates receiving a callback from the BigBlueButton server indicating the recordings for meetings are ready for viewing.<syntaxhighlight lang="gherkin">
And the BigBlueButtonBN server has sent recording ready notifications
</syntaxhighlight>

The following steps are specific to the lesson activity. Note that in 4.0, some links (such as the "edit" and the "grade essays" links) are replaced by buttons, so you need to update your old steps with the new ones.<syntaxhighlight lang="gherkin">
And I edit the lesson
</syntaxhighlight>A new step is added to be used in lesson activities to edit them. This step navigates the user to the lesson edit page.

<syntaxhighlight lang="gherkin">
And I grade lesson essays
</syntaxhighlight>It's a new step to go to the "Grade essays" page of the lesson we are currently in.

<syntaxhighlight lang="gherkin">
And I select edit type "edit type"
</syntaxhighlight>Select the lesson edit type when we are in the the lesson's edit page. "edit type" can either be "Collapsed" or "Expanded".

The following new step can be used to navigate to the exports page in the course gradebook and select the specified export type from the grade exports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "export option" export page in the course gradebook
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "XML file" export page in the course gradebook
</syntaxhighlight>

Similarly, there's a new step to navigate to the imports page in the course gradebook and select the specified import type from the grade imports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "import option" import page in the course gradebook
</syntaxhighlight>

=== Boost steps ===
In addition to the steps listed in the previous section, there are also some Boost specific steps coming with Moodle 4.0. These steps only work in Boost or Boost child themes, so you need to make sure they are not used in scenarios that may be run by non-Boost themes.

The following step checks whether a node is active in the secondary navigation.<syntaxhighlight lang="gherkin">
And I should see :name is active in secondary navigation
</syntaxhighlight>

The Boost theme shows the language selector menu in the primary navigation when not logged in, and within the user menu when logged in. The following steps are to check if the primary navigation includes the language selector menu.<syntaxhighlight lang="gherkin">
And language selector menu should exist in the navbar
And language selector menu should not exist in the navbar
</syntaxhighlight>

And the following steps can be used to check whether an item exists in the language selector menu in the Boost theme.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the language selector menu
And "item text" "selector type" should not exist in the language selector menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "English &lrm;(en)&lrm;" "link" should exist in the language selector menu
</syntaxhighlight>

=== Modified steps ===
The step <code>I change the (window|viewport) size to "size"</code> now supports 2 new values for the size argument. The size argument now accepts <code>mobile</code> and <code>tablet</code> values in addition to <code>small</code>, <code>medium</code> and <code>large</code>.

=== Removed steps ===
Some behat steps are removed or replaced with new steps.

As a result of some design changes, hidden or restricted activities are no longer dimmed. Therefore the step<syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be dimmed
</syntaxhighlight>is now removed.

Depending on what you were using that step for, you may be able to use these steps:<syntaxhighlight lang="gherkin">
And "Label name" label should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And I should see "Activity or resource name"
And "Activity or resource name" "link" should not exist in the "region-main" "region"
</syntaxhighlight>

=== Other things to consider ===
To make behat tests more readable and easy to maintain, it is recommended to use the most direct steps to get what the test needs. It is highly recommended to use
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
instead of navigating to the activity via
I am on "Course" course homepage
I follow "Activity name"
Now that [https://docs.moodle.org/dev/Prototypes#Course_creation_improvements Course index] is integrated these behat steps
I am on "Course" course homepage
I follow "Activity name"
will fail using Boost theme.

The reason for it is that the drawer used in Boost is hiding the course index. So when the test is trying to follow an "Activity name" link, it finds two different links:
* one in the course index
* another one in the course main content.
But the first one, the one in the course index, is hidden by the drawer, and the test fails.

However the recommended behat steps
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
Old behat steps that may now fail can be updated to the new steps.
For example:
And I am on the "Test assignment name" "assign activity" page logged in as teacher1
instead of:
When I log in as "teacher1"
And I am on "Course" course homepage
And I follow "Test assignment name"
There are also similar stream-lined navigation steps for accessing question bank pages. See MDL-74130.
== Other ==
=== Core plugins review ===
A few plugins from core Moodle LMS which are no longer or hardly used have been removed and, if appropriate, added to the Moodle plugins directory.

More information about this project, the list of plugins to be removed and the process to follow for keeping them before upgrading to 4.0 can be found in the [[Core plugins review]] page.
=== Site admin presets plugin ===
The third-party plugin [https://moodle.org/plugins/block_admin_presets Admin presets], created by David Monllaó and maintained by developers from [https://pimenko.com/ Pimenko] has been adapted and integrated into Moodle 4.0. It stores settings and plugins status (enabled/disabled) in what's called "presets" to let admins quickly switch between different configurations.

More information about this project can be found in the [[Site admin presets|Site admin presets plugin]] page.
=== JavaScript browser support changes ===
From Moodle 4.0, Internet Explorer is no longer supported. See MDL-73915 and MDLSITE-6109 for further information on this change.

This change means that changes built on 4.0 onwards (including the master branch) will be different to older versions of Moodle.

For plugin developers supporting multiple versions of Moodle using a single plugin version, the compiled javascript files are backwards compatible and will _work_ on all supported versions, however if you run the `grunt` command on multiple versions you will see unbuilt changes. Running grunt on all versions of Moodle is not necessary and this check can be safely disabled for Moodle versions 3.9 - 4.0, as long as only at least you run `grunt` against at least one version of Moodle.

If you need to support Internet Explorer and do not wish to fork your plugin for Moodle 4.0 onwards, then it is recommended that you run `grunt` on an older version of Moodle.
=== The course index element ===
The new course index feature can be themed using a set of scss variables. Use them to change the look and feel instead of adding custom css
/theme/boost/scss/moodle/courseindex.scss
With the introduction of the course index component, the previous and next links shown underneath each activity are no longer needed and they will be removed.
=== Activity icons ===
The icons used for activities have been redesigned and updated for all core moodle activities.

When viewing the new icons in a file manager, for example for the quiz activity, you will see a simple black monochrome icon with a transparent background.

On the course page, or in the activity chooser, the icon will display as a white icon on a coloured background. Styling of the icons on the coursepage is controlled by the css in theme/boost/scss/moodle/icons.scss.

The background colour for activity icons is set using a new variable in function [modname]_supports(). The quiz activity is of type assessment, so in function quiz_supports() there is a new line defining the purpose:
case FEATURE_MOD_PURPOSE: return MOD_PURPOSE_ASSESSMENT;
Available purposes are:
* MOD_PURPOSE_COMMUNICATION
* MOD_PURPOSE_ASSESSMENT
* MOD_PURPOSE_COLLABORATION
* MOD_PURPOSE_CONTENT
* MOD_PURPOSE_ADMINISTRATION
* MOD_PURPOSE_INTERFACE
The background colours linked to these purposes are set in theme/boost/scss/moodle/variables.scss
$activity-icon-colors: map-merge(
(
"administration": #5d63f6,
"assessment": #eb66a2,
"collaboration": #f7634d,
"communication": #11a676,
"content": #399be2,
"interface": #a378ff
),
$activity-icon-colors
);
If activity plugins do not define FEATURE_MOD_PURPOSE the activity icon will be rendered against a light grey background. There is no requirement to define the purpose of activity plugins, it will only affect the icon styling.

Plugins implementing the variable FEATURE_MOD_PURPOSE are only supported on Moodle 4.0 and newer.

Customising the activity icon can be done in an alternative way. For example using the styles.css in mod/[pluginname/styles.css

In the example below the activity plugin developer chooses to keep the coloured icon for the activity and render it as large as the coloured background on the core activities
.modicon_subcourse.activityiconcontainer {
background-color: transparent;
padding: 0;
}

.modicon_subcourse.activityiconcontainer img {
width: 50px;
height: 50px;
}
To customize all icon colours use this scss array and add it to the ‘Raw initial SCSS’ in the theme Boost advanced settings page. The complete array of icon background colours can be overridden using the ‘Raw initial SCSS’ in the theme settings page. The example below changes the colours of each activity type.
$activity-icon-colors: (
"administration": #5D63F6,
"assessment": #11A676,
"collaboration": #EB66A2,
"communication": #F7634D,
"content": #399BE2,
"interface": #A378FF
)

== I'm a developer, what do I need to know? ==
=== Modules ===
If you are a module developer (activity / resources) then you need to review the following updates and changes:

* If using settings, reformat to work with the secondary navigation. We have significantly changed the way that settings are shown. Settings added to the course and activity administration branch of the navigation are now by default shown in the secondary navigation. You will most likely find them in the more section of the secondary navigation. Please avoid creating settings in containers (a parent navigation node with children). These settings will still be shown (details about that), but this goes against the pattern that we are trying to establish for navigation around the site. If you have a lot of settings, consider creating a specific page to handle your additional settings (screenshot?).
** The order of the items in the secondary navigation may not be to your liking. This can be changed. See [[Moodle_4.0_developer_update#Changing_the_order_of_tabs|changing the order of tabs]]
* Update my behat tests to use new steps for site navigation. See [[Moodle_4.0_developer_update#Behat_changes|new behat steps]].
* Update my module to use the new activity_header API. See [[Moodle_4.0_developer_update#The_activity_header_class|the activity header]].
* Update my pages to make it work with the general format of the tertiary navigation. See [[Moodle_4.0_developer_update#Tertiary_navigation|the tertiary navigation]].
* Update my activity icon to use the API and set a purpose. See [[Moodle_4.0_developer_update#Activity_icons|activity icons]].

=== Themes ===
If you are a theme developer then you may want to consider the following:
* Take a look at the [[Moodle_4.0_developer_update#Navigation_changes|new navigation]] and decide if you want to incorporate this into your theme.
** A new layout ([[Moodle_4.0_developer_update#New_layout_page|drawers]])
** An [[Moodle_4.0_developer_update#Edit_switch|edit switch]]
** The [[Moodle_4.0_developer_update#The_course_index_element|course index]]
* Use of the flat nav
* New Site administration page and layout
* Course settings and how they are displayed

Moodle 4.0 developer update

2022-03-14T07:28:38Z

Abgreeve: Base for theme developers

{{Moodle 4.0}}This page highlights the important changes that are coming in Moodle 4.0 for developers. Including how the UX improvements impact custom themes, relevant API changes, and what you can do as developer to prepare for the 4.0 release.
== Navigation changes ==
The core Navigation API has been left mostly untouched. The callbacks to all navigation callbacks remains unchanged and will be called as part of the regular 'navigation' and 'settingsnav' initialisation. Some new core classes have been created and exist within a new namespace 'core/navigation' and serves as conduit to rearrange, cherry-pick existing navigation nodes from the navigation/settingsnav trees and display within the respective navigation type. As such, it is highly recommended to provide unique keys for custom navigation nodes as this helps in the cherry-picking / rearranging process within the new classes.
=== Primary navigation ===
The primary navigation(the navbar) apart from the existing content will now display links to the Dashboard, My Courses, Site Admin and Course search, by default. You can still add items to the navbar via the 'custom menu' option. This will be displayed within the 'More' menu. We have transitioned the menus to be rendered via templates - refer user_menu.mustache. The lang menu has been moved to reside within the user menu.
==== Customising the primary navigation ====
Not yet implemented but we are looking at allowing the full addition and removal of any of the primary navigation tabs in the boost theme config file.
=== Secondary navigation ===
The main content area shows tabs for secondary navigation with a maximum of 5 items being rendered in this ‘more’ menu. A new UI component has been created to render menus like this. Files:
/lib/templates/moremenu.mustache
==== Changing the order of tabs ====
Apart from the previously mentioned functions, you can also create a custom secondary class as mentioned earlier. This will automatically be picked by getter and used to render the secondary nav within the activity. E.g. mod_assign/local/views/secondary. Note: This is currently only possible on an activity and block level.
=== Tertiary navigation ===
We've moved action buttons to the top of the page. We would encourage you to do the same.
If you have any buttons on an activity page that go to another page, or open a form (or similar), then we encourage you to move them from the body of your activity page to the top. All of the core activities have been updated to follow this pattern. Please take a look to see how you can format your activity in a similar fashion. There is no API here. You are welcome to create the buttons and display them as you wish in this top area.

=== New API functions ===
==== Page API ====
* Magic getters to fetch the primary and secondary navs and the primary output.
* The secondarynav magic getter also checks whether a custom secondary class has been defined within the module's local\views directory. Use this if you want to deviate from the standard secondary nav structure/order.

* set_secondary_nav - Force override the secondary navigation class

* has_secondary_navigation_setter - Sets the ‘_hassecondarynavigation’ to indicate whether a page should render the secondary navigation
==== Navigationlib ====
* set_show_in_secondary_navigation - whether or not a node should be displayed in the secondary nav. Accepts a single boolean argument
* set_force_into_more_menu- whether or not to force a node into the 'More' menu. Accepts a single boolean argument
==== The activity header class ====
There is a new activity header class that handles the display of information common to activities. 3rd party activities are not required to explicitly output this information as part of rendering individual pages.

The common information that are currently handled by the class are:
* title
* description
* completion information

As part of the update it was required that the initial information to be displayed by the class be toggable at a theme and layout level. Taking this into account the following theme level configurable exists:
* activityheaderconfig => An array that currently only enforces 'notitle' but can be expanded in the future NOTE: Boost has this set as true by default 'options'
The following layout level options that can be defined:
* noactivityheader - to remove the header in this specific layout.
* activityheader - An array that enforces the following options:
** notitle
** nocompletion
** nodescription
The class has a page level getter which you can use to fetch the current version of the class. The base state is initialised within the constructor with the completion information only fetched when data is exported for the template.

The class has setters for the following variables which can be leveraged to modify the header for a particular page in the format set_{variable_name}:
* hidecompletion
* description
* title
Alternately, bulk operations can also be done by passing the above variables in an array to 'set_attrs' which in turn calls the setters.<blockquote>'''Note: Any updates to the activityheader needs to be performed before the call to $OUTPUT->header'''</blockquote>
===== Theme updates: =====
In order for 3rd party themes to use the class they need to export the activity_header and include the following into their base template :<syntaxhighlight lang="html">
{{#headercontent}}
{{> core/activity_header}}
{{#headercontent}}
</syntaxhighlight>** headercontent being the array element that contains the exported activity_header data
===== Accessibility notes: =====
The jump to ‘maincontent’ div is now rendered within the activity header when within an activity context
== Component library ==
Each Moodle installation now ships with a Moodle User Interface (UI) Component library, a documentation system used to describe all the Bootstrap components and the custom Moodle components. The component Library is a helper tool for developers when creating user interfaces, a testing tool for theme developers and a documentation tool for core developers. The ultimate goal of having a component library is to encourage developers to create consistent user interfaces to improve Moodle’s overall user experience.

The library contains pages with documentation about User Interface components. It contains details on how to use the component, what variations are available and the JavaScript events / options are associated with the component.

When writing on these pages it is possible to render core mustache templates using some custom syntax like this:
<nowiki>{{< mustache template="core/notification_error" >}}</nowiki>
<nowiki>{{< /mustache >}}</nowiki>
You can also call core JavaScript or use HTML examples where the html code and the rendered result are visible in the Component Library. For more info visit the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-templates/ Moodle templates] page or the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-javascript/ Moodle JavaScript] page.

Each page in the library uses the current css from the default theme in your Moodle installation, if you have multiple themes installed and enabled the setting "Allow theme changes on url", the component library will have a theme selector option.

A hosted version of the Component Library can be found here. http://componentlibrary.moodle.com
=== Enabling the Component Library ===
Component library pages are written in the markdown language. These pages need to be compiled to HTML pages before the Component Library is visible. To compile the pages the server running Moodle needs to have the [[Javascript Modules#Install%20NVM%20and%20Node|JavaScript developer tools installed]] (nodeJs and Grunt)

If your server meets all requirements you can enable the library running
$ npm install
$ grunt componentlibrary
Further installation instructions can be found in the Component Library itself.
=== Documenting new UI Components ===
There are no set rules for adding new pages in the component library yet. These rules will need to be written and adopted in the integration process for Moodle code.

As a guideline for making this rules consideration are:

The component library is not about single use components, for example the Moodle grade book (a huge component with many custom features). Or about very common components like buttons, these are already covered by the Bootstrap section of the component library.

New features should be build keeping in mind the UI part needs to be customisable and if possible (and making sense) reusable. And example would be the new page drawers that we are introducing for the Navigation project. Or the custom primary navigation menus where overflowing items are pushed into a More section.
== Theme changes ==
=== Edit switch ===
On theme boost the “Turn editing on” and “Customise this page” buttons have been replaced by an edit switch in the top navbar. Theme Classic will keep using the old buttons. Child themes can choose to use the edit switch if the theme config.php is using this variable
$THEME->haseditswitch = true;
The languague menu, which used to be rendered in place of the custom menu has moved to the user dropdown when the user is logged in. If not logged in it will be placed next to the search / notification / messaging icon in the top navbar.
=== Login page ===
The login page has been redesigned and allows the admin to configure a background image for the login page only in the theme settings page. This change is available in both Boost and Classic. The login page still has all the features with an improved layout.
=== The page footer ===
In large screens, the page footer button is only visible when clicking a help button at the bottom right of the screen.
=== User initials as profile picture placeholder ===
If users do not upload a profile picture the user initials are displayed on a rounded gray background as a placeholder picture in the top navbar or any other page using a placeholder image. This change will be available in both Boost and Classic.

With the introduction of this placeholder image the full username will no longer be displayed in the top navbar.
=== Removal of back to top link ===
The "back to top" link will be removed for theme boost since the new course index reduced the dependence on page scrolling. Also, the new footer is positioned where this component used to be.
=== Styling changes ===
By default rounded edges will be used for UI components, for the page header and main content area the borders will be removed.
=== New layout page ===
Theme boost now uses the drawers.php layout for the course index and blocks.
== Question bank changes ==
There was a big project to deliver [[Question bank improvements for Moodle 4.0]] which added a new plugin type for adding features to the question banks, tracking the version history for each question as it is edited (question table has been split into <code>question</code>, <code>question_versions</code> and <code>question_bank_entries</code>), and tracking where each question is going to be used, with new tables <code>question_references</code> and <code>question_set_references</code>. This work was done in Epic MDL-70329 if you want to track down the details of any of the core changes.
=== Question type plugins ===
Amazingly, we (Safat and colleagues at Catalyst AU) managed to implement this without breaking most question type plugins.

However, the changes to the question bank, and the other Moodle 4.0 changes, probably broke the Behat tests for your plugin. To help with fixing that, MDL-74130 adds navigation to key question type pages (Preview and Edit for a question, and standard question bank pages like the bank itself, import and export) which should let you fix your test efficiently, and in a way that will work in all Moodle versions since 3.9.

The 'most' in the first paragraph here is becuase more advance question types may require more effort to fix. (For example qtype_combined which creates multi-part qusetions like the core qtype_multianswer; or qtype_pmatch or qtype_stack, which store additional data - questions tests - alongside the question itseld. How should that work with versionning?) But, if you have not done weird things like that, you are probably safe. If you find anything else that causes problems, please list it here.

The same thing should apply to question behaviour and question import/export format plugings: no significant changes required (probably just fixing the Behat tests because of the navigation changes).
=== New plugin type: qbank plugins ===
This is not something that will cause problems for people upgrading from 3.x. Rather, it is an exciting possibility you can explore once you have survived process of upgrading to 4.0. There is a whole new plugin type which you can create to add new features to the question bank. For example extra columns, new actions and bulk actions, and so on. See [[Question_bank_plugins]].
=== Activities that use questions ===
The probable bad news is if you have an activity module which uses questions. So far, the only activity which has been fixed is mod_quiz in Moodle core, so we don't yet have a good picture of what fixes will be necessary in other activities. Work is about to start fixing [https://github.com/studentquiz/moodle-mod_studentquiz mod_studentquiz], so watching that should give more clues. As we do that, we will try to update this section of this page. Other help writing the information required here would also be greatly appreciated.
== The course format system ==
Most of the logic for rendering and editing a course has been moved to a new subsystem called courseformat. The subsystem is located in "course/format" folder so it includes all the format plugins inside. The methods and modules which are distributed between the course and the course/format folders are now rearranged or refactored to be aligned with the current Moodle coding style.
=== Mandatory renderer in course formats ===
Now format plugins renderer is not optional anymore. Legacy formats without a renderer will get a deprecation message but it will continue working however, they should create a new renderer as soon as possible. The section-based format can do it by extending the provided core_courseformat\output\section_renderer class which includes all the necessary methods.
=== New format base class ===
The old base_format class (which all plugins extend) is now renamed as core_courseformat\base. The new class provides all the functionally of the previous base_format but it has been refactored to be used as a centralized source of truth for the course rendering. Legacy formats should extend the new class to avoid the deprecation message.

Now, the plugin format class provides information such as:
* If the page is displaying a single or multiple section
* Give access to other related format objects like the modinfo, the course record, maximum number of sections...
* If the format is compatible with features like course index, reactive components, ajax...
* Other format specifics like the page title, the default section name, default blocks...

The format instance is now the main object output components will use to render a course (see next section for more information).
=== New course output classes and mustache files ===
Traditionally, section-based course formats uses print_single_section_page and print_multiple_section_page to render the course content. In Moodle 4.0 most of the course rendering methods are migrated to output components and mustache templates. The old methods will get deprecation messages if they use the old renderer methods.

This is an example of a format rendering a course:<syntaxhighlight lang="php-brief">
// Get the course format instance.
$format = course_get_format($course);

// Get the specific format renderer.
$renderer = $format->get_renderer($PAGE);

if (!empty($displaysection)) {
// Setup the format instance to display a single section.
$format->set_section_number($displaysection);
}

// Create the ouptut instance and render it.
$outputclass = $format->get_output_classname('content');
$widget = new $outputclass($format);

echo $renderer->render($widget);
</syntaxhighlight>Format plugins are free to use its own output classes to render a course, or they could override the existing output classes by providing their own implementation. For example, the default output for "content" (as in the previous example) is "core_courseformat\output\local\|content", however, if the plugin has a "format_XXX\output\courseformat\content" class, the $format->class the get_output_class will return the overridden one.
Another important update on course rendering is that now all course structure is rendered using mustache templates instead of the original html_writer methods. Now themes are able to override the course format by providing alternative versions of the mustache files. All core course templates are located in "course/format/templates".

All the new output classes and a guide on how to migrate the current third-party plugins will be available soon.
=== Course editor javascript modules and frontend components ===
The majority of the javascript logic related to the course editing is replaced by AMD modules. Because this is a major change in the way courses are edited and rendered, by default format plugins will continue using the previous YUI modules for now. However, formats can start using the new libraries overriding the "$format->supports_components()" method.

Some Moodle 4.0 new features are only available for courses using the new editor library:
* Edit the course via the course index
* Creating sections without reloading the course page
* The new move section/activity modal
* Native browser drag&drop implementation
The new course editor uses a component-based reactive pattern to keep track of the course changes. The pattern highlights are:
* The main AMD module "core_crouseformat\courseeditor" maintains a data structure called state.
* Each UI element is implemented as a Component that observes the course state data and reacts to any data change
* When any reactive component needs to modify the course, it asks the course editor to execute a mutation. Mutations encapsulate all web services calls and alter the course state data.

The reactive library documentation, as well as the format plugin migration guide, will be available soon.
=== Other course related 4.0 changes ===
Two new web services have been added:
* core_courseformat_get_state: user by the new javascript course editor to get the current course state data (containing the list of sections, activities, and other course-related data)
* core_courseformat_update_course: to alter the current course content. Each call returns the parts of the course state altered by the action
== Behat changes ==

=== New steps ===
Moodle 4.0 introduces some new behat steps.

Sometimes you want to create a bulk number of activities. In that case you can use:<syntaxhighlight lang="gherkin">
:count :entitytype exist with the following data:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
Given 100 "mod_lti > tool types" exist with the following data:
|name |Test tool [count] |
|description |Example description [count] |
|baseurl |https://www.example.com/tool[count]|
</syntaxhighlight>

Dynamic (AJAX) tabs is a new feature contributed to Moodle 4.0 by the Workplace team (MDL-71943). You can use the following step to navigate between the tabs.<syntaxhighlight lang="gherkin">
And I click on the "tab title" dynamic tab
</syntaxhighlight>

To make sure that edit mode is (or is not) available on the current page, the following steps can be used.<syntaxhighlight lang="gherkin">
And edit mode should be available on the current page
And edit mode should not be available on the current page
</syntaxhighlight>

There are new aliases for the existing steps <code>I turn editing mode on</code> and <code>I turn editing mode off</code>.<syntaxhighlight lang="gherkin">
And I switch editing mode on
And I switch editing mode off
</syntaxhighlight>

In addition to the existing step to go to a course with editing mode on, we now have the following step to do the same but with editing mode being off.<syntaxhighlight lang="gherkin">
And I am on "course full name" course homepage with editing mode off
</syntaxhighlight>

The following step is similar to the old <code>following "link string" should download between "min bytes" and "max bytes" bytes</code> step, with more flexibility.<syntaxhighlight lang="gherkin">
And following "element string" "element type" in the "container string" "container type" should download between "min bytes" and "max bytes" bytes
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And following "Download" "link" in the "Starter" "table_row" should download between "0" and "5000" bytes
</syntaxhighlight>

The following step can be used to hover the mouse over the trigger area.<syntaxhighlight lang="gherkin">
And I hover over the "element string" "element type" in the "container string" "container type"
</syntaxhighlight>

The following step enables an installed plugin.<syntaxhighlight lang="gherkin">
And I enable "plugin name" "plugin type" plugin
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I enable "course_summary" "block" plugin
</syntaxhighlight>

The following is a special variation of 'I click on "<page name>" "link" in the "page" "region"'. It first checks to see if we are on the given page via the breadcrumb. If not we then attempt to follow the link name given.<syntaxhighlight lang="gherkin">
And I follow the breadcrumb "page name"
</syntaxhighlight>

You can use the following step to ensure a node is active in the navbar.<syntaxhighlight lang="gherkin">
And I should see "Node" is active in navigation
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I should see "My courses" is active in navigation
</syntaxhighlight>

The following step can be used to navigate to a given node in the primary navigation.<syntaxhighlight lang="gherkin">
And I select "Node" from primary navigation
</syntaxhighlight>

The following steps are to check whether an item exists in the user menu or not.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the user menu
And "item text" "selector type" should not exist in the user menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "Language" "link" should exist in the user menu
</syntaxhighlight>

The following steps are to check if a submenu of the user menu is shown, and if an item exists or does not exist in a given user submenu.<syntaxhighlight lang="gherkin">
And I should see "submenu name" user submenu
And "item text" "selector type" should exist in the "submenu name" user submenu
And "item text" "selector type" should not exist in the "submenu name" user submenu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I follow "Language" in the user menu
Then I should see "Language selector" user submenu
And "English &lrm;(en)&lrm;" "link" should exist in the "Language selector" user submenu
And "English (pirate) &lrm;(en_ar)&lrm;" "link" should not exist in the "Language selector" user submenu
</syntaxhighlight>

To add enrolment methods to courses you can use the following new step. The data that you provide in the next lines are used to fill the enrolment method form.<syntaxhighlight lang="gherkin">
And I add "enrolment method" in "course identifier" with:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I add "Self enrolment" enrolment method in "Course 1" with:
| Custom instance name | Test student enrolment |
| Enrolment key | moodle_rules |
| Use group enrolment keys | Yes |
</syntaxhighlight>

There are 3 new steps specific to the calendar component. These steps can be used to hover over a day in the mini-calendar or the full calendar.<syntaxhighlight lang="gherkin">
And I hover over day "day of month" of this month in the full calendar page
And I hover over day "day of month" of this month in the mini-calendar block
And I hover over today in the mini-calendar block
</syntaxhighlight>

Some new steps are added to question bank to be able to add comment to questions, verify the existence of a comment, and deleting comments form questions. Please note that the steps for adding comments only write the comment text in the comment field. You still need to click on the "Add comment" button to save the comment.<syntaxhighlight lang="gherkin">
And I add "comment text" comment to question
And I add "comment text" comment to question preview
And I delete "comment text" comment from question
And I delete "comment text" comment from question preview
And I should see "number of comments" on the comments column
And I click "number of comments" on the row on the comments column

</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "Question bank" in current page administration
And I should see "0" on the comments column
And I click "0" on the row on the comments column
And I add "test comment 01" comment to question
And I click on "Add comment" "button" in the ".modal-dialog" "css_element"
And I click on "Close" "button" in the ".modal-dialog" "css_element"
And I should see "1" on the comments column
And I click "1" on the row on the comments column
And I delete "test comment 01" comment from question
</syntaxhighlight>

Similar to the steps for comments, the following steps are to verify the number of a question's usage and to click on it in order to open the question usage modal.<syntaxhighlight lang="gherkin">
And I should see "usage count" on the usage column
And I click "usage count" on the usage column
</syntaxhighlight>

The following new steps are related to bulk actions in the question bank UI.<syntaxhighlight lang="gherkin">
And I click on question bulk action "action"
And I should see question bulk action "action"
And I should not see question bulk action "action"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I click on "First question" "checkbox"
And I click on "Second question" "checkbox"
And I click on "With selected" "button"
And I should see question bulk action "deleteselected"
And I click on question bulk action "deleteselected"
And I click on "Delete" "button" in the "Confirm" "dialogue"
</syntaxhighlight>

[https://docs.moodle.org/en/Report_builder Report builder] is a new feature contributed to Moodle 4.0 by the Workplace team. The following new step is added to Moodle 4.0 to select an action from the action menu in the list of custom reports table.<syntaxhighlight lang="gherkin">
And I press "action" action in the "report name" report row
</syntaxhighlight>

There's another step related to the report builder to set a column's aggregation in the report editor.<syntaxhighlight lang="gherkin">
And I set the "column title" column aggregation to "aggregation method"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I set the "First name" column aggregation to "Comma separated values"
</syntaxhighlight>

The following step needs to be used in scenarios that involve testing BigBlueButton. For this to work, you need to have a [https://github.com/moodlehq/bigbluebutton_mock BigBlueButton Mock API Server] and set <code>TEST_MOD_BIGBLUEBUTTONBN_MOCK_SERVER</code> to point to that in config.php.<syntaxhighlight lang="gherkin">
And a BigBlueButton mock server is configured
</syntaxhighlight>

The following step replicates receiving a callback from the BigBlueButton server indicating the recordings for meetings are ready for viewing.<syntaxhighlight lang="gherkin">
And the BigBlueButtonBN server has sent recording ready notifications
</syntaxhighlight>

The following steps are specific to the lesson activity. Note that in 4.0, some links (such as the "edit" and the "grade essays" links) are replaced by buttons, so you need to update your old steps with the new ones.<syntaxhighlight lang="gherkin">
And I edit the lesson
</syntaxhighlight>A new step is added to be used in lesson activities to edit them. This step navigates the user to the lesson edit page.

<syntaxhighlight lang="gherkin">
And I grade lesson essays
</syntaxhighlight>It's a new step to go to the "Grade essays" page of the lesson we are currently in.

<syntaxhighlight lang="gherkin">
And I select edit type "edit type"
</syntaxhighlight>Select the lesson edit type when we are in the the lesson's edit page. "edit type" can either be "Collapsed" or "Expanded".

The following new step can be used to navigate to the exports page in the course gradebook and select the specified export type from the grade exports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "export option" export page in the course gradebook
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "XML file" export page in the course gradebook
</syntaxhighlight>

Similarly, there's a new step to navigate to the imports page in the course gradebook and select the specified import type from the grade imports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "import option" import page in the course gradebook
</syntaxhighlight>

=== Boost steps ===
In addition to the steps listed in the previous section, there are also some Boost specific steps coming with Moodle 4.0. These steps only work in Boost or Boost child themes, so you need to make sure they are not used in scenarios that may be run by non-Boost themes.

The following step checks whether a node is active in the secondary navigation.<syntaxhighlight lang="gherkin">
And I should see :name is active in secondary navigation
</syntaxhighlight>

The Boost theme shows the language selector menu in the primary navigation when not logged in, and within the user menu when logged in. The following steps are to check if the primary navigation includes the language selector menu.<syntaxhighlight lang="gherkin">
And language selector menu should exist in the navbar
And language selector menu should not exist in the navbar
</syntaxhighlight>

And the following steps can be used to check whether an item exists in the language selector menu in the Boost theme.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the language selector menu
And "item text" "selector type" should not exist in the language selector menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "English &lrm;(en)&lrm;" "link" should exist in the language selector menu
</syntaxhighlight>

=== Modified steps ===
The step <code>I change the (window|viewport) size to "size"</code> now supports 2 new values for the size argument. The size argument now accepts <code>mobile</code> and <code>tablet</code> values in addition to <code>small</code>, <code>medium</code> and <code>large</code>.

=== Removed steps ===
Some behat steps are removed or replaced with new steps.

As a result of some design changes, hidden or restricted activities are no longer dimmed. Therefore the step<syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be dimmed
</syntaxhighlight>is now removed.

Depending on what you were using that step for, you may be able to use these steps:<syntaxhighlight lang="gherkin">
And "Label name" label should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And I should see "Activity or resource name"
And "Activity or resource name" "link" should not exist in the "region-main" "region"
</syntaxhighlight>

=== Other things to consider ===
To make behat tests more readable and easy to maintain, it is recommended to use the most direct steps to get what the test needs. It is highly recommended to use
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
instead of navigating to the activity via
I am on "Course" course homepage
I follow "Activity name"
Now that [https://docs.moodle.org/dev/Prototypes#Course_creation_improvements Course index] is integrated these behat steps
I am on "Course" course homepage
I follow "Activity name"
will fail using Boost theme.

The reason for it is that the drawer used in Boost is hiding the course index. So when the test is trying to follow an "Activity name" link, it finds two different links:
* one in the course index
* another one in the course main content.
But the first one, the one in the course index, is hidden by the drawer, and the test fails.

However the recommended behat steps
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
Old behat steps that may now fail can be updated to the new steps.
For example:
And I am on the "Test assignment name" "assign activity" page logged in as teacher1
instead of:
When I log in as "teacher1"
And I am on "Course" course homepage
And I follow "Test assignment name"
There are also similar stream-lined navigation steps for accessing question bank pages. See MDL-74130.
== Other ==
=== Core plugins review ===
A few plugins from core Moodle LMS which are no longer or hardly used have been removed and, if appropriate, added to the Moodle plugins directory.

More information about this project, the list of plugins to be removed and the process to follow for keeping them before upgrading to 4.0 can be found in the [[Core plugins review]] page.
=== Site admin presets plugin ===
The third-party plugin [https://moodle.org/plugins/block_admin_presets Admin presets], created by David Monllaó and maintained by developers from [https://pimenko.com/ Pimenko] has been adapted and integrated into Moodle 4.0. It stores settings and plugins status (enabled/disabled) in what's called "presets" to let admins quickly switch between different configurations.

More information about this project can be found in the [[Site admin presets|Site admin presets plugin]] page.
=== JavaScript browser support changes ===
From Moodle 4.0, Internet Explorer is no longer supported. See MDL-73915 and MDLSITE-6109 for further information on this change.

This change means that changes built on 4.0 onwards (including the master branch) will be different to older versions of Moodle.

For plugin developers supporting multiple versions of Moodle using a single plugin version, the compiled javascript files are backwards compatible and will _work_ on all supported versions, however if you run the `grunt` command on multiple versions you will see unbuilt changes. Running grunt on all versions of Moodle is not necessary and this check can be safely disabled for Moodle versions 3.9 - 4.0, as long as only at least you run `grunt` against at least one version of Moodle.

If you need to support Internet Explorer and do not wish to fork your plugin for Moodle 4.0 onwards, then it is recommended that you run `grunt` on an older version of Moodle.
=== The course index element ===
The new course index feature can be themed using a set of scss variables. Use them to change the look and feel instead of adding custom css
/theme/boost/scss/moodle/courseindex.scss
With the introduction of the course index component, the previous and next links shown underneath each activity are no longer needed and they will be removed.
=== Activity icons ===
The icons used for activities have been redesigned and updated for all core moodle activities.

When viewing the new icons in a file manager, for example for the quiz activity, you will see a simple black monochrome icon with a transparent background.

On the course page, or in the activity chooser, the icon will display as a white icon on a coloured background. Styling of the icons on the coursepage is controlled by the css in theme/boost/scss/moodle/icons.scss.

The background colour for activity icons is set using a new variable in function [modname]_supports(). The quiz activity is of type assessment, so in function quiz_supports() there is a new line defining the purpose:
case FEATURE_MOD_PURPOSE: return MOD_PURPOSE_ASSESSMENT;
Available purposes are:
* MOD_PURPOSE_COMMUNICATION
* MOD_PURPOSE_ASSESSMENT
* MOD_PURPOSE_COLLABORATION
* MOD_PURPOSE_CONTENT
* MOD_PURPOSE_ADMINISTRATION
* MOD_PURPOSE_INTERFACE
The background colours linked to these purposes are set in theme/boost/scss/moodle/variables.scss
$activity-icon-colors: map-merge(
(
"administration": #5d63f6,
"assessment": #eb66a2,
"collaboration": #f7634d,
"communication": #11a676,
"content": #399be2,
"interface": #a378ff
),
$activity-icon-colors
);
If activity plugins do not define FEATURE_MOD_PURPOSE the activity icon will be rendered against a light grey background. There is no requirement to define the purpose of activity plugins, it will only affect the icon styling.

Plugins implementing the variable FEATURE_MOD_PURPOSE are only supported on Moodle 4.0 and newer.

Customising the activity icon can be done in an alternative way. For example using the styles.css in mod/[pluginname/styles.css

In the example below the activity plugin developer chooses to keep the coloured icon for the activity and render it as large as the coloured background on the core activities
.modicon_subcourse.activityiconcontainer {
background-color: transparent;
padding: 0;
}

.modicon_subcourse.activityiconcontainer img {
width: 50px;
height: 50px;
}
To customize all icon colours use this scss array and add it to the ‘Raw initial SCSS’ in the theme Boost advanced settings page. The complete array of icon background colours can be overridden using the ‘Raw initial SCSS’ in the theme settings page. The example below changes the colours of each activity type.
$activity-icon-colors: (
"administration": #5D63F6,
"assessment": #11A676,
"collaboration": #EB66A2,
"communication": #F7634D,
"content": #399BE2,
"interface": #A378FF
)

== I'm a developer, what do I need to know? ==
=== Modules ===
If you are a module developer (activity / resources) then you need to review the following updates and changes:

* If using settings, reformat to work with the secondary navigation. We have significantly changed the way that settings are shown. Settings added to the course and activity administration branch of the navigation are now by default shown in the secondary navigation. You will most likely find them in the more section of the secondary navigation. Please avoid creating settings in containers (a parent navigation node with children). These settings will still be shown (details about that), but this goes against the pattern that we are trying to establish for navigation around the site. If you have a lot of settings, consider creating a specific page to handle your additional settings (screenshot?).
** The order of the items in the secondary navigation may not be to your liking. This can be changed. See [[Moodle_4.0_developer_update#Changing_the_order_of_tabs|changing the order of tabs]]
* Update my behat tests to use new steps for site navigation. See [[Moodle_4.0_developer_update#Behat_changes|new behat steps]].
* Update my module to use the new activity_header API. See [[Moodle_4.0_developer_update#The_activity_header_class|the activity header]].
* Update my pages to make it work with the general format of the tertiary navigation. See [[Moodle_4.0_developer_update#Tertiary_navigation|the tertiary navigation]].
* Update my activity icon to use the API and set a purpose. See [[Moodle_4.0_developer_update#Activity_icons|activity icons]].

=== Themes ===
If you are a theme developer then you may want to consider the following:
# Take a look at the [[Moodle_4.0_developer_update#Navigation_changes|new navigation]] and decide if you want to incorporate this into your theme.
## A new layout ([[Moodle_4.0_developer_update#New_layout_page|drawers]])
## An [[Moodle_4.0_developer_update#Edit_switch|edit switch]]
## The [[Moodle_4.0_developer_update#The_course_index_element|course index]]
# Use of the flat nav
# New Site administration page and layout
# Course settings and how they are displayed

Moodle 4.0 developer update

2022-03-14T07:15:02Z

Abgreeve: First lot of plugin developer specific comments

{{Moodle 4.0}}This page highlights the important changes that are coming in Moodle 4.0 for developers. Including how the UX improvements impact custom themes, relevant API changes, and what you can do as developer to prepare for the 4.0 release.
== Navigation changes ==
The core Navigation API has been left mostly untouched. The callbacks to all navigation callbacks remains unchanged and will be called as part of the regular 'navigation' and 'settingsnav' initialisation. Some new core classes have been created and exist within a new namespace 'core/navigation' and serves as conduit to rearrange, cherry-pick existing navigation nodes from the navigation/settingsnav trees and display within the respective navigation type. As such, it is highly recommended to provide unique keys for custom navigation nodes as this helps in the cherry-picking / rearranging process within the new classes.
=== Primary navigation ===
The primary navigation(the navbar) apart from the existing content will now display links to the Dashboard, My Courses, Site Admin and Course search, by default. You can still add items to the navbar via the 'custom menu' option. This will be displayed within the 'More' menu. We have transitioned the menus to be rendered via templates - refer user_menu.mustache. The lang menu has been moved to reside within the user menu.
==== Customising the primary navigation ====
Not yet implemented but we are looking at allowing the full addition and removal of any of the primary navigation tabs in the boost theme config file.
=== Secondary navigation ===
The main content area shows tabs for secondary navigation with a maximum of 5 items being rendered in this ‘more’ menu. A new UI component has been created to render menus like this. Files:
/lib/templates/moremenu.mustache
==== Changing the order of tabs ====
Apart from the previously mentioned functions, you can also create a custom secondary class as mentioned earlier. This will automatically be picked by getter and used to render the secondary nav within the activity. E.g. mod_assign/local/views/secondary. Note: This is currently only possible on an activity and block level.
=== Tertiary navigation ===
We've moved action buttons to the top of the page. We would encourage you to do the same.
If you have any buttons on an activity page that go to another page, or open a form (or similar), then we encourage you to move them from the body of your activity page to the top. All of the core activities have been updated to follow this pattern. Please take a look to see how you can format your activity in a similar fashion. There is no API here. You are welcome to create the buttons and display them as you wish in this top area.

=== New API functions ===
==== Page API ====
* Magic getters to fetch the primary and secondary navs and the primary output.
* The secondarynav magic getter also checks whether a custom secondary class has been defined within the module's local\views directory. Use this if you want to deviate from the standard secondary nav structure/order.

* set_secondary_nav - Force override the secondary navigation class

* has_secondary_navigation_setter - Sets the ‘_hassecondarynavigation’ to indicate whether a page should render the secondary navigation
==== Navigationlib ====
* set_show_in_secondary_navigation - whether or not a node should be displayed in the secondary nav. Accepts a single boolean argument
* set_force_into_more_menu- whether or not to force a node into the 'More' menu. Accepts a single boolean argument
==== The activity header class ====
There is a new activity header class that handles the display of information common to activities. 3rd party activities are not required to explicitly output this information as part of rendering individual pages.

The common information that are currently handled by the class are:
* title
* description
* completion information

As part of the update it was required that the initial information to be displayed by the class be toggable at a theme and layout level. Taking this into account the following theme level configurable exists:
* activityheaderconfig => An array that currently only enforces 'notitle' but can be expanded in the future NOTE: Boost has this set as true by default 'options'
The following layout level options that can be defined:
* noactivityheader - to remove the header in this specific layout.
* activityheader - An array that enforces the following options:
** notitle
** nocompletion
** nodescription
The class has a page level getter which you can use to fetch the current version of the class. The base state is initialised within the constructor with the completion information only fetched when data is exported for the template.

The class has setters for the following variables which can be leveraged to modify the header for a particular page in the format set_{variable_name}:
* hidecompletion
* description
* title
Alternately, bulk operations can also be done by passing the above variables in an array to 'set_attrs' which in turn calls the setters.<blockquote>'''Note: Any updates to the activityheader needs to be performed before the call to $OUTPUT->header'''</blockquote>
===== Theme updates: =====
In order for 3rd party themes to use the class they need to export the activity_header and include the following into their base template :<syntaxhighlight lang="html">
{{#headercontent}}
{{> core/activity_header}}
{{#headercontent}}
</syntaxhighlight>** headercontent being the array element that contains the exported activity_header data
===== Accessibility notes: =====
The jump to ‘maincontent’ div is now rendered within the activity header when within an activity context
== Component library ==
Each Moodle installation now ships with a Moodle User Interface (UI) Component library, a documentation system used to describe all the Bootstrap components and the custom Moodle components. The component Library is a helper tool for developers when creating user interfaces, a testing tool for theme developers and a documentation tool for core developers. The ultimate goal of having a component library is to encourage developers to create consistent user interfaces to improve Moodle’s overall user experience.

The library contains pages with documentation about User Interface components. It contains details on how to use the component, what variations are available and the JavaScript events / options are associated with the component.

When writing on these pages it is possible to render core mustache templates using some custom syntax like this:
<nowiki>{{< mustache template="core/notification_error" >}}</nowiki>
<nowiki>{{< /mustache >}}</nowiki>
You can also call core JavaScript or use HTML examples where the html code and the rendered result are visible in the Component Library. For more info visit the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-templates/ Moodle templates] page or the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-javascript/ Moodle JavaScript] page.

Each page in the library uses the current css from the default theme in your Moodle installation, if you have multiple themes installed and enabled the setting "Allow theme changes on url", the component library will have a theme selector option.

A hosted version of the Component Library can be found here. http://componentlibrary.moodle.com
=== Enabling the Component Library ===
Component library pages are written in the markdown language. These pages need to be compiled to HTML pages before the Component Library is visible. To compile the pages the server running Moodle needs to have the [[Javascript Modules#Install%20NVM%20and%20Node|JavaScript developer tools installed]] (nodeJs and Grunt)

If your server meets all requirements you can enable the library running
$ npm install
$ grunt componentlibrary
Further installation instructions can be found in the Component Library itself.
=== Documenting new UI Components ===
There are no set rules for adding new pages in the component library yet. These rules will need to be written and adopted in the integration process for Moodle code.

As a guideline for making this rules consideration are:

The component library is not about single use components, for example the Moodle grade book (a huge component with many custom features). Or about very common components like buttons, these are already covered by the Bootstrap section of the component library.

New features should be build keeping in mind the UI part needs to be customisable and if possible (and making sense) reusable. And example would be the new page drawers that we are introducing for the Navigation project. Or the custom primary navigation menus where overflowing items are pushed into a More section.
== Theme changes ==
=== Edit switch ===
On theme boost the “Turn editing on” and “Customise this page” buttons have been replaced by an edit switch in the top navbar. Theme Classic will keep using the old buttons. Child themes can choose to use the edit switch if the theme config.php is using this variable
$THEME->haseditswitch = true;
The languague menu, which used to be rendered in place of the custom menu has moved to the user dropdown when the user is logged in. If not logged in it will be placed next to the search / notification / messaging icon in the top navbar.
=== Login page ===
The login page has been redesigned and allows the admin to configure a background image for the login page only in the theme settings page. This change is available in both Boost and Classic. The login page still has all the features with an improved layout.
=== The page footer ===
In large screens, the page footer button is only visible when clicking a help button at the bottom right of the screen.
=== User initials as profile picture placeholder ===
If users do not upload a profile picture the user initials are displayed on a rounded gray background as a placeholder picture in the top navbar or any other page using a placeholder image. This change will be available in both Boost and Classic.

With the introduction of this placeholder image the full username will no longer be displayed in the top navbar.
=== Removal of back to top link ===
The "back to top" link will be removed for theme boost since the new course index reduced the dependence on page scrolling. Also, the new footer is positioned where this component used to be.
=== Styling changes ===
By default rounded edges will be used for UI components, for the page header and main content area the borders will be removed.
=== New layout page ===
Theme boost now uses the drawers.php layout for the course index and blocks.
== Question bank changes ==
There was a big project to deliver [[Question bank improvements for Moodle 4.0]] which added a new plugin type for adding features to the question banks, tracking the version history for each question as it is edited (question table has been split into <code>question</code>, <code>question_versions</code> and <code>question_bank_entries</code>), and tracking where each question is going to be used, with new tables <code>question_references</code> and <code>question_set_references</code>. This work was done in Epic MDL-70329 if you want to track down the details of any of the core changes.
=== Question type plugins ===
Amazingly, we (Safat and colleagues at Catalyst AU) managed to implement this without breaking most question type plugins.

However, the changes to the question bank, and the other Moodle 4.0 changes, probably broke the Behat tests for your plugin. To help with fixing that, MDL-74130 adds navigation to key question type pages (Preview and Edit for a question, and standard question bank pages like the bank itself, import and export) which should let you fix your test efficiently, and in a way that will work in all Moodle versions since 3.9.

The 'most' in the first paragraph here is becuase more advance question types may require more effort to fix. (For example qtype_combined which creates multi-part qusetions like the core qtype_multianswer; or qtype_pmatch or qtype_stack, which store additional data - questions tests - alongside the question itseld. How should that work with versionning?) But, if you have not done weird things like that, you are probably safe. If you find anything else that causes problems, please list it here.

The same thing should apply to question behaviour and question import/export format plugings: no significant changes required (probably just fixing the Behat tests because of the navigation changes).
=== New plugin type: qbank plugins ===
This is not something that will cause problems for people upgrading from 3.x. Rather, it is an exciting possibility you can explore once you have survived process of upgrading to 4.0. There is a whole new plugin type which you can create to add new features to the question bank. For example extra columns, new actions and bulk actions, and so on. See [[Question_bank_plugins]].
=== Activities that use questions ===
The probable bad news is if you have an activity module which uses questions. So far, the only activity which has been fixed is mod_quiz in Moodle core, so we don't yet have a good picture of what fixes will be necessary in other activities. Work is about to start fixing [https://github.com/studentquiz/moodle-mod_studentquiz mod_studentquiz], so watching that should give more clues. As we do that, we will try to update this section of this page. Other help writing the information required here would also be greatly appreciated.
== The course format system ==
Most of the logic for rendering and editing a course has been moved to a new subsystem called courseformat. The subsystem is located in "course/format" folder so it includes all the format plugins inside. The methods and modules which are distributed between the course and the course/format folders are now rearranged or refactored to be aligned with the current Moodle coding style.
=== Mandatory renderer in course formats ===
Now format plugins renderer is not optional anymore. Legacy formats without a renderer will get a deprecation message but it will continue working however, they should create a new renderer as soon as possible. The section-based format can do it by extending the provided core_courseformat\output\section_renderer class which includes all the necessary methods.
=== New format base class ===
The old base_format class (which all plugins extend) is now renamed as core_courseformat\base. The new class provides all the functionally of the previous base_format but it has been refactored to be used as a centralized source of truth for the course rendering. Legacy formats should extend the new class to avoid the deprecation message.

Now, the plugin format class provides information such as:
* If the page is displaying a single or multiple section
* Give access to other related format objects like the modinfo, the course record, maximum number of sections...
* If the format is compatible with features like course index, reactive components, ajax...
* Other format specifics like the page title, the default section name, default blocks...

The format instance is now the main object output components will use to render a course (see next section for more information).
=== New course output classes and mustache files ===
Traditionally, section-based course formats uses print_single_section_page and print_multiple_section_page to render the course content. In Moodle 4.0 most of the course rendering methods are migrated to output components and mustache templates. The old methods will get deprecation messages if they use the old renderer methods.

This is an example of a format rendering a course:<syntaxhighlight lang="php-brief">
// Get the course format instance.
$format = course_get_format($course);

// Get the specific format renderer.
$renderer = $format->get_renderer($PAGE);

if (!empty($displaysection)) {
// Setup the format instance to display a single section.
$format->set_section_number($displaysection);
}

// Create the ouptut instance and render it.
$outputclass = $format->get_output_classname('content');
$widget = new $outputclass($format);

echo $renderer->render($widget);
</syntaxhighlight>Format plugins are free to use its own output classes to render a course, or they could override the existing output classes by providing their own implementation. For example, the default output for "content" (as in the previous example) is "core_courseformat\output\local\|content", however, if the plugin has a "format_XXX\output\courseformat\content" class, the $format->class the get_output_class will return the overridden one.
Another important update on course rendering is that now all course structure is rendered using mustache templates instead of the original html_writer methods. Now themes are able to override the course format by providing alternative versions of the mustache files. All core course templates are located in "course/format/templates".

All the new output classes and a guide on how to migrate the current third-party plugins will be available soon.
=== Course editor javascript modules and frontend components ===
The majority of the javascript logic related to the course editing is replaced by AMD modules. Because this is a major change in the way courses are edited and rendered, by default format plugins will continue using the previous YUI modules for now. However, formats can start using the new libraries overriding the "$format->supports_components()" method.

Some Moodle 4.0 new features are only available for courses using the new editor library:
* Edit the course via the course index
* Creating sections without reloading the course page
* The new move section/activity modal
* Native browser drag&drop implementation
The new course editor uses a component-based reactive pattern to keep track of the course changes. The pattern highlights are:
* The main AMD module "core_crouseformat\courseeditor" maintains a data structure called state.
* Each UI element is implemented as a Component that observes the course state data and reacts to any data change
* When any reactive component needs to modify the course, it asks the course editor to execute a mutation. Mutations encapsulate all web services calls and alter the course state data.

The reactive library documentation, as well as the format plugin migration guide, will be available soon.
=== Other course related 4.0 changes ===
Two new web services have been added:
* core_courseformat_get_state: user by the new javascript course editor to get the current course state data (containing the list of sections, activities, and other course-related data)
* core_courseformat_update_course: to alter the current course content. Each call returns the parts of the course state altered by the action
== Behat changes ==

=== New steps ===
Moodle 4.0 introduces some new behat steps.

Sometimes you want to create a bulk number of activities. In that case you can use:<syntaxhighlight lang="gherkin">
:count :entitytype exist with the following data:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
Given 100 "mod_lti > tool types" exist with the following data:
|name |Test tool [count] |
|description |Example description [count] |
|baseurl |https://www.example.com/tool[count]|
</syntaxhighlight>

Dynamic (AJAX) tabs is a new feature contributed to Moodle 4.0 by the Workplace team (MDL-71943). You can use the following step to navigate between the tabs.<syntaxhighlight lang="gherkin">
And I click on the "tab title" dynamic tab
</syntaxhighlight>

To make sure that edit mode is (or is not) available on the current page, the following steps can be used.<syntaxhighlight lang="gherkin">
And edit mode should be available on the current page
And edit mode should not be available on the current page
</syntaxhighlight>

There are new aliases for the existing steps <code>I turn editing mode on</code> and <code>I turn editing mode off</code>.<syntaxhighlight lang="gherkin">
And I switch editing mode on
And I switch editing mode off
</syntaxhighlight>

In addition to the existing step to go to a course with editing mode on, we now have the following step to do the same but with editing mode being off.<syntaxhighlight lang="gherkin">
And I am on "course full name" course homepage with editing mode off
</syntaxhighlight>

The following step is similar to the old <code>following "link string" should download between "min bytes" and "max bytes" bytes</code> step, with more flexibility.<syntaxhighlight lang="gherkin">
And following "element string" "element type" in the "container string" "container type" should download between "min bytes" and "max bytes" bytes
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And following "Download" "link" in the "Starter" "table_row" should download between "0" and "5000" bytes
</syntaxhighlight>

The following step can be used to hover the mouse over the trigger area.<syntaxhighlight lang="gherkin">
And I hover over the "element string" "element type" in the "container string" "container type"
</syntaxhighlight>

The following step enables an installed plugin.<syntaxhighlight lang="gherkin">
And I enable "plugin name" "plugin type" plugin
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I enable "course_summary" "block" plugin
</syntaxhighlight>

The following is a special variation of 'I click on "<page name>" "link" in the "page" "region"'. It first checks to see if we are on the given page via the breadcrumb. If not we then attempt to follow the link name given.<syntaxhighlight lang="gherkin">
And I follow the breadcrumb "page name"
</syntaxhighlight>

You can use the following step to ensure a node is active in the navbar.<syntaxhighlight lang="gherkin">
And I should see "Node" is active in navigation
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I should see "My courses" is active in navigation
</syntaxhighlight>

The following step can be used to navigate to a given node in the primary navigation.<syntaxhighlight lang="gherkin">
And I select "Node" from primary navigation
</syntaxhighlight>

The following steps are to check whether an item exists in the user menu or not.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the user menu
And "item text" "selector type" should not exist in the user menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "Language" "link" should exist in the user menu
</syntaxhighlight>

The following steps are to check if a submenu of the user menu is shown, and if an item exists or does not exist in a given user submenu.<syntaxhighlight lang="gherkin">
And I should see "submenu name" user submenu
And "item text" "selector type" should exist in the "submenu name" user submenu
And "item text" "selector type" should not exist in the "submenu name" user submenu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I follow "Language" in the user menu
Then I should see "Language selector" user submenu
And "English &lrm;(en)&lrm;" "link" should exist in the "Language selector" user submenu
And "English (pirate) &lrm;(en_ar)&lrm;" "link" should not exist in the "Language selector" user submenu
</syntaxhighlight>

To add enrolment methods to courses you can use the following new step. The data that you provide in the next lines are used to fill the enrolment method form.<syntaxhighlight lang="gherkin">
And I add "enrolment method" in "course identifier" with:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I add "Self enrolment" enrolment method in "Course 1" with:
| Custom instance name | Test student enrolment |
| Enrolment key | moodle_rules |
| Use group enrolment keys | Yes |
</syntaxhighlight>

There are 3 new steps specific to the calendar component. These steps can be used to hover over a day in the mini-calendar or the full calendar.<syntaxhighlight lang="gherkin">
And I hover over day "day of month" of this month in the full calendar page
And I hover over day "day of month" of this month in the mini-calendar block
And I hover over today in the mini-calendar block
</syntaxhighlight>

Some new steps are added to question bank to be able to add comment to questions, verify the existence of a comment, and deleting comments form questions. Please note that the steps for adding comments only write the comment text in the comment field. You still need to click on the "Add comment" button to save the comment.<syntaxhighlight lang="gherkin">
And I add "comment text" comment to question
And I add "comment text" comment to question preview
And I delete "comment text" comment from question
And I delete "comment text" comment from question preview
And I should see "number of comments" on the comments column
And I click "number of comments" on the row on the comments column

</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "Question bank" in current page administration
And I should see "0" on the comments column
And I click "0" on the row on the comments column
And I add "test comment 01" comment to question
And I click on "Add comment" "button" in the ".modal-dialog" "css_element"
And I click on "Close" "button" in the ".modal-dialog" "css_element"
And I should see "1" on the comments column
And I click "1" on the row on the comments column
And I delete "test comment 01" comment from question
</syntaxhighlight>

Similar to the steps for comments, the following steps are to verify the number of a question's usage and to click on it in order to open the question usage modal.<syntaxhighlight lang="gherkin">
And I should see "usage count" on the usage column
And I click "usage count" on the usage column
</syntaxhighlight>

The following new steps are related to bulk actions in the question bank UI.<syntaxhighlight lang="gherkin">
And I click on question bulk action "action"
And I should see question bulk action "action"
And I should not see question bulk action "action"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I click on "First question" "checkbox"
And I click on "Second question" "checkbox"
And I click on "With selected" "button"
And I should see question bulk action "deleteselected"
And I click on question bulk action "deleteselected"
And I click on "Delete" "button" in the "Confirm" "dialogue"
</syntaxhighlight>

[https://docs.moodle.org/en/Report_builder Report builder] is a new feature contributed to Moodle 4.0 by the Workplace team. The following new step is added to Moodle 4.0 to select an action from the action menu in the list of custom reports table.<syntaxhighlight lang="gherkin">
And I press "action" action in the "report name" report row
</syntaxhighlight>

There's another step related to the report builder to set a column's aggregation in the report editor.<syntaxhighlight lang="gherkin">
And I set the "column title" column aggregation to "aggregation method"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I set the "First name" column aggregation to "Comma separated values"
</syntaxhighlight>

The following step needs to be used in scenarios that involve testing BigBlueButton. For this to work, you need to have a [https://github.com/moodlehq/bigbluebutton_mock BigBlueButton Mock API Server] and set <code>TEST_MOD_BIGBLUEBUTTONBN_MOCK_SERVER</code> to point to that in config.php.<syntaxhighlight lang="gherkin">
And a BigBlueButton mock server is configured
</syntaxhighlight>

The following step replicates receiving a callback from the BigBlueButton server indicating the recordings for meetings are ready for viewing.<syntaxhighlight lang="gherkin">
And the BigBlueButtonBN server has sent recording ready notifications
</syntaxhighlight>

The following steps are specific to the lesson activity. Note that in 4.0, some links (such as the "edit" and the "grade essays" links) are replaced by buttons, so you need to update your old steps with the new ones.<syntaxhighlight lang="gherkin">
And I edit the lesson
</syntaxhighlight>A new step is added to be used in lesson activities to edit them. This step navigates the user to the lesson edit page.

<syntaxhighlight lang="gherkin">
And I grade lesson essays
</syntaxhighlight>It's a new step to go to the "Grade essays" page of the lesson we are currently in.

<syntaxhighlight lang="gherkin">
And I select edit type "edit type"
</syntaxhighlight>Select the lesson edit type when we are in the the lesson's edit page. "edit type" can either be "Collapsed" or "Expanded".

The following new step can be used to navigate to the exports page in the course gradebook and select the specified export type from the grade exports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "export option" export page in the course gradebook
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "XML file" export page in the course gradebook
</syntaxhighlight>

Similarly, there's a new step to navigate to the imports page in the course gradebook and select the specified import type from the grade imports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "import option" import page in the course gradebook
</syntaxhighlight>

=== Boost steps ===
In addition to the steps listed in the previous section, there are also some Boost specific steps coming with Moodle 4.0. These steps only work in Boost or Boost child themes, so you need to make sure they are not used in scenarios that may be run by non-Boost themes.

The following step checks whether a node is active in the secondary navigation.<syntaxhighlight lang="gherkin">
And I should see :name is active in secondary navigation
</syntaxhighlight>

The Boost theme shows the language selector menu in the primary navigation when not logged in, and within the user menu when logged in. The following steps are to check if the primary navigation includes the language selector menu.<syntaxhighlight lang="gherkin">
And language selector menu should exist in the navbar
And language selector menu should not exist in the navbar
</syntaxhighlight>

And the following steps can be used to check whether an item exists in the language selector menu in the Boost theme.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the language selector menu
And "item text" "selector type" should not exist in the language selector menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "English &lrm;(en)&lrm;" "link" should exist in the language selector menu
</syntaxhighlight>

=== Modified steps ===
The step <code>I change the (window|viewport) size to "size"</code> now supports 2 new values for the size argument. The size argument now accepts <code>mobile</code> and <code>tablet</code> values in addition to <code>small</code>, <code>medium</code> and <code>large</code>.

=== Removed steps ===
Some behat steps are removed or replaced with new steps.

As a result of some design changes, hidden or restricted activities are no longer dimmed. Therefore the step<syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be dimmed
</syntaxhighlight>is now removed.

Depending on what you were using that step for, you may be able to use these steps:<syntaxhighlight lang="gherkin">
And "Label name" label should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And I should see "Activity or resource name"
And "Activity or resource name" "link" should not exist in the "region-main" "region"
</syntaxhighlight>

=== Other things to consider ===
To make behat tests more readable and easy to maintain, it is recommended to use the most direct steps to get what the test needs. It is highly recommended to use
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
instead of navigating to the activity via
I am on "Course" course homepage
I follow "Activity name"
Now that [https://docs.moodle.org/dev/Prototypes#Course_creation_improvements Course index] is integrated these behat steps
I am on "Course" course homepage
I follow "Activity name"
will fail using Boost theme.

The reason for it is that the drawer used in Boost is hiding the course index. So when the test is trying to follow an "Activity name" link, it finds two different links:
* one in the course index
* another one in the course main content.
But the first one, the one in the course index, is hidden by the drawer, and the test fails.

However the recommended behat steps
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
Old behat steps that may now fail can be updated to the new steps.
For example:
And I am on the "Test assignment name" "assign activity" page logged in as teacher1
instead of:
When I log in as "teacher1"
And I am on "Course" course homepage
And I follow "Test assignment name"
There are also similar stream-lined navigation steps for accessing question bank pages. See MDL-74130.
== Other ==
=== Core plugins review ===
A few plugins from core Moodle LMS which are no longer or hardly used have been removed and, if appropriate, added to the Moodle plugins directory.

More information about this project, the list of plugins to be removed and the process to follow for keeping them before upgrading to 4.0 can be found in the [[Core plugins review]] page.
=== Site admin presets plugin ===
The third-party plugin [https://moodle.org/plugins/block_admin_presets Admin presets], created by David Monllaó and maintained by developers from [https://pimenko.com/ Pimenko] has been adapted and integrated into Moodle 4.0. It stores settings and plugins status (enabled/disabled) in what's called "presets" to let admins quickly switch between different configurations.

More information about this project can be found in the [[Site admin presets|Site admin presets plugin]] page.
=== JavaScript browser support changes ===
From Moodle 4.0, Internet Explorer is no longer supported. See MDL-73915 and MDLSITE-6109 for further information on this change.

This change means that changes built on 4.0 onwards (including the master branch) will be different to older versions of Moodle.

For plugin developers supporting multiple versions of Moodle using a single plugin version, the compiled javascript files are backwards compatible and will _work_ on all supported versions, however if you run the `grunt` command on multiple versions you will see unbuilt changes. Running grunt on all versions of Moodle is not necessary and this check can be safely disabled for Moodle versions 3.9 - 4.0, as long as only at least you run `grunt` against at least one version of Moodle.

If you need to support Internet Explorer and do not wish to fork your plugin for Moodle 4.0 onwards, then it is recommended that you run `grunt` on an older version of Moodle.
=== The course index element ===
The new course index feature can be themed using a set of scss variables. Use them to change the look and feel instead of adding custom css
/theme/boost/scss/moodle/courseindex.scss
With the introduction of the course index component, the previous and next links shown underneath each activity are no longer needed and they will be removed.
=== Activity icons ===
The icons used for activities have been redesigned and updated for all core moodle activities.

When viewing the new icons in a file manager, for example for the quiz activity, you will see a simple black monochrome icon with a transparent background.

On the course page, or in the activity chooser, the icon will display as a white icon on a coloured background. Styling of the icons on the coursepage is controlled by the css in theme/boost/scss/moodle/icons.scss.

The background colour for activity icons is set using a new variable in function [modname]_supports(). The quiz activity is of type assessment, so in function quiz_supports() there is a new line defining the purpose:
case FEATURE_MOD_PURPOSE: return MOD_PURPOSE_ASSESSMENT;
Available purposes are:
* MOD_PURPOSE_COMMUNICATION
* MOD_PURPOSE_ASSESSMENT
* MOD_PURPOSE_COLLABORATION
* MOD_PURPOSE_CONTENT
* MOD_PURPOSE_ADMINISTRATION
* MOD_PURPOSE_INTERFACE
The background colours linked to these purposes are set in theme/boost/scss/moodle/variables.scss
$activity-icon-colors: map-merge(
(
"administration": #5d63f6,
"assessment": #eb66a2,
"collaboration": #f7634d,
"communication": #11a676,
"content": #399be2,
"interface": #a378ff
),
$activity-icon-colors
);
If activity plugins do not define FEATURE_MOD_PURPOSE the activity icon will be rendered against a light grey background. There is no requirement to define the purpose of activity plugins, it will only affect the icon styling.

Plugins implementing the variable FEATURE_MOD_PURPOSE are only supported on Moodle 4.0 and newer.

Customising the activity icon can be done in an alternative way. For example using the styles.css in mod/[pluginname/styles.css

In the example below the activity plugin developer chooses to keep the coloured icon for the activity and render it as large as the coloured background on the core activities
.modicon_subcourse.activityiconcontainer {
background-color: transparent;
padding: 0;
}

.modicon_subcourse.activityiconcontainer img {
width: 50px;
height: 50px;
}
To customize all icon colours use this scss array and add it to the ‘Raw initial SCSS’ in the theme Boost advanced settings page. The complete array of icon background colours can be overridden using the ‘Raw initial SCSS’ in the theme settings page. The example below changes the colours of each activity type.
$activity-icon-colors: (
"administration": #5D63F6,
"assessment": #11A676,
"collaboration": #EB66A2,
"communication": #F7634D,
"content": #399BE2,
"interface": #A378FF
)

== I'm a developer, what do I need to know? ==
=== Modules ===
If you are a module developer (activity / resources) then you need to review the following updates and changes:

* If using settings, reformat to work with the secondary navigation. We have significantly changed the way that settings are shown. Settings added to the course and activity administration branch of the navigation are now by default shown in the secondary navigation. You will most likely find them in the more section of the secondary navigation. Please avoid creating settings in containers (a parent navigation node with children). These settings will still be shown (details about that), but this goes against the pattern that we are trying to establish for navigation around the site. If you have a lot of settings, consider creating a specific page to handle your additional settings (screenshot?).
** The order of the items in the secondary navigation may not be to your liking. This can be changed. See [[Moodle_4.0_developer_update#Changing_the_order_of_tabs|changing the order of tabs]]
* Update my behat tests to use new steps for site navigation. See [[Moodle_4.0_developer_update#Behat_changes|new behat steps]].
* Update my module to use the new activity_header API. See [[Moodle_4.0_developer_update#The_activity_header_class|the activity header]].
* Update my pages to make it work with the general format of the tertiary navigation. See [[Moodle_4.0_developer_update#Tertiary_navigation|the tertiary navigation]].
* Update my activity icon to use the API and set a purpose. See [[Moodle_4.0_developer_update#Activity_icons|activity icons]].

Moodle 4.0 developer update

2022-03-14T07:07:57Z

Abgreeve: /* Tertiary navigation */

{{Moodle 4.0}}This page highlights the important changes that are coming in Moodle 4.0 for developers. Including how the UX improvements impact custom themes, relevant API changes, and what you can do as developer to prepare for the 4.0 release.
== Navigation changes ==
The core Navigation API has been left mostly untouched. The callbacks to all navigation callbacks remains unchanged and will be called as part of the regular 'navigation' and 'settingsnav' initialisation. Some new core classes have been created and exist within a new namespace 'core/navigation' and serves as conduit to rearrange, cherry-pick existing navigation nodes from the navigation/settingsnav trees and display within the respective navigation type. As such, it is highly recommended to provide unique keys for custom navigation nodes as this helps in the cherry-picking / rearranging process within the new classes.
=== Primary navigation ===
The primary navigation(the navbar) apart from the existing content will now display links to the Dashboard, My Courses, Site Admin and Course search, by default. You can still add items to the navbar via the 'custom menu' option. This will be displayed within the 'More' menu. We have transitioned the menus to be rendered via templates - refer user_menu.mustache. The lang menu has been moved to reside within the user menu.
==== Customising the primary navigation ====
Not yet implemented but we are looking at allowing the full addition and removal of any of the primary navigation tabs in the boost theme config file.
=== Secondary navigation ===
The main content area shows tabs for secondary navigation with a maximum of 5 items being rendered in this ‘more’ menu. A new UI component has been created to render menus like this. Files:
/lib/templates/moremenu.mustache
==== Changing the order of tabs ====
Apart from the previously mentioned functions, you can also create a custom secondary class as mentioned earlier. This will automatically be picked by getter and used to render the secondary nav within the activity. E.g. mod_assign/local/views/secondary. Note: This is currently only possible on an activity and block level.
=== Tertiary navigation ===
We've moved action buttons to the top of the page. We would encourage you to do the same.
If you have any buttons on an activity page that go to another page, or open a form (or similar), then we encourage you to move them from the body of your activity page to the top. All of the core activities have been updated to follow this pattern. Please take a look to see how you can format your activity in a similar fashion. There is no API here. You are welcome to create the buttons and display them as you wish in this top area.

=== New API functions ===
==== Page API ====
* Magic getters to fetch the primary and secondary navs and the primary output.
* The secondarynav magic getter also checks whether a custom secondary class has been defined within the module's local\views directory. Use this if you want to deviate from the standard secondary nav structure/order.

* set_secondary_nav - Force override the secondary navigation class

* has_secondary_navigation_setter - Sets the ‘_hassecondarynavigation’ to indicate whether a page should render the secondary navigation
==== Navigationlib ====
* set_show_in_secondary_navigation - whether or not a node should be displayed in the secondary nav. Accepts a single boolean argument
* set_force_into_more_menu- whether or not to force a node into the 'More' menu. Accepts a single boolean argument
==== The activity header class ====
There is a new activity header class that handles the display of information common to activities. 3rd party activities are not required to explicitly output this information as part of rendering individual pages.

The common information that are currently handled by the class are:
* title
* description
* completion information

As part of the update it was required that the initial information to be displayed by the class be toggable at a theme and layout level. Taking this into account the following theme level configurable exists:
* activityheaderconfig => An array that currently only enforces 'notitle' but can be expanded in the future NOTE: Boost has this set as true by default 'options'
The following layout level options that can be defined:
* noactivityheader - to remove the header in this specific layout.
* activityheader - An array that enforces the following options:
** notitle
** nocompletion
** nodescription
The class has a page level getter which you can use to fetch the current version of the class. The base state is initialised within the constructor with the completion information only fetched when data is exported for the template.

The class has setters for the following variables which can be leveraged to modify the header for a particular page in the format set_{variable_name}:
* hidecompletion
* description
* title
Alternately, bulk operations can also be done by passing the above variables in an array to 'set_attrs' which in turn calls the setters.<blockquote>'''Note: Any updates to the activityheader needs to be performed before the call to $OUTPUT->header'''</blockquote>
===== Theme updates: =====
In order for 3rd party themes to use the class they need to export the activity_header and include the following into their base template :<syntaxhighlight lang="html">
{{#headercontent}}
{{> core/activity_header}}
{{#headercontent}}
</syntaxhighlight>** headercontent being the array element that contains the exported activity_header data
===== Accessibility notes: =====
The jump to ‘maincontent’ div is now rendered within the activity header when within an activity context
== Component library ==
Each Moodle installation now ships with a Moodle User Interface (UI) Component library, a documentation system used to describe all the Bootstrap components and the custom Moodle components. The component Library is a helper tool for developers when creating user interfaces, a testing tool for theme developers and a documentation tool for core developers. The ultimate goal of having a component library is to encourage developers to create consistent user interfaces to improve Moodle’s overall user experience.

The library contains pages with documentation about User Interface components. It contains details on how to use the component, what variations are available and the JavaScript events / options are associated with the component.

When writing on these pages it is possible to render core mustache templates using some custom syntax like this:
<nowiki>{{< mustache template="core/notification_error" >}}</nowiki>
<nowiki>{{< /mustache >}}</nowiki>
You can also call core JavaScript or use HTML examples where the html code and the rendered result are visible in the Component Library. For more info visit the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-templates/ Moodle templates] page or the [http://componentlibrary.moodle.com/admin/tool/componentlibrary/docspage.php/library/moodle-javascript/ Moodle JavaScript] page.

Each page in the library uses the current css from the default theme in your Moodle installation, if you have multiple themes installed and enabled the setting "Allow theme changes on url", the component library will have a theme selector option.

A hosted version of the Component Library can be found here. http://componentlibrary.moodle.com
=== Enabling the Component Library ===
Component library pages are written in the markdown language. These pages need to be compiled to HTML pages before the Component Library is visible. To compile the pages the server running Moodle needs to have the [[Javascript Modules#Install%20NVM%20and%20Node|JavaScript developer tools installed]] (nodeJs and Grunt)

If your server meets all requirements you can enable the library running
$ npm install
$ grunt componentlibrary
Further installation instructions can be found in the Component Library itself.
=== Documenting new UI Components ===
There are no set rules for adding new pages in the component library yet. These rules will need to be written and adopted in the integration process for Moodle code.

As a guideline for making this rules consideration are:

The component library is not about single use components, for example the Moodle grade book (a huge component with many custom features). Or about very common components like buttons, these are already covered by the Bootstrap section of the component library.

New features should be build keeping in mind the UI part needs to be customisable and if possible (and making sense) reusable. And example would be the new page drawers that we are introducing for the Navigation project. Or the custom primary navigation menus where overflowing items are pushed into a More section.
== Theme changes ==
=== Edit switch ===
On theme boost the “Turn editing on” and “Customise this page” buttons have been replaced by an edit switch in the top navbar. Theme Classic will keep using the old buttons. Child themes can choose to use the edit switch if the theme config.php is using this variable
$THEME->haseditswitch = true;
The languague menu, which used to be rendered in place of the custom menu has moved to the user dropdown when the user is logged in. If not logged in it will be placed next to the search / notification / messaging icon in the top navbar.
=== Login page ===
The login page has been redesigned and allows the admin to configure a background image for the login page only in the theme settings page. This change is available in both Boost and Classic. The login page still has all the features with an improved layout.
=== The page footer ===
In large screens, the page footer button is only visible when clicking a help button at the bottom right of the screen.
=== User initials as profile picture placeholder ===
If users do not upload a profile picture the user initials are displayed on a rounded gray background as a placeholder picture in the top navbar or any other page using a placeholder image. This change will be available in both Boost and Classic.

With the introduction of this placeholder image the full username will no longer be displayed in the top navbar.
=== Removal of back to top link ===
The "back to top" link will be removed for theme boost since the new course index reduced the dependence on page scrolling. Also, the new footer is positioned where this component used to be.
=== Styling changes ===
By default rounded edges will be used for UI components, for the page header and main content area the borders will be removed.
=== New layout page ===
Theme boost now uses the drawers.php layout for the course index and blocks.
== Question bank changes ==
There was a big project to deliver [[Question bank improvements for Moodle 4.0]] which added a new plugin type for adding features to the question banks, tracking the version history for each question as it is edited (question table has been split into <code>question</code>, <code>question_versions</code> and <code>question_bank_entries</code>), and tracking where each question is going to be used, with new tables <code>question_references</code> and <code>question_set_references</code>. This work was done in Epic MDL-70329 if you want to track down the details of any of the core changes.
=== Question type plugins ===
Amazingly, we (Safat and colleagues at Catalyst AU) managed to implement this without breaking most question type plugins.

However, the changes to the question bank, and the other Moodle 4.0 changes, probably broke the Behat tests for your plugin. To help with fixing that, MDL-74130 adds navigation to key question type pages (Preview and Edit for a question, and standard question bank pages like the bank itself, import and export) which should let you fix your test efficiently, and in a way that will work in all Moodle versions since 3.9.

The 'most' in the first paragraph here is becuase more advance question types may require more effort to fix. (For example qtype_combined which creates multi-part qusetions like the core qtype_multianswer; or qtype_pmatch or qtype_stack, which store additional data - questions tests - alongside the question itseld. How should that work with versionning?) But, if you have not done weird things like that, you are probably safe. If you find anything else that causes problems, please list it here.

The same thing should apply to question behaviour and question import/export format plugings: no significant changes required (probably just fixing the Behat tests because of the navigation changes).
=== New plugin type: qbank plugins ===
This is not something that will cause problems for people upgrading from 3.x. Rather, it is an exciting possibility you can explore once you have survived process of upgrading to 4.0. There is a whole new plugin type which you can create to add new features to the question bank. For example extra columns, new actions and bulk actions, and so on. See [[Question_bank_plugins]].
=== Activities that use questions ===
The probable bad news is if you have an activity module which uses questions. So far, the only activity which has been fixed is mod_quiz in Moodle core, so we don't yet have a good picture of what fixes will be necessary in other activities. Work is about to start fixing [https://github.com/studentquiz/moodle-mod_studentquiz mod_studentquiz], so watching that should give more clues. As we do that, we will try to update this section of this page. Other help writing the information required here would also be greatly appreciated.
== The course format system ==
Most of the logic for rendering and editing a course has been moved to a new subsystem called courseformat. The subsystem is located in "course/format" folder so it includes all the format plugins inside. The methods and modules which are distributed between the course and the course/format folders are now rearranged or refactored to be aligned with the current Moodle coding style.
=== Mandatory renderer in course formats ===
Now format plugins renderer is not optional anymore. Legacy formats without a renderer will get a deprecation message but it will continue working however, they should create a new renderer as soon as possible. The section-based format can do it by extending the provided core_courseformat\output\section_renderer class which includes all the necessary methods.
=== New format base class ===
The old base_format class (which all plugins extend) is now renamed as core_courseformat\base. The new class provides all the functionally of the previous base_format but it has been refactored to be used as a centralized source of truth for the course rendering. Legacy formats should extend the new class to avoid the deprecation message.

Now, the plugin format class provides information such as:
* If the page is displaying a single or multiple section
* Give access to other related format objects like the modinfo, the course record, maximum number of sections...
* If the format is compatible with features like course index, reactive components, ajax...
* Other format specifics like the page title, the default section name, default blocks...

The format instance is now the main object output components will use to render a course (see next section for more information).
=== New course output classes and mustache files ===
Traditionally, section-based course formats uses print_single_section_page and print_multiple_section_page to render the course content. In Moodle 4.0 most of the course rendering methods are migrated to output components and mustache templates. The old methods will get deprecation messages if they use the old renderer methods.

This is an example of a format rendering a course:<syntaxhighlight lang="php-brief">
// Get the course format instance.
$format = course_get_format($course);

// Get the specific format renderer.
$renderer = $format->get_renderer($PAGE);

if (!empty($displaysection)) {
// Setup the format instance to display a single section.
$format->set_section_number($displaysection);
}

// Create the ouptut instance and render it.
$outputclass = $format->get_output_classname('content');
$widget = new $outputclass($format);

echo $renderer->render($widget);
</syntaxhighlight>Format plugins are free to use its own output classes to render a course, or they could override the existing output classes by providing their own implementation. For example, the default output for "content" (as in the previous example) is "core_courseformat\output\local\|content", however, if the plugin has a "format_XXX\output\courseformat\content" class, the $format->class the get_output_class will return the overridden one.
Another important update on course rendering is that now all course structure is rendered using mustache templates instead of the original html_writer methods. Now themes are able to override the course format by providing alternative versions of the mustache files. All core course templates are located in "course/format/templates".

All the new output classes and a guide on how to migrate the current third-party plugins will be available soon.
=== Course editor javascript modules and frontend components ===
The majority of the javascript logic related to the course editing is replaced by AMD modules. Because this is a major change in the way courses are edited and rendered, by default format plugins will continue using the previous YUI modules for now. However, formats can start using the new libraries overriding the "$format->supports_components()" method.

Some Moodle 4.0 new features are only available for courses using the new editor library:
* Edit the course via the course index
* Creating sections without reloading the course page
* The new move section/activity modal
* Native browser drag&drop implementation
The new course editor uses a component-based reactive pattern to keep track of the course changes. The pattern highlights are:
* The main AMD module "core_crouseformat\courseeditor" maintains a data structure called state.
* Each UI element is implemented as a Component that observes the course state data and reacts to any data change
* When any reactive component needs to modify the course, it asks the course editor to execute a mutation. Mutations encapsulate all web services calls and alter the course state data.

The reactive library documentation, as well as the format plugin migration guide, will be available soon.
=== Other course related 4.0 changes ===
Two new web services have been added:
* core_courseformat_get_state: user by the new javascript course editor to get the current course state data (containing the list of sections, activities, and other course-related data)
* core_courseformat_update_course: to alter the current course content. Each call returns the parts of the course state altered by the action
== Behat changes ==

=== New steps ===
Moodle 4.0 introduces some new behat steps.

Sometimes you want to create a bulk number of activities. In that case you can use:<syntaxhighlight lang="gherkin">
:count :entitytype exist with the following data:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
Given 100 "mod_lti > tool types" exist with the following data:
|name |Test tool [count] |
|description |Example description [count] |
|baseurl |https://www.example.com/tool[count]|
</syntaxhighlight>

Dynamic (AJAX) tabs is a new feature contributed to Moodle 4.0 by the Workplace team (MDL-71943). You can use the following step to navigate between the tabs.<syntaxhighlight lang="gherkin">
And I click on the "tab title" dynamic tab
</syntaxhighlight>

To make sure that edit mode is (or is not) available on the current page, the following steps can be used.<syntaxhighlight lang="gherkin">
And edit mode should be available on the current page
And edit mode should not be available on the current page
</syntaxhighlight>

There are new aliases for the existing steps <code>I turn editing mode on</code> and <code>I turn editing mode off</code>.<syntaxhighlight lang="gherkin">
And I switch editing mode on
And I switch editing mode off
</syntaxhighlight>

In addition to the existing step to go to a course with editing mode on, we now have the following step to do the same but with editing mode being off.<syntaxhighlight lang="gherkin">
And I am on "course full name" course homepage with editing mode off
</syntaxhighlight>

The following step is similar to the old <code>following "link string" should download between "min bytes" and "max bytes" bytes</code> step, with more flexibility.<syntaxhighlight lang="gherkin">
And following "element string" "element type" in the "container string" "container type" should download between "min bytes" and "max bytes" bytes
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And following "Download" "link" in the "Starter" "table_row" should download between "0" and "5000" bytes
</syntaxhighlight>

The following step can be used to hover the mouse over the trigger area.<syntaxhighlight lang="gherkin">
And I hover over the "element string" "element type" in the "container string" "container type"
</syntaxhighlight>

The following step enables an installed plugin.<syntaxhighlight lang="gherkin">
And I enable "plugin name" "plugin type" plugin
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I enable "course_summary" "block" plugin
</syntaxhighlight>

The following is a special variation of 'I click on "<page name>" "link" in the "page" "region"'. It first checks to see if we are on the given page via the breadcrumb. If not we then attempt to follow the link name given.<syntaxhighlight lang="gherkin">
And I follow the breadcrumb "page name"
</syntaxhighlight>

You can use the following step to ensure a node is active in the navbar.<syntaxhighlight lang="gherkin">
And I should see "Node" is active in navigation
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I should see "My courses" is active in navigation
</syntaxhighlight>

The following step can be used to navigate to a given node in the primary navigation.<syntaxhighlight lang="gherkin">
And I select "Node" from primary navigation
</syntaxhighlight>

The following steps are to check whether an item exists in the user menu or not.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the user menu
And "item text" "selector type" should not exist in the user menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "Language" "link" should exist in the user menu
</syntaxhighlight>

The following steps are to check if a submenu of the user menu is shown, and if an item exists or does not exist in a given user submenu.<syntaxhighlight lang="gherkin">
And I should see "submenu name" user submenu
And "item text" "selector type" should exist in the "submenu name" user submenu
And "item text" "selector type" should not exist in the "submenu name" user submenu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I follow "Language" in the user menu
Then I should see "Language selector" user submenu
And "English &lrm;(en)&lrm;" "link" should exist in the "Language selector" user submenu
And "English (pirate) &lrm;(en_ar)&lrm;" "link" should not exist in the "Language selector" user submenu
</syntaxhighlight>

To add enrolment methods to courses you can use the following new step. The data that you provide in the next lines are used to fill the enrolment method form.<syntaxhighlight lang="gherkin">
And I add "enrolment method" in "course identifier" with:
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
When I add "Self enrolment" enrolment method in "Course 1" with:
| Custom instance name | Test student enrolment |
| Enrolment key | moodle_rules |
| Use group enrolment keys | Yes |
</syntaxhighlight>

There are 3 new steps specific to the calendar component. These steps can be used to hover over a day in the mini-calendar or the full calendar.<syntaxhighlight lang="gherkin">
And I hover over day "day of month" of this month in the full calendar page
And I hover over day "day of month" of this month in the mini-calendar block
And I hover over today in the mini-calendar block
</syntaxhighlight>

Some new steps are added to question bank to be able to add comment to questions, verify the existence of a comment, and deleting comments form questions. Please note that the steps for adding comments only write the comment text in the comment field. You still need to click on the "Add comment" button to save the comment.<syntaxhighlight lang="gherkin">
And I add "comment text" comment to question
And I add "comment text" comment to question preview
And I delete "comment text" comment from question
And I delete "comment text" comment from question preview
And I should see "number of comments" on the comments column
And I click "number of comments" on the row on the comments column

</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "Question bank" in current page administration
And I should see "0" on the comments column
And I click "0" on the row on the comments column
And I add "test comment 01" comment to question
And I click on "Add comment" "button" in the ".modal-dialog" "css_element"
And I click on "Close" "button" in the ".modal-dialog" "css_element"
And I should see "1" on the comments column
And I click "1" on the row on the comments column
And I delete "test comment 01" comment from question
</syntaxhighlight>

Similar to the steps for comments, the following steps are to verify the number of a question's usage and to click on it in order to open the question usage modal.<syntaxhighlight lang="gherkin">
And I should see "usage count" on the usage column
And I click "usage count" on the usage column
</syntaxhighlight>

The following new steps are related to bulk actions in the question bank UI.<syntaxhighlight lang="gherkin">
And I click on question bulk action "action"
And I should see question bulk action "action"
And I should not see question bulk action "action"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I click on "First question" "checkbox"
And I click on "Second question" "checkbox"
And I click on "With selected" "button"
And I should see question bulk action "deleteselected"
And I click on question bulk action "deleteselected"
And I click on "Delete" "button" in the "Confirm" "dialogue"
</syntaxhighlight>

[https://docs.moodle.org/en/Report_builder Report builder] is a new feature contributed to Moodle 4.0 by the Workplace team. The following new step is added to Moodle 4.0 to select an action from the action menu in the list of custom reports table.<syntaxhighlight lang="gherkin">
And I press "action" action in the "report name" report row
</syntaxhighlight>

There's another step related to the report builder to set a column's aggregation in the report editor.<syntaxhighlight lang="gherkin">
And I set the "column title" column aggregation to "aggregation method"
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I set the "First name" column aggregation to "Comma separated values"
</syntaxhighlight>

The following step needs to be used in scenarios that involve testing BigBlueButton. For this to work, you need to have a [https://github.com/moodlehq/bigbluebutton_mock BigBlueButton Mock API Server] and set <code>TEST_MOD_BIGBLUEBUTTONBN_MOCK_SERVER</code> to point to that in config.php.<syntaxhighlight lang="gherkin">
And a BigBlueButton mock server is configured
</syntaxhighlight>

The following step replicates receiving a callback from the BigBlueButton server indicating the recordings for meetings are ready for viewing.<syntaxhighlight lang="gherkin">
And the BigBlueButtonBN server has sent recording ready notifications
</syntaxhighlight>

The following steps are specific to the lesson activity. Note that in 4.0, some links (such as the "edit" and the "grade essays" links) are replaced by buttons, so you need to update your old steps with the new ones.<syntaxhighlight lang="gherkin">
And I edit the lesson
</syntaxhighlight>A new step is added to be used in lesson activities to edit them. This step navigates the user to the lesson edit page.

<syntaxhighlight lang="gherkin">
And I grade lesson essays
</syntaxhighlight>It's a new step to go to the "Grade essays" page of the lesson we are currently in.

<syntaxhighlight lang="gherkin">
And I select edit type "edit type"
</syntaxhighlight>Select the lesson edit type when we are in the the lesson's edit page. "edit type" can either be "Collapsed" or "Expanded".

The following new step can be used to navigate to the exports page in the course gradebook and select the specified export type from the grade exports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "export option" export page in the course gradebook
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And I navigate to "XML file" export page in the course gradebook
</syntaxhighlight>

Similarly, there's a new step to navigate to the imports page in the course gradebook and select the specified import type from the grade imports navigation selector.<syntaxhighlight lang="gherkin">
And I navigate to "import option" import page in the course gradebook
</syntaxhighlight>

=== Boost steps ===
In addition to the steps listed in the previous section, there are also some Boost specific steps coming with Moodle 4.0. These steps only work in Boost or Boost child themes, so you need to make sure they are not used in scenarios that may be run by non-Boost themes.

The following step checks whether a node is active in the secondary navigation.<syntaxhighlight lang="gherkin">
And I should see :name is active in secondary navigation
</syntaxhighlight>

The Boost theme shows the language selector menu in the primary navigation when not logged in, and within the user menu when logged in. The following steps are to check if the primary navigation includes the language selector menu.<syntaxhighlight lang="gherkin">
And language selector menu should exist in the navbar
And language selector menu should not exist in the navbar
</syntaxhighlight>

And the following steps can be used to check whether an item exists in the language selector menu in the Boost theme.<syntaxhighlight lang="gherkin">
And "item text" "selector type" should exist in the language selector menu
And "item text" "selector type" should not exist in the language selector menu
</syntaxhighlight>For example:<syntaxhighlight lang="gherkin">
And "English &lrm;(en)&lrm;" "link" should exist in the language selector menu
</syntaxhighlight>

=== Modified steps ===
The step <code>I change the (window|viewport) size to "size"</code> now supports 2 new values for the size argument. The size argument now accepts <code>mobile</code> and <code>tablet</code> values in addition to <code>small</code>, <code>medium</code> and <code>large</code>.

=== Removed steps ===
Some behat steps are removed or replaced with new steps.

As a result of some design changes, hidden or restricted activities are no longer dimmed. Therefore the step<syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be dimmed
</syntaxhighlight>is now removed.

Depending on what you were using that step for, you may be able to use these steps:<syntaxhighlight lang="gherkin">
And "Label name" label should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And "Activity or resource name" activity should be hidden
</syntaxhighlight><syntaxhighlight lang="gherkin">
And I should see "Activity or resource name"
And "Activity or resource name" "link" should not exist in the "region-main" "region"
</syntaxhighlight>

=== Other things to consider ===
To make behat tests more readable and easy to maintain, it is recommended to use the most direct steps to get what the test needs. It is highly recommended to use
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
instead of navigating to the activity via
I am on "Course" course homepage
I follow "Activity name"
Now that [https://docs.moodle.org/dev/Prototypes#Course_creation_improvements Course index] is integrated these behat steps
I am on "Course" course homepage
I follow "Activity name"
will fail using Boost theme.

The reason for it is that the drawer used in Boost is hiding the course index. So when the test is trying to follow an "Activity name" link, it finds two different links:
* one in the course index
* another one in the course main content.
But the first one, the one in the course index, is hidden by the drawer, and the test fails.

However the recommended behat steps
I am on the "Activity name" "[modname] activity" page
or
I am on the "Activity name" "[modname] activity" page logged in as "user"
Old behat steps that may now fail can be updated to the new steps.
For example:
And I am on the "Test assignment name" "assign activity" page logged in as teacher1
instead of:
When I log in as "teacher1"
And I am on "Course" course homepage
And I follow "Test assignment name"
There are also similar stream-lined navigation steps for accessing question bank pages. See MDL-74130.
== Other ==
=== Core plugins review ===
A few plugins from core Moodle LMS which are no longer or hardly used have been removed and, if appropriate, added to the Moodle plugins directory.

More information about this project, the list of plugins to be removed and the process to follow for keeping them before upgrading to 4.0 can be found in the [[Core plugins review]] page.
=== Site admin presets plugin ===
The third-party plugin [https://moodle.org/plugins/block_admin_presets Admin presets], created by David Monllaó and maintained by developers from [https://pimenko.com/ Pimenko] has been adapted and integrated into Moodle 4.0. It stores settings and plugins status (enabled/disabled) in what's called "presets" to let admins quickly switch between different configurations.

More information about this project can be found in the [[Site admin presets|Site admin presets plugin]] page.
=== JavaScript browser support changes ===
From Moodle 4.0, Internet Explorer is no longer supported. See MDL-73915 and MDLSITE-6109 for further information on this change.

This change means that changes built on 4.0 onwards (including the master branch) will be different to older versions of Moodle.

For plugin developers supporting multiple versions of Moodle using a single plugin version, the compiled javascript files are backwards compatible and will _work_ on all supported versions, however if you run the `grunt` command on multiple versions you will see unbuilt changes. Running grunt on all versions of Moodle is not necessary and this check can be safely disabled for Moodle versions 3.9 - 4.0, as long as only at least you run `grunt` against at least one version of Moodle.

If you need to support Internet Explorer and do not wish to fork your plugin for Moodle 4.0 onwards, then it is recommended that you run `grunt` on an older version of Moodle.
=== The course index element ===
The new course index feature can be themed using a set of scss variables. Use them to change the look and feel instead of adding custom css
/theme/boost/scss/moodle/courseindex.scss
With the introduction of the course index component, the previous and next links shown underneath each activity are no longer needed and they will be removed.
=== Activity icons ===
The icons used for activities have been redesigned and updated for all core moodle activities.

When viewing the new icons in a file manager, for example for the quiz activity, you will see a simple black monochrome icon with a transparent background.

On the course page, or in the activity chooser, the icon will display as a white icon on a coloured background. Styling of the icons on the coursepage is controlled by the css in theme/boost/scss/moodle/icons.scss.

The background colour for activity icons is set using a new variable in function [modname]_supports(). The quiz activity is of type assessment, so in function quiz_supports() there is a new line defining the purpose:
case FEATURE_MOD_PURPOSE: return MOD_PURPOSE_ASSESSMENT;
Available purposes are:
* MOD_PURPOSE_COMMUNICATION
* MOD_PURPOSE_ASSESSMENT
* MOD_PURPOSE_COLLABORATION
* MOD_PURPOSE_CONTENT
* MOD_PURPOSE_ADMINISTRATION
* MOD_PURPOSE_INTERFACE
The background colours linked to these purposes are set in theme/boost/scss/moodle/variables.scss
$activity-icon-colors: map-merge(
(
"administration": #5d63f6,
"assessment": #eb66a2,
"collaboration": #f7634d,
"communication": #11a676,
"content": #399be2,
"interface": #a378ff
),
$activity-icon-colors
);
If activity plugins do not define FEATURE_MOD_PURPOSE the activity icon will be rendered against a light grey background. There is no requirement to define the purpose of activity plugins, it will only affect the icon styling.

Plugins implementing the variable FEATURE_MOD_PURPOSE are only supported on Moodle 4.0 and newer.

Customising the activity icon can be done in an alternative way. For example using the styles.css in mod/[pluginname/styles.css

In the example below the activity plugin developer chooses to keep the coloured icon for the activity and render it as large as the coloured background on the core activities
.modicon_subcourse.activityiconcontainer {
background-color: transparent;
padding: 0;
}

.modicon_subcourse.activityiconcontainer img {
width: 50px;
height: 50px;
}
To customize all icon colours use this scss array and add it to the ‘Raw initial SCSS’ in the theme Boost advanced settings page. The complete array of icon background colours can be overridden using the ‘Raw initial SCSS’ in the theme settings page. The example below changes the colours of each activity type.
$activity-icon-colors: (
"administration": #5D63F6,
"assessment": #11A676,
"collaboration": #EB66A2,
"communication": #F7634D,
"content": #399BE2,
"interface": #A378FF
)

Moodle 4.0 developer update

2022-03-03T06:26:30Z

Abgreeve: Changing header levels

Moodle 4.0 developer update

2022-03-03T06:07:44Z

Abgreeve: /* Behat changes -- removed MDLs */

Moodle 4.0 developer update

2022-03-03T06:05:37Z

Abgreeve: Major rearrangement of page content

Prototypes

2021-07-27T06:18:29Z

Abgreeve: /* New projects and prototype site demonstrations */ Update to show the navigation prototype

This page provides links to prototype sites demonstrating new features that will be included in coming versions of Moodle.

''We would love to hear what you think of these new features! After exploring the sites, please post your feedback in the [https://moodle.org/mod/forum/view.php?id=8052 Future major features forum].''

== New projects and prototype site demonstrations ==

=== Calendar usability improvements ===
{| class="wikitable" border="1"
|-
| Description
| As part of the UX improvements for Moodle 4.0, we are working on updates to the calendar.

The main aims for this project are to make the calendar, calendar block and subscription management more intuitive, easier to use and improve accessibility.
|-
| Project Tracker
| [https://tracker.moodle.org/browse/MDL-71770 Tracker epic containing all related issues]
|-
| Prototype
| [https://calendartest.prototype.moodledemo.net/ Calendar usability improvements demo]
|-
| Target Version
| 4.0
|}

=== Course creation improvements ===
{| class="wikitable" border="1"
|-
| Description
| As part of the UX improvements for Moodle 4.0, we are working on making the like easier on creating and editing courses.

The main aims for this project are to improve the user experience of creating and editing courses in Moodle helping teachers to create and organize their courses. Adding new cool features like course index will allow teachers an easy way to view course structure, add new sections and activities, reorganize them and so on.

|-
| Project Tracker
| [https://tracker.moodle.org/browse/MDL-70907 Tracker epic containing all related issues]
|-
| Prototype
| [https://createcourse.prototype.moodledemo.net/ Course creation improvements demo]
|-
| Target Version
| 4.0
|}

=== Navigation update ===
{| class="wikitable" border="1"
|-
| Description
| We are updating the navigation around Moodle.

The main aim is to reduce the cognitive load associated with navigating around a Moodle site. For anyone that is new to using our LMS, there are a lot of settings that are immediately present and possibly not relevant. We are going through and improving the layout of the navigation from the front page all the way to how different activities are displaying settings and buttons.

|-
| Project Tracker
| [https://tracker.moodle.org/browse/MDL-69588 Tracker epic containing all related issues]
|-
| Prototype
| [https://navigation.prototype.moodledemo.net/ Navigation prototype demo]
|-
| Target Version
| 4.0
|}
 

'''''More prototype site links coming soon...'''''
 
 

== How to contribute ==

=== [[File:logo moodle.png|frameless|100px]] Moodle User Experience (UX) Forums ===

{| class="wikitable" border="1"
|-
| Description
| As part of the UX 4.0 release, the UX team are establishing a presence on the Moodle.org platform in order to collaborate and communicate with the wider Moodle Community.
We're looking forward to working with you and sharing what we learn and what we do!
|-
| More
| User Experience Forum [https://moodle.org/course/view.php?id=17248 Want to shape the Moodle future with us?].
|-
| Project Tracker
| Moodle UX 4.0 [https://tracker.moodle.org/projects/UX/issues/ tracker issues and epics]
|-
| Prototypes
| [https://www.figma.com/proto/A4d9WOUVxCqS93mvXVCr8P/4.0-UX-Demo?node-id=2394%3A15559&viewport=727%2C769%2C0.07944665849208832&scaling=scale-down 4.0 Desktop Navigation UX Project]
[https://www.figma.com/proto/A4d9WOUVxCqS93mvXVCr8P/4.0-UX-Demo?node-id=2392%3A11210&viewport=1413%2C310%2C0.31215807795524597&scaling=scale-down 4.0 Mobile Navigation UX Project]
|-
| Target Version
| 4.0
|}

=== [[File:logo_moodle_tracker.jpg|frameless|100px]] Moodle Tracker ===

{| class="wikitable" border="1"
|-
| Description
| This is where we record and manage all issues related to Moodle and related systems.
It's not just for developers! :-) All users should use this system to report problems or new ideas for Moodle and help us make it better.
|-
| More
| Moodle Tracker [https://tracker.moodle.org/secure/Dashboard.jspa Want to shape the Moodle future with us?].
|}

=== [[File:mua-logo-small-onblue.png|frameless|100px]] Moodle Users Association ===

{| class="wikitable" border="1"
|-
| Description
| MUA's mission is to support the growth of Moodle by providing a strong and united voice to users, giving direction and resources for new developments.
|-
| More
| Join MUA [https://moodle.org/course/view.php?id=17248 Shape the future of Moodle today.].
|}
 
 

== [[File:logo_moodle_dev.jpg|frameless|100px]] Other Moodle demo sites ==

=== QA Moodle Demo ===

{| class="wikitable" border="1"
|-
| Description
| It is updated daily at 13:00 UTC with the latest fixes for testers to test and do a final check for any problems.
Every hour (on the hour) the database and files are reset.
|-
| Moodle Version
| The latest Moodle dev release!
|-
|-
| Site
| '''[https://qa.moodledemo.net/ qa.moodledemo.net/]'''
|}

=== School Moodle Demo ===

{| class="wikitable" border="1"
|-
| Description
| This demonstration site gives you the opportunity to explore Moodle in action as a manager, teacher, student, parent or privacy officer with realistic content.
This site is reset every hour on the hour so anything you "break" will get fixed.
|-
| Moodle Version
| The latest Moodle stable release!
|-
|-
| Site
| '''[https://school.moodledemo.net/ school.moodledemo.net/]'''
|}

=== Sandbox Moodle Demo ===

{| class="wikitable" border="1"
|-
| Description
| This site is a plain installation of Moodle using the Boost theme.
This site is reset to its blank state every hour, on the hour.
|-
| Moodle Version
| The latest Moodle stable release!
|-
|-
| Site
| '''[https://sandbox.moodledemo.net/ sandbox.moodledemo.net/]'''
|}
 

==See also==

* [[Roadmap]] - for an overview of new features planned for the next release
* [[Releases]] - for all official releases of Moodle, grouped by branch in reverse chronological order

Prototypes

2020-02-04T06:03:45Z

Abgreeve: Update to show the activity chooser

Activity chooser

2020-01-10T05:36:48Z

Abgreeve: Removed H5P as that no longer has it's own tab.

{{Infobox Project
|state = In progress
|name = Activity chooser
|tracker = MDL-67255 (epic), MDL-57828, MDL-61511
|discussion = https://moodle.org/mod/forum/discuss.php?d=346664
|assignee = Team Alpha
}}

== Introduction ==

Through our road-map creation process of looking at highly voted tracker issues and relevant forum posts, as well as MUA interaction, an update to the activity chooser to simplify and make less intimidating, was chosen.

MDL-57828 was created and worked on, but unfortunately stalled, and did not complete its way through the integration process. There is a substantial forum post [https://moodle.org/mod/forum/discuss.php?d=346664], with many suggestions and current pain points with the activity chooser. The MUA created a proposal issue (MDL-61511) to tackle the same issue.

We have recently been analysing how course creation is achieved. Two main ideas were tested with focus groups to try and find the best away to approach course creation. With this information we are confident that we have a user focused design that will improve the activity chooser for everyone.

We would like to invite everyone to express their opinion on this improvement. Course creation is a Moodle activity that is fundamental to teaching a course online, and we would like to ensure that the process is as easy and intuitive as possible.

== Features ==

The following are changes that we are planning on making in this project. We have a demo that can be viewed and interacted with.
[https://projects.invisionapp.com/share/SVSREPYNBYG#/screens/388682478 Invisio mockup of the activity chooser].

Our current work can be viewed at [https://activitychooser.prototype.moodledemo.net/ activity chooser prototype]. Please take a look.

=== Larger display area ===

The activity chooser will be wider and have the activities in a grid format. This allows for more activities to be seen at once.

=== Activities and resources are now merged ===

Our research found that the distinction been activities and resources was not useful to teachers and so now these two categories have been merged together.

=== Starred / Favourites tab ===

The user can now select activities to be added to the Starred tab. The starred tab is shown by default to users when pulling up the activity chooser.

[[File:activity-chooser-starred.png|The starred tab]]

=== Recommended tab ===

Site administrators will now be able to set a selection of activities as recommended. These recommended activities will show up in a tab in the activity chooser for the course creator to view. If no recommendations are made then this tab will not be displayed.

[[File:activity-chooser-recommend.png|The recommended tab]]

=== Smart search bar ===

To help find activities from the activity chooser, we will be adding a search bar, that will search through both the names of the activities, and also the information text, to try and find relevant activities that the user may want.

=== Other activity types ===

Other activity types such as LTI will be able to be added to the activity chooser for the user to select.

=== Activity information hidden ===

The information about an activity will be accessible through the 'i' icon. Clicking the link will show additional information about the activity. This will free up space for other activities to be shown rather than always taking up half of the activity chooser.

[[File:activity-chooser-info.png|Additional information about an activity]]

== Third party plugin developers ==

For developers who wish to add items to the activity chooser, this is still done through the {plugin}_get_shortcuts() callback which is placed in the plugin's lib.php file.
Developers who are currently using this callback are requested to now return an ID with each object. The ID has the following requirements:
* Must be unique to your component.
* Must not change.
* Must be of type integer.

It is not mandatory to add this ID, but your items will not have the ability to be favourited or recommended.

Activity chooser

2020-01-10T02:56:16Z

Abgreeve: update to link

{{Infobox Project
|state = In progress
|name = Activity chooser
|tracker = MDL-67255 (epic), MDL-57828, MDL-61511
|discussion = https://moodle.org/mod/forum/discuss.php?d=346664
|assignee = Team Alpha
}}

== Introduction ==

Through our road-map creation process of looking at highly voted tracker issues and relevant forum posts, as well as MUA interaction, an update to the activity chooser to simplify and make less intimidating, was chosen.

MDL-57828 was created and worked on, but unfortunately stalled, and did not complete its way through the integration process. There is a substantial forum post [https://moodle.org/mod/forum/discuss.php?d=346664], with many suggestions and current pain points with the activity chooser. The MUA created a proposal issue (MDL-61511) to tackle the same issue.

We have recently been analysing how course creation is achieved. Two main ideas were tested with focus groups to try and find the best away to approach course creation. With this information we are confident that we have a user focused design that will improve the activity chooser for everyone.

We would like to invite everyone to express their opinion on this improvement. Course creation is a Moodle activity that is fundamental to teaching a course online, and we would like to ensure that the process is as easy and intuitive as possible.

== Features ==

The following are changes that we are planning on making in this project. We have a demo that can be viewed and interacted with.
[https://projects.invisionapp.com/share/SVSREPYNBYG#/screens/388682478 Invisio mockup of the activity chooser].

Our current work can be viewed at [https://activitychooser.prototype.moodledemo.net/ activity chooser prototype]. Please take a look.

=== Larger display area ===

The activity chooser will be wider and have the activities in a grid format. This allows for more activities to be seen at once.

=== Activities and resources are now merged ===

Our research found that the distinction been activities and resources was not useful to teachers and so now these two categories have been merged together.

=== Starred / Favourites tab ===

The user can now select activities to be added to the Starred tab. The starred tab is shown by default to users when pulling up the activity chooser.

[[File:activity-chooser-starred.png|The starred tab]]

=== Recommended tab ===

Site administrators will now be able to set a selection of activities as recommended. These recommended activities will show up in a tab in the activity chooser for the course creator to view. If no recommendations are made then this tab will not be displayed.

[[File:activity-chooser-recommend.png|The recommended tab]]

=== H5P activities included ===

We are looking at adding the ability for users to select an H5P activity from the activity chooser.

=== Smart search bar ===

To help find activities from the activity chooser, we will be adding a search bar, that will search through both the names of the activities, and also the information text, to try and find relevant activities that the user may want.

=== Other activity types ===

Other activity types such as LTI will be able to be added to the activity chooser for the user to select.

=== Activity information hidden ===

The information about an activity will be accessible through the 'i' icon. Clicking the link will show additional information about the activity. This will free up space for other activities to be shown rather than always taking up half of the activity chooser.

[[File:activity-chooser-info.png|Additional information about an activity]]

== Third party plugin developers ==

For developers who wish to add items to the activity chooser, this is still done through the {plugin}_get_shortcuts() callback which is placed in the plugin's lib.php file.
Developers who are currently using this callback are requested to now return an ID with each object. The ID has the following requirements:
* Must be unique to your component.
* Must not change.
* Must be of type integer.

It is not mandatory to add this ID, but your items will not have the ability to be favourited or recommended.

Activity chooser

2020-01-10T02:54:54Z

Abgreeve: Prototype link and third party dev information

{{Infobox Project
|state = In progress
|name = Activity chooser
|tracker = MDL-67255 (epic), MDL-57828, MDL-61511
|discussion = https://moodle.org/mod/forum/discuss.php?d=346664
|assignee = Team Alpha
}}

== Introduction ==

Through our road-map creation process of looking at highly voted tracker issues and relevant forum posts, as well as MUA interaction, an update to the activity chooser to simplify and make less intimidating, was chosen.

MDL-57828 was created and worked on, but unfortunately stalled, and did not complete its way through the integration process. There is a substantial forum post [https://moodle.org/mod/forum/discuss.php?d=346664], with many suggestions and current pain points with the activity chooser. The MUA created a proposal issue (MDL-61511) to tackle the same issue.

We have recently been analysing how course creation is achieved. Two main ideas were tested with focus groups to try and find the best away to approach course creation. With this information we are confident that we have a user focused design that will improve the activity chooser for everyone.

We would like to invite everyone to express their opinion on this improvement. Course creation is a Moodle activity that is fundamental to teaching a course online, and we would like to ensure that the process is as easy and intuitive as possible.

== Features ==

The following are changes that we are planning on making in this project. We have a demo that can be viewed and interacted with.
[https://projects.invisionapp.com/share/SVSREPYNBYG#/screens/388682478 Invisio mockup of the activity chooser].

Our current work can be viewed at [https://activitychooser.prototype.moodledemo.net/]. Please take a look.

=== Larger display area ===

The activity chooser will be wider and have the activities in a grid format. This allows for more activities to be seen at once.

=== Activities and resources are now merged ===

Our research found that the distinction been activities and resources was not useful to teachers and so now these two categories have been merged together.

=== Starred / Favourites tab ===

The user can now select activities to be added to the Starred tab. The starred tab is shown by default to users when pulling up the activity chooser.

[[File:activity-chooser-starred.png|The starred tab]]

=== Recommended tab ===

Site administrators will now be able to set a selection of activities as recommended. These recommended activities will show up in a tab in the activity chooser for the course creator to view. If no recommendations are made then this tab will not be displayed.

[[File:activity-chooser-recommend.png|The recommended tab]]

=== H5P activities included ===

We are looking at adding the ability for users to select an H5P activity from the activity chooser.

=== Smart search bar ===

To help find activities from the activity chooser, we will be adding a search bar, that will search through both the names of the activities, and also the information text, to try and find relevant activities that the user may want.

=== Other activity types ===

Other activity types such as LTI will be able to be added to the activity chooser for the user to select.

=== Activity information hidden ===

The information about an activity will be accessible through the 'i' icon. Clicking the link will show additional information about the activity. This will free up space for other activities to be shown rather than always taking up half of the activity chooser.

[[File:activity-chooser-info.png|Additional information about an activity]]

== Third party plugin developers ==

For developers who wish to add items to the activity chooser, this is still done through the {plugin}_get_shortcuts() callback which is placed in the plugin's lib.php file.
Developers who are currently using this callback are requested to now return an ID with each object. The ID has the following requirements:
* Must be unique to your component.
* Must not change.
* Must be of type integer.

It is not mandatory to add this ID, but your items will not have the ability to be favourited or recommended.

Activity chooser

2019-11-18T01:46:49Z

Abgreeve: Removal of plugins adding activities and related discussion.

{{Infobox Project
|state = Open
|name = Activity chooser
|tracker = MDL-67255 (epic), MDL-57828, MDL-61511
|discussion = https://moodle.org/mod/forum/discuss.php?d=346664
|assignee = Team Alpha
}}

== Introduction ==

Through our road-map creation process of looking at highly voted tracker issues and relevant forum posts, as well as MUA interaction, an update to the activity chooser to simplify and make less intimidating, was chosen.

MDL-57828 was created and worked on, but unfortunately stalled, and did not complete its way through the integration process. There is a substantial forum post [https://moodle.org/mod/forum/discuss.php?d=346664], with many suggestions and current pain points with the activity chooser. The MUA created a proposal issue (MDL-61511) to tackle the same issue.

We have recently been analysing how course creation is achieved. Two main ideas were tested with focus groups to try and find the best away to approach course creation. With this information we are confident that we have a user focused design that will improve the activity chooser for everyone.

We would like to invite everyone to express their opinion on this improvement. Course creation is a Moodle activity that is fundamental to teaching a course online, and we would like to ensure that the process is as easy and intuitive as possible.

== Features ==

The following are changes that we are planning on making in this project. We have a demo that can be viewed and interacted with.
[https://projects.invisionapp.com/share/SVSREPYNBYG#/screens/388682478 Invisio mockup of the activity chooser].

=== Larger display area ===

The activity chooser will be wider and have the activities in a grid format. This allows for more activities to be seen at once.

=== Activities and resources are now merged ===

Our research found that the distinction been activities and resources was not useful to teachers and so now these two categories have been merged together.

=== Starred / Favourites tab ===

The user can now select activities to be added to the Starred tab. The starred tab is shown by default to users when pulling up the activity chooser.

[[File:activity-chooser-starred.png|The starred tab]]

=== Recommended tab ===

Site administrators will now be able to set a selection of activities as recommended. These recommended activities will show up in a tab in the activity chooser for the course creator to view. If no recommendations are made then this tab will not be displayed.

[[File:activity-chooser-recommend.png|The recommended tab]]

=== H5P activities included ===

We are looking at adding the ability for users to select an H5P activity from the activity chooser.

=== Smart search bar ===

To help find activities from the activity chooser, we will be adding a search bar, that will search through both the names of the activities, and also the information text, to try and find relevant activities that the user may want.

=== Other activity types ===

Other activity types such as LTI will be able to be added to the activity chooser for the user to select.

=== Activity information hidden ===

The information about an activity will be accessible through the 'i' icon. Clicking the link will show additional information about the activity. This will free up space for other activities to be shown rather than always taking up half of the activity chooser.

[[File:activity-chooser-info.png|Additional information about an activity]]

Talk:Activity chooser

2019-11-18T01:46:07Z

Abgreeve: Start of discussion

''It is currently possible to include additional items to the activity picker (such as the external tools). We are looking at expanding this to allow any plugin to add items to the activity picker.''

What do you mean by this? I can see it makes sense for mod_ plugins to be able to do this, but why any plugin type? Can you give an example that shows why this is a requirement. Thanks. --Tim.

Thanks for your comment Tim. We have a couple of future projects that we are trying to make allowances for. One is Moodle net and how to get content from there into a course, and the second is an ability to add plugins into a course. These are not well defined. To avoid confusion I'll remove this section and we'll put on hold this idea until it is absolutely necessary. -- Adrian

Activity chooser

2019-11-15T02:10:07Z

Abgreeve: Adding times via any plugin to the activity chooser.

Activity chooser

2019-11-15T01:31:55Z

Abgreeve: Very minor edit to add further detail to infobox.

Activity chooser

2019-11-15T01:30:58Z

Abgreeve: Minor update to add epic issue to project info box

{{Infobox Project
|state = Open
|name = Activity chooser
|tracker = MDL-67255, MDL-57828, MDL-61511
|discussion = https://moodle.org/mod/forum/discuss.php?d=346664
|assignee = Team Alpha
}}

== Introduction ==

Through our road-map creation process of looking at highly voted tracker issues and relevant forum posts, as well as MUA interaction, an update to the activity chooser to simplify and make less intimidating, was chosen.

MDL-57828 was created and worked on, but unfortunately stalled, and did not complete its way through the integration process. There is a substantial forum post [https://moodle.org/mod/forum/discuss.php?d=346664], with many suggestions and current pain points with the activity chooser. The MUA created a proposal issue (MDL-61511) to tackle the same issue.

We have recently been analysing how course creation is achieved. Two main ideas were tested with focus groups to try and find the best away to approach course creation. With this information we are confident that we have a user focused design that will improve the activity chooser for everyone.

We would like to invite everyone to express their opinion on this improvement. Course creation is a Moodle activity that is fundamental to teaching a course online, and we would like to ensure that the process is as easy and intuitive as possible.

== Features ==

The following are changes that we are planning on making in this project. We have a demo that can be viewed and interacted with.
[https://projects.invisionapp.com/share/SVSREPYNBYG#/screens/388682478 Invisio mockup of the activity chooser].

=== Larger display area ===

The activity chooser will be wider and have the activities in a grid format. This allows for more activities to be seen at once.

=== Activities and resources are now merged ===

Our research found that the distinction been activities and resources was not useful to teachers and so now these two categories have been merged together.

=== Starred / Favourites tab ===

The user can now select activities to be added to the Starred tab. The starred tab is shown by default to users when pulling up the activity chooser.

[[File:activity-chooser-starred.png|The starred tab]]

=== Recommended tab ===

Site administrators will now be able to set a selection of activities as recommended. These recommended activities will show up in a tab in the activity chooser for the course creator to view. If no recommendations are made then this tab will not be displayed.

[[File:activity-chooser-recommend.png|The recommended tab]]

=== H5P activities included ===

We are looking at adding the ability for users to select an H5P activity from the activity chooser.

=== Smart search bar ===

To help find activities from the activity chooser, we will be adding a search bar, that will search through both the names of the activities, and also the information text, to try and find relevant activities that the user may want.

=== Other activity types ===

Other activity types such as LTI will be able to be added to the activity chooser for the user to select.

=== Activity information hidden ===

The information about an activity will be accessible through the 'i' icon. Clicking the link will show additional information about the activity. This will free up space for other activities to be shown rather than always taking up half of the activity chooser.

[[File:activity-chooser-info.png|Additional information about an activity]]

Activity chooser

2019-10-28T06:00:11Z

Abgreeve: Initial information.

{{Infobox Project
|state = Open
|name = Activity chooser
|tracker = MDL-57828, MDL-61511
|discussion = https://moodle.org/mod/forum/discuss.php?d=346664
|assignee = Team Alpha
}}

== Introduction ==

Through our road-map creation process of looking at highly voted tracker issues and relevant forum posts, as well as MUA interaction, an update to the activity chooser to simplify and make less intimidating, was chosen.

MDL-57828 was created and worked on, but unfortunately stalled, and did not complete its way through the integration process. There is a substantial forum post [https://moodle.org/mod/forum/discuss.php?d=346664], with many suggestions and current pain points with the activity chooser. The MUA created a proposal issue (MDL-61511) to tackle the same issue.

We have recently been analysing how course creation is achieved. Two main ideas were tested with focus groups to try and find the best away to approach course creation. With this information we are confident that we have a user focused design that will improve the activity chooser for everyone.

We would like to invite everyone to express their opinion on this improvement. Course creation is a Moodle activity that is fundamental to teaching a course online, and we would like to ensure that the process is as easy and intuitive as possible.

== Features ==

The following are changes that we are planning on making in this project. We have a demo that can be viewed and interacted with.
[https://projects.invisionapp.com/share/SVSREPYNBYG#/screens/388682478 Invisio mockup of the activity chooser].

=== Larger display area ===

The activity chooser will be wider and have the activities in a grid format. This allows for more activities to be seen at once.

=== Activities and resources are now merged ===

Our research found that the distinction been activities and resources was not useful to teachers and so now these two categories have been merged together.

=== Starred / Favourites tab ===

The user can now select activities to be added to the Starred tab. The starred tab is shown by default to users when pulling up the activity chooser.

[[File:activity-chooser-starred.png|The starred tab]]

=== Recommended tab ===

Site administrators will now be able to set a selection of activities as recommended. These recommended activities will show up in a tab in the activity chooser for the course creator to view. If no recommendations are made then this tab will not be displayed.

[[File:activity-chooser-recommend.png|The recommended tab]]

=== H5P activities included ===

We are looking at adding the ability for users to select an H5P activity from the activity chooser.

=== Smart search bar ===

To help find activities from the activity chooser, we will be adding a search bar, that will search through both the names of the activities, and also the information text, to try and find relevant activities that the user may want.

=== Other activity types ===

Other activity types such as LTI will be able to be added to the activity chooser for the user to select.

=== Activity information hidden ===

The information about an activity will be accessible through the 'i' icon. Clicking the link will show additional information about the activity. This will free up space for other activities to be shown rather than always taking up half of the activity chooser.

[[File:activity-chooser-info.png|Additional information about an activity]]

File:activity-chooser-starred.png

2019-10-28T05:49:41Z

Abgreeve: Activity chooser starred / favourite tab.

Activity chooser starred / favourite tab.

File:activity-chooser-recommend.png

2019-10-28T05:49:13Z

Abgreeve: Activity chooser recommended tab.

Activity chooser recommended tab.

File:activity-chooser-info.png

2019-10-28T05:47:42Z

Abgreeve: Activity chooser information page.

Activity chooser information page.

Privacy API

2018-11-30T01:26:04Z

Abgreeve: Quick fix to code example.

The [https://en.wikipedia.org/wiki/General_Data_Protection_Regulation General Data Protection Regulation] (GDPR) is an EU directive that looks at providing users with more control over their data and how it is processed. This regulation will come into effect on 25th of May 2018 and covers any citizen or permanent resident of the European Union. The directive will be respected by a number of other countries outside of the European Union.

To help institutions become compliant with this new regulation we are adding functionality to Moodle. This includes a number of components, amongst others these include a user’s right to:

* request information on the types of personal data held, the instances of that data, and the deletion policy for each;
* access all of their data; and
* be forgotten.

The compliance requirements also extend to installed plugins (including third party plugins). These need to also be able to report what information they store or process regarding users, and have the ability to provide and delete data for a user request.

This document describes the proposed API changes required for plugins which will allow a Moodle installation to become GDPR compliant.

Target Audience: The intended audience for this document is Moodle plugin developers, who are aiming to ensure their plugins are updated to comply with GDPR requirements coming into effect in the EU in May, 2018.

==Personal data in Moodle==

From the GDPR Spec, Article 4:

''‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;''

In Moodle, we need to consider two main types of personal data; information entered by the user and information stored about the user. The key difference being that information stored about the user will have come from a source other than the user themselves. Both types of data can be used to form a profile of the individual.

The most obvious clue to finding personal data entered by the user is the presence of a userid on a database field. Any data on the record (or linked records) pertaining to that user may be deemed personal data for that user, including things like timestamps and record identification numbers. Additionally, any free text field which allows the user to enter information must also be considered to be the personal data of that user.

Data stored about the user includes things like ratings and comments made on a student submission. These may have been made by an assessor or teacher, but are considered the personal data of the student, as they are considered a reflection of the user’s competency in the subject matter and can be used to form a profile of that individual.

The sections that follow outline what you need to do as a plugin developer to ensure any personal data is advertised and can be accessed and deleted according to the GDPR requirements.

==Background==

===Architecture overview===

[[File:MoodlePrivacyMetadataUML.png|thumb|UML diagram of the metadata part of the privacy subsystem]]
[[File:MoodlePrivacyRequestUML.png|thumb|UML diagram of the request providers part of the privacy subsystem]]

A new system for Privacy has been created within Moodle. This is broken down into several main parts and forms the ''core_privacy'' subsystem:

* Some metadata providers - a set of PHP interfaces to be implemented by components for that component to describe the kind of data that it stores, and the purpose for its storage;
* Some request providers - a set of PHP interfaces to be implemented by components to allow that component to act upon user requests such as the Right to be Forgotten, and a Subject Access Request; and
* A manager - a concrete class used to bridge components which implement the providers with tools which request their data.

All plugins will implement one metadata provider, and zero, one or two request providers.

The 'request' providers are responsible for several separate areas:

# Detecting in which Moodle contexts a specific user has any personal data;
# Exporting all personal data from each of those contexts for that user;
# Deleting all personal data from each of those contexts for that user;
# Detecting which users have personal data in a specific Moodle context;
# Deleting all personal data for each of those users in that context; and
# Deleting all personal data for all users in a specific context.

The export and delete phases use data from the detection phase, which allows for the possibility to exclude all data from certain contexts, as required.

Please refer to the inline phpdocs of the [https://github.com/moodle/moodle/blob/v3.5.0/privacy/classes/manager.php#L31 core_privacy::manager class] for detailed description of the interfaces, their hierarchy and meaning.

Please note that support for locating and removing multiple users in a single context was added in MDL-62560 for Moodle 3.6, 3.5.3, and 3.4.6.
This functionality has been added to allow support for removal of user data for users subject to speific role criterion, and to support expiry of the same data by role too.

===Implementing a provider===

All plugins will need to create a concrete class which implements the relevant metadata and request providers. The exact providers you need to implement will depend on what data you store, and the type of plugin. This is covered in more detail in the following sections of the document.

In order to do so:

# You must create a class called ''provider'' within the namespace ''\your_pluginname\privacy''.
# This class must be created at ''path/to/your/plugin/classes/privacy/provider.php''.
# You must have your class implement the relevant metadata and request interfaces.

==Plugins which do not store personal data==

Many Moodle plugins do not store any personal data. This is usually the case for plugins which just add functionality, or which display the data already stored elsewhere in Moodle.

Some examples of plugin types which might fit this criteria include themes, blocks, filters, editor plugins, etc.

Plugins which cause data to be stored elsewhere in Moodle (e.g. via a subsystem call) are considered to store data.

One examples of a plugin which does not store any data would be the Calendar month block which just displays a view of the user’s calendar. It does not store any data itself.

An example of a plugin which must not use the null provider is the Comments block. The comments block is responsible for data subsequently being stored within Moodle. Although the block doesn’t store anything itself, it interacts with the comments subsystem and is the only component which knows how that data maps to a user.

===Implementation requirements===

In order to let Moodle know that you have audited your plugin, and that you do not store any personal user data, you must implement the ''\core_privacy\local\metadata\null_provider'' interface in your plugin’s provider.

These null providers can only be implemented where a plugin has:

* no external links (e.g. sends data to an external service like an LTI provider, repository plugin which you can search on)
* no database tables which store user data (including IP addresses)
* no user preferences

The ''null_provider'' requires you to define one function ''get_reason()'' which returns the language string identifier within your component.

====Example====

''blocks/calendar_month/classes/privacy/provider.php''

<code php>
<?php
// …

namespace block_calendar_month\privacy;

class provider implements
// This plugin does not store any personal user data.
\core_privacy\local\metadata\null_provider {

/**
* Get the language string identifier with the component's language
* file to explain why this plugin stores no data.
*
* @return string
*/
public static function get_reason() : string {
return 'privacy:metadata';
}
}
</code>

''blocks/calendar_month/lang/en/block_calendar_month.php''

<code php>
<?php
// …

...
$string['privacy:metadata'] = 'The Calendar block only displays existing calendar data.';
...
</code>

That’s it. Congratulations, your plugin now implements the Privacy API.

==Plugins which store personal data==

Many Moodle plugins do store some form of personal data.

In some cases this will be stored within database tables in your plugin, and in other cases this will be in one of Moodle’s core subsystems - for example your plugin may store files, ratings, comments, or tags.

Plugins which do store data will need to:

* Describe the type of data that they store;
* Provide a way to export that data; and
* Provide a way to delete that data.

Data is described via a ''metadata'' provider, and it is both exported and deleted via an implementation of a ''request'' provider.

These are both explained in the sections below.

===Describing the type of data you store===

In order to describe the type of data that you store, you must implement the ''\core_privacy\local\metadata\provider'' interface.

This interfaces requires that you define one function: ''get_metadata''.

There are several types of item to describe the data that you store. These are for:

* Items in the Moodle database;
* Items stored by you in a Moodle subsystem - for example files, and ratings; and
* User preferences stored site-wide within Moodle for your plugin

Note: All fields should include a description from a language string within your plugin.

====Example====

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …

namespace mod_forum\privacy;
use core_privacy\local\metadata\collection;

class provider implements
// This plugin does store personal user data.
\core_privacy\local\metadata\provider {

public static function get_metadata(collection $collection) : collection {

// Here you will add more items into the collection.

return $collection;
}
}
</code>

====Indicating that you store content in a Moodle subsystem====

Many plugins will use one of the core Moodle subsystems to store data.

As a plugin developer we do not expect you to describe those subsystems in detail, but we do need to know that you use them and to know what you use them for.

You can indicate this by calling the ''add_subsystem_link()'' method on the ''collection''.

=====Relevant subsystems=====

You are likely to need to indicate use of the following subsystems that store user data:

* Ratings (if users are allowed to rate items within your plugin)
* Tags (if users can tag items within your plugin)
* Comments (if users can make comments on items in your plugin)
* Questions (if the plugin uses core question types)
* Filesystem (if users can attach files to items within your plugin)
* ...?

Some subsystems which store user data do not need to be listed:

* (TBC - how about global search? Nothing lists it that I could see.)

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_subsystem_link(
'core_files',
[],
'privacy:metadata:core_files'
);

return $collection;
}
</code>

''mod/forum/lang/en/forum.php''

<code php>
<?php

$string['privacy:metadata:core_files'] = 'The forum stores files which have been uploaded by the user to form part of a forum post.';
</code>

====Describing data stored in database tables====

Most Moodle plugins will store some form of user data in their own database tables.

As a plugin developer you will need to describe each database table, and each field which includes user data.

It is a matter of judgement which fields contain user data and which don't. Anything entered by, or directly about, the user probably counts as user data but it may be useful to include additional fields that explain the context of the data.

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_database_table(
'forum_discussion_subs',
[
'userid' => 'privacy:metadata:forum_discussion_subs:userid',
'discussionid' => 'privacy:metadata:forum_discussion_subs:discussionid',
'preference' => 'privacy:metadata:forum_discussion_subs:preference',

],
'privacy:metadata:forum_discussion_subs'
);

return $collection;
}
</code>

''mod/forum/lang/en/forum.php''

<code php>
<?php

$string['privacy:metadata:forum_discussion_subs'] = 'Information about the subscriptions to individual forum discussions. This includes when a user has chosen to subscribe to a discussion, or to unsubscribe from one where they would otherwise be subscribed.';
$string['privacy:metadata:forum_discussion_subs:userid'] = 'The ID of the user with this subscription preference.';
$string['privacy:metadata:forum_discussion_subs:discussionid'] = 'The ID of the discussion that was subscribed to.';
$string['privacy:metadata:forum_discussion_subs:preference'] = 'The start time of the subscription.';
</code>

====Indicating that you store site-wide user preferences====

Many plugins will include one or more user preferences. Unfortunately this is one of Moodle’s older components and many of the values stored are not pure user preferences. Each plugin should be aware of how it handles its own preferences and is best placed to determine whether they are site-wide preferences, or per-instance preferences.

Whilst most of these will have a fixed name (e.g. ''filepicker_recentrepository''), some will include a variable of some kind (e.g. ''tool_usertours_tour_completion_time_2''). Only the general name (in this case "tool_usertours_tour_completion_time_") needs to be indicated, rather than one copy for each possible value of the variable.

Also, these should only be ''site-wide'' user preferences which do not belong to a specific Moodle context.

In the above examples:

* Preference ''filepicker_recentrepository'' belongs to the file subsystem, and is a site-wide preference affecting the user anywhere that they view the filepicker.
* Preference ''tool_usertours_tour_completion_time_2'' belongs to user tours. User tours are a site-wide feature which can affect many parts of Moodle and cross multiple contexts.

In some cases a value may be stored in the preferences table but is known to belong to a specific context within Moodle. In these cases they should be stored as metadata against that context rather than as a site-wide user preference.

You can indicate this by calling the ''add_user_preference()'' method on the ''collection''.

Any plugin providing user preferences must also implement the ''\core_privacy\local\request\preference_provider''.

=====Example=====

''admin/tool/usertours/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_user_preference('tool_usertours_tour_completion_time',
'privacy:metadata:preference:tool_usertours_tour_completion_time');

return $collection;
}
</code>

''admin/tool/usertours/lang/en/tool_usertours.php''

<code php>
<?php

$string['privacy:metadata:tool_usertours_tour_completion_time'] = 'The time that a specific user tour was last completed by a user.';
</code>

====Indicating that you export data to an external location====

Many plugins will interact with external systems - for example cloud-based services. Often this external location is configurable within the plugin either at the site or the instance level.

As a plugin developer you will need to describe each ''type'' of target destination, alongside a list of each exported field which includes user data.
The ''actual'' destination does not need to be described as this can change based on configuration.

You can indicate this by calling the ''add_external_location_link()'' method on the collection.

=====Example=====

''mod/lti/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_external_location_link('lti_client', [
'userid' => 'privacy:metadata:lti_client:userid',
'fullname' => 'privacy:metadata:lti_client:fullname',
], 'privacy:metadata:lti_client');

return $collection;
}
</code>

''mod/lti/lang/en/lti.php''

<code php>
<?php

$string['privacy:metadata:lti_client'] = 'In order to integrate with a remote LTI service, user data needs to be exchanged with that service.';
$string['privacy:metadata:lti_client:userid'] = 'The userid is sent from Moodle to allow you to access your data on the remote system.';
$string['privacy:metadata:lti_client:fullname'] = 'Your full name is sent to the remote system to allow a better user experience.';
</code>

===Providing a way to export user data===

In order to export the user data that you store, you must implement the relevant request provider.

We have named these request providers because they are called in response to a specific request from a user to access their information, however they also deal with the removal of user data following it's expiry.

There are several different types of request provider, and you may need to implement several of these, depending on the type and nature of your plugin.

Broadly speaking plugins will fit into one of the following categories:

* Plugins which are a subplugin of another plugin. Examples include ''assignsubmission'', ''atto'', and ''datafield'';
* Plugins which are typically called by a Moodle subsystem. Examples include ''qtype'', and ''profilefield'';
* All other plugins which store data.

Most plugins will fit into this final category, whilst other plugins may fall into several categories.
Plugins which ''define'' a subplugin will also be responsible for collecting this data from their subplugins.

A final category exists - plugins which store user preferences. In some cases this may be the ''only'' provider implemented.

====Standard plugins which store data====

A majority of Moodle plugins will fit into this category and will be required to implement the ''\core_privacy\local\request\plugin\provider'' interface. This interface requires that you define four functions (the first two of which are dealt with in this section):

* ''get_contexts_for_userid'' - to explain where data is held within Moodle for your plugin; and
* ''export_user_data'' - to export a user’s personal data from your plugin.
* ''delete_data_for_all_users_in_context'' - to delete all data for all users in the specified context.
* ''delete_data_for_user'' - to delete all user data for the specified user, in the specified contexts.

These APIs make use of the Moodle ''context'' system to hierarchically store this data.

In addition to these requirements, since Moodle 3.4.6, 3.5.3, any plugin which implements the plugin provider interface must also implement the ''\core_privacy\local\request\core_userlist_provider'' provider and implement functions:

* ''get_users_in_context'' - to locate the users who hold any personal data in a specific context; and
* ''delete_data_for_users'' - to delete data for multiple users in the specified context.

A polyfill has not been provided for this new interface, but we recognise that developers who are maintaining older versions (Moodle 3.3) will hit problems with this new interface not existing. We recommend doing something similar to the following example.
<code php>
<?php

namespace assignsubmission_example\privacy;

if (interface_exists('\core_privacy\local\request\userlist')) {
interface my_userlist extends \core_privacy\local\request\userlist{}
} else {
interface my_userlist {};
}

class provider implements my_userlist {

/**
* Get the list of users who have data within a context.
*
* @param userlist $userlist The userlist containing the list of users who have data in this context/plugin combination.
*/
public static function get_users_in_context(userlist $userlist) {

}

/**
* Delete multiple users within a single context.
*
* @param approved_userlist $userlist The approved context and user information to delete information for.
*/
public static function delete_data_for_users(approved_userlist $userlist) {

}

}
</code>

=====Retrieving the list of contexts=====

You are required to return the list of contexts for which the plugin stores data about the user. These are the standard Moodle contexts - CONTEXT_COURSE, CONTEXT_USER, CONTEXT_MODULE and so on. In many cases the link between the module type and the context is self-evident (e.g. activity modules). In some cases it may be less so. For example, an enrolment plugin (that stores user data, which most don't) would link to course context (users enrol in courses). Other types of plugins may be less obvious but you need to pick something. One way might to consider what context you would use when checking role capabilities. Consider that this will be used to structure the exported data and define what data is deleted when a context is expired.

Contexts are retrieved using the ''get_contexts_for_userid'' function which takes the ID of the user being fetched, and returns a list of contexts in which the user has any data.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {}
</code>

The function returns a ''\core_privacy\local\request\contextlist'' which is used to keep a set of contexts together in a fixed fashion.

Because a Subject Access Request covers ''every'' piece of data that is held for a user within Moodle, efficiency and performance is highly important. As a result, contexts are added to the ''contextlist'' by defining one or more SQL queries which return just the contextid. Multiple SQL queries can be added as required.

Many plugins will interact with specific subsystems and store data within them.
These subsystems will also provide a way in which to link the data that you have stored with your own database tables.
At present these are still a work in progress and only the ''core_ratings'' subsystem includes this.

======Basic example======

The following example simply fetches the contextid for all forums where a user has a single discussion (note: this is an incomplete example):

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {
$contextlist = new \core_privacy\local\request\contextlist();

$sql = "SELECT c.id
FROM {context} c
INNER JOIN {course_modules} cm ON cm.id = c.instanceid AND c.contextlevel = :contextlevel
INNER JOIN {modules} m ON m.id = cm.module AND m.name = :modname
INNER JOIN {forum} f ON f.id = cm.instance
LEFT JOIN {forum_discussions} d ON d.forum = f.id
WHERE (
d.userid = :discussionuserid
)
";

$params = [
'modname' => 'forum',
'contextlevel' => CONTEXT_MODULE,
'discussionuserid' => $userid,
];

$contextlist->add_from_sql($sql, $params);

return $contextlist;
}
</code>

======More complete example======

The following example includes a link to core_rating.
It will find any forum, forum discussion, or forum post where the user has any data, including:

* Per-forum digest preferences;
* Per-forum subscription preferences;
* Per-forum read tracking preferences;
* Per-discussion subscription preferences;
* Per-post read data (if a user has read a post or not); and
* Per-post rating data.

In the case of the rating data, this will include any post where the user has rated the post of another user.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {
$ratingsql = \core_rating\privacy\provider::get_sql_join('rat', 'mod_forum', 'post', 'p.id', $userid);
// Fetch all forum discussions, and forum posts.
$sql = "SELECT c.id
FROM {context} c
INNER JOIN {course_modules} cm ON cm.id = c.instanceid AND c.contextlevel = :contextlevel
INNER JOIN {modules} m ON m.id = cm.module AND m.name = :modname
INNER JOIN {forum} f ON f.id = cm.instance
LEFT JOIN {forum_discussions} d ON d.forum = f.id
LEFT JOIN {forum_posts} p ON p.discussion = d.id
LEFT JOIN {forum_digests} dig ON dig.forum = f.id
LEFT JOIN {forum_subscriptions} sub ON sub.forum = f.id
LEFT JOIN {forum_track_prefs} pref ON pref.forumid = f.id
LEFT JOIN {forum_read} hasread ON hasread.forumid = f.id
LEFT JOIN {forum_discussion_subs} dsub ON dsub.forum = f.id
{$ratingsql->join}
WHERE (
p.userid = :postuserid OR
d.userid = :discussionuserid OR
dig.userid = :digestuserid OR
sub.userid = :subuserid OR
pref.userid = :prefuserid OR
hasread.userid = :hasreaduserid OR
dsub.userid = :dsubuserid OR
{$ratingsql->userwhere}
)
";

$params = [
'modname' => 'forum',
'contextlevel' => CONTEXT_MODULE,
'postuserid' => $userid,
'discussionuserid' => $userid,
'digestuserid' => $userid,
'subuserid' => $userid,
'prefuserid' => $userid,
'hasreaduserid' => $userid,
'dsubuserid' => $userid,
];
$params += $ratingsql->params;

$contextlist = new \core_privacy\local\request\contextlist();
$contextlist->add_from_sql($sql, $params);

return $contextlist;

}
</code>

=====Retrieving the users in a context=====

You are required to return the list of users holding personal data in a context for which the plugin stores data about the user.
This method is very similar to the ''get_contexts_for_userid'' function but has some important distinctions:

* It takes a ''userlist'' as an argument and does not require that you, as a developer, create it yourself;
* There is no need to return any value; and
* The argument for the ''userlist::add_from_sql'' are different to those for ''contextlist::add_from_sql'' (this is because we learnt some important lessons after the initial implementation).

<code php>
/**
* Get the list of users who have data within a context.
*
* @param userlist $userlist The userlist containing the list of users who have data in this context/plugin combination.
*/
public static function get_users_in_context(userlist $userlist) {}
</code>

======Basic example======

The following example simply fetches the userid for all users in a given forum context, who created a discussion or a post in that forum (note: this is an incomplete example):

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of users who have data within a context.
*
* @param userlist $userlist The userlist containing the list of users who have data in this context/plugin combination.
*/
public static function get_users_in_context(userlist $userlist) {

$context = $userlist->get_context();

if (!$context instanceof \context_module) {
return;
}

$params = [
'instanceid' => $context->instanceid,
'modulename' => 'forum',
];

// Discussion authors.
$sql = "SELECT d.userid
FROM {course_modules} cm
JOIN {modules} m ON m.id = cm.module AND m.name = :modulename
JOIN {forum} f ON f.id = cm.instance
JOIN {forum_discussions} d ON d.forum = f.id
WHERE cm.id = :instanceid";
$userlist->add_from_sql('userid', $sql, $params);

// Forum authors.
$sql = "SELECT p.userid
FROM {course_modules} cm
JOIN {modules} m ON m.id = cm.module AND m.name = :modulename
JOIN {forum} f ON f.id = cm.instance
JOIN {forum_discussions} d ON d.forum = f.id
JOIN {forum_posts} p ON d.id = p.discussion
WHERE cm.id = :instanceid";
$userlist->add_from_sql('userid', $sql, $params);

// ...
}
</code>

=====Exporting user data=====

After determining where in Moodle your plugin holds data about a user, the ''\core_privacy\manager'' will then ask your plugin to export all user data for a subset of those locations.

This is achieved through use of the ''export_user_data'' function which takes the list of approved contexts in a ''\core_privacy\local\request\approved_contextlist'' object.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Export all user data for the specified user, in the specified contexts, using the supplied exporter instance.
*
* @param approved_contextlist $contextlist The approved contexts to export information for.
*/
public static function export_user_data(approved_contextlist $contextlist) {}
</code>

The ''approved_contextlist'' includes both the user record, and a list of contexts, which can be retrieved by either processing it as an Iterator, or by calling ''get_contextids()'' or ''get_contexts()'' as required.

Data is exported using a ''\core_privacy\local\request\content_writer'', which is described in further detail below.

====Plugins which store user preferences====

Many plugins store a variety of user preferences, and must therefore export them.

Since user preferences are a site-wide preference, these are exported separately to other user data.
In some cases the only data present is user preference data, whilst in others there is a combination of user-provided data, and user preferences.

Storing of user preferences is achieved through implementation of the ''\core_privacy\local\request\user_preference_provider'' interface which defines one required function -- ''export_user_preferences''.

You need to provide a description of the value of the user preference. (This description is particularly useful in cases where the value might be, say, 3, but it actually means 'Alphabetical order'.) Most likely you can use an existing language string from your plugin.

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Export all user preferences for the plugin.
*
* @param int $userid The userid of the user whose data is to be exported.
*/
public static function export_user_preferences(int $userid) {
$markasreadonnotification = get_user_preference('markasreadonnotification', null, $userid);
if (null !== $markasreadonnotification) {
switch ($markasreadonnotification) {
case 0:
$markasreadonnotificationdescription = get_string('markasreadonnotificationno', 'mod_forum');
break;
case 1:
default:
$markasreadonnotificationdescription = get_string('markasreadonnotificationyes', 'mod_forum');
break;
}
writer::export_user_preference('mod_forum', 'markasreadonnotification', $markasreadonnotification, $markasreadonnotificationdescription);
}
}
</code>

==== Plugins which can have own subplugins ====

Many plugin types are also able to define their own subplugins and will need to define a contract between themselves and their subplugins in order to fetch their data.

This is required as the parent plugin and the child subplugin should be separate entities and the parent plugin must be able to function if one or more of its subplugins are uninstalled.

The parent plugin is responsible for defining the contract, and for interacting with its subplugins, though we intend to create helpers to make this easier.

The parent plugin should define a new interface for each type of subplugin that it defines. This interface should extend the ''\core_privacy\local\request\plugin\subplugin_provider'' interface.

===== When a parent plugin should and should not provide the interface for its subplugins =====

There can be cases when there is no point for a plugin to provide the "subplugin_provider" based interface, even if it has own subplugins. See the Atto or TinyMCE editors as real examples.

If the parent plugin has no data passed through to the subplugins, there is no benefit in defining a subplugin provider. For example, Atto subplugins are just used to enhance the functionality and they never receive anything like a context. Most of the time we need to define a subplugin provider, but in cases where there is no data passed from the plugin to its subplugins, there is no need to define the subplugin provider. If the subplugins still do store personal data that are not related to the parent plugin in any way, then subplugins should define their own standard provider.

Compare with something like mod_assign where the subplugins store data for the parent and that data is contextually relevant to the parent plugin. In those cases the subplugin stores data for the plugin and it only makes sense to do so in the context of its parent plugin.

=====Example=====

The following example defines the contract that assign submission subplugins may be required to implement.

The assignment module is responsible for returning the contexts of all assignments where a user has data, but in some cases it is unaware of all of those cases - for example if a Teacher comments on a student submission it may not be aware of these as the information about this interaction may not be stored within its own tables.

''mod/assign/privacy/assignsubmission_provider.php''

<code php>
<?php
// …

namespace mod_assign\privacy;
use \core_privacy\local\metadata\collection;

interface assignsubmission_provider extends
// This Interface defines a subplugin.
\core_privacy\local\request\plugin\subplugin_provider {

/**
* Get the SQL required to find all submission items where this user has had any involvements.
*
* @param int $userid The user to search.
* @return \stdClass Object containing the join, params, and where used to select a these records from the database.
*/
public static function get_items_with_user_interaction(int $userid) : \stdClass ;

/**
* Export all relevant user submissions information which match the combination of userid and attemptid.
*
* @param int $userid The user to search.
* @param \context $context The context to export this submission against.
* @param array $subcontext The subcontext within the context to export this information
* @param int $attid The id of the submission to export.
*/
public static function export_user_submissions(int $userid, \context $context, array $subcontext, int $attid) ;

}
</code>

====Plugins which are subplugins to another plugin====

If you are developing a sub-plugin of another plugin, then you will have to look at the relevant plugin in order to determine the exact contract.

Each subplugin type should define a new interface which extends the ''\core_privacy\local\request\plugin\subplugin_provider'' interface and it is up to the parent plugin to define how they will interact with their children.

The principles remain the same, but the exact implementation will differ depending upon requirements.

''mod/pluginname/classes/privacy/provider.php''

<code php>
<?php
// …
namespace assignsubmission\onlinetext;

class provider implements
// This plugin does store personal user data.
\core_privacy\local\metadata\provider,

// This plugin is a subplugin of assign and must meet that contract.
\mod_assign\privacy\assignsubmission_provider {
}
</code>

====Plugins which are typically called by a Moodle subsystem====

There are a number of plugintypes in Moodle which are typically called by a specific Moodle subsystem.

Some of these are ''only'' called by that subsystem, for example plugins which are of the ''plagiarism'' plugintype should never be called directly, but are always invoked via the ''core_plagiarism'' subsystem.

Conversely, there maybe other plugintypes which can be called both via a subsystem, and in some other fashion. We are still determining whether any plugintypes currently fit this pattern.

If you are developing a plugin which belongs to a specific subsystem, then you will have to look at the relevant plugin in order to determine the exact contract.

Each subsystem will define a new interface which extends the ''\core_privacy\local\request\plugin\subsystem_provider'' interface and it is up to that subsystem to define how they will interact with those plugins.

The principles remain the same, but the exact implementation will differ depending upon requirements.

''plagiarism/detectorator/classes/privacy/provider.php''

<code php>
<?php
// …
namespace plagiarism_detectorator\privacy;

class provider implements
// This plugin does export personal user data.
\core_privacy\local\metadata\provider,

// This plugin is always linked against another activity module via the Plagiarism API.
\core_plagiarism\privacy\plugin_provider {
}
</code>

====Exporting data====

Any plugin which stores data must also export it.

To cater for this the privacy API includes a ''\core_privacy\local\request\content_writer'', which defines a set of functions to store different types of data.

Broadly speaking data is broken into the following types:

* Data - this is the object being described. For example the post content in a forum post;
* Related data - this is data related to the object being stored. For example, ratings of a forum post;
* Metadata - This is metadata about the main object. For example whether you are subscribed to a forum discussion;
* User preferences - this is data about a site-wide preference;
* Files - Any files that you are stored within Moodle on behalf of this plugin; and
* Custom files - For custom file formats - e.g. a calendar feed for calendar data. These should be used sparingly.

Each piece of data is stored against a specific Moodle ''context'', which will define how the data is structured within the exporter.
Data, and Related data only accept the ''stdClass'' object, whilst metadata should be stored as a set of key/value pairs which include a description.

In some cases the data being stored belongs within an implicit structure. For example, one forum has many forum discussions, which each have a number of forum posts. This structure is represented by an ''array'' referred to as a ''subcontext''.

The ''content_writer'' must ''always'' be called with a specific context, and can be called as follows:

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …
use \core_privacy\local\request\writer;

writer::with_context($context)
->export_data($subcontext, $post)
->export_area_files($subcontext, 'mod_forum', 'post', $post->id)
->export_metadata($subcontext, 'postread', (object) ['firstread' => $firstread], new \lang_string('privacy:export:post:postread'));
</code>

Any text field which supports Moodle files must also be rewritten:

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …
use \core_privacy\local\request\writer;

$post->message = writer::with_context($context)
->rewrite_pluginfile_urls($subcontext, 'mod_forum', 'post', $post->id, $post->message);

</code>

===Providing a way to delete user data===

Deleting user data is also implemented in the request interface. There are two methods that need to be created. The first one to remove all user data from a context, the other to remove user data for a specific user in a list of contexts.

====Delete for a context====

A context is given and all user data (for all users) is to be deleted from the plugin. This will be called when the retention period for the context has expired to adhere to the privacy by design requirement. Retention periods are set in the Data registry.

Note that this will be called for '''any''' context being expired, not only those the plugin holds data for (as returned by get_contexts_for_userid()), so you must carefully check the contexts given.

When expiring content for a high-level context such as a course context, the function will be called not only with the course context but also with each context within the course: each module context, each block context, etc. At each level you should only expire data specifically related to that exact context. For a module plugin, this generally means you should only take action for CONTEXT_MODULE contexts and only if they relate to an instance of your module, as shown in the following example. (In the rare case where your module also stores user data related to the course, and not just for a module instance, then you do need to implement CONTEXT_COURSE level contexts to expire that course-level data.)

<code php>
/**
* Delete all personal data for all users in the specified context.
*
* @param context $context Context to delete data from.
*/
public static function delete_data_for_all_users_in_context(\context $context) {
global $DB;

if ($context->contextlevel != CONTEXT_MODULE) {
return;
}

$cm = get_coursemodule_from_id('choice', $context->instanceid);
if (!$cm) {
return;
}

$DB->delete_records('choice_answers', ['choiceid' => $cm->instance]);
}
</code>

====Delete personal information for a specific user and context(s)====

An ''approved_contextlist'' is given and user data related to that user should either be completely deleted, or overwritten if a structure needs to be maintained. This will be called when a user has requested the right to be forgotten. All attempts should be made to delete this data where practical while still allowing the plugin to be used by other users.

''mod/choice/classes/privacy/provider.php''

<code php>
public static function delete_data_for_user(approved_contextlist $contextlist) {
global $DB;

if (empty($contextlist->count())) {
return;
}
$userid = $contextlist->get_user()->id;
foreach ($contextlist->get_contexts() as $context) {
$instanceid = $DB->get_field('course_modules', 'instance', ['id' => $context->instanceid], MUST_EXIST);
$DB->delete_records('choice_answers', ['choiceid' => $instanceid, 'userid' => $userid]);
}
}
</code>

====Delete personal information for several users in a specific context====

An ''approved_userlist'' is given and user data related to all users in the specified context should either be completely deleted, or overwritten if a structure needs to be maintained. This will be called when a user has requested the right to be forgotten when per-role overrides exist, or when performing a per-role expiry of a context. All attempts should be made to delete this data where practical while still allowing the plugin to be used by other users.

''mod/chat/classes/privacy/provider.php''

<code php>
/**
* Delete multiple users within a single context.
*
* @param approved_userlist $userlist The approved context and user information to delete information for.
*/
public static function delete_data_for_users(approved_userlist $userlist) {
global $DB;

$context = $userlist->get_context();
$cm = $DB->get_record('course_modules', ['id' => $context->instanceid]);
$chat = $DB->get_record('chat', ['id' => $cm->instance]);

list($userinsql, $userinparams) = $DB->get_in_or_equal($userlist->get_userids(), SQL_PARAMS_NAMED);
$params = array_merge(['chatid' => $chat->id], $userinparams);
$sql = "chatid = :chatid AND userid {$userinsql}";

$DB->delete_records_select('chat_messages', $sql, $params);
$DB->delete_records_select('chat_messages_current', $sql, $params);
$DB->delete_records_select('chat_users', $sql, $params);
}
</code>

==Difference between Moodle 3.3 and more recent versions==
Moodle 3.3 has a minimum requirement of php 5.6 and so type hinting and return type declarations are not supported in this version.
Consequently the privacy API for this version does not have these features.
==Common Questions==
===What to do if you have one plugin that supports multiple branches===
This is something that we have considered and we have put in place a polyfill. This gets around the restrictions of one version having type hinting and return type declarations while another does not.

====Example====
To use the polyfill include the legacy polyfill trait and create the necessary static methods but with an underscore (shown below).
<code php>
class provider implements
\core_privacy\local\metadata\provider,
\core_privacy\local\request\plugin\provider {

// This trait must be included.
use \core_privacy\local\legacy_polyfill;

// The required methods must be in this format starting with an underscore.
public static function _get_metadata(collection $collection) {
// Code for returning metadata goes here.
}
</code>

===What to do if your plugin must implement a subplugin or subsystem plugin provider===
For subplugins (e.g. assignsubmission, assignfeedback, quiz report, quiz access rules), or subsystems which have a plugintype relationship (portfolio, plagiarism, and others), they will also define their own legacy polyfill.

In this instance you will need to include the trait for both the core polyfill, and the provider polyfill as appropriate.
==== Example ====
<code php>
class provider implements
// This plugin has data and must therefore define the metadata provider in order to describe it.
\core_privacy\local\metadata\provider,

// This is a plagiarism plugin. It interacts with the plagiarism subsystem rather than with core.
\core_plagiarism\privacy\plagiarism_provider {

// This trait must be included to provide the relevant polyfill for the metadata provider.
use \core_privacy\local\legacy_polyfill;

// This trait must be included to provide the relevant polyfill for the plagirism provider.
use \core_plagiarism\privacy\plagiarism_provider\legacy_polyfill;

// The required methods must be in this format starting with an underscore.
public static function _get_metadata(collection $collection) {
// Code for returning metadata goes here.
}

// This is one of the polyfilled methods from the plagiarism provider.
public static function _export_plagiarism_user_data($userid, \context $context, array $subcontext, array $linkarray) {
// ...
}
</code>

== Tips for development ==

* While implementing the privacy API into your plugin, there are CLI scripts that can help you to test things on the fly. Just don't forget these are not supposed to replace proper unit tests. See [[Privacy API/Utilities]] for details.
* Inherit Unit tests from the <code php>core_privacy\tests\provider_testcase</code>, not <code php>advanced_testcase</code>. Advanced test case doesn't reset the Privacy content_writer between tests!

==See also==

* [[Subject Access Request FAQ]]
* [[:en:GDPR|GDPR]] in the user documentation
* [[Privacy API/Utilities]] provides CLI scripts that are helpful during development

[[Category:Privacy]]
[[Category:GDPR]]
[[Category:API]]

Privacy API

2018-11-30T00:44:54Z

Abgreeve: New interface code example for developers supporting 3.3

The [https://en.wikipedia.org/wiki/General_Data_Protection_Regulation General Data Protection Regulation] (GDPR) is an EU directive that looks at providing users with more control over their data and how it is processed. This regulation will come into effect on 25th of May 2018 and covers any citizen or permanent resident of the European Union. The directive will be respected by a number of other countries outside of the European Union.

To help institutions become compliant with this new regulation we are adding functionality to Moodle. This includes a number of components, amongst others these include a user’s right to:

* request information on the types of personal data held, the instances of that data, and the deletion policy for each;
* access all of their data; and
* be forgotten.

The compliance requirements also extend to installed plugins (including third party plugins). These need to also be able to report what information they store or process regarding users, and have the ability to provide and delete data for a user request.

This document describes the proposed API changes required for plugins which will allow a Moodle installation to become GDPR compliant.

Target Audience: The intended audience for this document is Moodle plugin developers, who are aiming to ensure their plugins are updated to comply with GDPR requirements coming into effect in the EU in May, 2018.

==Personal data in Moodle==

From the GDPR Spec, Article 4:

''‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;''

In Moodle, we need to consider two main types of personal data; information entered by the user and information stored about the user. The key difference being that information stored about the user will have come from a source other than the user themselves. Both types of data can be used to form a profile of the individual.

The most obvious clue to finding personal data entered by the user is the presence of a userid on a database field. Any data on the record (or linked records) pertaining to that user may be deemed personal data for that user, including things like timestamps and record identification numbers. Additionally, any free text field which allows the user to enter information must also be considered to be the personal data of that user.

Data stored about the user includes things like ratings and comments made on a student submission. These may have been made by an assessor or teacher, but are considered the personal data of the student, as they are considered a reflection of the user’s competency in the subject matter and can be used to form a profile of that individual.

The sections that follow outline what you need to do as a plugin developer to ensure any personal data is advertised and can be accessed and deleted according to the GDPR requirements.

==Background==

===Architecture overview===

[[File:MoodlePrivacyMetadataUML.png|thumb|UML diagram of the metadata part of the privacy subsystem]]
[[File:MoodlePrivacyRequestUML.png|thumb|UML diagram of the request providers part of the privacy subsystem]]

A new system for Privacy has been created within Moodle. This is broken down into several main parts and forms the ''core_privacy'' subsystem:

* Some metadata providers - a set of PHP interfaces to be implemented by components for that component to describe the kind of data that it stores, and the purpose for its storage;
* Some request providers - a set of PHP interfaces to be implemented by components to allow that component to act upon user requests such as the Right to be Forgotten, and a Subject Access Request; and
* A manager - a concrete class used to bridge components which implement the providers with tools which request their data.

All plugins will implement one metadata provider, and zero, one or two request providers.

The 'request' providers are responsible for several separate areas:

# Detecting in which Moodle contexts a specific user has any personal data;
# Exporting all personal data from each of those contexts for that user;
# Deleting all personal data from each of those contexts for that user;
# Detecting which users have personal data in a specific Moodle context;
# Deleting all personal data for each of those users in that context; and
# Deleting all personal data for all users in a specific context.

The export and delete phases use data from the detection phase, which allows for the possibility to exclude all data from certain contexts, as required.

Please refer to the inline phpdocs of the [https://github.com/moodle/moodle/blob/v3.5.0/privacy/classes/manager.php#L31 core_privacy::manager class] for detailed description of the interfaces, their hierarchy and meaning.

Please note that support for locating and removing multiple users in a single context was added in MDL-62560 for Moodle 3.6, 3.5.3, and 3.4.6.
This functionality has been added to allow support for removal of user data for users subject to speific role criterion, and to support expiry of the same data by role too.

===Implementing a provider===

All plugins will need to create a concrete class which implements the relevant metadata and request providers. The exact providers you need to implement will depend on what data you store, and the type of plugin. This is covered in more detail in the following sections of the document.

In order to do so:

# You must create a class called ''provider'' within the namespace ''\your_pluginname\privacy''.
# This class must be created at ''path/to/your/plugin/classes/privacy/provider.php''.
# You must have your class implement the relevant metadata and request interfaces.

==Plugins which do not store personal data==

Many Moodle plugins do not store any personal data. This is usually the case for plugins which just add functionality, or which display the data already stored elsewhere in Moodle.

Some examples of plugin types which might fit this criteria include themes, blocks, filters, editor plugins, etc.

Plugins which cause data to be stored elsewhere in Moodle (e.g. via a subsystem call) are considered to store data.

One examples of a plugin which does not store any data would be the Calendar month block which just displays a view of the user’s calendar. It does not store any data itself.

An example of a plugin which must not use the null provider is the Comments block. The comments block is responsible for data subsequently being stored within Moodle. Although the block doesn’t store anything itself, it interacts with the comments subsystem and is the only component which knows how that data maps to a user.

===Implementation requirements===

In order to let Moodle know that you have audited your plugin, and that you do not store any personal user data, you must implement the ''\core_privacy\local\metadata\null_provider'' interface in your plugin’s provider.

These null providers can only be implemented where a plugin has:

* no external links (e.g. sends data to an external service like an LTI provider, repository plugin which you can search on)
* no database tables which store user data (including IP addresses)
* no user preferences

The ''null_provider'' requires you to define one function ''get_reason()'' which returns the language string identifier within your component.

====Example====

''blocks/calendar_month/classes/privacy/provider.php''

<code php>
<?php
// …

namespace block_calendar_month\privacy;

class provider implements
// This plugin does not store any personal user data.
\core_privacy\local\metadata\null_provider {

/**
* Get the language string identifier with the component's language
* file to explain why this plugin stores no data.
*
* @return string
*/
public static function get_reason() : string {
return 'privacy:metadata';
}
}
</code>

''blocks/calendar_month/lang/en/block_calendar_month.php''

<code php>
<?php
// …

...
$string['privacy:metadata'] = 'The Calendar block only displays existing calendar data.';
...
</code>

That’s it. Congratulations, your plugin now implements the Privacy API.

==Plugins which store personal data==

Many Moodle plugins do store some form of personal data.

In some cases this will be stored within database tables in your plugin, and in other cases this will be in one of Moodle’s core subsystems - for example your plugin may store files, ratings, comments, or tags.

Plugins which do store data will need to:

* Describe the type of data that they store;
* Provide a way to export that data; and
* Provide a way to delete that data.

Data is described via a ''metadata'' provider, and it is both exported and deleted via an implementation of a ''request'' provider.

These are both explained in the sections below.

===Describing the type of data you store===

In order to describe the type of data that you store, you must implement the ''\core_privacy\local\metadata\provider'' interface.

This interfaces requires that you define one function: ''get_metadata''.

There are several types of item to describe the data that you store. These are for:

* Items in the Moodle database;
* Items stored by you in a Moodle subsystem - for example files, and ratings; and
* User preferences stored site-wide within Moodle for your plugin

Note: All fields should include a description from a language string within your plugin.

====Example====

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …

namespace mod_forum\privacy;
use core_privacy\local\metadata\collection;

class provider implements
// This plugin does store personal user data.
\core_privacy\local\metadata\provider {

public static function get_metadata(collection $collection) : collection {

// Here you will add more items into the collection.

return $collection;
}
}
</code>

====Indicating that you store content in a Moodle subsystem====

Many plugins will use one of the core Moodle subsystems to store data.

As a plugin developer we do not expect you to describe those subsystems in detail, but we do need to know that you use them and to know what you use them for.

You can indicate this by calling the ''add_subsystem_link()'' method on the ''collection''.

=====Relevant subsystems=====

You are likely to need to indicate use of the following subsystems that store user data:

* Ratings (if users are allowed to rate items within your plugin)
* Tags (if users can tag items within your plugin)
* Comments (if users can make comments on items in your plugin)
* Questions (if the plugin uses core question types)
* Filesystem (if users can attach files to items within your plugin)
* ...?

Some subsystems which store user data do not need to be listed:

* (TBC - how about global search? Nothing lists it that I could see.)

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_subsystem_link(
'core_files',
[],
'privacy:metadata:core_files'
);

return $collection;
}
</code>

''mod/forum/lang/en/forum.php''

<code php>
<?php

$string['privacy:metadata:core_files'] = 'The forum stores files which have been uploaded by the user to form part of a forum post.';
</code>

====Describing data stored in database tables====

Most Moodle plugins will store some form of user data in their own database tables.

As a plugin developer you will need to describe each database table, and each field which includes user data.

It is a matter of judgement which fields contain user data and which don't. Anything entered by, or directly about, the user probably counts as user data but it may be useful to include additional fields that explain the context of the data.

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_database_table(
'forum_discussion_subs',
[
'userid' => 'privacy:metadata:forum_discussion_subs:userid',
'discussionid' => 'privacy:metadata:forum_discussion_subs:discussionid',
'preference' => 'privacy:metadata:forum_discussion_subs:preference',

],
'privacy:metadata:forum_discussion_subs'
);

return $collection;
}
</code>

''mod/forum/lang/en/forum.php''

<code php>
<?php

$string['privacy:metadata:forum_discussion_subs'] = 'Information about the subscriptions to individual forum discussions. This includes when a user has chosen to subscribe to a discussion, or to unsubscribe from one where they would otherwise be subscribed.';
$string['privacy:metadata:forum_discussion_subs:userid'] = 'The ID of the user with this subscription preference.';
$string['privacy:metadata:forum_discussion_subs:discussionid'] = 'The ID of the discussion that was subscribed to.';
$string['privacy:metadata:forum_discussion_subs:preference'] = 'The start time of the subscription.';
</code>

====Indicating that you store site-wide user preferences====

Many plugins will include one or more user preferences. Unfortunately this is one of Moodle’s older components and many of the values stored are not pure user preferences. Each plugin should be aware of how it handles its own preferences and is best placed to determine whether they are site-wide preferences, or per-instance preferences.

Whilst most of these will have a fixed name (e.g. ''filepicker_recentrepository''), some will include a variable of some kind (e.g. ''tool_usertours_tour_completion_time_2''). Only the general name (in this case "tool_usertours_tour_completion_time_") needs to be indicated, rather than one copy for each possible value of the variable.

Also, these should only be ''site-wide'' user preferences which do not belong to a specific Moodle context.

In the above examples:

* Preference ''filepicker_recentrepository'' belongs to the file subsystem, and is a site-wide preference affecting the user anywhere that they view the filepicker.
* Preference ''tool_usertours_tour_completion_time_2'' belongs to user tours. User tours are a site-wide feature which can affect many parts of Moodle and cross multiple contexts.

In some cases a value may be stored in the preferences table but is known to belong to a specific context within Moodle. In these cases they should be stored as metadata against that context rather than as a site-wide user preference.

You can indicate this by calling the ''add_user_preference()'' method on the ''collection''.

Any plugin providing user preferences must also implement the ''\core_privacy\local\request\preference_provider''.

=====Example=====

''admin/tool/usertours/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_user_preference('tool_usertours_tour_completion_time',
'privacy:metadata:preference:tool_usertours_tour_completion_time');

return $collection;
}
</code>

''admin/tool/usertours/lang/en/tool_usertours.php''

<code php>
<?php

$string['privacy:metadata:tool_usertours_tour_completion_time'] = 'The time that a specific user tour was last completed by a user.';
</code>

====Indicating that you export data to an external location====

Many plugins will interact with external systems - for example cloud-based services. Often this external location is configurable within the plugin either at the site or the instance level.

As a plugin developer you will need to describe each ''type'' of target destination, alongside a list of each exported field which includes user data.
The ''actual'' destination does not need to be described as this can change based on configuration.

You can indicate this by calling the ''add_external_location_link()'' method on the collection.

=====Example=====

''mod/lti/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_external_location_link('lti_client', [
'userid' => 'privacy:metadata:lti_client:userid',
'fullname' => 'privacy:metadata:lti_client:fullname',
], 'privacy:metadata:lti_client');

return $collection;
}
</code>

''mod/lti/lang/en/lti.php''

<code php>
<?php

$string['privacy:metadata:lti_client'] = 'In order to integrate with a remote LTI service, user data needs to be exchanged with that service.';
$string['privacy:metadata:lti_client:userid'] = 'The userid is sent from Moodle to allow you to access your data on the remote system.';
$string['privacy:metadata:lti_client:fullname'] = 'Your full name is sent to the remote system to allow a better user experience.';
</code>

===Providing a way to export user data===

In order to export the user data that you store, you must implement the relevant request provider.

We have named these request providers because they are called in response to a specific request from a user to access their information, however they also deal with the removal of user data following it's expiry.

There are several different types of request provider, and you may need to implement several of these, depending on the type and nature of your plugin.

Broadly speaking plugins will fit into one of the following categories:

* Plugins which are a subplugin of another plugin. Examples include ''assignsubmission'', ''atto'', and ''datafield'';
* Plugins which are typically called by a Moodle subsystem. Examples include ''qtype'', and ''profilefield'';
* All other plugins which store data.

Most plugins will fit into this final category, whilst other plugins may fall into several categories.
Plugins which ''define'' a subplugin will also be responsible for collecting this data from their subplugins.

A final category exists - plugins which store user preferences. In some cases this may be the ''only'' provider implemented.

====Standard plugins which store data====

A majority of Moodle plugins will fit into this category and will be required to implement the ''\core_privacy\local\request\plugin\provider'' interface. This interface requires that you define four functions (the first two of which are dealt with in this section):

* ''get_contexts_for_userid'' - to explain where data is held within Moodle for your plugin; and
* ''export_user_data'' - to export a user’s personal data from your plugin.
* ''delete_data_for_all_users_in_context'' - to delete all data for all users in the specified context.
* ''delete_data_for_user'' - to delete all user data for the specified user, in the specified contexts.

These APIs make use of the Moodle ''context'' system to hierarchically store this data.

In addition to these requirements, since Moodle 3.4.6, 3.5.3, any plugin which implements the plugin provider interface must also implement the ''\core_privacy\local\request\core_userlist_provider'' provider and implement functions:

* ''get_users_in_context'' - to locate the users who hold any personal data in a specific context; and
* ''delete_data_for_users'' - to delete data for multiple users in the specified context.

A polyfill has not been provided for this new interface, but we recognise that developers who are maintaining older versions (Moodle 3.3) will hit problems with this new interface not existing. We recommend doing something similar to the following example.
<code php>
<?php

namespace assignsubmission_example\privacy;

if (class_exists('\core_privacy\local\request\userlist')) {
interface my_userlist extends \core_privacy\local\request\userlist{}
} else {
interface my_userlist {};
}

class provider implements my_userlist {

/**
* Get the list of users who have data within a context.
*
* @param userlist $userlist The userlist containing the list of users who have data in this context/plugin combination.
*/
public static function get_users_in_context(userlist $userlist) {

}

/**
* Delete multiple users within a single context.
*
* @param approved_userlist $userlist The approved context and user information to delete information for.
*/
public static function delete_data_for_users(approved_userlist $userlist) {

}

}
</code>

=====Retrieving the list of contexts=====

You are required to return the list of contexts for which the plugin stores data about the user. These are the standard Moodle contexts - CONTEXT_COURSE, CONTEXT_USER, CONTEXT_MODULE and so on. In many cases the link between the module type and the context is self-evident (e.g. activity modules). In some cases it may be less so. For example, an enrolment plugin (that stores user data, which most don't) would link to course context (users enrol in courses). Other types of plugins may be less obvious but you need to pick something. One way might to consider what context you would use when checking role capabilities. Consider that this will be used to structure the exported data and define what data is deleted when a context is expired.

Contexts are retrieved using the ''get_contexts_for_userid'' function which takes the ID of the user being fetched, and returns a list of contexts in which the user has any data.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {}
</code>

The function returns a ''\core_privacy\local\request\contextlist'' which is used to keep a set of contexts together in a fixed fashion.

Because a Subject Access Request covers ''every'' piece of data that is held for a user within Moodle, efficiency and performance is highly important. As a result, contexts are added to the ''contextlist'' by defining one or more SQL queries which return just the contextid. Multiple SQL queries can be added as required.

Many plugins will interact with specific subsystems and store data within them.
These subsystems will also provide a way in which to link the data that you have stored with your own database tables.
At present these are still a work in progress and only the ''core_ratings'' subsystem includes this.

======Basic example======

The following example simply fetches the contextid for all forums where a user has a single discussion (note: this is an incomplete example):

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {
$contextlist = new \core_privacy\local\request\contextlist();

$sql = "SELECT c.id
FROM {context} c
INNER JOIN {course_modules} cm ON cm.id = c.instanceid AND c.contextlevel = :contextlevel
INNER JOIN {modules} m ON m.id = cm.module AND m.name = :modname
INNER JOIN {forum} f ON f.id = cm.instance
LEFT JOIN {forum_discussions} d ON d.forum = f.id
WHERE (
d.userid = :discussionuserid
)
";

$params = [
'modname' => 'forum',
'contextlevel' => CONTEXT_MODULE,
'discussionuserid' => $userid,
];

$contextlist->add_from_sql($sql, $params);

return $contextlist;
}
</code>

======More complete example======

The following example includes a link to core_rating.
It will find any forum, forum discussion, or forum post where the user has any data, including:

* Per-forum digest preferences;
* Per-forum subscription preferences;
* Per-forum read tracking preferences;
* Per-discussion subscription preferences;
* Per-post read data (if a user has read a post or not); and
* Per-post rating data.

In the case of the rating data, this will include any post where the user has rated the post of another user.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {
$ratingsql = \core_rating\privacy\provider::get_sql_join('rat', 'mod_forum', 'post', 'p.id', $userid);
// Fetch all forum discussions, and forum posts.
$sql = "SELECT c.id
FROM {context} c
INNER JOIN {course_modules} cm ON cm.id = c.instanceid AND c.contextlevel = :contextlevel
INNER JOIN {modules} m ON m.id = cm.module AND m.name = :modname
INNER JOIN {forum} f ON f.id = cm.instance
LEFT JOIN {forum_discussions} d ON d.forum = f.id
LEFT JOIN {forum_posts} p ON p.discussion = d.id
LEFT JOIN {forum_digests} dig ON dig.forum = f.id
LEFT JOIN {forum_subscriptions} sub ON sub.forum = f.id
LEFT JOIN {forum_track_prefs} pref ON pref.forumid = f.id
LEFT JOIN {forum_read} hasread ON hasread.forumid = f.id
LEFT JOIN {forum_discussion_subs} dsub ON dsub.forum = f.id
{$ratingsql->join}
WHERE (
p.userid = :postuserid OR
d.userid = :discussionuserid OR
dig.userid = :digestuserid OR
sub.userid = :subuserid OR
pref.userid = :prefuserid OR
hasread.userid = :hasreaduserid OR
dsub.userid = :dsubuserid OR
{$ratingsql->userwhere}
)
";

$params = [
'modname' => 'forum',
'contextlevel' => CONTEXT_MODULE,
'postuserid' => $userid,
'discussionuserid' => $userid,
'digestuserid' => $userid,
'subuserid' => $userid,
'prefuserid' => $userid,
'hasreaduserid' => $userid,
'dsubuserid' => $userid,
];
$params += $ratingsql->params;

$contextlist = new \core_privacy\local\request\contextlist();
$contextlist->add_from_sql($sql, $params);

return $contextlist;

}
</code>

=====Retrieving the users in a context=====

You are required to return the list of users holding personal data in a context for which the plugin stores data about the user.
This method is very similar to the ''get_contexts_for_userid'' function but has some important distinctions:

* It takes a ''userlist'' as an argument and does not require that you, as a developer, create it yourself;
* There is no need to return any value; and
* The argument for the ''userlist::add_from_sql'' are different to those for ''contextlist::add_from_sql'' (this is because we learnt some important lessons after the initial implementation).

<code php>
/**
* Get the list of users who have data within a context.
*
* @param userlist $userlist The userlist containing the list of users who have data in this context/plugin combination.
*/
public static function get_users_in_context(userlist $userlist) {}
</code>

======Basic example======

The following example simply fetches the userid for all users in a given forum context, who created a discussion or a post in that forum (note: this is an incomplete example):

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of users who have data within a context.
*
* @param userlist $userlist The userlist containing the list of users who have data in this context/plugin combination.
*/
public static function get_users_in_context(userlist $userlist) {

$context = $userlist->get_context();

if (!$context instanceof \context_module) {
return;
}

$params = [
'instanceid' => $context->instanceid,
'modulename' => 'forum',
];

// Discussion authors.
$sql = "SELECT d.userid
FROM {course_modules} cm
JOIN {modules} m ON m.id = cm.module AND m.name = :modulename
JOIN {forum} f ON f.id = cm.instance
JOIN {forum_discussions} d ON d.forum = f.id
WHERE cm.id = :instanceid";
$userlist->add_from_sql('userid', $sql, $params);

// Forum authors.
$sql = "SELECT p.userid
FROM {course_modules} cm
JOIN {modules} m ON m.id = cm.module AND m.name = :modulename
JOIN {forum} f ON f.id = cm.instance
JOIN {forum_discussions} d ON d.forum = f.id
JOIN {forum_posts} p ON d.id = p.discussion
WHERE cm.id = :instanceid";
$userlist->add_from_sql('userid', $sql, $params);

// ...
}
</code>

=====Exporting user data=====

After determining where in Moodle your plugin holds data about a user, the ''\core_privacy\manager'' will then ask your plugin to export all user data for a subset of those locations.

This is achieved through use of the ''export_user_data'' function which takes the list of approved contexts in a ''\core_privacy\local\request\approved_contextlist'' object.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Export all user data for the specified user, in the specified contexts, using the supplied exporter instance.
*
* @param approved_contextlist $contextlist The approved contexts to export information for.
*/
public static function export_user_data(approved_contextlist $contextlist) {}
</code>

The ''approved_contextlist'' includes both the user record, and a list of contexts, which can be retrieved by either processing it as an Iterator, or by calling ''get_contextids()'' or ''get_contexts()'' as required.

Data is exported using a ''\core_privacy\local\request\content_writer'', which is described in further detail below.

====Plugins which store user preferences====

Many plugins store a variety of user preferences, and must therefore export them.

Since user preferences are a site-wide preference, these are exported separately to other user data.
In some cases the only data present is user preference data, whilst in others there is a combination of user-provided data, and user preferences.

Storing of user preferences is achieved through implementation of the ''\core_privacy\local\request\user_preference_provider'' interface which defines one required function -- ''export_user_preferences''.

You need to provide a description of the value of the user preference. (This description is particularly useful in cases where the value might be, say, 3, but it actually means 'Alphabetical order'.) Most likely you can use an existing language string from your plugin.

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Export all user preferences for the plugin.
*
* @param int $userid The userid of the user whose data is to be exported.
*/
public static function export_user_preferences(int $userid) {
$markasreadonnotification = get_user_preference('markasreadonnotification', null, $userid);
if (null !== $markasreadonnotification) {
switch ($markasreadonnotification) {
case 0:
$markasreadonnotificationdescription = get_string('markasreadonnotificationno', 'mod_forum');
break;
case 1:
default:
$markasreadonnotificationdescription = get_string('markasreadonnotificationyes', 'mod_forum');
break;
}
writer::export_user_preference('mod_forum', 'markasreadonnotification', $markasreadonnotification, $markasreadonnotificationdescription);
}
}
</code>

==== Plugins which can have own subplugins ====

Many plugin types are also able to define their own subplugins and will need to define a contract between themselves and their subplugins in order to fetch their data.

This is required as the parent plugin and the child subplugin should be separate entities and the parent plugin must be able to function if one or more of its subplugins are uninstalled.

The parent plugin is responsible for defining the contract, and for interacting with its subplugins, though we intend to create helpers to make this easier.

The parent plugin should define a new interface for each type of subplugin that it defines. This interface should extend the ''\core_privacy\local\request\plugin\subplugin_provider'' interface.

===== When a parent plugin should and should not provide the interface for its subplugins =====

There can be cases when there is no point for a plugin to provide the "subplugin_provider" based interface, even if it has own subplugins. See the Atto or TinyMCE editors as real examples.

If the parent plugin has no data passed through to the subplugins, there is no benefit in defining a subplugin provider. For example, Atto subplugins are just used to enhance the functionality and they never receive anything like a context. Most of the time we need to define a subplugin provider, but in cases where there is no data passed from the plugin to its subplugins, there is no need to define the subplugin provider. If the subplugins still do store personal data that are not related to the parent plugin in any way, then subplugins should define their own standard provider.

Compare with something like mod_assign where the subplugins store data for the parent and that data is contextually relevant to the parent plugin. In those cases the subplugin stores data for the plugin and it only makes sense to do so in the context of its parent plugin.

=====Example=====

The following example defines the contract that assign submission subplugins may be required to implement.

The assignment module is responsible for returning the contexts of all assignments where a user has data, but in some cases it is unaware of all of those cases - for example if a Teacher comments on a student submission it may not be aware of these as the information about this interaction may not be stored within its own tables.

''mod/assign/privacy/assignsubmission_provider.php''

<code php>
<?php
// …

namespace mod_assign\privacy;
use \core_privacy\local\metadata\collection;

interface assignsubmission_provider extends
// This Interface defines a subplugin.
\core_privacy\local\request\plugin\subplugin_provider {

/**
* Get the SQL required to find all submission items where this user has had any involvements.
*
* @param int $userid The user to search.
* @return \stdClass Object containing the join, params, and where used to select a these records from the database.
*/
public static function get_items_with_user_interaction(int $userid) : \stdClass ;

/**
* Export all relevant user submissions information which match the combination of userid and attemptid.
*
* @param int $userid The user to search.
* @param \context $context The context to export this submission against.
* @param array $subcontext The subcontext within the context to export this information
* @param int $attid The id of the submission to export.
*/
public static function export_user_submissions(int $userid, \context $context, array $subcontext, int $attid) ;

}
</code>

====Plugins which are subplugins to another plugin====

If you are developing a sub-plugin of another plugin, then you will have to look at the relevant plugin in order to determine the exact contract.

Each subplugin type should define a new interface which extends the ''\core_privacy\local\request\plugin\subplugin_provider'' interface and it is up to the parent plugin to define how they will interact with their children.

The principles remain the same, but the exact implementation will differ depending upon requirements.

''mod/pluginname/classes/privacy/provider.php''

<code php>
<?php
// …
namespace assignsubmission\onlinetext;

class provider implements
// This plugin does store personal user data.
\core_privacy\local\metadata\provider,

// This plugin is a subplugin of assign and must meet that contract.
\mod_assign\privacy\assignsubmission_provider {
}
</code>

====Plugins which are typically called by a Moodle subsystem====

There are a number of plugintypes in Moodle which are typically called by a specific Moodle subsystem.

Some of these are ''only'' called by that subsystem, for example plugins which are of the ''plagiarism'' plugintype should never be called directly, but are always invoked via the ''core_plagiarism'' subsystem.

Conversely, there maybe other plugintypes which can be called both via a subsystem, and in some other fashion. We are still determining whether any plugintypes currently fit this pattern.

If you are developing a plugin which belongs to a specific subsystem, then you will have to look at the relevant plugin in order to determine the exact contract.

Each subsystem will define a new interface which extends the ''\core_privacy\local\request\plugin\subsystem_provider'' interface and it is up to that subsystem to define how they will interact with those plugins.

The principles remain the same, but the exact implementation will differ depending upon requirements.

''plagiarism/detectorator/classes/privacy/provider.php''

<code php>
<?php
// …
namespace plagiarism_detectorator\privacy;

class provider implements
// This plugin does export personal user data.
\core_privacy\local\metadata\provider,

// This plugin is always linked against another activity module via the Plagiarism API.
\core_plagiarism\privacy\plugin_provider {
}
</code>

====Exporting data====

Any plugin which stores data must also export it.

To cater for this the privacy API includes a ''\core_privacy\local\request\content_writer'', which defines a set of functions to store different types of data.

Broadly speaking data is broken into the following types:

* Data - this is the object being described. For example the post content in a forum post;
* Related data - this is data related to the object being stored. For example, ratings of a forum post;
* Metadata - This is metadata about the main object. For example whether you are subscribed to a forum discussion;
* User preferences - this is data about a site-wide preference;
* Files - Any files that you are stored within Moodle on behalf of this plugin; and
* Custom files - For custom file formats - e.g. a calendar feed for calendar data. These should be used sparingly.

Each piece of data is stored against a specific Moodle ''context'', which will define how the data is structured within the exporter.
Data, and Related data only accept the ''stdClass'' object, whilst metadata should be stored as a set of key/value pairs which include a description.

In some cases the data being stored belongs within an implicit structure. For example, one forum has many forum discussions, which each have a number of forum posts. This structure is represented by an ''array'' referred to as a ''subcontext''.

The ''content_writer'' must ''always'' be called with a specific context, and can be called as follows:

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …
use \core_privacy\local\request\writer;

writer::with_context($context)
->export_data($subcontext, $post)
->export_area_files($subcontext, 'mod_forum', 'post', $post->id)
->export_metadata($subcontext, 'postread', (object) ['firstread' => $firstread], new \lang_string('privacy:export:post:postread'));
</code>

Any text field which supports Moodle files must also be rewritten:

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …
use \core_privacy\local\request\writer;

$post->message = writer::with_context($context)
->rewrite_pluginfile_urls($subcontext, 'mod_forum', 'post', $post->id, $post->message);

</code>

===Providing a way to delete user data===

Deleting user data is also implemented in the request interface. There are two methods that need to be created. The first one to remove all user data from a context, the other to remove user data for a specific user in a list of contexts.

====Delete for a context====

A context is given and all user data (for all users) is to be deleted from the plugin. This will be called when the retention period for the context has expired to adhere to the privacy by design requirement. Retention periods are set in the Data registry.

Note that this will be called for '''any''' context being expired, not only those the plugin holds data for (as returned by get_contexts_for_userid()), so you must carefully check the contexts given.

When expiring content for a high-level context such as a course context, the function will be called not only with the course context but also with each context within the course: each module context, each block context, etc. At each level you should only expire data specifically related to that exact context. For a module plugin, this generally means you should only take action for CONTEXT_MODULE contexts and only if they relate to an instance of your module, as shown in the following example. (In the rare case where your module also stores user data related to the course, and not just for a module instance, then you do need to implement CONTEXT_COURSE level contexts to expire that course-level data.)

<code php>
/**
* Delete all personal data for all users in the specified context.
*
* @param context $context Context to delete data from.
*/
public static function delete_data_for_all_users_in_context(\context $context) {
global $DB;

if ($context->contextlevel != CONTEXT_MODULE) {
return;
}

$cm = get_coursemodule_from_id('choice', $context->instanceid);
if (!$cm) {
return;
}

$DB->delete_records('choice_answers', ['choiceid' => $cm->instance]);
}
</code>

====Delete personal information for a specific user and context(s)====

An ''approved_contextlist'' is given and user data related to that user should either be completely deleted, or overwritten if a structure needs to be maintained. This will be called when a user has requested the right to be forgotten. All attempts should be made to delete this data where practical while still allowing the plugin to be used by other users.

''mod/choice/classes/privacy/provider.php''

<code php>
public static function delete_data_for_user(approved_contextlist $contextlist) {
global $DB;

if (empty($contextlist->count())) {
return;
}
$userid = $contextlist->get_user()->id;
foreach ($contextlist->get_contexts() as $context) {
$instanceid = $DB->get_field('course_modules', 'instance', ['id' => $context->instanceid], MUST_EXIST);
$DB->delete_records('choice_answers', ['choiceid' => $instanceid, 'userid' => $userid]);
}
}
</code>

====Delete personal information for several users in a specific context====

An ''approved_userlist'' is given and user data related to all users in the specified context should either be completely deleted, or overwritten if a structure needs to be maintained. This will be called when a user has requested the right to be forgotten when per-role overrides exist, or when performing a per-role expiry of a context. All attempts should be made to delete this data where practical while still allowing the plugin to be used by other users.

''mod/chat/classes/privacy/provider.php''

<code php>
/**
* Delete multiple users within a single context.
*
* @param approved_userlist $userlist The approved context and user information to delete information for.
*/
public static function delete_data_for_users(approved_userlist $userlist) {
global $DB;

$context = $userlist->get_context();
$cm = $DB->get_record('course_modules', ['id' => $context->instanceid]);
$chat = $DB->get_record('chat', ['id' => $cm->instance]);

list($userinsql, $userinparams) = $DB->get_in_or_equal($userlist->get_userids(), SQL_PARAMS_NAMED);
$params = array_merge(['chatid' => $chat->id], $userinparams);
$sql = "chatid = :chatid AND userid {$userinsql}";

$DB->delete_records_select('chat_messages', $sql, $params);
$DB->delete_records_select('chat_messages_current', $sql, $params);
$DB->delete_records_select('chat_users', $sql, $params);
}
</code>

==Difference between Moodle 3.3 and more recent versions==
Moodle 3.3 has a minimum requirement of php 5.6 and so type hinting and return type declarations are not supported in this version.
Consequently the privacy API for this version does not have these features.
==Common Questions==
===What to do if you have one plugin that supports multiple branches===
This is something that we have considered and we have put in place a polyfill. This gets around the restrictions of one version having type hinting and return type declarations while another does not.

====Example====
To use the polyfill include the legacy polyfill trait and create the necessary static methods but with an underscore (shown below).
<code php>
class provider implements
\core_privacy\local\metadata\provider,
\core_privacy\local\request\plugin\provider {

// This trait must be included.
use \core_privacy\local\legacy_polyfill;

// The required methods must be in this format starting with an underscore.
public static function _get_metadata(collection $collection) {
// Code for returning metadata goes here.
}
</code>

===What to do if your plugin must implement a subplugin or subsystem plugin provider===
For subplugins (e.g. assignsubmission, assignfeedback, quiz report, quiz access rules), or subsystems which have a plugintype relationship (portfolio, plagiarism, and others), they will also define their own legacy polyfill.

In this instance you will need to include the trait for both the core polyfill, and the provider polyfill as appropriate.
==== Example ====
<code php>
class provider implements
// This plugin has data and must therefore define the metadata provider in order to describe it.
\core_privacy\local\metadata\provider,

// This is a plagiarism plugin. It interacts with the plagiarism subsystem rather than with core.
\core_plagiarism\privacy\plagiarism_provider {

// This trait must be included to provide the relevant polyfill for the metadata provider.
use \core_privacy\local\legacy_polyfill;

// This trait must be included to provide the relevant polyfill for the plagirism provider.
use \core_plagiarism\privacy\plagiarism_provider\legacy_polyfill;

// The required methods must be in this format starting with an underscore.
public static function _get_metadata(collection $collection) {
// Code for returning metadata goes here.
}

// This is one of the polyfilled methods from the plagiarism provider.
public static function _export_plagiarism_user_data($userid, \context $context, array $subcontext, array $linkarray) {
// ...
}
</code>

== Tips for development ==

* While implementing the privacy API into your plugin, there are CLI scripts that can help you to test things on the fly. Just don't forget these are not supposed to replace proper unit tests. See [[Privacy API/Utilities]] for details.
* Inherit Unit tests from the <code php>core_privacy\tests\provider_testcase</code>, not <code php>advanced_testcase</code>. Advanced test case doesn't reset the Privacy content_writer between tests!

==See also==

* [[Subject Access Request FAQ]]
* [[:en:GDPR|GDPR]] in the user documentation
* [[Privacy API/Utilities]] provides CLI scripts that are helpful during development

[[Category:Privacy]]
[[Category:GDPR]]
[[Category:API]]

Message API

2018-11-12T02:49:26Z

Abgreeve: Deprecation of using a stdClass for creating a message mentioned.

==What is this document?==

This document describes how to make use of the Moodle Messaging API to send messages to Moodle users.

If you are after a general introduction on using the Moodle Messaging system go to [[:en:Messaging|messaging user documentation]].

If you are looking for details of how the Messaging system's internal structure was implemented, go to [[Messaging 2.0]].

If you are looking for instructions on the implementation of a custom message processor (a component that receives messages sent to a user), go to [[Messaging custom components]].

If you are looking for instructions on sending messages programatically within Moodle then read on...

==Overview==

Moodle components have the ability to send messages to users via the Moodle messaging system. Any type of component, for example a plugin or block, can register as a message producer then send messages to users.

==File locations==

The Message API code is contained within lib/messagelib.php and is automatically included for you during page setup.

==Functions==

message_send() is the primary point of contact for the message API. Call it to send a message to a user. You can find a full description of the arguments that must be supplied at (link to phpdocs). There is also an example below.

==Message popup==
{{Moodle_2.9}}
A Javascript popup can be displayed through a link to invite a user to message another. In order to use this feature, you need to require the Javascript libraries using ''message_messenger_requirejs()'' and create a link with the attributes returned by ''message_messenger_sendmessage_link_params()''. More in the examples.

==Examples==

===How to register as a message producer===

The messages produced by a message provider is defined in the /db/messages.php file of a component. Below is code from the quiz module's messages.php file, shown as an example.
<code php>
defined('MOODLE_INTERNAL') || die();
$messageproviders = array (
// Notify teacher that a student has submitted a quiz attempt
'submission' => array (
'capability' => 'mod/quiz:emailnotifysubmission'
),
// Confirm a student's quiz attempt
'confirmation' => array (
'capability' => 'mod/quiz:emailconfirmsubmission'
)
);
</code>

The quiz can send two kinds of messages, quiz "submission" and "confirmation" notifications. Each message type is only available to users with the appropriate capability. Please note that the capability is checked at the system level context. Users who have this capability will have this message listed in their messaging preferences. You can omit the capability section if your message should be visible for all users. For example forum post notifications are available to all users.

<code php>
$messageproviders = array (
// Ordinary single forum posts
'posts' => array (
)
);
</code>

When displaying your message types in a user's messaging preferences it will use a string from your component's language file called "messageprovider:messagename". For example here are the relevant strings from the quiz's language file.
<code php>
$string['messageprovider:confirmation'] = 'Confirmation of your own quiz submissions';
$string['messageprovider:submission'] = 'Notification of quiz submissions';
</code>

Once your messages.php is complete you need to increase the version number of your component in its version.php. That will cause Moodle to check messages.php looking for new or changed message definitions. Log in as an admin and go to /admin/index.php (the Notifications page) to start the upgrade process.
===Setting defaults===
The default processor can be set using an element of the array
e.g.
<code php>
'mynotification' => [
'defaults' => [
'popup' => MESSAGE_PERMITTED + MESSAGE_DEFAULT_LOGGEDIN + MESSAGE_DEFAULT_LOGGEDOFF,
'email' => MESSAGE_PERMITTED
],
],
</code>
With that setting email will be permitted but disabled for each user by default. It can be turned on by each user through the preferences/notification preferences options (/message/notificationpreferences.php?userid=X)
The possible values are recorded in the lib.php file of messaging
<code php>
/**
* Define contants for messaging default settings population. For unambiguity of
* plugin developer intentions we use 4-bit value (LSB numbering):
* bit 0 - whether to send message when user is loggedin (MESSAGE_DEFAULT_LOGGEDIN)
* bit 1 - whether to send message when user is loggedoff (MESSAGE_DEFAULT_LOGGEDOFF)
* bit 2..3 - messaging permission (MESSAGE_DISALLOWED|MESSAGE_PERMITTED|MESSAGE_FORCED)
*
* MESSAGE_PERMITTED_MASK contains the mask we use to distinguish permission setting
*/
</code>
Note that if you change the values in message.php and then upgrade the plugin the values will not automatically be changed in the config_plugins table where they are stored.

===How to send a message===
{{Moodle_2.9}}
Here is example code showing you how to actually send a message. The example shows the construction of a object with specific properties, which is then passed to the message_send() function that uses the information to send a message.
<code php>
$message = new \core\message\message();
$message->component = 'moodle';
$message->name = 'instantmessage';
$message->userfrom = $USER;
$message->userto = $user;
$message->subject = 'message subject 1';
$message->fullmessage = 'message body';
$message->fullmessageformat = FORMAT_MARKDOWN;
$message->fullmessagehtml = 'message body';
$message->smallmessage = 'small message';
$message->notification = '0';
$message->contexturl = 'http://GalaxyFarFarAway.com';
$message->contexturlname = 'Context name';
$message->replyto = "random@example.com";
$content = array('*' => array('header' => ' test ', 'footer' => ' test ')); // Extra content for specific processor
$message->set_additional_content('email', $content);
$message->courseid = $course->id; // This is required in recent versions, use it from 3.2 on https://tracker.moodle.org/browse/MDL-47162

// Create a file instance.
$usercontext = context_user::instance($user->id);
$file = new stdClass;
$file->contextid = $usercontext->id;
$file->component = 'user';
$file->filearea = 'private';
$file->itemid = 0;
$file->filepath = '/';
$file->filename = '1.txt';
$file->source = 'test';

$fs = get_file_storage();
$file = $fs->create_file_from_string($file, 'file1 content');
$message->attachment = $file;

$messageid = message_send($message);
</code>

Before 2.9 message data used to be a stdClass object as shown below (This formation of a message will no longer work as of Moodle 3.6. Only a message object will be accepted):-

<code php>
$message = new stdClass();
$message->component = 'mod_quiz'; //your component name
$message->name = 'submission'; //this is the message name from messages.php
$message->userfrom = $USER;
$message->userto = $touser;
$message->subject = $subject;
$message->fullmessage = $message;
$message->fullmessageformat = FORMAT_PLAIN;
$message->fullmessagehtml = '';
$message->smallmessage = '';
$message->notification = 1; //this is only set to 0 for personal messages between users
message_send($message);
</code>

===How to set-up the message popup===

Here is example code showing you how to set-up the Javascript popup link.
<code php>
require_once('message/lib.php');
$userid = 2;
$userto = $DB->get_record('user', array('id' => $userid));

message_messenger_requirejs();
$url = new moodle_url('message/index.php', array('id' => $userto->id));
$attributes = message_messenger_sendmessage_link_params($userto);
echo html_writer::link($url, 'Send a message', $attributes);
</code>

==See also==
* [[Core APIs]]

[[Category:API]]
[[Category:Tutorial]]
[[Category:Plugins]]
[[Category:Messaging]]

Privacy API

2018-04-10T08:02:13Z

Abgreeve: /* Example - fix up for my bad English */

The [https://en.wikipedia.org/wiki/General_Data_Protection_Regulation General Data Protection Regulation] (GDPR) is an EU directive that looks at providing users with more control over their data and how it is processed. This regulation will come into effect on 25th of May 2018 and covers any citizen or permanent resident of the European Union. The directive will be respected by a number of other countries outside of the European Union.

To help institutions become compliant with this new regulation we are adding functionality to Moodle. This includes a number of components, amongst others these include a user’s right to:

* request information on the types of personal data held, the instances of that data, and the deletion policy for each;
* access all of their data; and
* be forgotten.

The compliance requirements also extend to installed plugins (including third party plugins). These need to also be able to report what information they store or process regarding users, and have the ability to provide and delete data for a user request.

This document describes the proposed API changes required for plugins which will allow a Moodle installation to become GDPR compliant.

Target Audience: The intended audience for this document is Moodle plugin developers, who are aiming to ensure their plugins are updated to comply with GDPR requirements coming into effect in the EU in May, 2018.

==Personal data in Moodle==

From the GDPR Spec, Article 4:

''‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;''

In Moodle, we need to consider two main types of personal data; information entered by the user and information stored about the user. The key difference being that information stored about the user will have come from a source other than the user themselves. Both types of data can be used to form a profile of the individual.

The most obvious clue to finding personal data entered by the user is the presence of a userid on a database field. Any data on the record (or linked records) pertaining to that user may be deemed personal data for that user, including things like timestamps and record identification numbers. Additionally, any free text field which allows the user to enter information must also be considered to be the personal data of that user.

Data stored about the user includes things like ratings and comments made on a student submission. These may have been made by an assessor or teacher, but are considered the personal data of the student, as they are considered a reflection of the user’s competency in the subject matter and can be used to form a profile of that individual.

The sections that follow outline what you need to do as a plugin developer to ensure any personal data is advertised and can be accessed and deleted according to the GDPR requirements.

==Background==

===Architecture overview===

A new system for Privacy has been created within Moodle. This is broken down into several main parts and forms the ''core_privacy'' subsystem:

* Some metadata providers - a set of PHP interfaces to be implemented by components for that component to describe the kind of data that it stores, and the purpose for its storage;
* Some request providers - a set of PHP interfaces to be implemented by components to allow that component to act upon user requests such as the Right to be Forgotten, and a Subject Access Request; and
* A manager - a concrete class used to bridge components which implement the providers with tools which request their data.

All plugins will implement one metadata provider, and zero, one or two request providers.

The fetching of data is broken into two separate steps:

# Detecting in which Moodle contexts the user has any data; and
# Exporting all data from each of those contexts.

This has been broken into two steps to later allow administrators to exclude certain contexts from an export - e.g. for courses currently in progress.

A third component will later be added to facilitate the deletion of data within these contexts which will help to satisfy the Right to be Forgotten. This will also use the first step.

===Implementing a provider===

All plugins will need to create a concrete class which implements the relevant metadata and request providers. The exact providers you need to implement will depend on what data you store, and the type of plugin. This is covered in more detail in the following sections of the document.

In order to do so:

# You must create a class called ''provider'' within the namespace ''\your_pluginname\privacy''.
# This class must be created at ''path/to/your/plugin/classes/privacy/provider.php''.
# You must have your class implement the relevant metadata and request interfaces.

==Plugins which do not store personal data==

Many Moodle plugins do not store any personal data. This is usually the case for plugins which just add functionality, or which display the data already stored elsewhere in Moodle.

Some examples of plugin types which might fit this criteria include themes, blocks, filters, editor plugins, etc.

Plugins which cause data to be stored elsewhere in Moodle (e.g. via a subsystem call) are considered to store data.

One examples of a plugin which does not store any data would be the Calendar month block which just displays a view of the user’s calendar. It does not store any data itself.

An example of a plugin which must not use the null provider is the Comments block. The comments block is responsible for data subsequently being stored within Moodle. Although the block doesn’t store anything itself, it interacts with the comments subsystem and is the only component which knows how that data maps to a user.

===Implementation requirements===

In order to let Moodle know that you have audited your plugin, and that you do not store any personal user data, you must implement the ''\core_privacy\local\metadata\null_provider'' interface in your plugin’s provider.

The ''null_provider'' requires you to define one function ''get_reason()'' which returns the language string identifier within your component.

====Example====

''block/calendar_month/classes/privacy/provider.php''

<code php>
<?php
// …

namespace block_calendar_month\privacy;

class provider implements
// This plugin does not store any personal user data.
\core_privacy\local\metadata\null_provider {

/**
* Get the language string identifier with the component's language
* file to explain why this plugin stores no data.
*
* @return string
*/
public static function get_reason() : string {
return 'privacy:null_reason';
}
}
</code>

''block/calendar_month/lang/en/block_calendar_month.php''

<code php>
<?php

$string['privacy:null_reason'] = 'The calendar month block displays information from the Calendar, but does not effect or store any data itself. All changes are made via the Calendar.';
</code>

That’s it. Congratulations, your plugin now implements the Privacy API.

==Plugins which store personal data==

Many Moodle plugins do store some form of personal data.

In some cases this will be stored within database tables in your plugin, and in other cases this will be in one of Moodle’s core subsystems - for example your plugin may store files, ratings, comments, or tags.

Plugins which do store data will need to:

* Describe the type of data that they store;
* Provide a way to export that data; and
* Provide a way to delete that data.

Data is described via a ''metadata'' provider, and it is both exported and deleted via an implementation of a ''request'' provider.

These are both explained in the sections below.

===Describing the type of data you store===

In order to describe the type of data that you store, you must implement the ''\core_privacy\local\metadata\provider'' interface.

This interfaces requires that you define one function: ''get_metadata''.

There are several types of item to describe the data that you store. These are for:

* Items in the Moodle database;
* Items stored by you in a Moodle subsystem - for example files, and ratings; and
* User preferences stored site-wide within Moodle for your plugin

Note: All fields should include a description from a language string within your plugin.

====Example====

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …

namespace mod_forum\privacy;
use \core_privacy\local\metadata\collection;

class provider implements
// This plugin does store personal user data.
\core_privacy\local\metadata\provider {
public static function get_metadata(collection $collection) : collection {
return $collection;
}
}
</code>

====Indicating that you store content in a Moodle subsystem====

Many plugins will use one of the core Moodle subsystems to store data.

As a plugin developer we do not expect you to describe those subsystems in detail, but we do need to know that you use them and to know what you use them for.

You can indicate this by calling the ''link_subsystem()'' method on the ''collection''.

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->link_subsystem(
'core_files',
'privacy:metadata:core_files'
);

return $collection;
}
</code>

''mod/forum/lang/en/forum.php''

<code php>
<?php

$string['privacy:metadata:core_files'] = 'The forum stores files which have been uploaded by the user to form part of a forum post.';
</code>

====Describing data stored in database tables====

Most Moodle plugins will store some form of user data in their own database tables.

As a plugin developer you will need to describe each database table, and each field which includes user data.

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_database_table(
'forum_discussion_subs',
[
'userid' => 'privacy:metadata:forum_discussion_subs:userid',
'discussionid' => 'privacy:metadata:forum_discussion_subs:discussionid',
'preference' => 'privacy:metadata:forum_discussion_subs:preference',

],
'privacy:metadata:forum_discussion_subs'
);

return $collection;
}
</code>

''mod/forum/lang/en/forum.php''

<code php>
<?php

$string['privacy:metadata:forum_discussion_subs'] = 'Information about the subscriptions to individual forum discussions. This includes when a user has chosen to subscribe to a discussion, or to unsubscribe from one where they would otherwise be subscribed.';
$string['privacy:metadata:forum_discussion_subs:userid'] = 'The ID of the user with this subscription preference.';
$string['privacy:metadata:forum_discussion_subs:discussionid'] = 'The ID of the discussion that was subscribed to.';
$string['privacy:metadata:forum_discussion_subs:preference'] = 'The start time of the subscription.';
</code>

====Indicating that you store site-wide user preferences====

Many plugins will include one or more user preferences. Unfortunately this is one of Moodle’s older components and many of the values stored are not pure user preferences. Each plugin should be aware of how it handles its own preferences and is best placed to determine whether they are site-wide preferences, or per-instance preferences.

Whilst most of these will have a fixed name (e.g. ''filepicker_recentrepository''), some will include a variable of some kind (e.g. ''tool_usertours_tour_completion_time_2''). Only the general name needs to be indicated rather than one copy for each preference.

Also, these should only be ''site-wide'' user preferences which do not belong to a specific Moodle context.

In the above examples:

* Preference ''filepicker_recentrepository'' belongs to the file subsystem, and is a site-wide preference affecting the user anywhere that they view the filepicker.
* Preference ''tool_usertours_tour_completion_time_2'' belongs to user tours. User tours are a site-wide feature which can affect many parts of Moodle and cross multiple contexts.

In some cases a value may be stored in the preferences table but is known to belong to a specific context within Moodle. In these cases they should be stored as metadata against that context rather than as a site-wide user preference.

You can indicate this by calling the ''add_user_preference()'' method on the ''collection''.

Any plugin providing user preferences must also implement the ''\core_privacy\local\request\preference_provider''.

=====Example=====

''admin/tool/usertours/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_user_preference('tool_usertours_tour_completion_time,
'privacy:metadata:preference:tool_usertours_tour_completion_time');

return $collection;
}
</code>

''admin/tool/usertours/lang/en/tool_usertours.php''

<code php>
<?php

$string['privacy:metadata:tool_usertours_tour_completion_time'] = 'The time that a specific user tour was last completed by a user.';
</code>

====Indicating that you export data to an external location====

Many plugins will interact with external systems - for example cloud-based services. Often this external location is configurable within the plugin either at the site or the instance level.

As a plugin developer you will need to describe each ''type'' of target destination, alongside a list of each exported field which includes user data.
The ''actual'' destination does not need to be described as this can change based on configuration.

You can indicate this by calling the ''link_external_location()'' method on the collection.

=====Example=====

''mod/lti/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->link_external_location('lti_client', [
'userid' => 'privacy:metadata:lti_client:userid',
'fullname' => 'privacy:metadata:lti_client:fullname',
], 'privacy:metadata:lti_client');

return $collection;
}
</code>

''mod/lti/lang/en/lti.php''

<code php>
<?php

$string['privacy:metadata:lti_client'] = 'In order to integrate with a remote LTI service, user data needs to be exchanged with that service.';
$string['privacy:metadata:lti_client:userid'] = 'The userid is sent from Moodle to allow you to access your data on the remote system.';
$string['privacy:metadata:lti_client:fullname'] = 'Your full name is sent to the remote system to allow a better user experience.';
</code>

===Providing a way to export user data===

In order to export the user data that you store, you must implement the relevant request provider.

We have named these request providers because they are called in response to a specific request from a user to access their information.

There are several different types of request provider, and you may need to implement several of these, depending on the type and nature of your plugin.

Broadly speaking plugins will fit into one of the following categories:

* Plugins which are a subplugin of another plugin. Examples include ''assignsubmission'', ''atto'', and ''datafield'';
* Plugins which are typically called by a Moodle subsystem. Examples include ''qtype'', and ''profilefield'';
* All other plugins which store data.

Most plugins will fit into this final category, whilst other plugins may fall into several categories.
Plugins which ''define'' a subplugin will also be responsible for collecting this data from their subplugins.

A final category exists - plugins which store user preferences. In some cases this may be the ''only'' provider implemented.

====Standard plugins which store data====

A majority of Moodle plugins will fit into this category and will be required to implement the ''\core_privacy\local\request\plugin\provider'' interface. This interface requires that you define two functions:

* ''get_contexts_for_userid'' - to explain where data is held within Moodle for your plugin; and
* ''export_user_data'' - to export a user’s personal data from your plugin.

These APIs make use of the Moodle ''context'' system to hierarchically store this data.

====Retrieving the list of contexts====

Contexts are retrieved using the ''get_contexts_for_userid'' function which takes the ID of the user being fetched, and returns a list of contexts in which the user has any data.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {}
</code>

The function returns a ''\core_privacy\local\request\contextlist'' which is used to keep a set of contexts together in a fixed fashion.

Because a Subject Access Request covers ''every'' piece of data that is held for a user within Moodle, efficiency and performance is highly important. As a result, contexts are added to the ''contextlist'' by defining one or more SQL queries which return just the contextid. Multiple SQL queries can be added as required.

Many plugins will interact with specific subsystems and store data within them.
These subsystems will also provide a way in which to link the data that you have stored with your own database tables.
At present these are still a work in progress and only the ''core_ratings'' subsystem includes this.

=====Basic example=====

The following example simply fetches the contextid for all forums where a user has a single discussion (note: this is an incomplete example):

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {
$contextlist = new \core_privacy\local\request\contextlist();

$sql = "SELECT c.id
FROM {context} c
INNER JOIN {course_modules} cm ON cm.id = c.instanceid AND c.contextlevel = :contextlevel
INNER JOIN {modules} m ON m.id = cm.module AND m.name = :modname
INNER JOIN {forum} f ON f.id = cm.instance
LEFT JOIN {forum_discussions} d ON d.forum = f.id
WHERE (
d.userid = :discussionuserid
)
";

$params = [
'modname' => 'forum',
'contextlevel' => CONTEXT_MODULE,
'discussionuserid' => $userid,
];

$contextlist->add_from_sql($sql, $params);
}
</code>

=====More complete example=====

The following example includes a link to core_rating.
It will find any forum, forum discussion, or forum post where the user has any data, including:

* Per-forum digest preferences;
* Per-forum subscription preferences;
* Per-forum read tracking preferences;
* Per-discussion subscription preferences;
* Per-post read data (if a user has read a post or not); and
* Per-post rating data.

In the case of the rating data, this will include any post where the user has rated the post of another user.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {
$ratingsql = \core_rating\privacy\provider::get_sql_join('rat', 'mod_forum', 'post', 'p.id', $userid);
// Fetch all forum discussions, and forum posts.
$sql = "SELECT c.id
FROM {context} c
INNER JOIN {course_modules} cm ON cm.id = c.instanceid AND c.contextlevel = :contextlevel
INNER JOIN {modules} m ON m.id = cm.module AND m.name = :modname
INNER JOIN {forum} f ON f.id = cm.instance
LEFT JOIN {forum_discussions} d ON d.forum = f.id
LEFT JOIN {forum_posts} p ON p.discussion = d.id
LEFT JOIN {forum_digests} dig ON dig.forum = f.id
LEFT JOIN {forum_subscriptions} sub ON sub.forum = f.id
LEFT JOIN {forum_track_prefs} pref ON pref.forumid = f.id
LEFT JOIN {forum_read} hasread ON hasread.forumid = f.id
LEFT JOIN {forum_discussion_subs} dsub ON dsub.forum = f.id
{$ratingsql->join}
WHERE (
p.userid = :postuserid OR
d.userid = :discussionuserid OR
dig.userid = :digestuserid OR
sub.userid = :subuserid OR
pref.userid = :prefuserid OR
hasread.userid = :hasreaduserid OR
dsub.userid = :dsubuserid OR
{$ratingsql->userwhere}
)
";

$params = [
'modname' => 'forum',
'contextlevel' => CONTEXT_MODULE,
'postuserid' => $userid,
'discussionuserid' => $userid,
'digestuserid' => $userid,
'subuserid' => $userid,
'prefuserid' => $userid,
'hasreaduserid' => $userid,
'dsubuserid' => $userid,
];
$params += $ratingsql->params;

$contextlist = new \core_privacy\local\request\contextlist();
$contextlist->add_from_sql($sql, $params);

return $contextlist;

}
</code>

====Exporting user data====

After determining where in Moodle your plugin holds data about a user, the ''\core_privacy\manager'' will then ask your plugin to export all user data for a subset of those locations.

This is achieved through use of the ''export_user_data'' function which takes the list of approved contexts in a ''\core_privacy\local\request\approved_contextlist'' object.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Export all user data for the specified user, in the specified contexts, using the supplied exporter instance.
*
* @param approved_contextlist $contextlist The approved contexts to export information for.
*/
public static function export_user_data(approved_contextlist $contextlist) {}
</code>

The ''approved_contextlist'' includes both the user record, and a list of contexts, which can be retrieved by either processing it as an Iterator, or by calling ''get_contextids()'' or ''get_contexts()'' as required.

Data is exported using a ''\core_privacy\local\request\content_writer'', which is described in further detail below.

===Plugins which store user preferences===

Many plugins store a variety of user preferences, and must therefore export them.

Since user preferences are a site-wide preference, these are exported separately to other user data.
In some cases the only data present is user preference data, whilst in others there is a combination of user-provided data, and user preferences.

Storing of user preferences is achieved through implementation of the ''\core_privacy\local\request\preference_provider'' interface which defines one required function -- ''export_user_preferences''.

====Example====

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Export all user preferences for the plugin.
*
* @param int $userid The userid of the user whose data is to be exported.
*/
public static function export_user_preferences(int $userid) {
$markasreadonnotification = get_user_preference('markasreadonnotification', null, $userid);
if (null !== $markasreadonnotification) {
switch ($markasreadonnotification) {
case 0:
$markasreadonnotificationdescription = get_string('markasreadonnotificationno', 'mod_forum');
break;
case 1:
default:
$markasreadonnotificationdescription = get_string('markasreadonnotificationyes', 'mod_forum');
break;
}
writer::export_user_preference('mod_forum', 'markasreadonnotification', $markasreadonnotification, $markasreadonnotificationdescription);
}
}
</code>

===Plugins which define a subplugin===

Many plugin types are also able to define their own subplugins and will need to define a contract between themselves and their subplugins in order to fetch their data.

This is required as the parent plugin and the child subplugin should be separate entities and the parent plugin must be able to function if one or more of its subplugins are uninstalled.

The parent plugin is responsible for defining the contract, and for interacting with its subplugins, though we intend to create helpers to make this easier.

The parent plugin should define a new interface for each type of subplugin that it defines. This interface should extend the ''\core_privacy\local\request\plugin\subplugin_provider'' interface.

====Example====

The following example defines the contract that assign submission subplugins may be required to implement.

The assignment module is responsible for returning the contexts of all assignments where a user has data, but in some cases it is unaware of all of those cases - for example if a Teacher comments on a student submission it may not be aware of these as the information about this interaction may not be stored within its own tables.

''mod/assign/privacy/assignsubmission_provider.php''

<code php>
<?php
// …

namespace mod_assign\privacy;
use \core_privacy\local\metadata\collection;

interface assignsubmission_provider extends
// This Interface defines a subplugin.
\core_privacy\local\request\subplugin_provider {

/**
* Get the SQL required to find all submission items where this user has had any involvements.
*
* @param int $userid The user to search.
* @return \stdClass Object containing the join, params, and where used to select a these records from the database.
*/
public static function get_items_with_user_interaction(int $userid) : \stdClass ;

/**
* Export all relevant user submissions information which match the combination of userid and attemptid.
*
* @param int $userid The user to search.
* @param \context $context The context to export this submission against.
* @param array $subcontext The subcontext within the context to export this information
* @param int $attid The id of the submission to export.
*/
public static function export_user_submissions(int $userid, \context $context, array $subcontext, int $attid) ;

}
</code>

===Plugins which are subplugins to another plugin===

If you are developing a sub-plugin of another plugin, then you will have to look at the relevant plugin in order to determine the exact contract.

Each subplugin type should define a new interface which extends the ''\core_privacy\local\request\plugin\subplugin_provider'' interface and it is up to the parent plugin to define how they will interact with their children.

The principles remain the same, but the exact implementation will differ depending upon requirements.

''mod/pluginname/classes/privacy/provider.php''

<code php>
<?php
// …
namespace assignsubmission\onlinetext;

class provider implements
// This plugin does store personal user data.
\core_privacy\local\metadata\provider,

// This plugin is a subplugin of assign and must meet that contract.
\mod_assign\privacy\assignsubmission_provider {
}
</code>

===Plugins which are typically called by a Moodle subsystem===

There are a number of plugintypes in Moodle which are typically called by a specific Moodle subsystem.

Some of these are ''only'' called by that subsystem, for example plugins which are of the ''plagiarism'' plugintype should never be called directly, but are always invoked via the ''core_plagiarism'' subsystem.

Conversely, there maybe other plugintypes which can be called both via a subsystem, and in some other fashion. We are still determining whether any plugintypes currently fit this pattern.

If you are developing a plugin which belongs to a specific subsystem, then you will have to look at the relevant plugin in order to determine the exact contract.

Each subsystem will define a new interface which extends the ''\core_privacy\local\request\plugin\subsystem_provider'' interface and it is up to that subsystem to define how they will interact with those plugins.

The principles remain the same, but the exact implementation will differ depending upon requirements.

''plagiarism/detectorator/classes/privacy/provider.php''

<code php>
<?php
// …
namespace plagiarism_detectorator\privacy;

class provider implements
// This plugin does export personal user data.
\core_privacy\local\metadata\provider,

// This plugin is always linked against another activity module via the Plagiarism API.
\core_plagiarism\privacy\plugin_provider {
}
</code>

===Exporting data===

Any plugin which stores data must also export it.

To cater for this the privacy API includes a ''\core_privacy\local\request\content_writer'', which defines a set of functions to store different types of data.

Broadly speaking data is broken into the following types:

* Data - this is the object being described. For example the post content in a forum post;
* Related data - this is data related to the object being stored. For example, ratings of a forum post;
* Metadata - This is metadata about the main object. For example whether you are subscribed to a forum discussion;
* User preferences - this is data about a site-wide preference;
* Files - Any files that you are stored within Moodle on behalf of this plugin; and
* Custom files - For custom file formats - e.g. a calendar feed for calendar data. These should be used sparingly.

Each piece of data is stored against a specific Moodle ''context'', which will define how the data is structured within the exporter.
Data, and Related data only accept the ''stdClass'' object, whilst metadata should be stored as a set of key/value pairs which include a description.

In some cases the data being stored belongs within an implicit structure. For example, one forum has many forum discussions, which each have a number of forum posts. This structure is represented by an ''array'' referred to as a ''subcontext''.

The ''content_writer'' must ''always'' be called with a specific context, and can be called as follows:

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …
use \core_privacy\local\request\writer;

writer::with_context($context)
->export_data($subcontext, $post)
->export_area_files($subcontext, 'mod_forum', 'post', $post->id)
->export_metadata($subcontext, 'postread', (object) ['firstread' => $firstread], new \lang_string('privacy:export:post:postread'));
</code>

Any text field which supports Moodle files must also be rewritten:

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …
use \core_privacy\local\request\writer;

writer::with_context($context)
->rewrite_pluginfile_urls($postarea, 'mod_forum', 'post', $post->id, $post->message);

</code>

===Providing a way to delete user data===

Deleting user data is also implemented in the request interface. There are two methods that need to be created. The first one to remove all user data from a context, the other to remove user data for a specific user in a list of contexts.

====Delete for a context====

A context is given and all user data (for all users) is to be deleted from the plugin. This will be called when the retention period for the plugin has expired to adhere to the privacy by design requirement.�

''mod/choice/classes/privacy/provider.php''

<code php>
public static function delete_data_for_all_users_in_context(deletion_criteria $criteria) {
global $DB;
$context = $criteria->get_context();
if (empty($context)) {
return;
}
$instanceid = $DB->get_field('course_modules', 'instance', ['id' => $context->instanceid], MUST_EXIST);
$DB->delete_records('choice_answers', ['choiceid' => $instanceid]);
}
</code>

====Delete personal information for a specific user and context(s)====

An ''approved_contextlist'' is given and user data related to that user should either be completely deleted, or overwritten if a structure needs to be maintained. This will be called when a user has requested the right to be forgotten. All attempts should be made to delete this data where practical while still allowing the plugin to be used by other users.

''mod/choice/classes/privacy/provider.php''

<code php>
public static function delete_data_for_user(approved_contextlist $contextlist) {
global $DB;

if (empty($contextlist->count())) {
return;
}
$userid = $contextlist->get_user()->id;
foreach ($contextlist->get_contexts() as $context) {
$instanceid = $DB->get_field('course_modules', 'instance', ['id' => $context->instanceid], MUST_EXIST);
$DB->delete_records('choice_answers', ['choiceid' => $instanceid, 'userid' => $userid]);
}
}
</code>

===Difference between Moodle 3.3 and more recent versions===
Moodle 3.3 has a minimum requirement of php 5.6 and so type hinting and return type declarations are not supported in this version. Consequently the privacy API for this version does not have these features.
====What to do if you have one plugin that supports multiple branches====
This is something that we have considered and we have put in place a polyfill. This gets around the restrictions of one version having type hinting and return type declarations while another does not.

====Example====
To use the polyfill include the legacy polyfill trait and create the necessary static methods but with an underscore (shown below).
<code php>
class provider implements
\core_privacy\local\metadata\provider,
\core_privacy\local\request\plugin\provider {

// This trait must be included.
use \core_privacy\local\legacy_polyfill;

// The required methods must be in this format starting with an underscore.
public static function _get_metadata(collection $collection) {
// Code for returning metadata goes here.
}
</code>

==See also==

* [[Subject Access Request FAQ]]
* [[:en:GDPR|GDPR]] in the user documentation

[[Category:GDPR]]
[[Category:API]]

Privacy API

2018-04-10T06:53:29Z

Abgreeve: /* What to do if you have one plugin that supports multiple features - minor update to title*/

The [https://en.wikipedia.org/wiki/General_Data_Protection_Regulation General Data Protection Regulation] (GDPR) is an EU directive that looks at providing users with more control over their data and how it is processed. This regulation will come into effect on 25th of May 2018 and covers any citizen or permanent resident of the European Union. The directive will be respected by a number of other countries outside of the European Union.

To help institutions become compliant with this new regulation we are adding functionality to Moodle. This includes a number of components, amongst others these include a user’s right to:

* request information on the types of personal data held, the instances of that data, and the deletion policy for each;
* access all of their data; and
* be forgotten.

The compliance requirements also extend to installed plugins (including third party plugins). These need to also be able to report what information they store or process regarding users, and have the ability to provide and delete data for a user request.

This document describes the proposed API changes required for plugins which will allow a Moodle installation to become GDPR compliant.

Target Audience: The intended audience for this document is Moodle plugin developers, who are aiming to ensure their plugins are updated to comply with GDPR requirements coming into effect in the EU in May, 2018.

==Personal data in Moodle==

From the GDPR Spec, Article 4:

''‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;''

In Moodle, we need to consider two main types of personal data; information entered by the user and information stored about the user. The key difference being that information stored about the user will have come from a source other than the user themselves. Both types of data can be used to form a profile of the individual.

The most obvious clue to finding personal data entered by the user is the presence of a userid on a database field. Any data on the record (or linked records) pertaining to that user may be deemed personal data for that user, including things like timestamps and record identification numbers. Additionally, any free text field which allows the user to enter information must also be considered to be the personal data of that user.

Data stored about the user includes things like ratings and comments made on a student submission. These may have been made by an assessor or teacher, but are considered the personal data of the student, as they are considered a reflection of the user’s competency in the subject matter and can be used to form a profile of that individual.

The sections that follow outline what you need to do as a plugin developer to ensure any personal data is advertised and can be accessed and deleted according to the GDPR requirements.

==Background==

===Architecture overview===

A new system for Privacy has been created within Moodle. This is broken down into several main parts and forms the ''core_privacy'' subsystem:

* Some metadata providers - a set of PHP interfaces to be implemented by components for that component to describe the kind of data that it stores, and the purpose for its storage;
* Some request providers - a set of PHP interfaces to be implemented by components to allow that component to act upon user requests such as the Right to be Forgotten, and a Subject Access Request; and
* A manager - a concrete class used to bridge components which implement the providers with tools which request their data.

All plugins will implement one metadata provider, and zero, one or two request providers.

The fetching of data is broken into two separate steps:

# Detecting in which Moodle contexts the user has any data; and
# Exporting all data from each of those contexts.

This has been broken into two steps to later allow administrators to exclude certain contexts from an export - e.g. for courses currently in progress.

A third component will later be added to facilitate the deletion of data within these contexts which will help to satisfy the Right to be Forgotten. This will also use the first step.

===Implementing a provider===

All plugins will need to create a concrete class which implements the relevant metadata and request providers. The exact providers you need to implement will depend on what data you store, and the type of plugin. This is covered in more detail in the following sections of the document.

In order to do so:

# You must create a class called ''provider'' within the namespace ''\your_pluginname\privacy''.
# This class must be created at ''path/to/your/plugin/classes/privacy/provider.php''.
# You must have your class implement the relevant metadata and request interfaces.

==Plugins which do not store personal data==

Many Moodle plugins do not store any personal data. This is usually the case for plugins which just add functionality, or which display the data already stored elsewhere in Moodle.

Some examples of plugin types which might fit this criteria include themes, blocks, filters, editor plugins, etc.

Plugins which cause data to be stored elsewhere in Moodle (e.g. via a subsystem call) are considered to store data.

One examples of a plugin which does not store any data would be the Calendar month block which just displays a view of the user’s calendar. It does not store any data itself.

An example of a plugin which must not use the null provider is the Comments block. The comments block is responsible for data subsequently being stored within Moodle. Although the block doesn’t store anything itself, it interacts with the comments subsystem and is the only component which knows how that data maps to a user.

===Implementation requirements===

In order to let Moodle know that you have audited your plugin, and that you do not store any personal user data, you must implement the ''\core_privacy\local\metadata\null_provider'' interface in your plugin’s provider.

The ''null_provider'' requires you to define one function ''get_reason()'' which returns the language string identifier within your component.

====Example====

''block/calendar_month/classes/privacy/provider.php''

<code php>
<?php
// …

namespace block_calendar_month\privacy;

class provider implements
// This plugin does not store any personal user data.
\core_privacy\local\metadata\null_provider {

/**
* Get the language string identifier with the component's language
* file to explain why this plugin stores no data.
*
* @return string
*/
public static function get_reason() : string {
return 'privacy:null_reason';
}
}
</code>

''block/calendar_month/lang/en/block_calendar_month.php''

<code php>
<?php

$string['privacy:null_reason'] = 'The calendar month block displays information from the Calendar, but does not effect or store any data itself. All changes are made via the Calendar.';
</code>

That’s it. Congratulations, your plugin now implements the Privacy API.

==Plugins which store personal data==

Many Moodle plugins do store some form of personal data.

In some cases this will be stored within database tables in your plugin, and in other cases this will be in one of Moodle’s core subsystems - for example your plugin may store files, ratings, comments, or tags.

Plugins which do store data will need to:

* Describe the type of data that they store;
* Provide a way to export that data; and
* Provide a way to delete that data.

Data is described via a ''metadata'' provider, and it is both exported and deleted via an implementation of a ''request'' provider.

These are both explained in the sections below.

===Describing the type of data you store===

In order to describe the type of data that you store, you must implement the ''\core_privacy\local\metadata\provider'' interface.

This interfaces requires that you define one function: ''get_metadata''.

There are several types of item to describe the data that you store. These are for:

* Items in the Moodle database;
* Items stored by you in a Moodle subsystem - for example files, and ratings; and
* User preferences stored site-wide within Moodle for your plugin

Note: All fields should include a description from a language string within your plugin.

====Example====

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …

namespace mod_forum\privacy;
use \core_privacy\local\metadata\collection;

class provider implements
// This plugin does store personal user data.
\core_privacy\local\metadata\provider {
public static function get_metadata(collection $collection) : collection {
return $collection;
}
}
</code>

====Indicating that you store content in a Moodle subsystem====

Many plugins will use one of the core Moodle subsystems to store data.

As a plugin developer we do not expect you to describe those subsystems in detail, but we do need to know that you use them and to know what you use them for.

You can indicate this by calling the ''link_subsystem()'' method on the ''collection''.

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->link_subsystem(
'core_files',
'privacy:metadata:core_files'
);

return $collection;
}
</code>

''mod/forum/lang/en/forum.php''

<code php>
<?php

$string['privacy:metadata:core_files'] = 'The forum stores files which have been uploaded by the user to form part of a forum post.';
</code>

====Describing data stored in database tables====

Most Moodle plugins will store some form of user data in their own database tables.

As a plugin developer you will need to describe each database table, and each field which includes user data.

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_database_table(
'forum_discussion_subs',
[
'userid' => 'privacy:metadata:forum_discussion_subs:userid',
'discussionid' => 'privacy:metadata:forum_discussion_subs:discussionid',
'preference' => 'privacy:metadata:forum_discussion_subs:preference',

],
'privacy:metadata:forum_discussion_subs'
);

return $collection;
}
</code>

''mod/forum/lang/en/forum.php''

<code php>
<?php

$string['privacy:metadata:forum_discussion_subs'] = 'Information about the subscriptions to individual forum discussions. This includes when a user has chosen to subscribe to a discussion, or to unsubscribe from one where they would otherwise be subscribed.';
$string['privacy:metadata:forum_discussion_subs:userid'] = 'The ID of the user with this subscription preference.';
$string['privacy:metadata:forum_discussion_subs:discussionid'] = 'The ID of the discussion that was subscribed to.';
$string['privacy:metadata:forum_discussion_subs:preference'] = 'The start time of the subscription.';
</code>

====Indicating that you store site-wide user preferences====

Many plugins will include one or more user preferences. Unfortunately this is one of Moodle’s older components and many of the values stored are not pure user preferences. Each plugin should be aware of how it handles its own preferences and is best placed to determine whether they are site-wide preferences, or per-instance preferences.

Whilst most of these will have a fixed name (e.g. ''filepicker_recentrepository''), some will include a variable of some kind (e.g. ''tool_usertours_tour_completion_time_2''). Only the general name needs to be indicated rather than one copy for each preference.

Also, these should only be ''site-wide'' user preferences which do not belong to a specific Moodle context.

In the above examples:

* Preference ''filepicker_recentrepository'' belongs to the file subsystem, and is a site-wide preference affecting the user anywhere that they view the filepicker.
* Preference ''tool_usertours_tour_completion_time_2'' belongs to user tours. User tours are a site-wide feature which can affect many parts of Moodle and cross multiple contexts.

In some cases a value may be stored in the preferences table but is known to belong to a specific context within Moodle. In these cases they should be stored as metadata against that context rather than as a site-wide user preference.

You can indicate this by calling the ''add_user_preference()'' method on the ''collection''.

Any plugin providing user preferences must also implement the ''\core_privacy\local\request\preference_provider''.

=====Example=====

''admin/tool/usertours/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_user_preference('tool_usertours_tour_completion_time,
'privacy:metadata:preference:tool_usertours_tour_completion_time');

return $collection;
}
</code>

''admin/tool/usertours/lang/en/tool_usertours.php''

<code php>
<?php

$string['privacy:metadata:tool_usertours_tour_completion_time'] = 'The time that a specific user tour was last completed by a user.';
</code>

====Indicating that you export data to an external location====

Many plugins will interact with external systems - for example cloud-based services. Often this external location is configurable within the plugin either at the site or the instance level.

As a plugin developer you will need to describe each ''type'' of target destination, alongside a list of each exported field which includes user data.
The ''actual'' destination does not need to be described as this can change based on configuration.

You can indicate this by calling the ''link_external_location()'' method on the collection.

=====Example=====

''mod/lti/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->link_external_location('lti_client', [
'userid' => 'privacy:metadata:lti_client:userid',
'fullname' => 'privacy:metadata:lti_client:fullname',
], 'privacy:metadata:lti_client');

return $collection;
}
</code>

''mod/lti/lang/en/lti.php''

<code php>
<?php

$string['privacy:metadata:lti_client'] = 'In order to integrate with a remote LTI service, user data needs to be exchanged with that service.';
$string['privacy:metadata:lti_client:userid'] = 'The userid is sent from Moodle to allow you to access your data on the remote system.';
$string['privacy:metadata:lti_client:fullname'] = 'Your full name is sent to the remote system to allow a better user experience.';
</code>

===Providing a way to export user data===

In order to export the user data that you store, you must implement the relevant request provider.

We have named these request providers because they are called in response to a specific request from a user to access their information.

There are several different types of request provider, and you may need to implement several of these, depending on the type and nature of your plugin.

Broadly speaking plugins will fit into one of the following categories:

* Plugins which are a subplugin of another plugin. Examples include ''assignsubmission'', ''atto'', and ''datafield'';
* Plugins which are typically called by a Moodle subsystem. Examples include ''qtype'', and ''profilefield'';
* All other plugins which store data.

Most plugins will fit into this final category, whilst other plugins may fall into several categories.
Plugins which ''define'' a subplugin will also be responsible for collecting this data from their subplugins.

A final category exists - plugins which store user preferences. In some cases this may be the ''only'' provider implemented.

====Standard plugins which store data====

A majority of Moodle plugins will fit into this category and will be required to implement the ''\core_privacy\local\request\plugin\provider'' interface. This interface requires that you define two functions:

* ''get_contexts_for_userid'' - to explain where data is held within Moodle for your plugin; and
* ''export_user_data'' - to export a user’s personal data from your plugin.

These APIs make use of the Moodle ''context'' system to hierarchically store this data.

====Retrieving the list of contexts====

Contexts are retrieved using the ''get_contexts_for_userid'' function which takes the ID of the user being fetched, and returns a list of contexts in which the user has any data.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {}
</code>

The function returns a ''\core_privacy\local\request\contextlist'' which is used to keep a set of contexts together in a fixed fashion.

Because a Subject Access Request covers ''every'' piece of data that is held for a user within Moodle, efficiency and performance is highly important. As a result, contexts are added to the ''contextlist'' by defining one or more SQL queries which return just the contextid. Multiple SQL queries can be added as required.

Many plugins will interact with specific subsystems and store data within them.
These subsystems will also provide a way in which to link the data that you have stored with your own database tables.
At present these are still a work in progress and only the ''core_ratings'' subsystem includes this.

=====Basic example=====

The following example simply fetches the contextid for all forums where a user has a single discussion (note: this is an incomplete example):

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {
$contextlist = new \core_privacy\local\request\contextlist();

$sql = "SELECT c.id
FROM {context} c
INNER JOIN {course_modules} cm ON cm.id = c.instanceid AND c.contextlevel = :contextlevel
INNER JOIN {modules} m ON m.id = cm.module AND m.name = :modname
INNER JOIN {forum} f ON f.id = cm.instance
LEFT JOIN {forum_discussions} d ON d.forum = f.id
WHERE (
d.userid = :discussionuserid
)
";

$params = [
'modname' => 'forum',
'contextlevel' => CONTEXT_MODULE,
'discussionuserid' => $userid,
];

$contextlist->add_from_sql($sql, $params);
}
</code>

=====More complete example=====

The following example includes a link to core_rating.
It will find any forum, forum discussion, or forum post where the user has any data, including:

* Per-forum digest preferences;
* Per-forum subscription preferences;
* Per-forum read tracking preferences;
* Per-discussion subscription preferences;
* Per-post read data (if a user has read a post or not); and
* Per-post rating data.

In the case of the rating data, this will include any post where the user has rated the post of another user.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {
$ratingsql = \core_rating\privacy\provider::get_sql_join('rat', 'mod_forum', 'post', 'p.id', $userid);
// Fetch all forum discussions, and forum posts.
$sql = "SELECT c.id
FROM {context} c
INNER JOIN {course_modules} cm ON cm.id = c.instanceid AND c.contextlevel = :contextlevel
INNER JOIN {modules} m ON m.id = cm.module AND m.name = :modname
INNER JOIN {forum} f ON f.id = cm.instance
LEFT JOIN {forum_discussions} d ON d.forum = f.id
LEFT JOIN {forum_posts} p ON p.discussion = d.id
LEFT JOIN {forum_digests} dig ON dig.forum = f.id
LEFT JOIN {forum_subscriptions} sub ON sub.forum = f.id
LEFT JOIN {forum_track_prefs} pref ON pref.forumid = f.id
LEFT JOIN {forum_read} hasread ON hasread.forumid = f.id
LEFT JOIN {forum_discussion_subs} dsub ON dsub.forum = f.id
{$ratingsql->join}
WHERE (
p.userid = :postuserid OR
d.userid = :discussionuserid OR
dig.userid = :digestuserid OR
sub.userid = :subuserid OR
pref.userid = :prefuserid OR
hasread.userid = :hasreaduserid OR
dsub.userid = :dsubuserid OR
{$ratingsql->userwhere}
)
";

$params = [
'modname' => 'forum',
'contextlevel' => CONTEXT_MODULE,
'postuserid' => $userid,
'discussionuserid' => $userid,
'digestuserid' => $userid,
'subuserid' => $userid,
'prefuserid' => $userid,
'hasreaduserid' => $userid,
'dsubuserid' => $userid,
];
$params += $ratingsql->params;

$contextlist = new \core_privacy\local\request\contextlist();
$contextlist->add_from_sql($sql, $params);

return $contextlist;

}
</code>

====Exporting user data====

After determining where in Moodle your plugin holds data about a user, the ''\core_privacy\manager'' will then ask your plugin to export all user data for a subset of those locations.

This is achieved through use of the ''export_user_data'' function which takes the list of approved contexts in a ''\core_privacy\local\request\approved_contextlist'' object.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Export all user data for the specified user, in the specified contexts, using the supplied exporter instance.
*
* @param approved_contextlist $contextlist The approved contexts to export information for.
*/
public static function export_user_data(approved_contextlist $contextlist) {}
</code>

The ''approved_contextlist'' includes both the user record, and a list of contexts, which can be retrieved by either processing it as an Iterator, or by calling ''get_contextids()'' or ''get_contexts()'' as required.

Data is exported using a ''\core_privacy\local\request\content_writer'', which is described in further detail below.

===Plugins which store user preferences===

Many plugins store a variety of user preferences, and must therefore export them.

Since user preferences are a site-wide preference, these are exported separately to other user data.
In some cases the only data present is user preference data, whilst in others there is a combination of user-provided data, and user preferences.

Storing of user preferences is achieved through implementation of the ''\core_privacy\local\request\preference_provider'' interface which defines one required function -- ''export_user_preferences''.

====Example====

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Export all user preferences for the plugin.
*
* @param int $userid The userid of the user whose data is to be exported.
*/
public static function export_user_preferences(int $userid) {
$markasreadonnotification = get_user_preference('markasreadonnotification', null, $userid);
if (null !== $markasreadonnotification) {
switch ($markasreadonnotification) {
case 0:
$markasreadonnotificationdescription = get_string('markasreadonnotificationno', 'mod_forum');
break;
case 1:
default:
$markasreadonnotificationdescription = get_string('markasreadonnotificationyes', 'mod_forum');
break;
}
writer::export_user_preference('mod_forum', 'markasreadonnotification', $markasreadonnotification, $markasreadonnotificationdescription);
}
}
</code>

===Plugins which define a subplugin===

Many plugin types are also able to define their own subplugins and will need to define a contract between themselves and their subplugins in order to fetch their data.

This is required as the parent plugin and the child subplugin should be separate entities and the parent plugin must be able to function if one or more of its subplugins are uninstalled.

The parent plugin is responsible for defining the contract, and for interacting with its subplugins, though we intend to create helpers to make this easier.

The parent plugin should define a new interface for each type of subplugin that it defines. This interface should extend the ''\core_privacy\local\request\plugin\subplugin_provider'' interface.

====Example====

The following example defines the contract that assign submission subplugins may be required to implement.

The assignment module is responsible for returning the contexts of all assignments where a user has data, but in some cases it is unaware of all of those cases - for example if a Teacher comments on a student submission it may not be aware of these as the information about this interaction may not be stored within its own tables.

''mod/assign/privacy/assignsubmission_provider.php''

<code php>
<?php
// …

namespace mod_assign\privacy;
use \core_privacy\local\metadata\collection;

interface assignsubmission_provider extends
// This Interface defines a subplugin.
\core_privacy\local\request\subplugin_provider {

/**
* Get the SQL required to find all submission items where this user has had any involvements.
*
* @param int $userid The user to search.
* @return \stdClass Object containing the join, params, and where used to select a these records from the database.
*/
public static function get_items_with_user_interaction(int $userid) : \stdClass ;

/**
* Export all relevant user submissions information which match the combination of userid and attemptid.
*
* @param int $userid The user to search.
* @param \context $context The context to export this submission against.
* @param array $subcontext The subcontext within the context to export this information
* @param int $attid The id of the submission to export.
*/
public static function export_user_submissions(int $userid, \context $context, array $subcontext, int $attid) ;

}
</code>

===Plugins which are subplugins to another plugin===

If you are developing a sub-plugin of another plugin, then you will have to look at the relevant plugin in order to determine the exact contract.

Each subplugin type should define a new interface which extends the ''\core_privacy\local\request\plugin\subplugin_provider'' interface and it is up to the parent plugin to define how they will interact with their children.

The principles remain the same, but the exact implementation will differ depending upon requirements.

''mod/pluginname/classes/privacy/provider.php''

<code php>
<?php
// …
namespace assignsubmission\onlinetext;

class provider implements
// This plugin does store personal user data.
\core_privacy\local\metadata\provider,

// This plugin is a subplugin of assign and must meet that contract.
\mod_assign\privacy\assignsubmission_provider {
}
</code>

===Plugins which are typically called by a Moodle subsystem===

There are a number of plugintypes in Moodle which are typically called by a specific Moodle subsystem.

Some of these are ''only'' called by that subsystem, for example plugins which are of the ''plagiarism'' plugintype should never be called directly, but are always invoked via the ''core_plagiarism'' subsystem.

Conversely, there maybe other plugintypes which can be called both via a subsystem, and in some other fashion. We are still determining whether any plugintypes currently fit this pattern.

If you are developing a plugin which belongs to a specific subsystem, then you will have to look at the relevant plugin in order to determine the exact contract.

Each subsystem will define a new interface which extends the ''\core_privacy\local\request\plugin\subsystem_provider'' interface and it is up to that subsystem to define how they will interact with those plugins.

The principles remain the same, but the exact implementation will differ depending upon requirements.

''plagiarism/detectorator/classes/privacy/provider.php''

<code php>
<?php
// …
namespace plagiarism_detectorator\privacy;

class provider implements
// This plugin does export personal user data.
\core_privacy\local\metadata\provider,

// This plugin is always linked against another activity module via the Plagiarism API.
\core_plagiarism\privacy\plugin_provider {
}
</code>

===Exporting data===

Any plugin which stores data must also export it.

To cater for this the privacy API includes a ''\core_privacy\local\request\content_writer'', which defines a set of functions to store different types of data.

Broadly speaking data is broken into the following types:

* Data - this is the object being described. For example the post content in a forum post;
* Related data - this is data related to the object being stored. For example, ratings of a forum post;
* Metadata - This is metadata about the main object. For example whether you are subscribed to a forum discussion;
* User preferences - this is data about a site-wide preference;
* Files - Any files that you are stored within Moodle on behalf of this plugin; and
* Custom files - For custom file formats - e.g. a calendar feed for calendar data. These should be used sparingly.

Each piece of data is stored against a specific Moodle ''context'', which will define how the data is structured within the exporter.
Data, and Related data only accept the ''stdClass'' object, whilst metadata should be stored as a set of key/value pairs which include a description.

In some cases the data being stored belongs within an implicit structure. For example, one forum has many forum discussions, which each have a number of forum posts. This structure is represented by an ''array'' referred to as a ''subcontext''.

The ''content_writer'' must ''always'' be called with a specific context, and can be called as follows:

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …
use \core_privacy\local\request\writer;

writer::with_context($context)
->export_data($subcontext, $post)
->export_area_files($subcontext, 'mod_forum', 'post', $post->id)
->export_metadata($subcontext, 'postread', (object) ['firstread' => $firstread], new \lang_string('privacy:export:post:postread'));
</code>

Any text field which supports Moodle files must also be rewritten:

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …
use \core_privacy\local\request\writer;

writer::with_context($context)
->rewrite_pluginfile_urls($postarea, 'mod_forum', 'post', $post->id, $post->message);

</code>

===Providing a way to delete user data===

Deleting user data is also implemented in the request interface. There are two methods that need to be created. The first one to remove all user data from a context, the other to remove user data for a specific user in a list of contexts.

====Delete for a context====

A context is given and all user data (for all users) is to be deleted from the plugin. This will be called when the retention period for the plugin has expired to adhere to the privacy by design requirement.�

''mod/choice/classes/privacy/provider.php''

<code php>
public static function delete_data_for_all_users_in_context(deletion_criteria $criteria) {
global $DB;
$context = $criteria->get_context();
if (empty($context)) {
return;
}
$instanceid = $DB->get_field('course_modules', 'instance', ['id' => $context->instanceid], MUST_EXIST);
$DB->delete_records('choice_answers', ['choiceid' => $instanceid]);
}
</code>

====Delete personal information for a specific user and context(s)====

An ''approved_contextlist'' is given and user data related to that user should either be completely deleted, or overwritten if a structure needs to be maintained. This will be called when a user has requested the right to be forgotten. All attempts should be made to delete this data where practical while still allowing the plugin to be used by other users.

''mod/choice/classes/privacy/provider.php''

<code php>
public static function delete_data_for_user(approved_contextlist $contextlist) {
global $DB;

if (empty($contextlist->count())) {
return;
}
$userid = $contextlist->get_user()->id;
foreach ($contextlist->get_contexts() as $context) {
$instanceid = $DB->get_field('course_modules', 'instance', ['id' => $context->instanceid], MUST_EXIST);
$DB->delete_records('choice_answers', ['choiceid' => $instanceid, 'userid' => $userid]);
}
}
</code>

===Difference between Moodle 3.3 and more recent versions===
Moodle 3.3 has a minimum requirement of php 5.6 and so type hinting and return type declarations are not supported in this version. Consequently the privacy API for this version does not have these features.
====What to do if you have one plugin that supports multiple branches====
This is something that we have considered and we have put in place a polyfill. This gets around the restrictions of one version having type hinting and return type declarations while another does not.

====Example====
To use the polyfill include the legacy polyfill trait and create the necessary static methods but with an underscore (shown below).
<code php>
class provider implements
\core_privacy\local\metadata\provider,
\core_privacy\local\request\plugin\provider {

// This is a trait must be included.
use \core_privacy\local\legacy_polyfill;

// The required methods must be in this format starting with an underscore.
public static function _get_metadata(collection $collection) {
// Code for returning metadata goes here.
}
</code>

==See also==

* [[Subject Access Request FAQ]]
* [[:en:GDPR|GDPR]] in the user documentation

[[Category:GDPR]]
[[Category:API]]

Privacy API

2018-04-10T06:52:28Z

Abgreeve: Polyfill details entered.

The [https://en.wikipedia.org/wiki/General_Data_Protection_Regulation General Data Protection Regulation] (GDPR) is an EU directive that looks at providing users with more control over their data and how it is processed. This regulation will come into effect on 25th of May 2018 and covers any citizen or permanent resident of the European Union. The directive will be respected by a number of other countries outside of the European Union.

To help institutions become compliant with this new regulation we are adding functionality to Moodle. This includes a number of components, amongst others these include a user’s right to:

* request information on the types of personal data held, the instances of that data, and the deletion policy for each;
* access all of their data; and
* be forgotten.

The compliance requirements also extend to installed plugins (including third party plugins). These need to also be able to report what information they store or process regarding users, and have the ability to provide and delete data for a user request.

This document describes the proposed API changes required for plugins which will allow a Moodle installation to become GDPR compliant.

Target Audience: The intended audience for this document is Moodle plugin developers, who are aiming to ensure their plugins are updated to comply with GDPR requirements coming into effect in the EU in May, 2018.

==Personal data in Moodle==

From the GDPR Spec, Article 4:

''‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;''

In Moodle, we need to consider two main types of personal data; information entered by the user and information stored about the user. The key difference being that information stored about the user will have come from a source other than the user themselves. Both types of data can be used to form a profile of the individual.

The most obvious clue to finding personal data entered by the user is the presence of a userid on a database field. Any data on the record (or linked records) pertaining to that user may be deemed personal data for that user, including things like timestamps and record identification numbers. Additionally, any free text field which allows the user to enter information must also be considered to be the personal data of that user.

Data stored about the user includes things like ratings and comments made on a student submission. These may have been made by an assessor or teacher, but are considered the personal data of the student, as they are considered a reflection of the user’s competency in the subject matter and can be used to form a profile of that individual.

The sections that follow outline what you need to do as a plugin developer to ensure any personal data is advertised and can be accessed and deleted according to the GDPR requirements.

==Background==

===Architecture overview===

A new system for Privacy has been created within Moodle. This is broken down into several main parts and forms the ''core_privacy'' subsystem:

* Some metadata providers - a set of PHP interfaces to be implemented by components for that component to describe the kind of data that it stores, and the purpose for its storage;
* Some request providers - a set of PHP interfaces to be implemented by components to allow that component to act upon user requests such as the Right to be Forgotten, and a Subject Access Request; and
* A manager - a concrete class used to bridge components which implement the providers with tools which request their data.

All plugins will implement one metadata provider, and zero, one or two request providers.

The fetching of data is broken into two separate steps:

# Detecting in which Moodle contexts the user has any data; and
# Exporting all data from each of those contexts.

This has been broken into two steps to later allow administrators to exclude certain contexts from an export - e.g. for courses currently in progress.

A third component will later be added to facilitate the deletion of data within these contexts which will help to satisfy the Right to be Forgotten. This will also use the first step.

===Implementing a provider===

All plugins will need to create a concrete class which implements the relevant metadata and request providers. The exact providers you need to implement will depend on what data you store, and the type of plugin. This is covered in more detail in the following sections of the document.

In order to do so:

# You must create a class called ''provider'' within the namespace ''\your_pluginname\privacy''.
# This class must be created at ''path/to/your/plugin/classes/privacy/provider.php''.
# You must have your class implement the relevant metadata and request interfaces.

==Plugins which do not store personal data==

Many Moodle plugins do not store any personal data. This is usually the case for plugins which just add functionality, or which display the data already stored elsewhere in Moodle.

Some examples of plugin types which might fit this criteria include themes, blocks, filters, editor plugins, etc.

Plugins which cause data to be stored elsewhere in Moodle (e.g. via a subsystem call) are considered to store data.

One examples of a plugin which does not store any data would be the Calendar month block which just displays a view of the user’s calendar. It does not store any data itself.

An example of a plugin which must not use the null provider is the Comments block. The comments block is responsible for data subsequently being stored within Moodle. Although the block doesn’t store anything itself, it interacts with the comments subsystem and is the only component which knows how that data maps to a user.

===Implementation requirements===

In order to let Moodle know that you have audited your plugin, and that you do not store any personal user data, you must implement the ''\core_privacy\local\metadata\null_provider'' interface in your plugin’s provider.

The ''null_provider'' requires you to define one function ''get_reason()'' which returns the language string identifier within your component.

====Example====

''block/calendar_month/classes/privacy/provider.php''

<code php>
<?php
// …

namespace block_calendar_month\privacy;

class provider implements
// This plugin does not store any personal user data.
\core_privacy\local\metadata\null_provider {

/**
* Get the language string identifier with the component's language
* file to explain why this plugin stores no data.
*
* @return string
*/
public static function get_reason() : string {
return 'privacy:null_reason';
}
}
</code>

''block/calendar_month/lang/en/block_calendar_month.php''

<code php>
<?php

$string['privacy:null_reason'] = 'The calendar month block displays information from the Calendar, but does not effect or store any data itself. All changes are made via the Calendar.';
</code>

That’s it. Congratulations, your plugin now implements the Privacy API.

==Plugins which store personal data==

Many Moodle plugins do store some form of personal data.

In some cases this will be stored within database tables in your plugin, and in other cases this will be in one of Moodle’s core subsystems - for example your plugin may store files, ratings, comments, or tags.

Plugins which do store data will need to:

* Describe the type of data that they store;
* Provide a way to export that data; and
* Provide a way to delete that data.

Data is described via a ''metadata'' provider, and it is both exported and deleted via an implementation of a ''request'' provider.

These are both explained in the sections below.

===Describing the type of data you store===

In order to describe the type of data that you store, you must implement the ''\core_privacy\local\metadata\provider'' interface.

This interfaces requires that you define one function: ''get_metadata''.

There are several types of item to describe the data that you store. These are for:

* Items in the Moodle database;
* Items stored by you in a Moodle subsystem - for example files, and ratings; and
* User preferences stored site-wide within Moodle for your plugin

Note: All fields should include a description from a language string within your plugin.

====Example====

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …

namespace mod_forum\privacy;
use \core_privacy\local\metadata\collection;

class provider implements
// This plugin does store personal user data.
\core_privacy\local\metadata\provider {
public static function get_metadata(collection $collection) : collection {
return $collection;
}
}
</code>

====Indicating that you store content in a Moodle subsystem====

Many plugins will use one of the core Moodle subsystems to store data.

As a plugin developer we do not expect you to describe those subsystems in detail, but we do need to know that you use them and to know what you use them for.

You can indicate this by calling the ''link_subsystem()'' method on the ''collection''.

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->link_subsystem(
'core_files',
'privacy:metadata:core_files'
);

return $collection;
}
</code>

''mod/forum/lang/en/forum.php''

<code php>
<?php

$string['privacy:metadata:core_files'] = 'The forum stores files which have been uploaded by the user to form part of a forum post.';
</code>

====Describing data stored in database tables====

Most Moodle plugins will store some form of user data in their own database tables.

As a plugin developer you will need to describe each database table, and each field which includes user data.

=====Example=====

''mod/forum/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_database_table(
'forum_discussion_subs',
[
'userid' => 'privacy:metadata:forum_discussion_subs:userid',
'discussionid' => 'privacy:metadata:forum_discussion_subs:discussionid',
'preference' => 'privacy:metadata:forum_discussion_subs:preference',

],
'privacy:metadata:forum_discussion_subs'
);

return $collection;
}
</code>

''mod/forum/lang/en/forum.php''

<code php>
<?php

$string['privacy:metadata:forum_discussion_subs'] = 'Information about the subscriptions to individual forum discussions. This includes when a user has chosen to subscribe to a discussion, or to unsubscribe from one where they would otherwise be subscribed.';
$string['privacy:metadata:forum_discussion_subs:userid'] = 'The ID of the user with this subscription preference.';
$string['privacy:metadata:forum_discussion_subs:discussionid'] = 'The ID of the discussion that was subscribed to.';
$string['privacy:metadata:forum_discussion_subs:preference'] = 'The start time of the subscription.';
</code>

====Indicating that you store site-wide user preferences====

Many plugins will include one or more user preferences. Unfortunately this is one of Moodle’s older components and many of the values stored are not pure user preferences. Each plugin should be aware of how it handles its own preferences and is best placed to determine whether they are site-wide preferences, or per-instance preferences.

Whilst most of these will have a fixed name (e.g. ''filepicker_recentrepository''), some will include a variable of some kind (e.g. ''tool_usertours_tour_completion_time_2''). Only the general name needs to be indicated rather than one copy for each preference.

Also, these should only be ''site-wide'' user preferences which do not belong to a specific Moodle context.

In the above examples:

* Preference ''filepicker_recentrepository'' belongs to the file subsystem, and is a site-wide preference affecting the user anywhere that they view the filepicker.
* Preference ''tool_usertours_tour_completion_time_2'' belongs to user tours. User tours are a site-wide feature which can affect many parts of Moodle and cross multiple contexts.

In some cases a value may be stored in the preferences table but is known to belong to a specific context within Moodle. In these cases they should be stored as metadata against that context rather than as a site-wide user preference.

You can indicate this by calling the ''add_user_preference()'' method on the ''collection''.

Any plugin providing user preferences must also implement the ''\core_privacy\local\request\preference_provider''.

=====Example=====

''admin/tool/usertours/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->add_user_preference('tool_usertours_tour_completion_time,
'privacy:metadata:preference:tool_usertours_tour_completion_time');

return $collection;
}
</code>

''admin/tool/usertours/lang/en/tool_usertours.php''

<code php>
<?php

$string['privacy:metadata:tool_usertours_tour_completion_time'] = 'The time that a specific user tour was last completed by a user.';
</code>

====Indicating that you export data to an external location====

Many plugins will interact with external systems - for example cloud-based services. Often this external location is configurable within the plugin either at the site or the instance level.

As a plugin developer you will need to describe each ''type'' of target destination, alongside a list of each exported field which includes user data.
The ''actual'' destination does not need to be described as this can change based on configuration.

You can indicate this by calling the ''link_external_location()'' method on the collection.

=====Example=====

''mod/lti/classes/privacy/provider.php''

<code php>
public static function get_metadata(collection $collection) : collection {

$collection->link_external_location('lti_client', [
'userid' => 'privacy:metadata:lti_client:userid',
'fullname' => 'privacy:metadata:lti_client:fullname',
], 'privacy:metadata:lti_client');

return $collection;
}
</code>

''mod/lti/lang/en/lti.php''

<code php>
<?php

$string['privacy:metadata:lti_client'] = 'In order to integrate with a remote LTI service, user data needs to be exchanged with that service.';
$string['privacy:metadata:lti_client:userid'] = 'The userid is sent from Moodle to allow you to access your data on the remote system.';
$string['privacy:metadata:lti_client:fullname'] = 'Your full name is sent to the remote system to allow a better user experience.';
</code>

===Providing a way to export user data===

In order to export the user data that you store, you must implement the relevant request provider.

We have named these request providers because they are called in response to a specific request from a user to access their information.

There are several different types of request provider, and you may need to implement several of these, depending on the type and nature of your plugin.

Broadly speaking plugins will fit into one of the following categories:

* Plugins which are a subplugin of another plugin. Examples include ''assignsubmission'', ''atto'', and ''datafield'';
* Plugins which are typically called by a Moodle subsystem. Examples include ''qtype'', and ''profilefield'';
* All other plugins which store data.

Most plugins will fit into this final category, whilst other plugins may fall into several categories.
Plugins which ''define'' a subplugin will also be responsible for collecting this data from their subplugins.

A final category exists - plugins which store user preferences. In some cases this may be the ''only'' provider implemented.

====Standard plugins which store data====

A majority of Moodle plugins will fit into this category and will be required to implement the ''\core_privacy\local\request\plugin\provider'' interface. This interface requires that you define two functions:

* ''get_contexts_for_userid'' - to explain where data is held within Moodle for your plugin; and
* ''export_user_data'' - to export a user’s personal data from your plugin.

These APIs make use of the Moodle ''context'' system to hierarchically store this data.

====Retrieving the list of contexts====

Contexts are retrieved using the ''get_contexts_for_userid'' function which takes the ID of the user being fetched, and returns a list of contexts in which the user has any data.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {}
</code>

The function returns a ''\core_privacy\local\request\contextlist'' which is used to keep a set of contexts together in a fixed fashion.

Because a Subject Access Request covers ''every'' piece of data that is held for a user within Moodle, efficiency and performance is highly important. As a result, contexts are added to the ''contextlist'' by defining one or more SQL queries which return just the contextid. Multiple SQL queries can be added as required.

Many plugins will interact with specific subsystems and store data within them.
These subsystems will also provide a way in which to link the data that you have stored with your own database tables.
At present these are still a work in progress and only the ''core_ratings'' subsystem includes this.

=====Basic example=====

The following example simply fetches the contextid for all forums where a user has a single discussion (note: this is an incomplete example):

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {
$contextlist = new \core_privacy\local\request\contextlist();

$sql = "SELECT c.id
FROM {context} c
INNER JOIN {course_modules} cm ON cm.id = c.instanceid AND c.contextlevel = :contextlevel
INNER JOIN {modules} m ON m.id = cm.module AND m.name = :modname
INNER JOIN {forum} f ON f.id = cm.instance
LEFT JOIN {forum_discussions} d ON d.forum = f.id
WHERE (
d.userid = :discussionuserid
)
";

$params = [
'modname' => 'forum',
'contextlevel' => CONTEXT_MODULE,
'discussionuserid' => $userid,
];

$contextlist->add_from_sql($sql, $params);
}
</code>

=====More complete example=====

The following example includes a link to core_rating.
It will find any forum, forum discussion, or forum post where the user has any data, including:

* Per-forum digest preferences;
* Per-forum subscription preferences;
* Per-forum read tracking preferences;
* Per-discussion subscription preferences;
* Per-post read data (if a user has read a post or not); and
* Per-post rating data.

In the case of the rating data, this will include any post where the user has rated the post of another user.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Get the list of contexts that contain user information for the specified user.
*
* @param int $userid The user to search.
* @return contextlist $contextlist The list of contexts used in this plugin.
*/
public static function get_contexts_for_userid(int $userid) : contextlist {
$ratingsql = \core_rating\privacy\provider::get_sql_join('rat', 'mod_forum', 'post', 'p.id', $userid);
// Fetch all forum discussions, and forum posts.
$sql = "SELECT c.id
FROM {context} c
INNER JOIN {course_modules} cm ON cm.id = c.instanceid AND c.contextlevel = :contextlevel
INNER JOIN {modules} m ON m.id = cm.module AND m.name = :modname
INNER JOIN {forum} f ON f.id = cm.instance
LEFT JOIN {forum_discussions} d ON d.forum = f.id
LEFT JOIN {forum_posts} p ON p.discussion = d.id
LEFT JOIN {forum_digests} dig ON dig.forum = f.id
LEFT JOIN {forum_subscriptions} sub ON sub.forum = f.id
LEFT JOIN {forum_track_prefs} pref ON pref.forumid = f.id
LEFT JOIN {forum_read} hasread ON hasread.forumid = f.id
LEFT JOIN {forum_discussion_subs} dsub ON dsub.forum = f.id
{$ratingsql->join}
WHERE (
p.userid = :postuserid OR
d.userid = :discussionuserid OR
dig.userid = :digestuserid OR
sub.userid = :subuserid OR
pref.userid = :prefuserid OR
hasread.userid = :hasreaduserid OR
dsub.userid = :dsubuserid OR
{$ratingsql->userwhere}
)
";

$params = [
'modname' => 'forum',
'contextlevel' => CONTEXT_MODULE,
'postuserid' => $userid,
'discussionuserid' => $userid,
'digestuserid' => $userid,
'subuserid' => $userid,
'prefuserid' => $userid,
'hasreaduserid' => $userid,
'dsubuserid' => $userid,
];
$params += $ratingsql->params;

$contextlist = new \core_privacy\local\request\contextlist();
$contextlist->add_from_sql($sql, $params);

return $contextlist;

}
</code>

====Exporting user data====

After determining where in Moodle your plugin holds data about a user, the ''\core_privacy\manager'' will then ask your plugin to export all user data for a subset of those locations.

This is achieved through use of the ''export_user_data'' function which takes the list of approved contexts in a ''\core_privacy\local\request\approved_contextlist'' object.

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Export all user data for the specified user, in the specified contexts, using the supplied exporter instance.
*
* @param approved_contextlist $contextlist The approved contexts to export information for.
*/
public static function export_user_data(approved_contextlist $contextlist) {}
</code>

The ''approved_contextlist'' includes both the user record, and a list of contexts, which can be retrieved by either processing it as an Iterator, or by calling ''get_contextids()'' or ''get_contexts()'' as required.

Data is exported using a ''\core_privacy\local\request\content_writer'', which is described in further detail below.

===Plugins which store user preferences===

Many plugins store a variety of user preferences, and must therefore export them.

Since user preferences are a site-wide preference, these are exported separately to other user data.
In some cases the only data present is user preference data, whilst in others there is a combination of user-provided data, and user preferences.

Storing of user preferences is achieved through implementation of the ''\core_privacy\local\request\preference_provider'' interface which defines one required function -- ''export_user_preferences''.

====Example====

''mod/forum/classes/privacy/provider.php''

<code php>
/**
* Export all user preferences for the plugin.
*
* @param int $userid The userid of the user whose data is to be exported.
*/
public static function export_user_preferences(int $userid) {
$markasreadonnotification = get_user_preference('markasreadonnotification', null, $userid);
if (null !== $markasreadonnotification) {
switch ($markasreadonnotification) {
case 0:
$markasreadonnotificationdescription = get_string('markasreadonnotificationno', 'mod_forum');
break;
case 1:
default:
$markasreadonnotificationdescription = get_string('markasreadonnotificationyes', 'mod_forum');
break;
}
writer::export_user_preference('mod_forum', 'markasreadonnotification', $markasreadonnotification, $markasreadonnotificationdescription);
}
}
</code>

===Plugins which define a subplugin===

Many plugin types are also able to define their own subplugins and will need to define a contract between themselves and their subplugins in order to fetch their data.

This is required as the parent plugin and the child subplugin should be separate entities and the parent plugin must be able to function if one or more of its subplugins are uninstalled.

The parent plugin is responsible for defining the contract, and for interacting with its subplugins, though we intend to create helpers to make this easier.

The parent plugin should define a new interface for each type of subplugin that it defines. This interface should extend the ''\core_privacy\local\request\plugin\subplugin_provider'' interface.

====Example====

The following example defines the contract that assign submission subplugins may be required to implement.

The assignment module is responsible for returning the contexts of all assignments where a user has data, but in some cases it is unaware of all of those cases - for example if a Teacher comments on a student submission it may not be aware of these as the information about this interaction may not be stored within its own tables.

''mod/assign/privacy/assignsubmission_provider.php''

<code php>
<?php
// …

namespace mod_assign\privacy;
use \core_privacy\local\metadata\collection;

interface assignsubmission_provider extends
// This Interface defines a subplugin.
\core_privacy\local\request\subplugin_provider {

/**
* Get the SQL required to find all submission items where this user has had any involvements.
*
* @param int $userid The user to search.
* @return \stdClass Object containing the join, params, and where used to select a these records from the database.
*/
public static function get_items_with_user_interaction(int $userid) : \stdClass ;

/**
* Export all relevant user submissions information which match the combination of userid and attemptid.
*
* @param int $userid The user to search.
* @param \context $context The context to export this submission against.
* @param array $subcontext The subcontext within the context to export this information
* @param int $attid The id of the submission to export.
*/
public static function export_user_submissions(int $userid, \context $context, array $subcontext, int $attid) ;

}
</code>

===Plugins which are subplugins to another plugin===

If you are developing a sub-plugin of another plugin, then you will have to look at the relevant plugin in order to determine the exact contract.

Each subplugin type should define a new interface which extends the ''\core_privacy\local\request\plugin\subplugin_provider'' interface and it is up to the parent plugin to define how they will interact with their children.

The principles remain the same, but the exact implementation will differ depending upon requirements.

''mod/pluginname/classes/privacy/provider.php''

<code php>
<?php
// …
namespace assignsubmission\onlinetext;

class provider implements
// This plugin does store personal user data.
\core_privacy\local\metadata\provider,

// This plugin is a subplugin of assign and must meet that contract.
\mod_assign\privacy\assignsubmission_provider {
}
</code>

===Plugins which are typically called by a Moodle subsystem===

There are a number of plugintypes in Moodle which are typically called by a specific Moodle subsystem.

Some of these are ''only'' called by that subsystem, for example plugins which are of the ''plagiarism'' plugintype should never be called directly, but are always invoked via the ''core_plagiarism'' subsystem.

Conversely, there maybe other plugintypes which can be called both via a subsystem, and in some other fashion. We are still determining whether any plugintypes currently fit this pattern.

If you are developing a plugin which belongs to a specific subsystem, then you will have to look at the relevant plugin in order to determine the exact contract.

Each subsystem will define a new interface which extends the ''\core_privacy\local\request\plugin\subsystem_provider'' interface and it is up to that subsystem to define how they will interact with those plugins.

The principles remain the same, but the exact implementation will differ depending upon requirements.

''plagiarism/detectorator/classes/privacy/provider.php''

<code php>
<?php
// …
namespace plagiarism_detectorator\privacy;

class provider implements
// This plugin does export personal user data.
\core_privacy\local\metadata\provider,

// This plugin is always linked against another activity module via the Plagiarism API.
\core_plagiarism\privacy\plugin_provider {
}
</code>

===Exporting data===

Any plugin which stores data must also export it.

To cater for this the privacy API includes a ''\core_privacy\local\request\content_writer'', which defines a set of functions to store different types of data.

Broadly speaking data is broken into the following types:

* Data - this is the object being described. For example the post content in a forum post;
* Related data - this is data related to the object being stored. For example, ratings of a forum post;
* Metadata - This is metadata about the main object. For example whether you are subscribed to a forum discussion;
* User preferences - this is data about a site-wide preference;
* Files - Any files that you are stored within Moodle on behalf of this plugin; and
* Custom files - For custom file formats - e.g. a calendar feed for calendar data. These should be used sparingly.

Each piece of data is stored against a specific Moodle ''context'', which will define how the data is structured within the exporter.
Data, and Related data only accept the ''stdClass'' object, whilst metadata should be stored as a set of key/value pairs which include a description.

In some cases the data being stored belongs within an implicit structure. For example, one forum has many forum discussions, which each have a number of forum posts. This structure is represented by an ''array'' referred to as a ''subcontext''.

The ''content_writer'' must ''always'' be called with a specific context, and can be called as follows:

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …
use \core_privacy\local\request\writer;

writer::with_context($context)
->export_data($subcontext, $post)
->export_area_files($subcontext, 'mod_forum', 'post', $post->id)
->export_metadata($subcontext, 'postread', (object) ['firstread' => $firstread], new \lang_string('privacy:export:post:postread'));
</code>

Any text field which supports Moodle files must also be rewritten:

''mod/forum/classes/privacy/provider.php''

<code php>
<?php
// …
use \core_privacy\local\request\writer;

writer::with_context($context)
->rewrite_pluginfile_urls($postarea, 'mod_forum', 'post', $post->id, $post->message);

</code>

===Providing a way to delete user data===

Deleting user data is also implemented in the request interface. There are two methods that need to be created. The first one to remove all user data from a context, the other to remove user data for a specific user in a list of contexts.

====Delete for a context====

A context is given and all user data (for all users) is to be deleted from the plugin. This will be called when the retention period for the plugin has expired to adhere to the privacy by design requirement.�

''mod/choice/classes/privacy/provider.php''

<code php>
public static function delete_data_for_all_users_in_context(deletion_criteria $criteria) {
global $DB;
$context = $criteria->get_context();
if (empty($context)) {
return;
}
$instanceid = $DB->get_field('course_modules', 'instance', ['id' => $context->instanceid], MUST_EXIST);
$DB->delete_records('choice_answers', ['choiceid' => $instanceid]);
}
</code>

====Delete personal information for a specific user and context(s)====

An ''approved_contextlist'' is given and user data related to that user should either be completely deleted, or overwritten if a structure needs to be maintained. This will be called when a user has requested the right to be forgotten. All attempts should be made to delete this data where practical while still allowing the plugin to be used by other users.

''mod/choice/classes/privacy/provider.php''

<code php>
public static function delete_data_for_user(approved_contextlist $contextlist) {
global $DB;

if (empty($contextlist->count())) {
return;
}
$userid = $contextlist->get_user()->id;
foreach ($contextlist->get_contexts() as $context) {
$instanceid = $DB->get_field('course_modules', 'instance', ['id' => $context->instanceid], MUST_EXIST);
$DB->delete_records('choice_answers', ['choiceid' => $instanceid, 'userid' => $userid]);
}
}
</code>

===Difference between Moodle 3.3 and more recent versions===
Moodle 3.3 has a minimum requirement of php 5.6 and so type hinting and return type declarations are not supported in this version. Consequently the privacy API for this version does not have these features.
====What to do if you have one plugin that supports multiple features====
This is something that we have considered and we have put in place a polyfill. This gets around the restrictions of one version having type hinting and return type declarations while another does not.
====Example====
To use the polyfill include the legacy polyfill trait and create the necessary static methods but with an underscore (shown below).
<code php>
class provider implements
\core_privacy\local\metadata\provider,
\core_privacy\local\request\plugin\provider {

// This is a trait must be included.
use \core_privacy\local\legacy_polyfill;

// The required methods must be in this format starting with an underscore.
public static function _get_metadata(collection $collection) {
// Code for returning metadata goes here.
}
</code>

==See also==

* [[Subject Access Request FAQ]]
* [[:en:GDPR|GDPR]] in the user documentation

[[Category:GDPR]]
[[Category:API]]

Plugin contribution checklist

2017-12-27T03:05:45Z

Abgreeve: /* Namespace collisions - module exception */

{{Plugins development}}

Before approaching the [https://moodle.org/plugins Moodle plugins directory] and submitting your plugin (or a new plugin version), you are encouraged to go through the checklists below and fix eventual issues with your plugin. Doing so will make the reviewer of your plugin happy :-) and may have impact on how long your plugin has to spend in the approval queue before it lands smoothly.

== Meta-data ==

=== Plugin descriptions ===

* Have a meaningful description of your plugin prepared in English.
* You will need a short concise description (just a sentence or two) for the short description field, and another elaborated one for the full description field.
* It is encouraged to have the same info at the plugin record page and in its <tt>README</tt> file.

=== Supported Moodle versions ===

* New plugins submitted into the plugins directory must support at least one of the currently maintained Moodle version.
* See [[Releases]] for the list of currently maintained Moodle versions (policy issue MDL-47579).

=== Code repository name ===

* Provide a consistent experience for other Moodle developers and site administrators - follow the repository naming convention for Moodle plugins: <tt>moodle-{plugintype}_{pluginname}</tt>.

=== Source control URL ===

* Facilitate sharing and further development of your open-source plugin - provide publicly accessible URL of your code repository.
* Github is a choice of most Moodle plugin developers.

=== Bug tracker URL ===

* Encourage participation and have a place to report issues, bugs, make feature requests, or suggest other types of improvements.
* Both [[Tracker guide|Moodle tracker]] and [https://guides.github.com/features/issues/ Github issues] are common.
* See [[Plugin_contribution#Tracker]] if you want to use the Moodle tracker.

=== Documentation URL ===

* Have a place where further documentation of your plugin will be located.
* [[Plugin documentation|Moodle docs]] is preferred location, [https://guides.github.com/features/wikis/ Github wikis] or your own website will work, too.

=== Illustrative screenshots ===

* Capture some screenshots of your plugin to help folks get an idea of what it looks like when installed.
* We will use these screenshots at more places in the plugins directory in the future.

=== Licensing ===

* All files that implement the interface between the Moodle core and the plugin must be licensed under GNU GPL v3 (or later).
* Additional files contained in the plugin ZIP package (such as third party libraries used by the plugin, or included media) may eventually use other license as long as it is [http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses GPL compatible]. See [[Plugin files#thirdpartylibs.xml]] for how to do it.
* Note that binary files violate GPL unless the source code is also included or available (e.g. Java classes or Flash).

=== Subscription needed ===

* If the plugin requires a third-party subscription based service, make sure the description states it very clearly.
* To allow the testing of the plugin functionality, prepare demo credentials (such as API keys etc) so that the approval team can use them to see the plugin in action.

== Usability ==

=== Installation ===

* Make sure the plugin installs smoothly from the ZIP package using the in-build plugin installation interface.
* If any non-standard post-installation steps are needed, make sure they are clearly listed in both plugin description and the <tt>README</tt> file.

=== Dependencies ===

* If the plugin depends on another additional plugin, make sure it is clearly stated in the description and in the <tt>README</tt> file.
* Also declare the dependency explicitly in the plugin's [[version.php]] file.

=== Functionality ===

* Test the plugin functionality with full developer debugging enabled.
* Make sure the code does not throw unexpected PHP warnings, notices or even errors.

=== Cross-DB compatibility ===

* Test the plugin with multiple database engines supported by Moodle.
* At very least, the plugin is supposed to work with MySQL and PostgreSQL unless reasons are clearly explained in the description and the <tt>README</tt> file (such as the plugin is a wrapper for third-party DB specific utility).
* [[Data manipulation API]] helps you to ensure cross-db compatibility.

== Coding ==

=== Coding style ===

* It is encouraged to follow [[Coding style|Moodle coding style]] and other [[Coding|coding guidelines]].
* It's not always possible to achieve "all greens" in automated syntax checks (especially when third party libraries are involved) but you should aim to it.
* Consistent style helps others to read and understand your code (not only during the approval review).

=== English ===

* Moodle is an international project. To facilitate sharing, reviews of and contributions to your code, all comments, variable names, function names etc. should be in English.

=== Boilerplate ===

* All files should contain the common boilerplate at the beginning with explicit GPL license statement.
* See the section [[Coding_style#Files]] for the template.

=== Copyrights ===

* All files should contain the <tt>@copyright</tt> tag with your name.
* If you are re-using someone else's file, keep the original copyrights reference to the previous author and add your name as a copyright holder.
* Both things should be clear: (1) that it is you to be blamed for the file code and (2) that your work is based on someone else's work.

=== CSS styles ===

* Make sure to use properly namespaced selectors so that your style sheets can be safely concatenated with the ones provided by other plugins.
* Plugin specific CSS selectors are needed to make sure that your styling does not accidentally affect other parts of Moodle outside your plugin scope.
* For example, instead of the selector <tt>.contentarea</tt> it is better to use something like <tt>.path-mod-mymodule .contentarea</tt> as the .path-* classes are automatically added by the Moodle core renderers to the HTML <body> tag.

=== Namespace collisions ===

* Check that all your DB tables, settings, functions, classes, constants and variables are named correctly. In most cases their names must start with the plugin type and plugin name, as in <tt>block_yourname_something</tt> (so called [[Frankenstyle|frankenstyle]] prefix). Modules are an exception to this rule as functions such as get_coursemodule_from_id() rely on there being no preface of 'mod'.
* Do not define own classes, functions, variables or constants in the global PHP scope without the valid frankenstyle prefix.
* See [[Coding style#Functions and Methods]] for details.

=== Settings storage ===

* Check that your settings are stored in the table <tt>config_plugins</tt> and not in the main <tt>config</tt> table.
* This helps to avoid <tt>$CFG</tt> bloat and potential collisions.
* Use <tt>get_config()</tt> to pull the settings data out of the <tt>config_plugins</tt> table.
* In the file <tt>settings.php</tt>, the setting names are supposed to be <tt>plugintype_pluginname/settingname</tt> (note the slash) and not <tt>plugintype_pluginname_settingname</tt> or even just <tt>settingname</tt>.
* If you eventually need to change the settings yourself, use <tt>set_config()</tt>.

=== Strings ===

* Avoid hard-code texts in the code, always use <tt>get_string()</tt>.
* Just the English strings should ship with the plugin. All other translations are supposed to be submitted as contributions at [https://lang.moodle.org https://lang.moodle.org] once your plugin is approved - see [[Translating plugins]].
* Your code must not rely on trailing and leading whitespace in strings.
* The string file must be considered as pure data file with the syntax <tt>$string['id'] = 'value';</tt>. No other PHP syntax such as [http://php.net/manual/en/language.operators.string.php concatenation], [http://php.net/manual/en/language.types.string.php heredoc and nowdoc] is supported by the tools that we use when processing your strings (even if it may work in Moodle itself).
* The English language pack (lang/en/) in Moodle does not use "Capitalised Titles".

=== Security ===

* Never trust the user input.
* Do not access superglobals like <tt>$_REQUEST</tt> directly, use wrappers like <tt>required_param()</tt> with correct type declared to sanitize input.
* Always use placeholders in custom SQL queries (<tt>?</tt> or <tt>:named</tt>).
* Always check for the <tt>sesskey</tt> before taking an action on submitted data.
* Check for <tt>require_login()</tt>.
* Always check that the user has appropriate capabilities before displaying the widgets ''and'' before taking the actual action.
* Avoid using malicious functions like <tt>call_user_func()</tt>, <tt>eval()</tt>, <tt>unserialize()</tt> and so on, especially when they would be called with user-supplied data.

== See also ==

* [https://moodle.org/mod/forum/discuss.php?d=263614 Some common issues in submitted plugins] post at the Plugins traffic forum at moodle.org

Moodle 3.3 release notes

2017-12-22T00:34:32Z

Abgreeve: /* Server requirements - utf8mb4 is not a requirement for 3.3 */

[[Releases]] > {{FULLPAGENAME}}

Release date: 15 May 2017

Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%223.3%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in 3.3].

See our [https://docs.moodle.org/33/en/New_features New Features page] for a more user-friendly introduction to Moodle 3.3 with screenshots.

If you are upgrading from previous version, make sure you read the [https://docs.moodle.org/33/en/Upgrading Upgrading] documentation.

==Server requirements==

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

* Moodle upgrade: Moodle 2.7 or later (if upgrading from earlier versions, you must upgrade to 2.7.14 as a first step)
* PHP version: minimum PHP 5.6.5. ''Note: minimum PHP version has increased since Moodle 3.1''. PHP 7.0.x and 7.1.x are supported but have some [https://docs.moodle.org/dev/Moodle_and_PHP7#Can_I_use_PHP7_yet.3F engine limitations].
* PHP extensions '''openssl''' and '''fileinfo''' are now required in Moodle 3.3 (they were recommended in 3.2)
* If you use PostgreSQL the minimum supported version is now 9.3 (was 9.1 in Moodle 3.2)
* (Recommendation only) If you use MySQL or MariaDB, make sure your database supports full UTF-8 (utf8mb4) if you install a new instance of Moodle. CLI script may be used to convert to utf8mb4 if you're upgrading. You may choose to keep using 'utf8_*', but then a warning will show that the database isn't using full UTF-8 support and suggest moving to 'utf8mb4_unicode_ci'. See [[:en:MySQL full unicode support|MySQL full unicode support]] for details.

=== 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.

{| class="nicetable"
|-
! Database
! Minimum version
! Recommended
|-
| [http://www.postgresql.org/ PostgreSQL]
| 9.3
| Latest
|-
| [http://www.mysql.com/ MySQL]
| 5.5.31
| Latest
|-
| [https://mariadb.org/ MariaDB]
| 5.5.31
| Latest
|-
| [http://www.microsoft.com/en-us/server-cloud/products/sql-server/ Microsoft SQL Server]
| 2008
| Latest
|-
| [http://www.oracle.com/us/products/database/overview/index.html Oracle Database]
| 10.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.3:
* Internet Explorer 10 and below
* Safari 7 and below

==Major features==

=== Highlights ===

* MDL-55611 - New [https://docs.moodle.org/33/en/Course_overview Course overview] dashboard block featuring timeline of events
* MDL-58220 - Make use of [https://docs.moodle.org/33/en/OAuth_2_services OAuth 2 services] to allow users to [https://docs.moodle.org/33/en/OAuth_2_authentication authenticate with Google G-Suite or Microsoft Office accounts] and manage files from associated drives
* MDL-39913 - New [https://docs.moodle.org/33/en/Assignment_settings Assignment setting] for restricting submission file types
* MDL-4782 - [https://docs.moodle.org/33/en/Stealth_activities "Stealth mode"] for resources/activities in a course - not displayed on the course page but available for students
* MDL-40759 - New Font Awesome icon font for all icons in Moodle

=== For teachers ===

* MDL-58138 - [https://docs.moodle.org/33/en/Activity_completion_settings Activity completion settings] for setting activity completion defaults and bulk editing of completion requirements
* MDL-48771 - [https://docs.moodle.org/33/en/Building_Quiz Quiz activity]: Option to delete multiple questions
* MDL-53814 - Quiz activity: Question type icons are displayed in the quiz manual grading overview
* MDL-55459 - [https://docs.moodle.org/33/en/Assignment_settings Assignment activity]: Annotated PDF comments are collapsible
* MDL-23919 - [https://docs.moodle.org/33/en/Database_activity_settings Database activity]: The setting "Required entries" is now an activity completion condition
* MDL-57769 - Topic and weeks course formats: After a course is created, sections can be added and removed only from the course page (it is no longer possible to have "orphaned" activities)
* MDL-46929, MDL-57456, MDL-57457 - [https://docs.moodle.org/33/en/Using_Forum Forum posts], [https://docs.moodle.org/33/en/Using_Glossary glossary entries] and [https://docs.moodle.org/33/en/Book_settings book chapters] may be tagged
* MDL-56251 - For courses in weekly format, a new [https://docs.moodle.org/33/en/Course_settings course setting] allows for the course end date to be calculated automatically
* MDL-47354 - Allow the page size in the Single view report to be configurable

=== Backup and restore ===

* MDL-34859 - Add site defaults for all restore settings, improve UI around "Overwrite course configuration" select
* MDL-40838 - Allow to restore non-default enrollment methods without restoring users
* MDL-57769 - When restoring/importing big courses in Weeks and Topics formats into small existing courses ajust the number of sections automatically

=== For administrators ===

Please read carefully: [https://docs.moodle.org/33/en/Upgrading#Possible_issues_that_may_affect_you_in_Moodle_3.3 Possible issues that may affect you in Moodle 3.3]

* MDL-46375 - Support for storing files not on the local drive (there are no open-source solutions at the moment, developer's help is required to implement custom cloud storage)
* MDL-55528, MDL-58280 - New [https://docs.moodle.org/33/en/Document_converters document converter] plugin type allows alternatives to unoconv, such as the [https://docs.moodle.org/33/en/Google_Drive_converter Google Drive converter]
* MDL-55980 - Run individual scheduled tasks from web interface
* MDL-57896 - CLI wrapper for get_config() and set_config() methods
* MDL-57789 - Use Cache-Control: immutable when serving files
* MDL-37765 - New capability to bypass access restrictions, separated from capability to view hidden activities
* MDL-57913 - Convert external database authentication synchronisation to scheduled task

==== Plugins removal and deprecation ====

* The repository Skydrive is deprecated; please migrate to the newer [https://docs.moodle.org/33/en/OneDrive_repository OneDrive repository]
* The Dashboard block Course overview is replaced with a new block [https://docs.moodle.org/33/en/Course_overview Course overview] which is a different plugin. If you want to use the old block, you need to download and install it from https://moodle.org/plugins/block_course_overview

=== Mobile app support ===

* MDL-57410 - Allow admins to add new external links to pages in the main menu of the Mobile app
* MDL-57408 - Add new settings for allowing renaming strings in the Mobile app
* MDL-49423 - Add new settings for disabling Mobile app functionalities
* MDL-57759 - Allow offline attempts via the Mobile app in the lesson module
* MDL-57162 - Support Native App install banners for Android as well as iOS for the mobile app

=== Other improvements ===

* MDL-33483 - Google Docs repository: Save Doc files in different formats to RTF
* MDL-42266 - Improve the list of maximum file size options for file uploads
* MDL-51853 - Calendar subscriptions from imported files should be editable
* MDL-41729 - Add ability to change passwords for users using Shibboleth
* MDL-57572, MDL-57570, MDL-57355 - Redis and static caches performance improvements if igbinary library is installed
* MDL-56808 - SCORM module: Performance improvements when running SCORM 1.2 packages
* MDL-57686 - Add support for PDO databases in external database authentication
* MDL-57638 - RSS Block: RSS feeds are more heavily cached and correctly respect skip values

===For developers===

* MDL-55528 - New plugin type 'fileconverter' for file conversions, unoconv is now a plugin that can be replaced with scalable commercial solutions (see [[File Converters]])
* MDL-40759 - Font Awesome icon font is used for all icons in Moodle (see [[Moodle_icons#Font_awesome_icons|Moodle icons]])
* MDL-46375 - Support for storing files not on the local drive is implemented by allowing to override functionality of file_storage and stored_file classes (see [[File System API]])
* MDL-12689 - Convert all authentication plugins to use settings.php (see [https://github.com/moodle/moodle/blob/master/auth/upgrade.txt upgrade.txt])
* MDL-53978 - Add extra plugin callbacks for every major stage of page render (see [https://github.com/moodle/moodle/commit/5ebd1fb9768969956c9131df4274f9cdff7f0134 commit])
* MDL-58138 - Course modules may provide additional callbacks to participate in bulk editing of activities completion rules in a course
* MDL-58220 - Better office integration
* MDL-45584 - Multiple caches can be instantiated with the same definition but with different identifiers
* MDL-57769 - Course formats: Attribute 'numsections' was removed from topics and weeks, other course formats may want to implement similar changes
* MDL-55956 - Priority field for the calendar events allowing to specify the priority of overrides
* MDL-58566 - New methods for retrieving calendar events
* MDL-55941 - New element to select first name of first/last names is implemented in tablelib or can be used by developers elsewhere ([https://github.com/moodle/moodle/blob/master/lib/templates/initials_bar.mustache template])
* MDL-56519 - Lint behat .feature files
* MDL-57273 - New classes (core\persistent, core\form\persistent, core\external\exporter, \core\external\persistent_exporter) used to represent a data-model and export that data in a standard format for webservices (previously was used in competencies) (see [[Persistent form]], [[Persistent]], [[Exporter]])
* MDL-57490 - Removed several legacy JS functions from javascript-static.js
* MDL-57690 - mcore YUI rollup is no longer included on every single Moodle page (see [[https://moodle.org/mod/forum/discuss.php?d=346520 forum post]])

==== Upgrading plugins ====

'''1. Check for changes in core APIs'''

Read lib/upgrade.txt to check for the deprecations and core API changes, make sure you applied them to your plugin. Note that entries there are not sorted by priority but rather by integration time. Below is the list of upgrade.txt files that contain information about upgrading from Moodle 3.2 to Moodle 3.3 (note that if you upgrade from earlier versions there may be more files):

* [https://raw.githubusercontent.com/moodle/moodle/master/lib/upgrade.txt lib/upgrade.txt] changes to various core APIs, deprecations, functions removal
* [https://raw.githubusercontent.com/moodle/moodle/master/admin/upgrade.txt admin/upgrade.txt] changes to administration-related functions
* [https://raw.githubusercontent.com/moodle/moodle/master/cache/upgrade.txt cache/upgrade.txt] changes to Cache API
* [https://raw.githubusercontent.com/moodle/moodle/master/calendar/upgrade.txt calendar/upgrade.txt] changes to Calendar API
* [https://raw.githubusercontent.com/moodle/moodle/master/competency/upgrade.txt competency/upgrade.txt] changes to Competency API
* [https://raw.githubusercontent.com/moodle/moodle/master/course/upgrade.txt course/upgrade.txt] changes to course-related functions

For the next releases we are thinking about improving the format of upgrade.txt notes, please have your say on policy issue MDL-58879

'''2. Check for changes in the API of your plugin type'''

Below is the list of plugin types that had API changes between Moodle 3.2 and 3.3:
* [https://raw.githubusercontent.com/moodle/moodle/master/auth/upgrade.txt auth/upgrade.txt] Authentication plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/blocks/upgrade.txt blocks/upgrade.txt] Block plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/course/format/upgrade.txt course/format/upgrade.txt] Course format plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/enrol/upgrade.txt enrol/upgrade.txt] Enrolment method plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/media/upgrade.txt media/upgrade.txt] Media player plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/mod/upgrade.txt mod/upgrade.txt] Activity module plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/question/type/upgrade.txt question/type/upgrade.txt] Question types plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/repository/upgrade.txt repository/upgrade.txt] Repository plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/theme/upgrade.txt theme/upgrade.txt] Themes

'''3. Check for changes in the depended plugins'''

If your plugin depends on another plugin or calls methods from another plugin, read upgrade.txt in this plugin directory (if it exists). Below is the list of standard plugins that had changes between Moodle 3.2 and 3.3:

Due to changes in Authentication plugins settings all standard auth plugins were updated: [https://raw.githubusercontent.com/moodle/moodle/master/auth/cas/upgrade.txt auth_cas], [https://raw.githubusercontent.com/moodle/moodle/master/auth/db/upgrade.txt auth_db], [https://raw.githubusercontent.com/moodle/moodle/master/auth/email/upgrade.txt auth_email], [https://raw.githubusercontent.com/moodle/moodle/master/auth/fc/upgrade.txt auth_fc], [https://raw.githubusercontent.com/moodle/moodle/master/auth/imap/upgrade.txt auth_imap], [https://raw.githubusercontent.com/moodle/moodle/master/auth/ldap/upgrade.txt auth_ldap], [https://raw.githubusercontent.com/moodle/moodle/master/auth/manual/upgrade.txt auth_manual], [https://raw.githubusercontent.com/moodle/moodle/master/auth/mnet/upgrade.txt auth_mnet], [https://raw.githubusercontent.com/moodle/moodle/master/auth/nntp/upgrade.txt auth_nntp], [https://raw.githubusercontent.com/moodle/moodle/master/auth/none/upgrade.txt auth_none], [https://raw.githubusercontent.com/moodle/moodle/master/auth/pam/upgrade.txt auth_pam], [https://raw.githubusercontent.com/moodle/moodle/master/auth/pop3/upgrade.txt auth_pop3], [https://raw.githubusercontent.com/moodle/moodle/master/auth/shibboleth/upgrade.txt auth_shibboleth]

Other standard plugins that were updated in 3.3: [https://raw.githubusercontent.com/moodle/moodle/master/admin/tool/lp/upgrade.txt tool_lp], [https://raw.githubusercontent.com/moodle/moodle/master/admin/tool/mobile/upgrade.txt tool_mobile], [https://raw.githubusercontent.com/moodle/moodle/master/enrol/ldap/upgrade.txt enrol_ldap], [https://raw.githubusercontent.com/moodle/moodle/master/mod/assign/upgrade.txt mod_assign], [https://raw.githubusercontent.com/moodle/moodle/master/mod/data/upgrade.txt mod_data], [https://raw.githubusercontent.com/moodle/moodle/master/mod/feedback/upgrade.txt mod_feedback], [https://raw.githubusercontent.com/moodle/moodle/master/mod/forum/upgrade.txt mod_forum], [https://raw.githubusercontent.com/moodle/moodle/master/mod/lesson/upgrade.txt mod_lesson]

'''4. Do a smoke test of your plugin with developer debugging mode'''

'''5. Run all behat and phpunit tests'''

==See also==
*[[Moodle 3.2 release notes]]

[[Category:Release notes]]
[[Category:Moodle 3.3]]

[[fr:Notes de mise à jour de Moodle 3.3]]
[[es:Notas de Moodle 3.3]]

Moodle libraries credits

2017-11-01T01:19:11Z

Abgreeve: /* HTML Purifier - update of version */

Some of Moodle's libraries were written by other people, and are being redistributed as part of Moodle under their respective open source licenses that thankfully allow us to do so. Thanks to the authors of all these excellent products - without them Moodle would be missing important functionality. Copyright information for each package is included below:

==ADOdb==

''lib/adodb''

Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.

Version: 5.20.9

@copyright (c) 2000-2013 John Lim (jlim#natsoft.com). All rights reserved.

@copyright (c) 2014 Damien Regad, Mark Newnham and the ADOdb community

License: Dual LGPL and BSD-style

http://adodb.sourceforge.net

==Bennu==

"lib/bennu"

Bennu is an object-oriented library written in PHP that implements the iCalendar standard (RFC 2445).

Version: 0.1 (customized since then)

Copyright (c) 2005, Jon Papaioannou

License: LGPL 2.1+

http://bennu.sourceforge.net/

==Amazon S3==

''repository/s3/S3.php''

A standalone Amazon S3 (REST) client for PHP 5.2.x using CURL that does not require PEAR.

Version: 0.5.1

Copyright (c) 2013, Donovan Schönknecht

License: BSD 2-Clause

https://github.com/tpyo/amazon-s3-php-class/releases

==CAS==

''auth/cas/CAS''

phpCAS library to support CAS authentication plugin

Copyright Jasig

License: Apache License 2.0

https://wiki.jasig.org/display/CASC/phpCAS

==Chart.js==

''lib/amd/src/chartjs-lazy.js''

Simple yet flexible JavaScript charting for designers & developers

Version: 2.7.0

Copyright 2016 Nick Downie

License: MIT

http://www.chartjs.org

==EvalMath==

''lib/evalmath''

Class to safely evaluate math expressions

Copyright Miles Kaufmann

License: BSD

http://www.twmagic.com/

==FLV player==

''filter/mediaplugin/flvplayer.swf''

Flash movie to play FLV files

Copyright Jeroen Wijering

License: GNU GPL

http://www.jeroenwijering.com

(This library is not currently used in Moodle)

==FPDF Class==

''lib/fpdf''

Class to generate PDF files

Version: 1.54

Copyright Olivier PLATHEY

License: Freeware

http://www.setasign.com/products/fpdi/downloads

== GeoIp2 ==

''lib/maxmind/GeoIp2''

Library for precessing of GeoIP data files

Version: 2.6.0

Copyright MaxMind

License: Apache 2.0

https://github.com/maxmind/GeoIP2-php

==Google APIs==

"lib/google"

Library Google APIs Client Library for PHP

Version: 1.1.7

License: Apache License Version 2.0

https://github.com/google/google-api-php-client

==Graph Class==

''lib/graphlib.php''

Class to draw line, point, bar, and area graphs, including numeric x-axis and double y-axis.

Version: 1.6.3 (with modifications)

Copyright © 2000 Herman Veluwenkamp (''hermanV AT mindless DOT com'')

License: LGPL

==Horde==

''lib/horde''

Library used by the inbound e-mail handling system.

Version: 5.2.7

Copyright © Horde LLC

License: LGPL

http://www.horde.org/

==html2text==

''lib/html2text''

PHP script to convert HTML into an approximate text equivalent

Version: 4.1.0

Copyright (c) 2005-2007 Jon Abernathy <jon@chuggnutt.com>

License: GNU GPL

https://github.com/mtibben/html2text.git

==htmlArea==

''lib/editor''

Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla

Version: 3.0 beta (with modifications)

Copyright © 2002 interactivetools.com, inc.

License: htmlArea License (based on BSD license)

(This library is not currently used in Moodle)

==HTML Purifier==

"lib/htmlpurifier"

Filters HTML.

Version: 4.9.3

License: LGPL

==IP-Atlas==

''lib/ipatlas''

PHP scripts to show the location of an IP address on a map.

Version: 1.0 (with modifications)

Copyright © 2002 Ivan Kozik

License: GNU GPL

http://www.xpenguin.com/ip-atlas.php

(This library is not currently used in Moodle)

==jQuery==

''lib/jquery''

jQuery is a fast, small, and feature-rich JavaScript library widely used on moodle.

Version: 3.2.1

Copyright: 2016 The jQuery Foundation

License: MIT

https://jquery.com

==jQuery migrate==

''lib/jquery/jquery-migrate-1.4.0.js''

Library used migrate older jQuery code to jQuery 3.0.

Version: 1.4.0

Copyright: 2016 The jQuery Foundation and other contributors

License: MIT

https://github.com/jquery/jquery-migrate

==jQuery UI==

''lib/jquery/ui-1.12.1/''

jQuery UI is a set of user interface interactions, effects, widgets, and themes built on top of the jQuery library.

Version: 1.12.1

Copyright: 2016 The jQuery Foundation and other contributors

License: MIT

https://github.com/jquery/jquery-migrate

==Services_JSON==

''lib/json''

Allows PHP->JS communication via JSON

Version: 1.3.1

Copyright © 2005 Michal Migurski

License: Modified BSD (GPL-compatible)

http://pear.php.net/pepr/pepr-proposal-show.php?id=198

(This library is not currently used in Moodle)

==kses==

''lib/kses.php''

HTML/XHTML filter that only allows some elements and attributes

Version: 0.2.2

Copyright © 2002, 2003, 2005 Ulf Harnhammar

License: GNU GPL

http://sourceforge.net/projects/kses

(This library is not currently used in Moodle)

==less.php==

The less.php is a PHP port of the official LESS processor used by moodle themes.

''lib/lessphp''

Version: 1.7.0.10

License: Apache 2.0

http://lessphp.typesettercms.com/

Copyright: Matt Agar and Martin Jantošovič
==loglevel.js==

Minimal lightweight simple logging for JavaScript.

Version 1.5.1

Copyright (c) 2013 Tim Perry

License: MIT

https://github.com/pimterry/loglevel/

==MathJax==

JavaScript filter library for displaying LaTeX, AsciiMath notation, and MathML.

Not actually included in Moodle. Instead, Moodle [[:en:MathJax filter|has a setting]] for where the library is located to be loaded from. It is currently pointing to the Cloudflare CDN by default.

© Copyright 2009 - 2017 The MathJax Consortium

* Default MathJax version: 2.7.2 (Moodle 3.4)
* License: Apache 2.0
* Homepage: https://www.mathjax.org/

==MatthiasMullie\Minify==
CSS & JavaScript minifier, in PHP

Version 1.3.37

License: MIT

https://github.com/matthiasmullie/minify

==mimeTeX==

''filter/tex''

Compiled C program to convert TeX into GIFs

Version: 1.4

Copyright © 2002-2004 John Forkosh Associates, Inc

License: GNU GPL

http://www.forkosh.com/mimetex.html

==Mustache.js==

"lib/amd/src/mustache.js"

JS library for displaying mustache templates.

Version: 2.3.0

Copyright (c) 2009 Chris Wanstrath (Ruby)

Copyright (c) 2010-2014 Jan Lehnardt (JavaScript)

Copyright (c) 2010-2015 The mustache.js community

License: MIT

https://github.com/janl/mustache.js/releases

==Mustache==

"lib/mustache"

PHP library for displaying mustache templates.

Version: 2.12.0

Copyright (c) 2010-2016 Justin Hileman

License: MIT

https://github.com/bobthecow/mustache.php/releases

==mp3player==

''lib/mp3player''

Flash movie to play streaming MP3s

Copyright © 2005 Andrew Walker

License: GNU GPL

(This library is not currently used in Moodle)

==overlibmws==

''lib/overlib.js''

Javascript library to enable DHTML popups, floating windows, events etc

Version: July 2004

Copyright © 2002-2004 Foteos Macrides

Copyright © 1998-2004 Erik Bosrup

License: Artistic Open Source License

http://www.macridesweb.com/oltest/

(This library is not currently used in Moodle)

==PclZip==

''lib/pclzip''

Class to create, manage and unpack zip files.

Version: 2.4 RC1

Copyright © 2004 Vincent Blavet (''vincent AT phpconcept DOT net'')

License: GNU GPL

http://www.phpconcept.net

==PEAR OLE Classes==

''lib/pear''

Class to write Excel files

Version: 0.5

Copyright © 2004 Xavier Noguer

License: PHP (plus special exemption for Moodle to make it compatible)

http://pear.php.net/package/OLE

(This library is not currently used in Moodle)

==PEAR Spreadsheet_Excel_Writer==

''lib/pear''

Class to write Excel files

Version: 0.9.1

Copyright © 2004 Xavier Noguer and Mika Tuupola

License: LGPL

http://pear.php.net/package/Spreadsheet_Excel_Writer

(This library is not currently used in Moodle)

==PEAR HTML_Quickform==

''lib/pear''

Class to write forms

Version: 3.2.6

Copyright © 2004 Bertrand Mansion, Adam Daniel, Alexey Borzov

License: PHP (plus special exemption for Moodle to make it compatible)

http://pear.php.net/package/HTML_Quickform

==PEAR HTML_Quickform_Renderer_Tableless==

''lib/pear''

Class to render forms without tables

Version: 0.3.4

Copyright © 2005 Mark Wiesemann

License: PHP (plus special exemption for Moodle to make it compatible)

http://pear.php.net/package/HTML_Quickform_Renderer_Tableless

==PEAR HTML_QuickForm_DHTMLRulesTableless==

''lib/pear''

Class to render validation notices with dhtml

Version: 0.1.2

Copyright © 2005 Alexey Borzov, Adam Daniel, Bertrand Mansion, Justin Patrin, Mark Wiesemann

License: PHP (plus special exemption for Moodle to make it compatible)

http://pear.php.net/package/HTML_QuickForm_DHTMLRulesTableless

==PEAR HTML_Common==

''lib/pear''

Class with many common HTML functions (used by HTML Quickform)

Version: 0.3.4

Copyright © 2004 Adam Daniel, Bertrand Mansion, Klaus Guenther, Alexey Borzov

License: PHP (plus special exemption for Moodle to make it compatible)

http://pear.php.net/package/HTML_Common

==PEAR XML_Parser==

''lib/pear''

Class implementing one handy (sax-expat) XML parser

Version: 1.3.2

Copyright © 2004-2008 The PHP Group & Stephan Schmidt

License: New BSD License

http://pear.php.net/package/XML_Parser

(This library is not currently used in Moodle)

==PHP-CSS-Parser==

''lib/php-css-parser''

A Parser for CSS Files written in PHP.

Version: 8.1.0

Copyright (c) 2011 Raphael Schweikert, http://sabberworm.com/

License: MIT

https://github.com/sabberworm/PHP-CSS-Parser

==PHPExcel==

''lib/phpexcel/PHPExcel.php''

Library to read, write and create spreadsheet documents in PHP.

Version 1.8.1

Copyright © 2006 - 2015 PHPExcel
License: LGPL

https://github.com/PHPOffice/PHPExcel

==PHP mailer==

''lib/class.phpmailer.php''

Class for sending email using either sendmail, PHP mail(), or SMTP. Methods are based upon the standard AspEmail(tm) classes.

Version 6.0.1

Copyright © 2003 Brent R. Matzelle (''bmatzelle AT yahoo DOT com'')
License: LGPL

http://phpmailer.sourceforge.net
https://github.com/PHPMailer/PHPMailer/releases

==PHP Markdown==

''lib/markdown.php''

Functions to convert from the Markdown text format into clean XHTML.

Version: 1.7.0 (with modifications)

* @copyright 2004-2016 Michel Fortin <https://michelf.com/projects/php-markdown/>

* @copyright (Original Markdown) 2004-2006 John Gruber <https://daringfireball.net/projects/markdown/>
All rights reserved.

License: BSD

http://www.michelf.com/projects/php-markdown/

==RequireJS==

''/lib/requirejs/''

RequireJS is a JavaScript file and module loader.

Version 2.3.5

License: new BSD or MIT

http://requirejs.org/

==scssphp==

''/lib/scssphp/''

scssphp is a compiler for SCSS written in PHP.

Version: 0.6.5

Copyright (c) 2015 Leaf Corcoran

License: MIT

http://leafo.github.io/scssphp

==SimplePie==

"/lib/simplepie"

Simple Pie helps with blogs.

Version 1.5

License: BSD

https://github.com/simplepie/simplepie

==Snoopy==

''lib/snoopy''

A PHP net client

Version: 1.0

Copyright © 1999-2000 Monte Ohrt (''monte AT ispi DOT net'')
License: GNU LGPL

http://snoopy.sourceforge.com

(This library is not currently used in Moodle)

==SMTP class==

''lib/class.smtp.php''

Class that can be used to connect and communicate with any SMTP server. It implements all the SMTP functions defined in RFC821 except TURN.

Version: 03/26/2001

Copyright © 2001 Chris Ryan (''chris AT greatbridge DOT com'')

(This library is not currently used in Moodle)

==Spike PHPCoverage==

''lib/spikephpcoverage''

PHP code coverage reporting tool

Version: 0.8.2 (with modifications)

Copyright © 2004 SpikeSource Inc

License: LGPL

http://developer.spikesource.com/projects/phpcoverage

(This library is not currently used in Moodle)

==Spout==

"lib/spout"

Library for importing and exporting csv / excel / ODS files.

Version 2.7.3

License: Apache

https://github.com/box/spout/

==Typo3 Character Set Class==

''lib/typo3''

Class for conversion between charsets and multibyte-savy operations with strings.

Version: 4.7.19

Copyright © 2003-2005 Kasper Skaarhoj

Licence: GNU GPL

http://typo3.org/

==Yahoo User Interface==

''lib/yui''

The Yahoo! User Interface Library is a set of utilities and controls, in JavaScript, for building richly interactive web applications using techniques such as DOM scripting, DHTML and AJAX. The YUI Library also includes several core CSS resources.Set of user-interface components using AJAX, DHTML etc. We use it for all our AJAX-related stuff.

CVS version: 2.3.0

Copyright (c) 2006, Yahoo! Inc.

Licence: BSD

http://developer.yahoo.com/yui/

==Mustache.js==

"lib/amd/src/mustache.js"

JS library for displaying mustache templates.

Version: 2.2.1

Copyright (c) 2009 Chris Wanstrath (Ruby)

Copyright (c) 2010-2014 Jan Lehnardt (JavaScript)

Copyright (c) 2010-2015 The mustache.js community

License: MIT

https://github.com/janl/mustache.js/releases

==LTI Tool Provider Library for PHP==

"lib/ltiprovider/"

PHP library for communicating with learning tools as per the LTI specification.

Version: 3.0.2

© 2016 IMS Global Learning Consortium Inc. All Rights Reserved. Trademark Policy - (www.imsglobal.org/trademarks)

License: Apache 2

https://github.com/IMSGlobal/LTI-Tool-Provider-Library-PHP

==Popper.js==

"admin/tool/usertours/amd/src/popper.js"

A kickass library used to created Poppers in web applications

© 2016 Federico Zivolo and contributors

License: MIT

https://github.com/FezVrasta/popper.js

==Flexitour==

"admin/tool/usertours/amd/src/tour.js"

A JS library for tours

© 2016 Andrew Nicols and contributors

License: GPLv3

https://github.com/andrewnicols/flexitour

[[Category:Credits]]