DACore · coming December 2026

How DACore built-in events work

DACore fires a handful of PHP events on login, permission refresh, admin page render, and AI chat. Other modules subscribe with Events::on in module.listeners.php — the same bus as the framework. That is how you debug “did login run?”, “did withMenu finish?”, “did rights refresh?” without patching DACore. Framework names (dotapp.databaser.execute, router, module lifecycle) are listed in built-in events and database triggers. This article is only what DACore itself triggers.

Common mistakes

The six names

DACore calls DotApp::DotApp()->trigger(…). After lowercase, subscribe to the keys in the first column. Mixed case in the source still lands in the same bucket.

There are no other DACore trigger() calls in the module. Email senders, notifications, menu register, and rights helpers do not publish events — they are DotApp::call APIs.

Debug from your module

File: app/modules/Shop/module.listeners.php. Do not put this in DACore.

use Dotsystems\App\Parts\Events;
use Dotsystems\App\Parts\Logger;

public function register($dotApp)
{
    Events::on('dacore.login.before', function ($email) {
        Logger::use()->warning('DACore login attempt', ['email' => $email]);
        // do not log the password (second argument)
    });

    Events::on('dacore.login.after', function ($login) {
        Logger::use()->warning('DACore login result', [
            'logged' => is_array($login) ? ($login['logged'] ?? false) : false,
            'error' => is_array($login) ? ($login['error'] ?? null) : null,
        ]);
    });

    Events::on('dacore.permissions.refresh', function () {
        Logger::use()->warning('DACore permissions refreshed');
        // rebuild a cached AI context here if you keep one
    });

    Events::on('dacore:page@withmenu.rendering', function ($title, $body, $header, $css, $js, $menuId) {
        Logger::use()->warning('DACore page', [
            'title' => $title,
            'menuId' => $menuId,
            'body_len' => is_string($body) ? strlen($body) : 0,
        ]);
    });

    Events::on('dacore.ai.chat.active', function () {
        Logger::use()->warning('DACore AI chat became active');
    });
}
    

login.after runs even when credentials fail or the account is later found inactive. Read $login['logged'] / $login['error']. Shape: Auth and 2FA.

permissions.refresh fires only when Config::module('DACore', 'permissionsAutorefresh') is on and the DSM timer elapsed. DACore then calls Auth::permissionRefresh(), merges role permissions, and reloads the profile — then the event. If your module caches “what this operator can see”, drop that cache here.

Page@withMenu hooks

The source names are Dacore:Page@withMenu.rendering and .rendered (note the spelling Dacore). After lowercase they become dacore:page@withmenu.rendering / .rendered. Subscribe to the lowercase form so hasListener checks you write yourself stay honest.

The comment in DACore says other modules can hook “custom renderers”. You still cannot rewrite $title or $viewcode through a listener return. Use rendering to notice which desk page is about to paint; use rendered to measure the finished HTML. To change chrome, pass CSS/JS into Page@withMenu! from your controller, or add assets in your module. Admin template and menu.

AI chat

dacore.ai.chat.active fires when a session is created or when an existing chat id is reused. No payload. If you keep extra system context per operator, refresh it here with DACore:AI@addSystemContext. Tool calls are not events — they are registered tools.

Framework 404 that DACore may own

DACore does not invent a new 404 event. In module.init.php it does:

if (Events::hasListener('dotapp.router.resolve.404') === false) {
    Events::on('dotapp.router.resolve.404', function () {
        // DACore 404 page
    });
}

If your module registers that name first, DACore leaves it alone and your listener wins. If you only want to log 404s, do not steal the event — log from a second listener if DACore already registered, or log inside your own 404 body. Kernel 404 behaviour: built-in framework events.

Not events

• DACore:Email@send! / listSenders! — email senders
• DACore:Notifications@push — inbox API, not a bus name
• DACore:Rights@* / Menu@register / AITools@register
• SQL around those tables — use dotapp.databaser.execute from the framework catalog if you need a query log