Not for the moment. The reason is that using the custom directory is not yet stable. For example, the solution for an external module to make the include of the main.inc.php file is not clear yet. The other reason is that it works for on custom dir. Change should be done to have as much custom as there is external module to allow to keep usage of external modules inside different source (for example having one module on doliforge, another one on github or a svn server). Another reason is that there is still feature not working (even with 3.2). Also don't forget that using the alternate path slow down usage of dolibarr compared to including in same root. So architecture may still change in future so it is better to keep this feature for dev only or experienced integrator but not for non technical end users (for the moment, but i agree we must achieve this goal,we are on the good way but not yet ready for public documentation).
2012/5/5 Juanjo Menent <jmen...@2byte.es> > ** > Since version 3 it is possible to define an alternative root > directory.This allows to store, in same place, plug-ins and custom > templates. > > We should prioritize the use of this option > (/path_of_dolibarr/htdocs/custom/mymodule) compared to traditional > (/path_of_dolibarr/htdocs/mymodule)? > > If yes, we should update the wiki... > > _______________________________________________ > Dolibarr-dev mailing list > Dolibarr-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > >
_______________________________________________ Dolibarr-dev mailing list Dolibarr-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
