Developer Documentation Note

For developers

WHMDC is distributed with core files in an encoded format. You cannot browse or search the source code directly. This documentation is your primary reference for building addons, modules, and integrations.

Supported extension points

See the Extension Stability & Support Contract for explicit guarantees. In summary:

• Hooks – addAction, addFilter. Documented in Hooks Reference. Stable.
• Addons – modules/addons/. module.json, hooks.php. Stable.
• Server modules – modules/servers/. ModuleInterface. Stable.
• Registrar modules – modules/registrars/. ModuleInterface. Stable.
• Gateway modules – modules/gateways/. ModuleInterface. Stable.
• Public REST API – /api/v1/. API key auth. Stable.
• Outgoing webhooks – Configure via API. Events, payload, signature. Stable.

Not supported / intentionally not exposed

• Modifying core PHP files (they are encoded)
• Internal API endpoints or undocumented routes
• Direct database writes to core tables (use API or helpers)

Debugging without reading core

• Logs: Check system_logs table, activity_log, email_logs, webhook_deliveries. Error output may go to PHP error_log.
• Debug mode: If available in Admin → Settings, enable debug to get more verbose errors. Avoid in production.
• Hooks: Add temporary logging in your addon hooks.php: error_log(print_r($data, true)); to inspect payloads.

Overriding UI/templates without core edits

Use themes/ to override templates. Copy the default theme, modify templates. Do not edit core view files. Use admin_footer, client_footer hooks to inject scripts or HTML.