menu close

Newroad Moodle server site environment snapshots

moodle, server, client, newroad

Context

Taking a snapshot of the current (4.0.9) Moodle server site environment and the maximum upgradable version for the records and reference while migrating.

Current (4.0.9) server environment snapshot

  • Moodle: 4.0.9 (Build: 20230612) — OK. (Environment page is the correct place to verify requirements.) ([Moodle Docs][1])
  • PHP: 8.0.30 — supported for Moodle 4.0.x (4.0 supports PHP 7.3–8.0). ([Moodle Docs][2])
  • Database: MariaDB 11.4.8-MariaDB-cll-lve — above the minimum 10.2.29 for Moodle 4.0. ([moodledev.io][3])
  • Unicode: enabled — OK. (Required for Moodle; the environment tool checks this.) ([Moodle Docs][1])

PHP extensions (from the checks shown)

All listed core extensions are OK: iconv, mbstring, curl, openssl, tokenizer, soap, ctype, zip, zlib, gd, simplexml, spl, pcre, dom, xml, xmlreader, intl, json, hash, fileinfo, sodium, exif.

  • (These are part of the required/recommended set for 4.0.)* ([moodledev.io][4])

  • xmlrpc: status “Revisar” (Review). Note: the XML-RPC PHP extension is no longer needed by current Moodle core; legacy MNet features use a PHP library instead. Can be ignored unless specifically relying on XML-RPC services.

PHP settings (from the checks shown)

  • memory_limit — recommended value detected: OK.
  • file_uploads — recommended value detected: OK.
  • opcache.enable — recommended value detected: OK. (OPcache is recommended for performance.) ([Moodle Docs][6])

Perfect—this is exactly what we needed. Two things first:

About the dropdown (why you can’t pick > 4.2): That menu is driven by Moodle’s “Environment component.” You can fetch newer requirement definitions with Site administration → Server → Environment → “Update component”. If, after updating, your 4.0.9 site still shows only “4.2 arriba”, that’s just a limitation of the definitions available to that install—not a hard block on upgrading. The authoritative version requirements for 4.2 and 5.1 are in the official release notes (see citations). ([Moodle Docs][1])

Environment snapshot — checking for 4.2

  • Moodle: “Requires 3.11.8 or later; running 4.0.9” — OK. (This line confirms your current is an allowed source for 4.2.) ([moodledev.io][2])
  • Unicode: Enabled — OK. (Required.) ([Moodle Docs][1])
  • Database: MariaDB 11.4.8 — OK (4.2 requires ≥ 10.6.7). ([moodledev.io][2])
  • PHP: 8.0.30 — OK (4.2 requires ≥ 8.0.0; note 4.2.3+ also supports PHP 8.2). ([moodledev.io][2])
  • PHP extensions/settings (all shown as OK in your captures): iconv, mbstring, curl, openssl, tokenizer, soap, ctype, zip, zlib, gd, simplexml, spl, pcre, dom, xml, xmlreader, intl, json, hash, fileinfo, sodium, exif; plus settings memory_limit, file_uploads, opcache.enable — OK. (4.2 specifically calls out sodium required and exif recommended.) ([moodledev.io][2])

“Other checks” (one action item flagged)

  • “Assignment 2.2 subplugins present” — Review. 4.2+ will refuse to upgrade if legacy mod/assignment (Assignment 2.2) artifacts are present. The official checks say these must be uninstalled/removed before upgrading. (There’s a specific MoodleDocs page for this environment warning.) ([Moodle Docs][3])

Heads-up for later: for 5.1 the release notes require PHP ≥ 8.2, upgrade source ≥ 4.2.3, we’ll need to serve Moodle from the new /public webroot/router. We’ll verify these when we’re ready to plan the hop. ([moodledev.io][4])