Hooks system

From Dolibarr ERP CRM Wiki
Revision as of 00:26, 17 January 2019 by Ssherratt (talk | contribs)
Jump to navigation Jump to search


Every business always requires something "extra" or different to the Dolibarr core functionality. While all improvements and extensions to the Dolibarr code should be contributed back via Github to be included in a future version, some modifications will be too specific to be of interest to all. Hence the Hooks system was introduced in Dolibarr 3.2 onwards. This allows developers to add custom code/features to the Dolibarr core files without the need to modify the core files. This greatly simplifies the upgrading process by keeping modifications separate from the core code.

As opposed to triggers (actions linked to a business event) − hooks are entry points into the program and can modify any part of the program functions. There are many hooks already built into the code and you may add more. They can be considered a point where the code execution is diverted "out" of the current page and runs your code, then returns back. Your custom code may add something or modify an object or completely replace an existing code block, depending on the implementation of the hook in that specific instance.

Every hook has a name, eg. "doActions" found in this code: $reshook=$hookmanager->executeHooks('doActions',$parameters,$object,$action); However the hook name is often not unique, so it must be defined within a "context" name. The context name is which code block contains the hook. So to use a hook, you need to know its context (its location) and its name.

  • The Hook Context name (e.g.: "productcard" for products, "invoicecard" for invoices, etc..). can be found by searching for "initHooks(" in php files.

This will find results such as $hookmanager->initHooks(array('thirdpartycomm','globalcard')); where "thirdpartycomm" is the context.

  • The Hook name can be found by searching for "executeHooks(".

This will find results such as $reshook = $hookmanager->executeHooks('addMoreBoxStatsCustomer', $parameters, $object, $action); where "addMoreBoxStatsCustomer" is the Hook name.

Add a hook to insert code

To implement a hook in your own module (so that your module can be hooked by others), you have two steps to follow.

These steps must be followed for every php script of your module where you want to implement hooks. This is also how hooks are implemented in Dolibarr core modules.

1- Initialize the HookManager object (put this in the beginning of your script, just after includes):

// Initialize technical object to manage hooks of thirdparties. Note that conf->hooks_modules contains array array
$hookmanager=new HookManager($db);

$hookmanager->initHooks() takes 1 parameter (an array of contexts) and activate the hooks management for this script:

- 'context' is a context string. This is simply a indicator that hooking functions can use to detect in which context they are called.

Note: you can set several contexts in the same init (for example if you want to have a common context into several pages and want also a specific context deidcated to your page).

2- Place hooks where you want to allow external code:

$reshook=$hookmanager->executeHooks('hookname',$parameters,$object,$action); // See description below
// Note that $action and $object may have been modified by hook
if (empty($reshook))
   ... // standard code that can be disabled/replaced by hook if return code > 0.

$hookmanager->executeHooks() takes 4 parameters and add a hook (an entry point in your script for external functions):

- 'hookname' is the hook's name as a string (can be anything you want, or you can follow the Dolibarr's nomenclatura, look at the list of hooks below). eg: 'formObjectOptions'

- $parameters is a custom array to send more custom data to the hook (the hooking function can then process it). Place here anything you want, it can be a file, an array of strings, anything...


$parameters=array('file'=>'my/path/to/a/file', 'customnames'=>array('henry','david','john'));

- $object is the object you want to pass onto the hooking function, mainly the current module's data (eg: invoice object if it is invoice module, etc..). This can be anything you want, but remember this will be the main component hooking functions will be using.

- $action is a string indicating the current action (can be set to null or to something sensible like 'create' or 'edit').

Note: You will want to redo this step if you want to add multiple hooks at different places in your script.

Now your module should be hookable, and you can follow the procedure below in Implement a hook to implement a hooking function that will take advantage of your new hooks.

Implement the Hook

To use a hook (add or replace a part of code), you first need to already have defined a module descriptor (see Module_development#Create_your_module_descriptor), and then you need to do 2 things:

1- add your module to the list of contexts you want to hook on. This means that when a context you hook will happen, your module hook code will be called. To do that, just edit your /htdocs/yourmodulename/core/modules/modYourModuleName.class.php and edit the $this->module_parts variable with something like this:

$this->module_parts = array(
'hooks' => array('hookcontext1','hookcontext2')  // Set here all hooks context you want to support

Of course change YourModuleName with your own module's name.

Note: you can find the current module's context with print('Module context: '.$object->context); (put this inside the module's php file where the hook resides and that you want to hook).

Warning.png Be careful: do not forget to DISABLE then ENABLE the module in the admin panel to accept the new context, because these constants are only added/refreshed to the database when re-enabling your module.

2- You will overload a hook (a function) with your own.

Create a file /htdocs/yourmodulename/class/actions_yourmodulename.class.php and then put something like this:

class ActionsYourModuleName
	 * Overloading the doActions function : replacing the parent's function with the one below
	 * @param   array()         $parameters     Hook metadatas (context, etc...)
	 * @param   CommonObject    &$object        The object to process (an invoice if you are in invoice module, a propale in propale's module, etc...)
	 * @param   string          &$action        Current action (if set). Generally create or edit or null
	 * @param   HookManager     $hookmanager    Hook manager propagated to allow calling another hook
	 * @return  int                             < 0 on error, 0 on success, 1 to replace standard code
	function doActions($parameters, &$object, &$action, $hookmanager)
		$error = 0; // Error counter
		$myvalue = 'test'; // A result value

		echo "action: " . $action;

		if (in_array('somecontext', explode(':', $parameters['context'])))
		  // do something only for the context 'somecontext'

		if (! $error)
			$this->results = array('myreturn' => $myvalue);
			$this->resprints = 'A text to show';
			return 0; // or return 1 to replace standard code
			$this->errors[] = 'Error message';
			return -1;

Your function should now be called when you access the module/context and you will see the parameters and object and action.


  • $parameters is an array of meta-data about the datas contained by the hook (eg: the context, always accessible by $parameters['context']).
  • $object is the object that you may work on. Eg: the product if you are in the productcard context.
  • $action is the action if one is conveyed (generally "create", "edit" or "view").
  • $hookmanager is propagated only to allow your hook to call another hook.


  • The return code from a hook is 0 or 1 if success, negative if error. In general, it will be 0. It can be 1, which means that, in some specific cases, your code hook completely replaces what Dolibarr would do without the hook. If return code is negative, you can also set $this->errors[]='Error message to report to user'
  • If the method sets the property $this->results with an array, then the array $hookmanager->resArray will automatically be enriched with the contents of this array, which can be reused later.
  • If the method sets the property $this->resprints with a string, then this string will be displayed by the hook manager (method executeHook), immediately after your method exit.
  • Your code can also modify the value of $object and $action.

List of available Hooks in Dolibarr

How to find a complete list of all available hooks in Dolibarr's nomenclatura ? Just search for "executeHooks(" through the whole sourcecode (generally called "find in files") and you should easily find all the hooked methods calls.

This is however a small list of them (not complete):

  • afterLogin
  • beforePDFCreation
  • afterPDFCreation
  • afterODTCreation
  • createFrom
  • doActions
  • printLeftBlock
  • printSearchForm
  • printTopRightMenu
  • printObjectLine
  • formAddObject: Add a product into an element
  • formObjectOptions: called everytime fields associated to the main object are printed or inputted (eg: creation form, datasheet, edit form, etc..).
  • formConfirm
  • createDictionaryFieldlist
  • editDictionaryFieldlist
  • viewDictionaryFieldlist


Note: please note that this list may change in the future as hooks and contexts are added into Dolibarr, so if you really need to find a specific hooks, please search directly in the sourcecode.

List of available Contexts in Dolibarr

To find the complete list of available modules' context in Dolibarr's nomenclatura, the procedure is similar to finding hooks. Search for "initHooks(" through the whole sourcecode (generally called "find in files") and you should find all the possible contexts.

This is however a small list of them (not complete): adherents\card.php(111): membercard
adherents\type.php(73): membertypecard
categories\categorie.php(96): categorycard
comm\card.php(72): commcard
comm\propal.php(99): propalcard
comm\action\card.php(85): actioncard
comm\action\index.php(112): agenda
comm\mailing\card.php(55): mailingcard
commande\card.php(93): ordercard
compta\facture.php(105): invoicecard
compta\paiement.php(70): paiementcard
compta\deplacement\card.php(50): tripsandexpensescard
compta\dons\card.php(53): doncard
compta\localtax\clients.php(172): externalbalance
compta\salaries\card.php(47): salarycard
compta\tva\card.php(45): taxvatcard
contact\card.php(77): contactcard
contrat\card.php(70): contractcard
expedition\card.php(85): expeditioncard
fichinter\card.php(80): interventioncard
fourn\card.php(54): suppliercard
fourn\commande\card.php(80): ordersuppliercard
fourn\commande\orderstoinvoice.php(88): orderstoinvoicesupplier
fourn\facture\card.php(72): invoicesuppliercard
fourn\facture\paiement.php(71): paymentsupplier
livraison\card.php(68): deliverycard
product\card.php(91): productcard
product\fournisseurs.php(62): pricesuppliercard
product\stats\commande.php(45): productstatsorder
product\stats\commande_fournisseur.php(45): productstatssupplyorder
product\stats\contrat.php(45): productstatscontract
product\stats\facture.php(48): productstatsinvoice
product\stats\facture_fournisseur.php(47): productstatssupplyinvoice
product\stats\propal.php(45): productstatspropal
product\stock\card.php(54): warehousecard
projet\card.php(48): projectcard
projet\tasks.php(67): projecttaskcard
resource\card.php(60): resource_card
resource\element_resource.php(58): element_resource
societe\agenda.php(41): agendathirdparty
societe\commerciaux.php(40): salesrepresentativescard
societe\consumption.php(80): consumptionthirdparty
societe\info.php(41): infothirdparty
societe\soc.php(80): thirdpartycard
user\card.php(93): usercard
user\passwordforgotten.php(56): passwordforgottenpage

Note: please note that this list may change in the future as hooks and contexts are added into Dolibarr, so if you really need to find a specific hooks, please search directly in the sourcecode.

See also