Five risk areas deserve attention when moving from Moodle 5.1 to 5.2: server requirements, plugins and themes, local core changes, deployment layout, and one critical gradebook bug affecting particular point releases. They are checks, not five failures that occur on every upgrade. Moodle has not published a ranked list or failure-rate study for 5.1-to-5.2 upgrades.
1. Server requirements can stop the upgrade
Moodle 5.2 accepts Moodle 4.4 or later as an upgrade source, so a site on 5.1 is within the supported version range. The server still has to meet the target release’s requirements. Moodle 5.2 was released on 20 April 2026; its documented minimums include PHP 8.3, the PHP sodium extension, max_input_vars of at least 5000, and 64-bit PHP. Database minimums include PostgreSQL 16 and Microsoft SQL Server 2019. See Moodle’s Moodle 5.2 upgrade overview and requirements.
As an Amazon Associate I earn from qualifying purchases.
Before changing code, open the site’s Environment report and check the PHP version, required extensions, PHP settings, architecture, and database version against the target release. Resolve any unmet requirement first; a compatible Moodle source version does not compensate for an incompatible server.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match2. Plugins and themes may not be ready for Moodle 5.2
Third-party plugins and themes are separate from Moodle core, and their compatibility cannot be assumed from the site’s current operation. Check every installed component for a Moodle 5.2-compatible release before replacing core code. Moodle’s upgrade guide specifically advises checking plugin updates and notes that custom plugins may require a separate update. See Moodle’s upgrade guide.
#1 Best Overall
Test the upgrade on a copy of production, including the site’s important course, enrolment, and reporting workflows. If outdated plugin code blocks the upgrade, Moodle documents deleting that code as a possible recovery option; this can leave the plugin’s associated data intact. It is not a blanket instruction to remove plugins: assess the consequences for that component and its data before acting.
3. Local edits to Moodle core need a managed merge
If developers have modified Moodle core files, replacing the code tree can overwrite or conflict with those changes. Inventory the modifications and plan a merge, rebase, or equivalent review before upgrading. Moodle’s Git upgrade guidance directs core customizations to its developer guidance: Git for Administrators.
Rank #2
Test the resulting code on a production copy. Do not assume that the standard upgrade process will preserve local edits or that a successful database upgrade means the custom behavior still works.
4. The public-directory change is from Moodle 5.1, not 5.2
Moodle’s /public web-root change was introduced with Moodle 5.1. For a site already running 5.1, it is not a new change in 5.2. It is still worth checking if the site has an unusual Git checkout, custom deployment process, or plugin placement.
Moodle says Git upgrades from 5.0 or earlier to 5.1 and later do not automatically move third-party plugins into /public. For a 5.1-to-5.2 upgrade, keep plugins in the correct locations for the existing deployment and confirm that the web server serves the intended public directory. See Moodle’s upgrade overview and Git guidance.
5. A specific gradebook bug affects Moodle 5.1.6 and 5.2.2
Moodle’s 5.2.3 release note documents a critical gradebook calculation issue in 5.1.6 and 5.2.2: penalty-based grades were not frozen as needed when recalculation occurred. Moodle 5.2.3, released on 14 September 2026, includes the fix and advises sites on 5.2.2 to upgrade promptly. This is a point-release issue, not a general failure of 5.1-to-5.2 upgrades. Read the Moodle 5.2.3 release notes for its specific guidance.
If the site has been on either affected release, check the release note’s instructions before making further grading changes, especially if affected grades may already have been recalculated. Prefer a fixed target such as 5.2.3 or later, and consult the notes for the exact target version.
Free tools Windows power users keep installed
One-click scans. No signup required.
Upgrade preflight and deployment sequence
- Confirm the source and target. Verify the installed Moodle version and use a supported path; Moodle 5.2 accepts Moodle 4.4 or later.
- Check the environment. Compare the Environment report’s PHP version, extensions, settings, architecture, and database version with Moodle 5.2 requirements.
- Audit extensions and custom code. Confirm plugin and theme compatibility, inventory core modifications, and test the complete upgrade on a copy of production.
- Back up before the live change. Back up Moodle code, uploaded files and
moodledata, and the database. Moodle’s upgrade overview covers the process. - Prepare the live site. Enable maintenance mode and wait for running cron processes to finish.
- Replace the code cleanly. Use the new Moodle release code rather than copying new files over the old tree. Retain the correct configuration and install compatible plugin versions in their intended locations.
- Run the upgrade. Complete it through the browser or command line. Moodle recommends command-line upgrading for large sites; its Git guidance also describes running the upgrade after changing code. See Git for Administrators.
- Check the gradebook exception. If the source or an intermediate version was 5.1.6 or 5.2.2, follow the 5.2.3 release-note guidance before further grading activity.
These are documented risk areas and operating requirements, not evidence that five failures are inevitable. Moodle’s official material does not quantify how often 5.1-to-5.2 upgrades fail, so the useful assessment is the site’s exact source and target point releases, server environment, extensions, code customizations, and deployment layout.
Quick Recap
Best Value
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.
