Changes

Jump to navigation Jump to search
no edit summary
Line 6: Line 6:     
=== Inclusion ===  
 
=== Inclusion ===  
*To include a core file, use include_once/require_once/include/require DOL_DOCUMENT_ROOT.'/pathtofile';
+
* To include a core file, use include_once/require_once/include/require DOL_DOCUMENT_ROOT.'/pathtofile';
*To include to a module file from a module file, use include_once/require_once/include/require './mymodulefile';
+
* To include a file of module into a file of same module, use include_once/require_once/include/require './mymoduledir/...';
*To include to a module file from a core file (call by hook / trigger / speciales pages), use dol_include_once('/My_Module_directory/...');
+
* To include a file of another external module into a module file, use dol_include_once('/otherextmoduledir/...');
    
=== Link ===  
 
=== Link ===  
Line 17: Line 17:  
      
 
      
 
=== Core file modifications ===
 
=== Core file modifications ===
If core dolibarr files have to be modified for feature of your module :
+
If dolibarr core files have to be modified, it will be accepted :
*They were be accepted si they are pushed to dolibarr dev branch on GitHub (add feature to standard class without risk of regression, html.form.class.php/function.lib.php,...)
+
* If they are pushed to dolibarr dev branch on GitHub (add feature to standard class without risk of regression, html.form.class.php/function.lib.php,...)
*They were be accepted if adding hook/trigger is pushed to dolibarr dev branch on GitHub to be sure that on next dolibarr version your next module version will not have to change dolibarr core code 
  −
In all cases:
  −
* If and only if they are test with
  −
    if (!empty($conf->mymodule->enabled))
 

Navigation menu