Fix: ImpulseMinio is not appearing in ImpulseCore's modules registered table

You activated ImpulseMinio in WHMCS, but ImpulseCore's Overview tab doesn't list it under "Modules registered". The activate hook didn't successfully call into Core.

Last updated 20 days ago

Fix: ImpulseMinio is not appearing in ImpulseCore's modules registered table

What you're seeing

You activated ImpulseMinio under System Settings then Addon Modules in WHMCS. The activation appeared to succeed β€” no fatal, no error banner. But when you open Addons then ImpulseCore, the Overview tab's Modules registered table doesn't show a row for ImpulseMinio. Cron tasks aren't running. Hooks aren't firing.

Why it happens

Every Impulse module calls ImpulseCore::registerModule() from its WHMCS activate hook. If that call doesn't complete, the module is half-activated: its database tables may exist, but Core has no record of it and won't dispatch cron, hooks, or audit events to it.

Three common reasons the registration call fails silently:

  1. ImpulseCore isn't installed β€” you'll usually see a Class not found: ImpulseCore fatal, but if PHP's error display is off, it can swallow.

  2. ImpulseCore is older than the version ImpulseMinio requires β€” the manifest pins a minimum Core version, and the call throws an IncompatibleCoreVersion exception.

  3. ImpulseMinio's impulse_module.json manifest is malformed β€” JSON parse error, missing required keys, or wrong slug.

Fix

  1. Check ImpulseCore's audit log. Open Addons then ImpulseCore then Audit and filter to severity=error from the last hour. A failed registerModule() call writes a row with the verbatim error.

  2. If the error is Class not found: ImpulseCore, ImpulseCore isn't installed or active. See the Fix: "Class not found: ImpulseCore" article. Install or activate Core, then deactivate and re-activate ImpulseMinio.

  3. If the error is a Core version mismatch ("ImpulseCore X.Y.Z required, found A.B.C"), upgrade Core: drop the newer release archive into modules/addons/impulsecore/, re-activate Core (the activate hook is idempotent and runs schema migrations in place), then re-activate ImpulseMinio. See Fix: ImpulseCore version mismatch on module activation for the full flow.

  4. If the error mentions JSON parsing or missing manifest keys, look at modules/addons/impulseminio_addon/impulse_module.json on the WHMCS host. The file should be valid JSON with slug, display_name, version, and requires_impulsecore at minimum. If you've hand-edited it, restore the original from the release archive.

  5. Re-trigger registration. Deactivate ImpulseMinio under System Settings then Addon Modules, then activate it again. The activate hook re-runs registerModule(). The Modules registered table in Core's Overview tab should populate within seconds.

How to confirm it worked

Open Addons then ImpulseCore. The Modules registered table on the Overview tab shows a row for impulseminio with its version and registration timestamp. The audit log shows a fresh module.registered event. The cron runner picks up ImpulseMinio's tasks on its next tick.

Related