ImpulseCore
ImpulseCore is the shared addon every Impulse module depends on. Install it first — modules will not activate until Core is present and active.
- Blank page after activating ImpulseCoreWHMCS shows a blank page right after you click Activate on ImpulseCore. Almost always missing or wrong-version ionCube Loader — install it for your PHP version and restart PHP-FPM.
- Fix: "Class not found: ImpulseCore" when activating a moduleThis fatal means you tried to activate an Impulse module before ImpulseCore itself was installed and active. Install Core first, then come back and activate the module.
- Cron Health panel shows every task redEvery task on Core's Cron Health panel is red, not just one. The single Core cron line isn't firing — debug at the system cron level.
- Cron Health shows one task failing while others are greenOne specific cron task is amber or red on the Cron Health panel while the rest are green. The runner is fine — that task's handler is erroring on every run.
- CVE feed is stale (amber strip on the Security tab)An amber strip at the top of the admin Security tab says the CVE feed hasn't refreshed in over 6 hours. Almost always a transient network reach issue to one of three upstream feeds.
- Hooks aren't firing between Impulse modulesAn event from one module isn't reaching a handler in another. Either the subscription was never registered, or the handler is throwing on dispatch.
- Fix: "ImpulseCore X.Y.Z required, found A.B.C" on module activationThe module you're activating pins a newer ImpulseCore minimum than you have installed. Upgrade Core in place, then re-activate the module.
- Module activated but not showing in ImpulseCore's registered tableYou clicked Activate on a module and it doesn't appear in Core's Modules-registered table. The activate hook fired but registration didn't complete — almost always a manifest problem.
- How to find which project a service belongs toA short SQL query (or the Projects view in Core's admin tab) tells you which project a given service is grouped with, and what else is bundled alongside it.
- How to read the ImpulseCore audit logEvery state change across every Impulse module lands in one table. Filter by module, action, severity, or time — and drop to SQL when the admin UI isn't sharp enough.
- How to run an ImpulseCore cron task manuallyInvoke any registered cron task synchronously by name. Useful for debugging a failing task, forcing a daily task without waiting, or dry-running a new task while developing a module.
- How Core's cron runner worksOne crontab line invokes Core's cron.php every 5 minutes. The runner walks the registered tasks, dispatches each due task to its owning module, captures status, and surfaces totals on the Overview tab.
- Security & Maintenance pipeline overviewA high-level tour of how Core collects daily host snapshots, refreshes three CVE feeds, correlates risks against snapshots, and applies remediations inside customer maintenance windows.
- Understanding the audit logOne table, every state change, every Impulse module. How audit entries are shaped, where to filter them, the default retention behaviour, and the SQL fallback for grep-at-scale queries.
- Upgrading ImpulseCoreCore upgrades are a drop-in archive replacement. The activate hook runs idempotent schema migrations in place — no manual SQL, no downtime beyond a normal addon reload.
- Verifying ImpulseCore healthHow to read the Overview tab — Modules registered, Cron heartbeat, Audit log, CVE feed status — and the SQL spot checks for when the admin UI isn't loading.
- What is an Impulse project?A project bundles one or more services across Impulse modules into a single customer-facing grouping — one managed Postgres plus one object-storage bucket plus one cache, all tied to one app.
- What is ImpulseCore, and why does every module need it?ImpulseCore is the shared addon every Impulse module depends on for project membership, cron, hook dispatch, licensing, audit, and the Security & Maintenance pipeline. You only install it once; every module hooks into it.
- Installing ImpulseCore — step-by-stepA five-step install. Drop the archive into WHMCS, activate the addon, add one crontab line, verify the Overview tab, then activate your modules. ~5 minutes end to end.