Inspect widgets and event hooks

These pages help administrators and extension developers inspect how modules connect to the interface and application events.

Widget Registry

1. Open Extensions → Widgets.
2. Find the slot used by the page you are investigating. Review the module, template and priority of each entry.
3. If an installed module’s widgets are missing after an update, select Rediscover Widgets and reload the affected page.

Widgets are discovered from module declarations. Lower priority numbers render first within a slot. Rediscovery rebuilds this registry; it does not create a custom widget or enable a disabled module. Check the module and its declared template if an entry remains missing.

Registered hooks

1. Open Extensions → Overview → Hooks.
2. Review the registered module and event pairs.
3. Check that the relevant extension is active and cron is running if an expected listener is missing.

Modules declare event listeners in their service classes. ClientFence connects those listeners during extension activation and cron’s hook-registration task. Administrators with hook-management permission can reconnect declared listeners through hook/batch_connect; existing connections are not duplicated.

The table is diagnostic, not a form for adding arbitrary event handlers. Manual hook invocation is restricted to Super Administrators and can run real business actions; avoid using it to test a production integration.

The widget registry lists each slot, module template and rendering priority.

Hooks lists registered modules and their event listeners.