Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Before upgrading Moodle 5.1 to 5.2, check five areas: server requirements, third-party plugins and themes, local core changes, deployment layout, and the exact point releases involved. These are documented risk areas—not five failures Moodle says happen on every upgrade. Moodle’s official materials do not provide a failure-rate study or rank the risks.
The most urgent exception is gradebook data: Moodle says Moodle 5.1.6 and 5.2.2 had a critical issue affecting penalty-based grade calculations. Moodle 5.2.3, released 14 September 2026, includes a fix. Administrators should identify their exact source and target versions before proceeding.
1. Server requirements can block the upgrade
Moodle 5.2 accepts Moodle 4.4 or later as the upgrade source, so a Moodle 5.1 site is within the supported version range. But the server must also meet Moodle 5.2’s requirements. If it does not, upgrade the relevant server components before replacing Moodle code. Moodle’s Moodle 5.2 server requirements specify PHP 8.3 or later, the sodium PHP extension, 64-bit PHP, and max_input_vars of at least 5000. The listed database minimums include PostgreSQL 16 and Microsoft SQL Server 2019.
Check Moodle’s Environment report and compare each item—including the database version and PHP settings—with the requirements for the target release. A server that currently runs Moodle 5.1 successfully is not necessarily ready for 5.2.
#1 Best Overall
2. Plugins and themes may not be ready for Moodle 5.2
Third-party plugins and themes are separate from Moodle core. A version that works on 5.1 may not be compatible with 5.2, and custom plugins may need their own updates. Moodle’s upgrade guide advises administrators to check for plugin updates before upgrading. Confirm that every installed plugin and theme has a version compatible with Moodle 5.2; do not treat the core upgrade as proof that extensions are ready.
If outdated plugin code prevents an upgrade, Moodle documents deleting that code as a possible recovery option. This can leave the plugin’s associated data intact, but it is not a universal cleanup recommendation: first determine whether the plugin is needed and follow the relevant plugin and Moodle guidance for your site.
3. Local changes to Moodle core need a deliberate merge
If developers have edited Moodle core files, replacing the code can overwrite those changes or make them incompatible with the new release. Inventory local changes and review them against the new core version. Moodle’s Git guidance for administrators directs core customizations to developer guidance; a managed merge, rebase, or equivalent review is needed rather than assuming an ordinary upgrade will preserve local edits.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Test the result on a copy of production before scheduling the live upgrade. Include locally modified code in the test, not just the database and standard plugins.
4. Check deployment layout and plugin placement
Moodle’s /public web-root change was introduced in Moodle 5.1; it is not a new change in Moodle 5.2. It still matters if the site has an unusual deployment or Git checkout. Moodle notes that Git upgrades from Moodle 5.0 or earlier to 5.1 or later do not automatically relocate third-party plugins into /public. For a site already on 5.1, verify that the web server serves the intended public directory and that plugins are in the correct locations for the current layout.
Use Moodle’s upgrade guidance and Git administration guidance for the deployment method in use. The key distinction is whether you are moving from an older release as part of the same deployment work or performing a standard 5.1-to-5.2 code upgrade.
5. Gradebook calculations require attention for specific point releases
Moodle’s Moodle 5.2.3 release notes document a critical gradebook issue in Moodle 5.2.2 and 5.1.6: penalty-based grades were not frozen as required when recalculation occurred. Moodle 5.2.3, released 14 September 2026, includes the fix, and Moodle advises sites on 5.2.2 to upgrade promptly.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →This is a version-specific data risk, not evidence that every 5.1-to-5.2 upgrade corrupts grades. If the site is on 5.1.6 or 5.2.2—or grades may have been recalculated while running one of those releases—read Moodle’s guidance for affected grade data before making further grading changes. Prefer a fixed target such as 5.2.3 or later, and review the notes for the exact target release.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Preflight checklist and upgrade sequence
- Confirm the versions. Record the installed Moodle version and verify that it is 4.4 or later. Identify whether the site has run 5.1.6 or 5.2.2, since those releases are relevant to the gradebook issue.
- Check the environment. In Moodle, review the Environment report and compare PHP, extensions, settings, architecture, and database version with the Moodle 5.2 requirements. Resolve unmet requirements before updating Moodle.
- Test and back up. Perform a trial upgrade on a copy of production. Before the live change, back up Moodle code, uploaded files and
moodledata, and the database. Moodle’s upgrade guide covers preparation and backup. - Prepare the live site. Put it in maintenance mode and wait for running cron processes to finish before changing code.
- Replace the code cleanly. Use the new Moodle release code rather than copying new files over the old code tree. Retain the correct configuration, use plugin versions compatible with the target, and verify the expected deployment and plugin locations.
- Run the upgrade. Complete it through the browser or command line. Moodle’s Git guidance describes running the upgrade after changing code; Moodle’s upgrade overview says command-line upgrading is advisable for large sites.
- Check the result. Confirm that the upgrade completed, review Moodle’s status and logs, and test key site functions, plugins, themes, and gradebook behavior before returning the site to normal use.
Use the current release notes for the precise source and target point releases. Moodle 5.2 was released on 20 April 2026; the published version and requirements may change as later point releases appear.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
