This document provides information for developers and partners on Dolibarr ERP CRM including: - Tips for developing modules such as using scheduled jobs, README/Changelog files, translation and variable substitutions. - Details like using save/restore search values, repositioning links, and making modules compatible with default values/sort orders and searches. - Information on including main.inc.php to load the Dolibarr framework for external modules regardless of installation method. The document also mentions upcoming demos of the Website and Module Builder modules.

1. DevCamp
Nancy - 2018
Laurent Destailleur – Project leader
2018
Dolibarr ERP CRM
Information for developers
and partners

2. ● You can provide Scheduled/Cron jobs with your modules.
● Provide README.md and ChangeLog.md with your module.
○ No more need to embed Markdown libraries in your module.
● Use the save/restore_lastsearch_values feature
● Use the “reposition” class on <a> links to have page at same position after reload
● Be compatible with the “default values and sort orders” feature -> Search fields
must be named “search_xxx”
● You can use a translation in substitutions with __(MYTRANSKEY)__
● You can use variables in substitutions with __[MYVAR_CONST]__
○ Example: for a personalised menu entry: 'url'=>'/product/list.php?search_categ=__[MYCATEG]__’
Things that should be more known

3. ● Use the new code sample found into files in modulebuilder directory to include
the main.inc.php file in your external module file => The only way to load the
dolibarr framework environment whatever is the way your Dolibarr and module
are installed (into custom, into root, using symbolic links, inside a virtual host or using an alias,
whatever is your web server setup, …)
Things that should be more known

4. Let’s have
a demo...
The Website module

5. Let’s build
an app in 5mn...
The Module Builder module

6. Let’s build
an app in 5mn...
The Module Builder module