Changes

'''Note''': If you develop a full module, you can also place the trigger file in your own module's subdirectly. Eg: if your module resides in htdocs/mymodule/, then you can place your triggers inside htdocs/mymodule/core/triggers/. But for this, you must declare the trigger into your module descriptor file (eg: '''/mymodule/core/modules/modMyModule.class.php'''). For this, add into this file triggers->1 into module_parts array:

'''Note''': If you develop a full module, you can also place the trigger file in your own module's subdirectly. Eg: if your module resides in htdocs/mymodule/, then you can place your triggers inside htdocs/mymodule/core/triggers/. But for this, you must declare the trigger into your module descriptor file (eg: '''/mymodule/core/modules/modMyModule.class.php'''). For this, add into this file triggers->1 into module_parts array:

<source lang="php">

<syntaxHighlight lang="php">

// Defined all module parts (triggers, login, substitutions, menus, etc...) (0=disable,1=enable)

// Defined all module parts (triggers, login, substitutions, menus, etc...) (0=disable,1=enable)

$this->module_parts = array('triggers' => 1);

$this->module_parts = array('triggers' => 1);

//              'substitutions' => 0,

//              'substitutions' => 0,

//              'menus' => 0);

//              'menus' => 0);

</source>

</syntaxHighlight>

Then disable and reenable your module. This will add a record into [[Table llx_const]] to tell Dolibarr that a trigger file must be searched in the module directory '''htdocs/mymodule/core/triggers/'''

Then disable and reenable your module. This will add a record into [[Table llx_const]] to tell Dolibarr that a trigger file must be searched in the module directory '''htdocs/mymodule/core/triggers/'''