hookscanner

Understanding Dolibarr hooks

Dolibarr's hook system allows third-party modules to intervene in the application's native behaviour without touching its source code. Every time Dolibarr runs $hookmanager->executeHooks('hookName', $parameters, $object), it invites all registered modules to respond via a method of the same name in their actions_xxx.class.php file. This is the core extensibility mechanism of Dolibarr: invoice creation, dashboard display, form validation, e-mail sending — all of it can be intercepted and enriched through a hook.

The problem: with over 1,000 extension points scattered across hundreds of PHP files, it is virtually impossible to know which hooks exist, which ones are already implemented in your modules, and which ones remain to be exploited.

What HookScanner does

HookScanner solves this by automatically scanning the entire file tree of your Dolibarr installation. It detects every $hookmanager->executeHooks(...) call, extracts the hook name (1st parameter) and the object variable (3rd parameter), and traces back to the corresponding PHP class and its .class.php file. The scan runs in the background using AJAX batches, so it never hits the PHP timeout limit.

From the Hooks tab, get an instant overview of all available extension points, filterable by name, source file or status. Each hook shows how many actions_*.class.php files in your modules already implement the corresponding method. Expanding a row gives you full details: exact call, object class, class file, and — for each module — the method with its code or a button to inject it automatically.

From the Action files tab, browse all actions_*.class.php files present on your server, with the list of their hook methods and a direct link back to the matching hook in the first tab.

Available in French, English, German, Italian and Spanish.