Module development: Difference between revisions

Jump to navigation Jump to search

Module development (view source)

Revision as of 07:51, 29 May 2013

1,274 bytes removed ,  13 years ago
→‎File:Art.png Enabling/activation condition of external module on DoliStore
VisualWikitext
Line 526: Line 526:


= [[File:Art.png]] Enabling/activation condition of external module on DoliStore =
= [[File:Art.png]] Enabling/activation condition of external module on DoliStore =
Here are the rules that will be apply by Dolibarr team on validation/activation of external module on [www.dolistore.com www.dolistore.com]


=== Inclusion ===
See [[Module_Dolistore_Validation_Rules|Validation Rules]]
*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 to a module file from a core file (call by hook / trigger / speciales pages), use dol_include_once('/My_Module_directory/...');
 
=== Link ===
All link to generated by HTML should be done by getNomUrl object class method or at least using dol_buildpath
 
=== Custom directory ===
An external module can be use in htdocs/custom/mymodule as well as in htdocs/mymodule
   
=== Core file modifications ===
If core dolibarr files have to be modified for feature of your module :
*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,...)
*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))
Fhenry
Bureaucrats, emailconfirmed, Administrators
825

edits

Retrieved from "https://wiki.dolibarr.org/index.php/Special:MobileDiff/29630"

Navigation menu