Verifying an NES for IOMAD Installation

After installing, confirm that the site is running NES for IOMAD and that no upstream files were left behind. IOMAD carries two version files - one for core and one for the bundled local_iomad plugin - so check both.

From the Admin UI

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

Moodle 4.3.4+4.3.3 (Build: 20260622)

4.3.4 is the NES version, 4.3.3 is the IOMAD release it was forked from, and Build: 20260622 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 2023100904.01. Every NES release increments that number, so check it against the release notes entry for the version you installed.

To confirm the bundled IOMAD plugin updated as well, go to Site administration → Plugins → Plugins overview and check the version reported for local_iomad.

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.4+4.3.3 (Build: 20260622) and version returns 2023100904.01. 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
grep -E '^\$plugin->(version|release)' local/iomad/version.php

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

Variable	Expected value
`$version`	`2023100904.01`
`$release`	`4.3.4+4.3.3 (Build: 20260622)`
`$branch`	`403`
`$maturity`	`MATURITY_STABLE`
`$plugin->version`	`2026062200`
`$plugin->release`	`4.3.4+4.3.3 (Build: 20260622)`

If $branch is not 403, plugin compatibility checks will fail. If $release does not contain the + origination suffix, the upstream distribution has likely been copied back over the NES files. If core reports the NES release but local_iomad does not, the database update has not been applied.

Site administration → Plugins → Plugins overview still shows IOMAD 4.3.3 version numbers for the other bundled components - local_email, the local/report_* plugins, the iomad_* blocks, and the iomad themes among them. That is expected. A bundled component's version only moves when that component itself needed a change; all of them are covered by your subscription and all of them ship in the archive. What should not appear is any plugin reported as missing from disk - that points to an incomplete extraction.

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, IOMAD 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

IOMAD inherits Moodle's built-in update check, which compares your site against download.moodle.org and does not know about NES for IOMAD releases. An NES for IOMAD 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.