Verifying an NES for Moodle Installation

After installing, confirm that the site is running NES for Moodle and that no upstream files were left behind.

From the Admin UI

Navigate to Site administration → Notifications. The Moodle version reported at the bottom of the page should show the NES release string, for example:

Moodle 4.3.13+4.3.12 (Build: 20260618)

4.3.13 is the NES version, 4.3.12 is the upstream Moodle release it was forked from, and Build: 20260618 is the date the build was cut - not the date the release was published.

Hover over that version link to see the numeric $version value in the tooltip. For this release it reads 2023100913.00, continuing the upstream sequence directly: Moodle 4.3.12 was 2023100912.00. Every NES release increments that number, so check it against the release notes entry for the version you installed.

From the Command Line

sudo -u www-data php admin/cli/cfg.php --name=release
sudo -u www-data php admin/cli/cfg.php --name=version

For this release, release returns 4.3.13+4.3.12 (Build: 20260618) and version returns 2023100913.00. The release value must carry the + origination suffix - without it, you are looking at an upstream build, not an NES one.

Checking the Version Files Directly

grep -E '^\$(version|release|branch|maturity)' version.php

Expected values for the NES for Moodle 4.3.13 release. Later releases increment $version and carry a newer build stamp - check the release notes entry for the version you installed:

Confirming the Database Update Ran

An install whose database update has not been applied will show pending notices in the admin interface.

From the admin interface: go to Site administration → Notifications. If an update is still pending, Moodle starts the update process - confirm it to apply the database update, then purge caches from Site administration → Development → Purge caches.

From the command line:

sudo -u www-data php admin/cli/upgrade.php
sudo -u www-data php admin/cli/purge_caches.php

Update Notifications

Moodle's built-in update check compares your site against download.moodle.org, which does not know about NES for Moodle releases. An NES for Moodle site therefore reports itself as out of date on Site administration → Notifications. That is expected.

Disable the check in config.php so the site stops reporting a false result and stops contacting download.moodle.org:

$CFG->disableupdatenotifications = true;
$CFG->disableupdateautodeploy = true;

The release notes are updated with every release, and HeroDevs emails customers a monthly release summary. If you are not receiving it, contact support@herodevs.com.