Dolibarr ERP CRM Wiki - User contributions [en]

ContributeursPRGithub

2026-03-25T10:03:54Z

Cbenke: Created page with "== Liste des contributeurs == {| class="wikitable" style="text-align:center;" ! Contributeur !! Commits !! PR 2024 !! PR 2025 !! PR 2026 |- style="background:#FFD700;" | fre..."

== Liste des contributeurs ==

{| class="wikitable" style="text-align:center;"
! Contributeur !! Commits !! PR 2024 !! PR 2025 !! PR 2026

|- style="background:#FFD700;"
| frederic34 || 6767 || 802 || 566 || 48
|- style="background:#FFD700;"
| mdeweerd || 2069 || 468 || 154 || 20
|- style="background:#FFD700;"
| hregis || 8500 || 69 || 137 || 2
|- style="background:#FFD700;"
| aspangaro || 3140 || 0 || 117 || 54
|- style="background:#FFD700;"
| defrance || 1052 || 30 || 110 || 29

|- style="background:#C0C0C0;"
| FHenry || 2279 || 88 || 81 || 6
|- style="background:#C0C0C0;"
| marc-dll || 233 || 9 || 64 || 0
|- style="background:#C0C0C0;"
| Hystepik || 306 || 127 || 59 || 17
|- style="background:#C0C0C0;"
| JonBendtsen || 125 || 49 || 58 || 0
|- style="background:#C0C0C0;"
| lvessiller-opendsi || 666 || 60 || 56 || 6
|- style="background:#C0C0C0;"
| thersane-john || 169 || 26 || 53 || 15

|- style="background:#E6B17A;"
| Daoud-mohamed || 156 || 60 || 48 || 2
|- style="background:#E6B17A;"
| thomas-Ngr || 225 || 20 || 46 || 16
|- style="background:#E6B17A;"
| rycks || 242 || 36 || 39 || 10
|- style="background:#E6B17A;"
| atm-florianm || 257 || 25 || 33 || 0
|- style="background:#E6B17A;"
| sonikf || 202 || 46 || 32 || 3
|- style="background:#E6B17A;"
| kkhelifa-opendsi || 150 || 17 || 29 || 4
|- style="background:#E6B17A;"
| atm-irvine || 44 || 14 || 29 || 0
|- style="background:#E6B17A;"
| jyhere || 122 || 29 || 26 || 6
|- style="background:#E6B17A;"
| altairis-noe || 168 || 22 || 25 || 5

|- style="background:#81D4FA;"
| fappels || 683 || 26 || 22 || 7
|- style="background:#81D4FA;"
| vmaury || 63 || 17 || 20 || 5
|- style="background:#81D4FA;"
| zahwyrix || 87 || 39 || 19 || 0
|- style="background:#81D4FA;"
| alexandre-janniaux || 71 || 13 || 18 || 0
|- style="background:#81D4FA;"
| BenjaminFlr || 67 || 14 || 16 || 5
|- style="background:#81D4FA;"
| atm-quentin || 304 || 5 || 14 || 2
|- style="background:#81D4FA;"
| YannisHoareau || 145 || 8 || 14 || 0
|- style="background:#81D4FA;"
| atm-lucasmantegari || 55 || 11 || 14 || 8
|- style="background:#81D4FA;"
| altairis-tof || 314 || 27 || 13 || 1
|- style="background:#81D4FA;"
| atm-lena || 104 || 27 || 12 || 0
|- style="background:#81D4FA;"
| atm-adrien || 185 || 0 || 11 || 1
|- style="background:#81D4FA;"
| noec764 || 82 || 18 || 10 || 3

|- style="background:#81C784;"
| priojk || 79 || 10 || 9 || 6
|- style="background:#81C784;"
| atm-GregM || 76 || 1 || 9 || 1
|- style="background:#81C784;"
| glu000 || 60 || 9 || 9 || 3
|- style="background:#81C784;"
| mapiolca || 83 || 0 || 8 || 4
|- style="background:#81C784;"
| homer8173 || 66 || 4 || 8 || 0
|- style="background:#81C784;"
| ptibogxiv || 972 || 22 || 7 || 1
|- style="background:#81C784;"
| fmarcet || 243 || 11 || 6 || 2
|- style="background:#81C784;"
| eldy || 88548 || 7 || 5 || 2
|- style="background:#81C784;"
| dolibit-ut || 745 || 5 || 5 || 0
|- style="background:#81C784;"
| SylvainLegrand || 61 || 11 || 5 || 3
|- style="background:#81C784;"
| comaiteseb || 46 || 12 || 5 || 0
|- style="background:#81C784;"
| moreauftheobald || 43 || 4 || 5 || 0
|- style="background:#81C784;"
| BB2A-Anthony || 397 || 16 || 4 || 15
|- style="background:#81C784;"
| joseplluis || 66 || 6 || 4 || 1
|- style="background:#81C784;"
| dolibarr95 || 66 || 4 || 3 || 0
|- style="background:#81C784;"
| FlorentPoinsaut || 58 || 10 || 3 || 0
|- style="background:#81C784;"
| bafbes || 183 || 10 || 2 || 0
|- style="background:#81C784;"
| ymollard || 70 || 4 || 2 || 0
|- style="background:#81C784;"
| ibuiv || 65 || 5 || 2 || 0
|- style="background:#81C784;"
| grandoc || 2871 || 12 || 1 || 0
|- style="background:#81C784;"
| inoveaconseil || 136 || 0 || 1 || 0
|- style="background:#81C784;"
| c3do || 125 || 3 || 1 || 0
|- style="background:#81C784;"
| jtraulle || 65 || 0 || 1 || 0

|}

Projet Dolibarr

2026-03-25T09:57:54Z

Cbenke: /* File:workcomputer.png Les accès GIT */

[[en:Dolibarr_Project]]
[[es:Proyecto_Dolibarr]]
[[zh:Dolibarr项目]]

{{DISPLAYTITLE:Les ressources et l'organisation du projet}}
{{TemplateDocDevFr}}
{{TemplateDocUtil}}
<div class="opacitymedium">Cette page fournit des informations sur l'organisation du projet, les rôles occupés par les différents acteurs (ainsi que les postes à pourvoir) et comment participer.</div>
 

=[[File:orientation.png]] Histoire et futur du projet (Roadmap)=
Voir la page [[Origines et histoire du projet|Origines, histoire et futures versions de Dolibarr]]

=[[File:who.png]] Les acteurs et leurs rôles dans la galaxie Dolibarr=

L'équipe Dolibarr est une armée de la galaxie Open Source, constituée de différents responsables, soutenus par divers contributeurs, physiques ou moraux (sociétés, associations, freelance).
Les lignes suivantes présentent les différents rôles et postes occupés dans la gestion du projet Dolibarr et permettent ainsi de comprendre le fonctionnement interne du projet.
De nombreux rôles et postes sont en permanence à pourvoir.

Les volontaires pour postuler à une responsabilité dans le projet sont invités à se manifester.

Si vous désirez des informations pour participer en tant que développeur, la page [[FAQ_D%C3%A9veloppeur#Comment_devenir_d.C3.A9veloppeur_officiel|FAQ Développeur - Comment devenir développeur officiel]] est peut-être plus appropriée.

Le lien suivant présente une liste des développeurs qui participent ou ont participé au projet et qui se sont déclarés publiquement: [[:Category:Everybody|Liste des acteurs]]

La suite présente les différents '''rôles développeurs''' dans un premier temps puis tous les '''rôles non développeurs'''. Tous ces rôles constituent un part du moteur de l'avancement de Dolibarr.

== La communication, protection et légal==

Objectifs/Autorisations: Détenir la marque, protéger le projet, gérer les obligations légales. Centraliser les outils. Stocker les versions de références. Organiser les devcamps officiels. Soutenir les autres forums, congrès, salons...

A ce rôle actuellement:

L'association Dolibarr https://asso.dolibarr.org

==Les rôles développeurs==

===Développeur grade '''Yoda''' (Chefs de projet commiteurs GIT, Head release manager)===

Objectifs/Autorisations: Fusionner les PR de la branche '''develop''' du projet Dolibarr. Gérer et annoncer les beta (freeze) et réaliser le packaging de la version standard.

Ont ce rôle actuellement (par ordre alphabétique):

{{ListOfYodas|lang=FR}}

Fonction à pourvoir: Non (par définition, ce rôle est limité au chef de projet et backups)

Mode de rotation: L'acteur en poste nomme son backup et son successeur en cas de démission. En cas de démission subie (décès, abandon), c'est le Yoda backup qui a le rôle de nommer le successeur à ce poste.

Note: Tous les gestes pour construire un package pour une nouvelle version de Dolibarr sont définis dans le fichier '''build/makepack-howto.txt''' disponible avec les sources.

===Développeur grade '''Jedi''' (Mainteneur et Release manager des versions de maintenance)===

Objectifs/Autorisations: Fusionner, et surtout tester, les PR de bugfix, sur les versions de maintenance (version des branches non develop). Peut aussi backporter les correctifs réalisés en develop (cherry-pick GIT). Package et diffuse les releases des versions de maintenance (branche non develop). Annoncer la mise à disposition de ces releases de versions de maintenance.

A ce rôle actuellement:
{{ListOfModulesWithDedicatedJedi
|lang=FR}}

Fonction à pourvoir: Non (ce poste requiert d'avoir déjà eu quelques PR de validées pour être éligibles).

Mode de rotation: C'est le développeur de grade Yoda qui nomme les personnes à ce poste. Un acteur en poste peut proposer un successeur en cas de démission.

 

===Développeur grade '''Amiral''' (Réaliseur de GIT Pull Request)===

Objectifs/Autorisations : Développer, ajouter, modifier ou supprimer du code dans l'outil de suivi de version de GIT.

L'obtention du grade d'Amiral est automatique dès lors que votre premier Pull Request sous Git est validé et intégré dans Dolibarr.

Vous pouvez alors demander à être intégré dans le groupe Admiral de Git (opération manuelle non automatique), ce qui vous permet d'avoir les droits d'édition sur les tags des issues ou de s'auto affecter une issue.

Fonction à pourvoir : Oui (Surtout pour la soumission de corrections de [https://github.com/dolibarr/dolibarr/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 bogues déclarés sur Github], fortement recommandé pour commencer).

Articles en relation : [[FAQ_Développeur#Comment_devenir_d.C3.A9veloppeur_officiel|FAQ Comment_devenir_développeur_officiel]].

Identifiés comme ayant ce rôle actuellement ou récemment (comptes actifs dans {{TemplateURLSCM}}) :

*Voir {{ListOfAdmirals|lang=FR}}

===Développeur grade '''Z-6PO''' (Traducteurs sur transifex.com)===

Objectifs/Autorisations : Traduire Dolibarr en utilisant la plateforme collaborative Transifex.

Tous les utilisateurs qui sont enregistrés en tant que traducteur sur le projet Transifex Dolibarr sont Z-6PO.

Identifiés comme ayant ce rôle actuellement:

*Beaucoup de gens sont en fait des Z-6PO (à ce jour, plus de 1 150 contributeurs dans plus de 80 langues).

Fonction à pourvoir : Oui sur les langues "rares" (aller sur https://www.transifex.com/projects/p/dolibarr/ pour trouver votre langue et aider à la traduire),

Articles en relation : [[Documentation traducteur]]

===Développeurs grade '''Soldat'''===

Objectifs/Autorisations: Animer les forums, la communauté, promouvoir Dolibarr.

Fonction à pourvoir : Oui (sans limite)

Identifiés comme ayant ce rôle actuellement:

*Nombre trop variable pour être recensé. Tout utilisateur Dolibarr est un soldat potentiel de l'armée Dolibarr.

===Et Dark Vador ?===

Il existe bien lui aussi dans la galaxie Dolibarr. Il y aura toujours des parasites qui polluent le forum, ou autres outils du projet, de critiques non constructives, qui ralentissent le développement de Dolibarr plutôt que d'offrir des suggestions aidant à progresser. Certains sont très forts en mauvaise foi ou mauvais ton. Ce sont eux que l'on appellent les Dark Vador.
Heureusement, statistiquement, on ne constate l'apparition et la mort que d'un à deux Dark Vador par an environ ... Ce qui est un très bon ratio par rapport aux autres projets Open-Source de même taille.

==Les autres rôles dans le projet Dolibarr==

===Role A: Hébergement site web (https://www.dolibarr.org ou sites locaux)===

Objectif: Fournir et maintenir une plateforme d'hébergement du site Dolibarr basée sur Joomla.

A ce rôle actuellement:
{{HosterOfWebSites}}

Fonction à pourvoir: Non mais des soumissions d'articles à poster sur le site (texte en anglais + image) sont les bienvenues..

===Role B: Hébergement site démo (https://demo.dolibarr.org<nowiki/>)===

Objectif: Fournir et maintenir une plateforme d'hébergement du site de démo online Dolibarr (Version internationale, langage autodétecté).

A ce rôle actuellement:

*Dolibarr foundation (Version internationale avec langage auto-détecté https://demo.dolibarr.org)

Fonction à pourvoir: Non

===Role C1: Hébergement wiki (https://wiki.dolibarr.org<nowiki/>)===

Objectif: Fournir et maintenir une plateforme d'hébergement du wiki Dolibarr

A ce rôle actuellement:

*Dolibarr foundation

Fonction à pourvoir: Non

===Role C2: Hébergement place de marché (https://wwww.dolistore.com<nowiki/>)===

Objectif: Fournir une plateforme de diffusion et/ou vente centralisant les modules externes (basée sur prestashop). Valider les soumissions de modules.

A ce rôle actuellement

*Dolibarr foundation (plateforme)

Fonction à pourvoir: No

===Role E1: Responsable DoliWamp (Installeur pour Windows)===

A ce rôle actuellement:

*[[Laurent Destailleur]] ([https://www.nltechno.com NLTechno])

Fonction à pourvoir: No

===Role E2: Responsable DoliDeb+DoliRpm (Installeur pour Ubuntu/Debian/Fedora/Mandriva/Redhat/Opensuse)===

A ce rôle actuellement:

*Ksar

Fonction à pourvoir: No

===Role E3: Responsable DoliMamp (Installeur pour Mac OS X)===

A ce rôle actuellement:

*Personne

Fonction à pourvoir: Non, le package a été abandonné.

===Role G: Gestion de l'association Dolibarr===

Objectif: Créer et gérer une association de promotion et d'utilisateurs Dolibarr

Identifiés comme ayant ce rôle actuellement:

*1 président - Voir la page [[Association Dolibarr]].
*1 secrétaire - Voir la page [[Association Dolibarr]].
*1 trésorier - Voir la page [[Association Dolibarr]].
*D'autres acteurs, membres du conseil d'administration de l'association - Voir la page [[Association Dolibarr]].

===Role H: Promoteur/Communication pour Dolibarr===

Objectif: Faire de la '''communication/évangélisation''' pour Dolibarr, sur les forums, sites de news, presse, etc... Mettre à jour la page wiki '''Revues de presse''' ([[Presse papier]]). Saisir des articles sur les sites de Dolibarr. Animer les réseaux sociaux.

Identifiés comme ayant ce rôle actuellement:

*L'[[Association Dolibarr]]
*Fonction à pourvoir. Merci aux amateurs de se manifester sur la ML Dolibarr. Volontaires fortement désirés.

Articles en relation: Quelques exemples de [[modèles de messages]] utilisés pour annoncer les beta ou release.

===Role I: Testeur Dolibarr===

Objectif: Tester la version courante de Dolibarr (Branch develop dand GIT) et reporter sur la mailing-list le maximum de bugs.

Identifiés comme ayant ce rôle actuellement:

*Une cinquantaine de personnes régulières environ (chiffre obtenu par analyse des messages du forum), beaucoup plus si on intègre les rapporteurs occasionnels.

===Role J: Administrer les noms de domaines===
Goal: Administrer les DNS/noms de domaines

Identifiés comme ayant ce rôle actuellement:
{{ListOfDomainAdmins}}

=[[File:workcomputer.png]] Les contributeurs sur GITHUB =

Chaque année est générée un classement des principaux contributeurs en terme de PR dans le code de Dolibarr
[[ContributeursPRGithub|Liste des contributeurs Github]]

=[[File:workcomputer.png]] Les accès GIT=

Le serveur GIT est hébergé chez {{TemplateUrlSCM}}

*Les instructions d'accès au GIT en lecture pour récupérer la version courante de développement sont sur [https://github.com/Dolibarr/dolibarr/ cette page]
*En ce qui concerne, les requêtes pour obtenir un accès en écriture, lire la [[FAQ_D%C3%A9veloppeur#Comment_devenir_d.C3.A9veloppeur_officiel|FAQ Comment devenir développeur officiel]] pour connaître l'organisation du projet et les étapes à franchir avant d'atteindre ce but.

=[[File:communaute.png]] Les canaux d'informations=
Voir la page [[FAQ Comment être informé de ce qui se passe sur Dolibarr ?]]

=[[File:Lug.png]] Comment aider le projet=
Voici une liste de pistes possibles pour vous permettre d'aider le projet Dolibarr.

'''Si vous êtes une développeur'''

*Si vous êtes un développeur, rejoignez l'équipe de développement Dolibarr pour contribuer au projet. Voir [[FAQ Développeur]] pour cela.

'''Si vous parlez une langue non anglophone'''

*Traduire Dolibarr dans votre langue si sa traduction n'existe pas ou est incomplète. Voir [[Documentation traducteur]].
*Soumettre des articles pour promouvoir Dolibarr sur les sites d'informations dans votre langue ou sur votre propre site. A défaut un lien vers le site https://www.dolibarr.org ne peut pas faire de mal.

'''Si vous n'êtes ni développeur, ni traducteur'''

*Vous pouvez compléter la documentation Dolibarr de ce wiki, notamment la rubrique [[Documentation utilisateur]].
{{Template:LinksToVoteForDolibarr}}

*Vous pouvez adhérer à l'association Dolibarr. [[Adhérer|Voir ici pour adhérer]].

'''Si vous voulez monter un groupe d'utilisateur ou une communauté locale'''

*Pour cela, lisez notre guide sur la page [[Create a Dolibarr local community]] (anglais uniquement).

=[[File:Lug.png]] Dons=
Même si vous ne voulez pas être membre de l'association Dolibarr, vous pouvez toujours faire une adhésion pour aider le développement financièrement: [[Adh%C3%A9rer]].

=[[File:Lug.png]] La mascotte=
La mascotte officielle du projet Dolibarr est le DoliBear. (vous pouvez l'acquerrir depuis le site https://goodies.dolibarr.org)

[[File:Mascot Dolibarr 1.jpg|border|300px|Le DoliBear, mascotte officielle de Dolibarr]]
[[File:Mascot Dolibarr 2.jpg|border|300px|Le DoliBear, mascotte officielle de Dolibarr, joue aux dés]]
[[File:Mascot Dolibarr 3.jpg|border|300px|Les DoliBears, mascottes officielles de Dolibarr]]
[[File:Mascot Dolibarr 4.png|border|300px|Le DoliBear, mascotte officielle de Dolibarr, sans fond]]

Application iOS et Android - DoliSmart

2025-08-22T16:32:05Z

Cbenke: indexation

{{TemplateDocUserFR}}

[[Category:Modules complémentaires]]
[[Category:Application Ios et Android - DoliSmart]]
[[Category:patas-monkey]]
[[Category:benke]]
<seo metak="application mobile, paramétrage avancé" />

=Informations=
{{TemplateModuleInfo
|modulename=DoliSmart
|editor=[[File:Dolismart by patas.png]]
|web=[https://www.dolismart.com/]
|status=stable
|minversion=18,0,0
|webbuy=www.dolistore.com[https://www.dolistore.com/product.php?id=2464&title=dolismart-dolibarr-depuis-un-smartphone-android-et-apple&l=fr]
|note=
}}

[[File:Presentation visuel dolismart.png]]

=Fonctionnalités=
DoliSmart offre un accès rapide, fluide et sécurisé à votre ERP depuis un smartphone, tout en respectant les habilitations définies.

*La solution nécessite le téléchargement de l'application gratuitement depuis les store Android ou Apple
*Un abonnement annuel est à commander sur notre boutique (tarif par volume de smartphone possible)
*Les communications entre Dolibarr et l'application mobile se font via les api de Dolibarr
*Il est possible d'accéder depuis l'application à plusieurs Dolibarr (limité à 3 environnements/profils).
*Un environnement de démonstration vous permet de tester toutes les fonctionnalités de l'application.

=Interface personnalisable=

Adaptez l’interface selon vos besoins métiers grâce à une personnalisation avancée directement depuis Dolibarr.

*Utilisation de la charte graphique de votre dolibarr
*Sélection des widgets sur les écrans principaux,
*Sélection des champs sur les écrans de détail et personnalisation de ceux-ci (renommage, surlignage, mise en gras)= Fonctionnalités clés =

*Connexion multi-comptes Dolibarr (jusqu’à 3 environnements)
*Gestion des tiers : clients et contacts
*Gestion des pièces commerciales : devis, commandes et factures
*Gestion des produits, stocks, expéditions et services
*Suivi de l'activité : contrats, interventions et tickets
*Fonction de recherche et navigation avancée dans toutes les sections
*Prise en compte de la charte graphique de votre entreprise et de la gestion des droits utilisateurs

=Fonctionnalités avancée=

*Gestion des Événements/Agenda associées aux éléments.
*Signature électronique des interventions et expéditions.
*Gestions des documents associés aux éléments.
*Et d'autres fonctionnalités à venir.

=Utilisation=

*Fiche technique [https://wwwdolismart.com]
*Démonstration [http://test.dolismart.com] : lien de menu secondaire "factory" du menu principal produit/services
*Guide utilisateur [https://wiki.patas-monkey.com/index.php?title=DoliSmart]

=Installation=

*Télécharger le fichier archive du module (.zip) depuis le site web dolistore.com
*Décompresser le fichier zip dans le répertoire '''/htdocs/''' de dolibarr.
*Le module peut alors être activé, paramétré si besoin (Accueil->Configuration->Modules) et utilisé

=Forum des utilisateurs=
Forum Dolibarr [https://www.dolibarr.fr/forum/t/dolismart-la-solution-mobile-pour-dolibarr/49744]

=Assistance=
Formulaire de contact [https://dolismart.com/index.php/31-2/]

2025-08-22T16:15:36Z

Cbenke: presentation dolismart mobile

Module DoliSmart

2025-08-22T16:10:55Z

Cbenke: nouveau module

[[Category:Modules complémentaires]]
[[Category:DoliSmart - DoliSmart]]
[[Category:patas-monkey]]
[[Category:benke]]
<seo metak="application mobile, paramétrage avancé"/>

= Informations =
{{TemplateModuleInfo
|modulename=DoliSmart
|editor=[[File:Patasmonkey.jpg]]
|web=[https://www.dolismart.com/]
|status=stable
|minversion=18,0,0
|webbuy=www.dolistore.com[https://www.dolistore.com/product.php?id=2464&title=dolismart-dolibarr-depuis-un-smartphone-android-et-apple&l=fr]
|note=
}}

= Fonctionnalités =
DoliSmart offre un accès rapide, fluide et sécurisé à votre ERP depuis un smartphone, tout en respectant les habilitations définies.

* La solution nécessite le téléchargement de l'application gratuitement depuis les store Android ou Apple
* Un abonnement annuel est à commander sur notre boutique (tarif par volume de smartphone possible)
* Les communications entre Dolibarr et l'application mobile se font via les api de Dolibarr
* Il est possible d'accéder depuis l'application à plusieurs Dolibarr (limité à 3 environnements/profils).
* Un environnement de démonstration vous permet de tester toutes les fonctionnalités de l'application.

= Interface personnalisable =

Adaptez l’interface selon vos besoins métiers grâce à une personnalisation avancée directement depuis Dolibarr.

* Utilisation de la charte graphique de votre dolibarr
* Sélection des widgets sur les écrans principaux,
* Sélection des champs sur les écrans de détail et personnalisation de ceux-ci (renommage, surlignage, mise en gras)

= Fonctionnalités clés =
* Connexion multi-comptes Dolibarr (jusqu’à 3 environnements)
* Gestion des tiers : clients et contacts
* Gestion des pièces commerciales : devis, commandes et factures
* Gestion des produits, stocks, expéditions et services
* Suivi de l'activité : contrats, interventions et tickets
* Fonction de recherche et navigation avancée dans toutes les sections
* Prise en compte de la charte graphique de votre entreprise et de la gestion des droits utilisateurs

= Fonctionnalités avancée =

* Gestion des Événements/Agenda associées aux éléments.
* Signature électronique des interventions et expéditions.
* Gestions des documents associés aux éléments.
* Et d'autres fonctionnalités à venir.

= Utilisation =
* Fiche technique [https://wwwdolismart.com]
* Démonstration [http://test.dolismart.com] : lien de menu secondaire "factory" du menu principal produit/services
* Guide utilisateur [https://wiki.patas-monkey.com/index.php?title=DoliSmart]

= Installation =
* Télécharger le fichier archive du module (.zip) depuis le site web dolistore.com
* Décompresser le fichier zip dans le répertoire '''/htdocs/''' de dolibarr.
* Le module peut alors être activé, paramétré si besoin (Accueil->Configuration->Modules) et utilisé

= Forum des utilisateurs =
Forum Dolibarr [https://www.dolibarr.fr/forum/t/dolismart-la-solution-mobile-pour-dolibarr/49744]

= Assistance =
Formulaire de contact [https://dolismart.com/index.php/31-2/]

Module Factory

2025-08-22T16:01:40Z

Cbenke: modification erreur

[[Category:Modules complémentaires]]
[[Category:Factory - Factory]]
[[Category:patas-monkey]]
[[Category:benke]]
<seo metak="aplication mobile, gestion de production, gestion, fabrication, composition"/>

= Informations =
{{TemplateModuleInfo
|modulename=Factory
|editor=[[File:Patasmonkey.jpg]]
|web=[https://www.patas-monkey.com/]
|status=stable
|minversion=18,0,0
|webbuy=www.dolistore.com[http://www.dolistore.com/fr/gestion-produits-ou-services/386-Factory--la-GPAO-pour-Dolibarr.html?search_query=factory&results=3]
|note=
}}

= Fonctionnalités =
Factory est le module de GPAO (gestion de produit assisté par ordinateur) de Dolibarr.
* Factory permet la composition, la planification de fabrication et complète la gestion globale de produits native de Dolibarr.
** Détermination de la composition
** Fabrication directe ou indirecte (ordres de fabrication)
** Grande ou petite série
** Interne ou externe
** Gestion des mouvements de stock associés
** Déclinaisons de produits.

= Utilisation =
* Fiche technique [http://patas-monkey.com/index.php/fr/support/repository/Pr%C3%A9sentation-de-nos-modules/Versions-fran%C3%A7aises/Pr%C3%A9sentation-Factory/]
* Démonstration [http://dlbdemo.patas-monkey.com/htdocs/factory/list.php?idmenu=45] : lien de menu secondaire "factory" du menu principal produit/services
* Guide utilisateur [http://patas-monkey.com/index.php/fr/support/repository/Documentation/FR/Guide-utilisateur-du-module-Factory/]

= Installation =
* Télécharger le fichier archive du module (.zip) depuis le site web dolistore.com
* Décompresser le fichier zip dans le répertoire '''/htdocs/''' de dolibarr.
* Le module peut alors être activé, paramétré si besoin (Accueil->Configuration->Modules) et utilisé

= Forum des utilisateurs =
Forum Dolibarr [http://www.dolibarr.fr/forum/511-creation-dun-nouveau-module/17277-module-gestion-de-production?start=90#57880]

= Assistance =
Formulaire de contact [http://patas-monkey.com/index.php/fr/contact/nous-contacter]

Module Factory

2025-08-22T15:57:29Z

Cbenke: Nouveau module

[[Category:Modules complémentaires]]
[[Category:DoliSmart - DoliSmart]]
[[Category:patas-monkey]]
[[Category:benke]]
<seo metak="aplication mobile, gestion de production, gestion, fabrication, composition"/>

= Informations =
{{TemplateModuleInfo
|modulename=Dolismart
|editor=[[File:Patasmonkey.jpg]]
|web=[https://dolismart.com/]
|status=stable
|minversion=18,0,0
|webbuy=www.dolistore.com[http://www.dolistore.com/fr/gestion-produits-ou-services/386-Factory--la-GPAO-pour-Dolibarr.html?search_query=factory&results=3]
|note=
}}

= Fonctionnalités =
Factory est le module de GPAO (gestion de produit assisté par ordinateur) de Dolibarr.
* Factory permet la composition, la planification de fabrication et complète la gestion globale de produits native de Dolibarr.
** Détermination de la composition
** Fabrication directe ou indirecte (ordres de fabrication)
** Grande ou petite série
** Interne ou externe
** Gestion des mouvements de stock associés
** Déclinaisons de produits.

= Utilisation =
* Fiche technique [http://patas-monkey.com/index.php/fr/support/repository/Pr%C3%A9sentation-de-nos-modules/Versions-fran%C3%A7aises/Pr%C3%A9sentation-Factory/]
* Démonstration [http://dlbdemo.patas-monkey.com/htdocs/factory/list.php?idmenu=45] : lien de menu secondaire "factory" du menu principal produit/services
* Guide utilisateur [http://patas-monkey.com/index.php/fr/support/repository/Documentation/FR/Guide-utilisateur-du-module-Factory/]

= Installation =
* Télécharger le fichier archive du module (.zip) depuis le site web dolistore.com
* Décompresser le fichier zip dans le répertoire '''/htdocs/''' de dolibarr.
* Le module peut alors être activé, paramétré si besoin (Accueil->Configuration->Modules) et utilisé

= Forum des utilisateurs =
Forum Dolibarr [http://www.dolibarr.fr/forum/511-creation-dun-nouveau-module/17277-module-gestion-de-production?start=90#57880]

= Assistance =
Formulaire de contact [http://patas-monkey.com/index.php/fr/contact/nous-contacter]

2018-10-29T10:30:10Z

Cbenke:

File:Charlène Benke.JPG

2018-10-16T12:14:58Z

Cbenke: Charlene Benke

Charlene Benke

2018-10-16T12:12:10Z

Cbenke: Created page with "Category:Everybody Category:User Active {{UserInfo| username=Charlène Benke| usercountry={{Flag_fr}}| userlogin=| userdate=2012-08-05| usercompany=Patas-Monkey| userweb..."

[[Category:Everybody]]
[[Category:User Active]]
{{UserInfo|
username=Charlène Benke|
usercountry={{Flag_fr}}|
userlogin=|
userdate=2012-08-05|
usercompany=Patas-Monkey|
userweb=http://www.patas-monkey.com/

|
usergrade={{Padavoine}}|
userstatus=active|
}}

Dolibarr Contributor.

DevCamp Valence 2018 Organization

2018-10-16T12:05:30Z

Cbenke: /* Attendees registration */

Charlie Benke

2018-01-29T13:15:29Z

Cbenke:

[[Category:Everybody]]
[[Category:User Active]]
{{UserInfo|
username=Charlène BENKE|
usercountry={{Flag_fr}}|
userlogin=cbenke|
userdate=1968-07-02|
userweb= www.benke.fr |
usercompany=Auto-Entrepreneur Patas-monkey
|
usergrade=aucun |
userstatus=active|
}}
Lead developper of Patas-monkey Team
Independant Dolibarr Modules Developers and sometimes Bug Corrector.

After 20 years of coding, Charlie BENKE started to write dolibarr modules at the beginning for it's own usage, then he made some core modules evolutions for its customer and now builds new module for enhance dolibarr feature.

Favorite Quote : "Code to Live, Live to Code"

File:Charlie b.JPG

2018-01-29T12:10:57Z

Cbenke: uploaded a new version of "File:Charlie b.JPG"

DevCamp Nancy 2018 Organization

2018-01-29T12:09:49Z

Cbenke: /* Validate registration */

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
'''Dolibarr Spring DevCamp 2018'''

First Dolibarr Devcamp in Nancy is planned.

The DevCamp is a meeting where developers meets each other to speak (and develop a little bit) about Dolibarr ERP CRM. We are speaking about What's new, best practice. Participating to the devcamp means you are and want to be evolved in Dolibarr project and knows the Dolibarr developers rules. It also means you are ready to speak during 2 days and 2 dates (see planning) with a dozen of other geeks. Talks done by project leader will be published on social networks.
This year, to avoid people subscribing and not coming, we are requesting to pay a 50 euros subscription. Number of places is limited to 20.

We hope to publish the main talks on social network like periscope or facebook live or youtube (to be defined)

== Dates ==
March 2018, 9-10-11

== Location ==
[HOTEL MERCURE NANCY CENTRE GARE],11 Rue Raymond Poincare
54000 NANCY - FRANCE
GPS :N 48° 41' 26.20'' E 6° 10' 28.51''

== How to come ==

* TrainStation : Nancy Centre - the hotel is 100m from the train station - Opposite the train station, Place Thiers exit
Shuttle to Lorraine TGV train station and Metz Nancy Airport nearby.
* Car: From Paris or Strasbourg: take the A4 motorways - From Brussels, Luxembourg and Dijon: take the A31 motorway. Head toward "centre ville" and then "gare SNCF"

== Main languages ==
* French / English

== Organizers ==
* Main: INOVEA CONSEIL (info@inovea-conseil.com) - TIARIS (jean.heimburger@tiaris.info)
* Hosting: INOVEA CONSEIL (info@inovea-conseil.com)
* Lodging and Catering: INOVEA CONSEIL (info@inovea-conseil.com)

== Lodging and catering ==
Meals and bedrooms will be provided during the devcamp by the Mercure hotel.

== Food ==
We will have a cocktail on Friday evening before dinner to welcome you in Nancy!

= Planning =

== Day 1 (Friday) ==
* 14:00 - Welcome - Presentation - Networking
* 18:00 - Presentation Dolibarr 7
* 20:00 - Dinner
* 21:00 - Bug tracking and closing issues

== Day 2 (Saturday) ==
* 8:00 - 12:00 - Bug tracking and closing issues
* 12:00 - Lunch
* 14:00 - 16:00 : Community tools presentation
* 17:00 : Dolibarr Foundation assembly
* 20:00 - Dinner
* Night : Dolibarr Hacking

== Day 3 (Sunday) ==
* 8:00 - 12:00 - Bug tracking and closing issues

= Topics and issues to work on =
''Open for suggestions and volunteers''
* Bugfix contest
* Tools for foundation
* Roadmap ?

= Attendees registration =
Please enter here your record if you plan to be present to this devcamp.
'''You need a wiki account. If you don't have it yet, send an email to contact@dolibarr.org to ask one or ask organisators '''.

* Lastname Firstname: CASTELLANO Claude
* Age:
* Coming from (town, country): Le Vigan (gard)
* Arrival date and hour: vendredi matin
* Departure date and hour: dimanche soir ou lundi matin
* Transportation (Train/Bus/Car/Plane): non décidé
* Food (Special diet, allergies, vegetarian, none…):
* Accommodation (Common booked hotel/self…): Mercure ou self, suivant le cas. Quelle est la date limite de réservation des chambres d'hotel?
* Book hotel for me (yes/no):à préciser ultérieurement
* Contact email:claude@cigaleaventure.com

= Validate registration =

'''To validate your registration, you must make a bank transfer of 50 € per person'''

Banque: CAISSE D'EPARGNE
Code banque: 14505
Code guichet: 00001
Numéro de compte: 08000207968
Clé: 70

Domiciliation: Agence Olivet
107, rue Jules-Marie Simon
45160 OLIVET
FRANCE
Nom du propriétaire du compte: Association Dolibarr
Code IBAN: FR76 1450 5000 0108 0002 0796 870
Code BIC/SWIFT: CEPAFRPP450

------------------------------------------

[[File:Nicolas_Zabouri.png‎|40px]]
* Lastname Firstname: [[Inovea Conseil | Nicolas ZABOURI]]
* Age: 35
* Coming from (town, country): Essegney (88), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Mercure
* Book hotel for me (yes/no): yes
* Contact email: info@inovea-conseil.com

[[File:Jean_Heimburger.png‎|40px]]
* Lastname Firstname: [[Jean_Heimburger | Heimburger Jean ]]
* Age: 57
* Coming from (town, country): Walscheid (57), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 16:00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Mercure
* Book hotel for me (yes/no): yes
* Contact email: jean.heimburger@tiaris.info

[[File:Laurent_Destailleur‎.png|40px]]
* Lastname Firstname: [[Laurent Destailleur|Laurent Destailleur]]
* Age: 45
* Coming from (town, country): Pessac (33), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): To be defined
* Book hotel for me (yes/no): yes
* Contact email: eldy@destailleur.fr

[[File:Philippe.GRAND.jpg|40px]]
* Lastname Firstname: [[Philippe Grand|Philippe Grand]]
* Age: unknown
* Coming from (town, country): Olivet (45), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): To be defined
* Book hotel for me (yes/no): no
* Contact email: philippe.grand@atoo-net.com

[[File:Maxime_Kohlhaas.png|40px]]
* Firstname Lastname:[[Maxime Kohlhaas]]
* Age: 30
* Coming from (town, country): Valence (26000), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…):Hotel Mercure
* Book hotel for me (yes/no): yes
* Contact email: maxime@atm-consulting.fr

[[File:Florian Henry.png|40px]]
* Lastname Firstname: [[Florian Henry]]
* Age: 37
* Coming from (town, country): Valence (26000), France
* Arrival date and hour: No
* Departure date and hour: No
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Hotel Mercure
* Book hotel for me (yes/no): yes
* Email for contact: florian.henry@atm-consulting.fr

[[File:Alexis Algoud.png|40px]]
* Lastname Firstname: [[Alexis Algoud]]
* Age: 37
* Coming from (town, country): Valence (26000), France
* Arrival date and hour: No
* Departure date and hour: No
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Hotel Mercure
* Book hotel for me (yes/no): yes
* Email for contact: alexis@atm-consulting.fr

[[File:.png|40px]]
* Lastname Firstname: [[Anthony Damhet]]
* Age: 33
* Coming from (town, country): Angoulême (16000), France
* Arrival date and hour: No
* Departure date and hour: No
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): self
* Book hotel for me (yes/no): no
* Email for contact: anthony.damhet@gmail.com

[[File:.png|40px]]
* Lastname Firstname: [[Olivier Tourvieille]]
* Age: 49
* Coming from (town, country): Angoulême (16000), France
* Arrival date and hour: No
* Departure date and hour: No
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): self
* Book hotel for me (yes/no): no
* Email for contact: o.tourvieille@gmail.com

[[File:Abbes_bahfir.png|40px]]
* Lastname Firstname: [[Abbes Bahfir]]
* Age: 51
* Coming from (town, country): Algiers (16000), Algeria
* Arrival date and hour: No
* Departure date and hour: No
* Transportation (Train/Bus/Car/Plane): Plane
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): self
* Book hotel for me (yes/no): no
* --> seem wrong Email for contact: o.tourvieille@gmail.com

[[File:Charlie_b.JPG‎|40px]]
* Firstname Lastname:[[Charlie Benke]]
* Age: 49
* Coming from (town, country): Lyon (69000), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): yes
* Contact email: charlie@benke.fr

DevCamp Orleans 2017 Organization

2017-03-01T00:11:19Z

Cbenke:

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
'''Dolibarr Spring DevCamp 2017'''

First Devcamp in Orléans, strongly foundation oriented, goal to work on next 6.0 release, adding a visit of Orléans.

== Dates ==
March 2017, 24-25-26

== Location ==
NOVOTEL ORLEANS SUD LA SOURCE, 2 rue Honoré de Balzac
ORLEANS 45100 - FRANCE
GPS. N 47° 48' 52.11'' E 1° 55' 43.65''
(Better ask Philippe for location).

== How to come ==

* Railway Station : Orléans centre.There you will take the tramway direction Hôpital de la Source (you go down to the last station and I will pick you up there)
* Car: From Paris on A10, head towards A71 Bourges Clermont-Ferrand, leave at exit 2 Olivet, Orléans La Source, La Ferté Saint Aubin. From Clermont-Ferrand on A71, leave at exit 2. After the lights, straight on for 1.2 miles, towards La Ferté Saint Aubin. DO NOT FOLLOW SIGNS FOR LA SOURCE. From Orleans center, take the D2020 (RN 20) towards Vierzon, La Ferté Saint Aubin, continue for 5 miles. At roundabout take 3rd exit. From La Ferté Saint Aubin, continue for 6.8 miles towards Orléans Centre.

== Main languages ==
* French / English

== Organizers ==
* Main: ATOO.NET (contact@atoo-net.com)
* Hosting: ATOO.NET (contact@atoo-net.com)
* Lodging and Catering: ATOO.NET (contact@atoo-net.com)

== Lodging and catering ==
Meals and bedrooms will be provided during the devcamp by the NOVOTEL hotel.

== Food ==
We will have a cocktail on Friday evening before dinner to welcome you in Orléans !

= Planning =

== Day 1 (Friday) ==
* 14:00 - Welcome

* 18:00 - Presentation "SEO on Dolibarr web sites"
* 19.00 - Cocktail
* 20:00 - Dinner

== Day 2 (Saturday) ==
* Presentation "Information for developers"
* A quick visit of Orleans
* Presentation "What's new in 6.0"

== Day 3 (Sunday) ==
* TO BE DEFINED

= Topics and issues to work on =
''Open for suggestions and volunteers''
* Bugfix contest
* Tools for foundation
* Roadmap ?

= Attendees registration =

------------------------------------------

[[File:Philippe.GRAND.jpg|40px]]
* Lastname Firstname: [[Grand Philippe]]
* Age:
* Coming from (town, country): Olivet (45160), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): no
* Contact email: philippe.grand@atoo-net.com

[[File:Laurent Destailleur.png|40px]]
* Lastname Firstname: [[Laurent Destailleur]]
* Age:
* Coming from (town, country): Pessac (33600, France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Train or Car
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): yes
* Contact email: eldy@destailleur.fr

[[File:Gschratzer.png|40px]]
* Lastname Firstname: [[Gschratzer| Schratzer Guido]]
* Age: 45
* Coming from (town, country): Salzburg, Austria
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 18:00
* Transportation (Train/Bus/Car/Plane): Plane + Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Campanile Orleans - La Source, 326, Rue de Chateaubriand, 45100 Orléans, Frankreich
* Book hotel for me (yes/no): no
* Contact email: guido.schratzer@backbone.co.at

[[File:Fappels.jpg|40px]]
* Lastname Firstname: [[Fappels| Appels Francis]]
* Age: 51
* Coming from (town, country): La Haye (50250), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): TBD
* Book hotel for me (yes/no): no
* Contact email: francis.appels@z-application.com

[[File:Jean_Heimburger.png|40px]]
* Lastname Firstname: [[Heimburger Jean]]
* Age:
* Coming from (town, country): Walscheid (57870), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Train/Car
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): yes
* Contact email: jean.heimburger@tiaris.info

* Lastname Firstname: [[Inovea Conseil | Nicolas ZABOURI]]
* Age: 34
* Coming from (town, country): Essegney (88), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Novotel
* Book hotel for me (yes/no): no
* Contact email: info@inovea-conseil.com

[[File:Charlie_b.JPG‎|40px]]
* Firstname Lastname:[[Charlie Benke]]
* Age: 48
* Coming from (town, country): Lyon (69000), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): yes
* Contact email: charlie@benke.fr

Setup Other

2016-11-06T13:56:02Z

Cbenke: /* Third parties module */

[[Category:Admin]]
{{TemplateDocUser}}

'''Help about screen:''' Other setup

'''Menu path:''' Home -> Setup -> Other

= Goal =
This page is built to add/edit new parameters without a dedicated page to edit them. In most cases, it is parameters for your own development, external modules, or hidden features.

For a standard usage of Dolibarr, this screen must be kept empty and not be used.

= List of known hidden options =
Some options are not visible in the interface (often because they are deprecated or beta features). In most cases you do not need these functions and their use may make the application unstable.

To enable them you have to define a constant to 1 in '''Home -> Setup -> Other setup''':

== Global options ==
* MAIN_FILESYSTEM_ENCODING => With some PHP version, PHP is not able to detect what is page code for filesystem of the server OS. To solve this, Dolibarr suppose your OS filesystem is UTF-8 if on linux or osx system, and iso-8859-1 if on Windows. If not, for example on a Windows server with a NTFS UTF-8 pagecode, you can set the variable MAIN_FILESYSTEM_ENCODING to "utf-8".

* MAIN_AUTO_TIMESTAMP_IN_PUBLIC_NOTES / MAIN_AUTO_TIMESTAMP_IN_PRIVATE_NOTES => Add a timestamp and user automatically when editing note (public or private depending on option).

* MAIN_SECURITY_CSRF_WITH_TOKEN (>= 5.0) => Activate a second anti CSRF protection on POST (a POST from another web site can't be done). Note there is already a default protection using test on referrer. This second protection uses TOKEN on forms and is less powerfull.

* MAIN_APPLICATION_TITLE => This will change the title of software (that appears on the login page by default). Warning, changing this may make Dolibarr version detection fails by smartphone applications like [[Application Android - DoliDroid]]

* MAIN_AUTOFILL_DATE => If this constant is defined (to something else than 0), the date of invoice, proposal, order or payment are filled with current date. It is highly recommended to NOT ENABLE this feature. This create a lot of input errors with no data not validated by users. This lead in bad values saved in database giving headaches when you have to do your accountancy reports ! However some users want it, so we provide it.

* MAIN_DISABLE_FULL_SCANLIST => Constant to define to disable complete scan of tables to know the total amount of element to allow the pagination to show total number of pages. To activate on systems with a very important number of data (Tables with more than 500 000 records).

* MAIN_FIRST_TO_UPPER => Dolibarr add upper case to thirdparties, contacts or members names if not done. Warning, with some languages (whose words with uppercase are not same words, or pagecode does not always have an uppercase, like cyrillic languages), this feature may alter your data.

* MAIN_ENABLE_LOG_TO_HTML (MAIN_LOGTOHTML before 3.9) => If this constants is defined, it is possible to have logs inside pages by adding the parameter &logtohtml=1 into URL.

* MAIN_USE_HOURMIN_IN_DATE_RANGE => On all entities lines (invoice, order, contract...), it is possible to add hour and minutes with date on fields "date start" and "date end".

* MAIN_REMOVE_INSTALL_WARNING => Remove all security warning that appears to administrator users if URL /install is public. You shoud solve the problem if warning occurs instead of removing this warning. For this, put a file called install.lock into Dolibarr root directory. This will remove warning but also make the page /install not possible to use to protect your installation.

* MAIN_OPTIMIZE_SPEED => Use some speed enhancements. See page [[Increase_Performance]] for more information.

* MAIN_REPLACE_TRANS_xx_XX => Where xx_XX is language code. If value is string1:newstring1;string2:newstring2 then replace string1 with newstring1 in all translation done for language xx_XX.

* MAIN_REPEATCONTACTONEACHTAB => If added and set to 1, this add contacts on all tabs, not only main tab.

* MAIN_DISABLE_JQUERY_JNOTIFY => Disable usage of JNotify to show confirm or error messages

* MAIN_USE_JQUERY_JEDITABLE => Allow to update from screnn, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this features, because, it overpass some business actions (updates onother data that should be done consitently) and ignore business controls on data you saved. So this feature breaks consitency of data and stability of software.

* MAIN_USE_JQUERY_MULTISELECT => Allow to use Ajax when a choice that require multiselect is used (for the moment only external modules uses select box with multiselect values). Set the value to the jQuery plugin name to use (multiselect, multiple-select, select2…). Setting it to any other value will result in unwanted side-effects and/or bugs.

* MAIN_HELPCENTER_LINKTOUSE => Define the url link to use as target for link "I need help" onto logon page

* MAIN_MODULES_FOR_EXTERNAL => Limit available modules for external users. By defaut value is 'facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda'

* MAIN_SHOW_TUNING_INFO => Add tuning information into javascript console. Better when xdebug is enabled.

* MAIN_DOL_SCRIPTS_ROOT => Define directory who contains 'scripts' directory (e.g /var/www/dolibarr)

* MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING => A warning saying setup of modules is not complete is shown if number of enabled modules is lower or equal than this value (1 if not defined)

* MAIN_ADD_SALE_REP_SIGNATURE_IN_NOTE => Add signature of first sale representative into documents (at end of public notes).

* MAIN_DISABLE_AJAX_COMBOX => If you have a large amount of thirdparty or product, you can disable the autocomplete feature on thirdparties list by setting constant MAIN_DISABLE_AJAX_COMBOX to 1 into Home-Setup-Other (with Dolibarr v3.6.0+).

* MAIN_USE_CACHE_MANIFEST => Add an HTML5 cache manifest to the page

* MAIN_FORCELANGDIR => relative path of the directory holding your custom langs folder.

* MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS => allow to define a default VAT rate

* MAIN_HTML_TITLE => can be used to control how html title is formated. If value contains key 'noapp', application name will not be output. If value contains 'thirdpartynameonly', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: 'noapp;thirdpartynameonly'

* MAIN_LANDING_PAGE => (>= 3.9) Can choose the first page to show after login. This option works as a global option (llx_const) and per user option (llx_user_param).

* MAIN_PROPAGATE_CONTACTS_FROM_ORIGIN => (>= 4.0) When creating an order, contract, invoice from another object, specific contacts of objects are set as specific contact of the new object when possible.

* MAIN_WEIGHT_DEFAULT_ROUND = Accuracy of weight (number of decimals)

* MAIN_WEIGHT_DEFAULT_UNIT = Default unit for weight (0=kg, -3=g, ...)

* MAIN_VOLUME_DEFAULT_ROUND = Accuracy of volume (number of decimals)

* MAIN_VOLUME_DEFAULT_UNIT = Default unit for weight (0=kg, -3=g, ...)

* MAIN_PUBLIC_NOTE_IN_ADDRESS >=4.0 => show public note in address block

== Look or Theme ==
* MAIN_OPTIMIZEFORTEXTBROWSER => Optimize output rendering for usage of a text browser (usefull for blind people)
* THEME_ELDY_DISABLE_IMAGE => Disabled images of top menu for eldy theme.
* MAIN_MENU_HIDE_UNAUTHORIZED => Hide menu if user not autorized rather than just grey them

== Email and SMS ==
* MAIN_MAIL_DEBUG => Write content with header of last mail into file dolibarr_mail.log into directory dolibarr_main_data_root.

* MAIN_SMS_DEBUG => Write content of SMS sent into file dolibarr_sms.log into directory dolibarr_main_data_root.

* MAIN_MAIL_ALLOW_SENDMAIL_F => On Linux or BSD system, PHP email function use the command sendmail local to server. In some cases, the sender email must be provided on command line of sendmail with option -f. This option is here to ask Dolibarr to call the function '''mail''' of PHP by adding value for the option -f. Note that in most cases, even with sendmail, sender email is correctly managed as it is added in the email technical header. This option is here only for rare setup of sendmail that ask the '''-f''' option to be mandatory or for sendmail setup that does not use by default the Return-path of header email to define the sender (with this option, the return-path will be provided also on command line and not lost by sendmail).

* MAIN_MAIL_SENDMAIL_FORCE_BA => On Lunix or BSD system, PHP email function use the command sendmail local to server. In some case, we want to recipient to be provided to sendmail into the email content instead of its command line parameter. For this we must add the '''-ba''' parameter to sendmail. This option ask PHP to provide this parameter when sending a mail. Note that another solution is to edit the '''mail.force_extra_parameters=-ba''' into '''php.ini''' file.

* MAIN_MAIL_NO_FULL_EMAIL => Recipient email and sender are cleaned to be on form "<email>" instead of "Name <email>". This might solve problem of compatibility with very old mailers.

* MAIN_FIX_FOR_BUGGED_MTA => Some MTA agent are bugged and add some CR chars each time they saw a LF. Because Dolibarr emails are forged to be already cleaned, if MTA agent do that, you will send an email with two CR chars. This may result in having recipient not able to read your email. To fix this, add this constant to 1. Dolibarr will then create an email that is not RFC compliant but because the MTA agent is bugged, the email will be modified and become correct during sending, solving the problem of bad email received. Add this constant if your recipient experience problems when opening email for example users using webmail of orange.fr or hotmail.com

* MAIN_MAIL_DO_NOT_USE_SIGN => Do not add user signature at end of suggested predefined email

* MAIL_FORCE_DELIVERY_RECEIPT_INVOICE, MAIL_FORCE_DELIVERY_RECEIPT_ORDER, MAIL_FORCE_DELIVERY_RECEIPT_PROPAL => Force delivery receipt to "Yes" onto form to send email.

* MAIN_EMAIL_USECCC => 1 = Show field BCC into email forms, If email = Show BCC prefilled with email.

* MAIN_MAIL_AUTOCOPY_PROPOSAL_TO, MAIN_MAIL_AUTOCOPY_ORDER_TO, MAIN_MAIL_AUTOCOPY_INVOICE_TO => Email to use as a BCC recipients when sending email for proposal, order or invoice. You can make this value visible by setting MAIN_EMAIL_USECCC (to 1 or to another email, see previous point)

* MAIN_EMAIL_ADD_TRACK_ID => When value is 1 (this is also default value if option is not set): The record "Message-id" added into smtp header includes a tracking id to define where the email was sent from. When value is 2: you send an email from thirdparty card, the sender email is completed with the email source tracking string "+thiXXX" on email (your email will be sent with the "From" that is myname+thi123@mycompany.com). So when user receiving email will make "Answer", email will be sent to myname@mycompany.com but with the tracking id included (into header or into target email), allowing you to know to which thirdparty or object, the email exchange is related to.

== Third parties module ==
* SOCIETE_DISABLE_CUSTOMERS => Remove all menu and features related to customers
* SOCIETE_DISABLE_PROSPECTS => Remove all menu and features related to prospects
* SOCIETE_DISABLE_STATE => Do not use field "state/province"
* THIRDPARTY_NOTCUSTOMERPROSPECT_BY_DEFAULT => Do not set status "Customer/Prospect" to "on" when creating a new third party from menu "New third party".
* THIRDPARTY_NOTSUPPLIER_BY_DEFAULT => Do not set status "Supplier" to "on" when creating a new third party from menu "New third party".
* SOCIETE_SORT_ON_TYPEENT = The combo list of "type of third party" is sorted on a field "position" that appears into dictionnary instead of alphabetical order.
* THIRDPARTY_DEFAULT_CREATE_CONTACT (Dolibarr 5.0+) => Default Thirparty create are individual
* MAIN_THIRDPARTY_CREATION_INDIVIDUAL (Dolibarr <5.0) => Default Thirparty create are individual
* THIRDPARTY_DEFAULT_USEVAT => When creating a new third party, the field "Use vat" is set to on or off depending on value of this parameter.
* THIRDPARTY_DEFAULT_USELOCALTAX1 => When creating a new third party, the field "Use second tax" is set to on or off depending on value of this parameter.
* THIRDPARTY_DEFAULT_USELOCALTAX2 => When creating a new third party, the field "Use third tax" is set to on or off depending on value of this parameter.

== Proposals module ==
* PROPAL_CLONE_ON_CREATE_PAGE => On the create proposal page, ask if we want to create the proposal by cloning an already existing one. You should use instead the "Clone" button available on existing proposals.
* MAIN_PROPAL_CHOOSE_ODT_DOCUMENT => On setup page, you'll be able to select which ODT document to use when close or cancel proposals.
* MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Add picture of product (the first one found if there is several) into the generated PDF of proposals. Note that using this reduce available width for product description.
* PROPAL_DISABLE_SIGNATURE => Do no show the box for signature.
* WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES => Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.
* PRODUIT_PDF_MERGE_PROPAL => When generating the proposal PDF, all PDFs linked to products linked to proposal are also included into final PDF

== Invoice module ==
* FACTURE_SHOW_SEND_REMINDER => Show link "Send reminder by mail", same feature than "Send by mail" (obsolete feature).
* INVOICE_CAN_ALWAYS_BE_REMOVED => Allow to always delete invoices (even if invoice is not last one).
* INVOICE_CAN_NEVER_BE_REMOVED => Never allow to delete invoices (except draft invoices).
* INVOICE_POSITIVE_CREDIT_NOTE => All amounts on PDF credit notes are positive.
* FACTURE_CHANGE_THIRDPARTY => Allow to change the third party in the draft invoices. If a discount was set from the original thirdparty, then discount remain, making data not coherent.
* FACTURE_USE_PROFORMAT => Enable PROFORMAT invoices type.
* FACTURE_DEPOSITS_ARE_JUST_PAYMENTS => Treats deposit invoices as a special case. Deposit invoices don't get counted on turnover. They are then applied as a payment, like a discount, on the final invoice. By default, when you include the deposit into draft of final invoice, the amount of final invoice is reduced. With this option, final amount is not reduced but a payment is registered.
* FACTURE_SENDBYEMAIL_FOR_ALL_STATUS => Can send invoice by email to customer even if invoice has status "draft".
* MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT => Disable VAT on genrated documents. like for an association. (it's work with crabe template)
* INVOICE_AUTO_FILLJS (FAC_AUTO_FILLJS < 4.0) => Display a button to autofill the payment amount for each invoice on the payment creation page
* INVOICE_CREDIT_NOTE_STANDALONE (dolibarr 3.9) => Can make a credit note without invoice.
* INVOICE_USE_SITUATION = Enable the "situation invoice" feature
* INVOICE_DISABLE_DEPOSIT = Disable deposit invoices
* INVOICE_DISABLE_REPLACEMENT = Disable replacement invoices
* INVOICE_DISABLE_CREDIT_NOTE = Disable credit notes
* WORKFLOW_BILL_ON_SHIPMENT = Change label of button with suitable label when you need to create invoice on shipments

== Order module ==
* COMMANDE_REQUIRE_SOURCE => Make the input field "Source of order" mandatory.
* COMMANDE_VALID_AFTER_CLOSE_PROPAL => When an order is created on a proposal close, the order is directly defined with status "Validated".

== Export module ==
* EXPORT_CSV_SEPARATOR_TO_USE => String value to use as separator to delimit fields int exported files (by default Dolibarr use ","). Example: EXPORT_CSV_SEPARATOR_TO_USE=;
* EXPORT_CSV_FORCE_CHARSET => Choose the charset of file built by CSV export. By default: UTF-8. Example: EXPORT_CSV_FORCE_CHARSET=ISO-8859-1
* EXPORTTOOL_CATEGORIES => Can export categories (several lines) into one column with the "product export profile"
* USE_STRICT_CSV_RULES => Use strict/real CSV format for export. Do not clean/replace CR+LF with '\n' but quote them using the escaping CSV char (").

== Agenda module ==
* AGENDA_MAX_EVENTS_DAY_VIEW => Define the maximum number of visible entries for each day in agenda. Default value is 3. Value 0 means no limit.
* AGENDA_USE_EVENT_TYPE => Add a mandatory field "Type" when creating an event (deprecated).
* AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS => To automatically set end date of event to start date + delta on event creation page.
* MAIN_ADD_EVENT_ON_ELEMENT_CARD => Allow to create an event from a document (proposal, order, invoice)

== Products module ==
* MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE => Avoid Custom code and country of origin to be set as product description when added to Propal/Order/Invoice
* PRODUCT_ADD_TYPE_IN_DOCUMENTS => Add text "Product" or "Service" at beginning of details lines on built PDF documents.
* PRODUCT_DONOTSEARCH_ANYWHERE => When Ajax search is enabled, search is done on criteria anywhere in label of product. By adding this option, search is done only on start of label. This is really faster when you have a huge number of products.
* PRODUIT_DESC_IN_LIST => Show long description of product/service into lists.
* PRODUIT_MULTIPRICES_LABELx (where x = 1,2,...) => When option mode to set prices are PRODUIT_MULTIPRICES (n different prices per product according to a customer level), this option will force a label for the level x. Value must be a key. If the key is found into translation files, it will be replaced by the translated value.
* PRODUIT_PDF_MERGE_PROPAL => Enable module Propal merge product PDF
* PRODUCT_USE_OLD_PATH_FOR_PHOTO => Ask dolibarr to check also old path (before 3.7) where photos were stored.
* PRODUCT_USE_UNITS => Enable units from dictionary in product/service card.

== Services module ==
* SERVICE_ARE_ECOMMERCE_200238EC => If this option is enabled, services are processed like eServices according to directove of EU Council Directive 2002/38/EC (http://ec.europa.eu/taxation_customs/taxation/vat/traders/e-commerce/article_1610_en.htm). Default VAT rate are based on buying country instead of selling country for BtoC sells.

== Stocks ==
* STOCK_SUPPORTS_SERVICES => Services are also increased/decreased into stocks.
* SUPPLIER_ORDER_DISABLE_STOCK_DISPATCH_WHEN_TOTAL_REACHED => Disable stock dispatch when total expected was already received.

== Point of Sale ==
* CASHDESK_SHOW_KEYPAD => Show a mouse key pad into Point Of Sale.

== Contracts ==
* CONTRACT_SUPPORT_PRODUCTS => Products are also suggested into module contract.

== Projects module ==
* PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS => Enable linking a project to any supplier even when using the third party link feature. Note: Set to 1 by default from 3.7.
* PROJECT_TIME_ON_ALL_TASKS_MY_PROJECTS => Can add time spent on tasks, even if i am not assigned to task (however, task must be a project i am a contact).
* PROJECT_SHOW_REF_INTO_LISTS => Add column with project ref into list (with 3.7 list of supplier invoices only, will be expanded to other lists)
* PROJECT_HIDE_UNSELECTABLES => Hide into select list, all project that we can't select (closed or draft)
* PROJECT_HIDE_TASKS => Hide tasks. For user using project only as an analytics key and not using tasks.
* PROJECT_LIST_SHOW_STARTDATE => Shows start date of projects in project lists.
* PROJECT_LINK_ON_OVERWIEW_DISABLED (4.0) => Hide the "link to" form on the overview page
* PROJECT_CREATE_ON_OVERVIEW_DISABLED (4.0) => Hide the "create ..." button on the overview page
* PROJECT_DEFAULT_PUBLIC (4.0) => 1=Set default value of visibility to "public" when creating a project

== Foundation module ==
* MEMBER_URL_REDIRECT_SUBSCRIPTION => Link called and shown when a member account is autocreated in member module by a guest user.
* MEMBER_EXT_URL_SUBSCRIPTION_INFO => Link of external page pointed by the "Show here" link to add in fron off payment cell form into the page to make online subscription.

== Interventions module ==
* FICHINTER_CLASSIFY_BILLED => Allow to classify an intervention card as "Billed". This add also trigger FICHINTER_CLASSIFY_BILLED into list of possible automatic event into agenda.
* FICHINTER_DISABLE_DETAILS => Disable entry of details line on intervention. Can validate with no line.

== Suppliers module ==
* FOURN_PRODUCT_AVAILABILITY => On the Suppliers price page of the products, active the supplier product availability. This is duplicate feature with delivery_delay introduced with 3.8.
* SUPPLIER_ORDER_AUTOADD_USER_CONTACT => Add user approving supplier order as a contact automatically.
* SUPPLIER_ORDER_USE_DISPATCH_STATUS => Add a status on each dispatch order line
* SUPPLIER_ORDER_NO_DIRECT_APPROVE => No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.
* SUPPLIER_ORDER_WITH_NOPRICEDEFINED => Can enter a product even if no supplier price defined.

== Bank module ==
* BANK_CAN_RECONCILIATE_CASHACCOUNT (3.8) => Can reconciliate cash accounts
* BANK_DISABLE_CHECK_DEPOSIT => Disable check deposit feature

== PDF options ==
* MAIN_DISABLE_FORCE_SAVEAS => If your browser ask always to save downloaded files on disk (like PDF), try to add this option. File might appears directly into your browser.

* MAIN_DISABLE_PDF_COMPRESSION => Disable PDF compression.

* MAIN_INVERT_SENDER_RECIPIENT => Invert sender and recipient in some PDF.

* MAIN_DISABLE_PDF_AUTOUPDATE => Disable automatic generation of PDF each time we add/update/delete a product line (we can still build document by clicking on "Generate"). This option may increase interface speed on server with low CPU.

* MAIN_USE_BACKGROUND_ON_PDF => Define this constant with short name of an image (example "myimage.jpg") that must be saved into directory "documents/mycompany/logos". This will add this background image into your generated PDF files. Warning: This option make TCPDF library beeing crazy sometime and content on image disappeared !

* MAIN_ADD_PDF_BACKGROUND => Define this constant with short name of a PDF file (example "mypdf.pdf") that must be saved into directory "documents/mycompany". This will add PDF as a background of some of your generated PDF files (proposals,invoices,orders). If you need to concat PDF, see instead [[Module Concat PDF]].

* MAIN_PDF_FORCE_FONT => To ignore font defined into language file and force usage of a particular font. For example "DejaVuSans".

* MAIN_PDF_MARGIN_LEFT, MAIN_PDF_MARGIN_RIGHT, MAIN_PDF_MARGIN_TOP, MAIN_PDF_MARGIN_BOTTOM => To force the margins (mm) of PDF documents (10 is default).

* MAIN_PDF_FREETEXT_HEIGHT => Change height of space reserved to output the free text.

* MAIN_PDF_TITLE_BACKGROUND_COLOR => Can define a background color onto title line. Example: '220,220,200'

* MAIN_USE_COMPANY_NAME_OF_CONTACT => Use contact name and information rather than company

* MAIN_ODT_AS_PDF => Activate PDF conversion from ODT document. If value is 'jodconverter', java and jodconverter command line tool must be available. If value is '/pathto/jodconverter.jar', then java and the jodconvertar jar must exists. soffice must also be available. MAIN_DOL_SCRIPTS_ROOT Must also be defined to path where the "scripts" directory is stored (for example /var/www/mydolibarr).

* MAIN_ODT_AS_PDF_DEL_SOURCE => For ODT generation. If set then initial behaviour is conserved, odt file is removed when generate pdf. Disabled by default

* MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Include first image of product into line of generated PDF proposal.

* MAIN_GENERATE_INVOICES_WITH_PICTURE => Include first image of product into line of generated PDF invoice.

* MAIN_DOCUMENTS_WITH_PICTURE_WIDTH => Can change size of picture when hidden option MAIN_GENERATE_PROPOSALS_WITH_PICTURE is used. By default value is 20.

* MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN => Hide column with VAT information but only column not total.

* PDF_SHOW_PROJECT => Show project onto PDF (supported on supplier order only for the moment)

* PDF_BANK_HIDE_NUMBER_SHOW_ONLY_BICIBAN => Hide bank number ("code banque/guichet/compte" for france, "sort number/account" for GB, ...) and keep only BIC/IBAN on PDF.

== WYSIWYG editor ==

* FCKEDITOR_ENABLE_DETAILS_FULL => Can cut and paste external images (hosted on external server) into description of proposal, orders or invoices. WARNING: PDF generation is not guaranted with this. Also if the image is removed or renamed by the image hoster, your proposal, order or invoice will be broken.

Charlie Benke

2016-10-20T08:43:13Z

Cbenke: moved Charlie BENKE to Charlie Benke

[[Category:Everybody]]
[[Category:User Active]]
{{UserInfo|
username=Charlie BENKE|
usercountry={{Flag_fr}}|
userlogin=cbenke|
userdate=1968-07-02|
userweb= www.benke.fr |
usercompany=Auto-Entrepreneur Patas-monkey
|
usergrade=aucun |
userstatus=active|
}}
Lead developper of Patas-monkey Team
Independant Dolibarr Modules Developers and sometimes Bug Corrector.

After 20 years of coding, Charlie BENKE started to write dolibarr modules at the beginning for it's own usage, then he made some core modules evolutions for its customer and now builds new module for enhance dolibarr feature.

Favorite Quote : "Code to Live, Live to Code"

Charles-Fr BENKE

2016-10-20T08:41:56Z

Cbenke: moved Charles-Fr BENKE to Charlie BENKE

#REDIRECT [[Charlie BENKE]]

Charlie Benke

2016-10-20T08:41:56Z

Cbenke: moved Charles-Fr BENKE to Charlie BENKE

Charlie Benke

2016-10-20T08:41:31Z

Cbenke:

DevCamp Valence 2016 Organization

2016-10-20T07:54:07Z

Cbenke: /* Attendees registration */

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
'''Dolibarr Christmas DevCamp 2016'''

2nd Devcamp in Valence after 2014, strongly technical oriented, goal to work on next 5.0 release, adding christmas gifts and chocolates ;)

== Dates ==
December 2016, 9-10-11

== Location ==
Ibis Hotel, 2-4 avenue de la Gare, Alixan (near Valence), France

== How to come ==
* Airplane: Lyon airport then train to Valence TGV
* Train: Valence TGV train station
* Car: Exit the A7 highway at Valence North or Valence South and follow TGV Station (Gare TGV)

== Main languages ==
* French / English

== Organizers ==
* Main: ATM Consulting (contact@atm-consulting.fr)
* Hosting: ATM Consulting (contact@atm-consulting.fr)
* Lodging and Catering: ATM Consulting (contact@atm-consulting.fr)

== Lodging and catering ==
Meals and bedrooms will be provided during the devcamp by the Ibis hotel. Feel free to bring sweets and beverages at your convenience.

== Food ==
We will have a cocktail on Friday evening before dinner to welcome you in Valence !

= Planning =

== Day 1 (Friday) ==
* 14:00 - Welcome

* 19.00 - Cocktail
* 20:00 - Dinner

== Day 2 (Saturday) ==
* TO BE DEFINED

== Day 3 (Sunday) ==
* TO BE DEFINED

= Topics and issues to work on =
''Open for suggestions and volunteers''
* Bugfix contest
* Accountancy module stability
* Multi-currency module stability
* Roadmap ?

= Attendees registration =

------------------------------------------
[[File:Maxime_Kohlhaas.png|40px]]
* Firstname Lastname:[[Maxime Kohlhaas]]
* Age: 29
* Coming from (town, country): Valence (26000), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 16:00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): No
* Contact email: maxime@atm-consulting.fr
------------------------------------------

------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname:[[Laurent Destailleur]]
* Age: 44
* Coming from (town, country): Pessac (33600), France
* Arrival date and hour: Friday 15:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): yes
* Contact email: eldy@destailleur.fr
------------------------------------------

------------------------------------------
[[File:Charlie_b.JPG‎|40px]]
* Firstname Lastname:[[Charlie Benke]]
* Age: 48
* Coming from (town, country): Lyon (69000), France
* Arrival date and hour: Friday 15:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): yes
* Contact email: charlie@benke.fr
------------------------------------------

File:Charlie b.JPG

2016-10-20T07:52:22Z

Cbenke:

DevCamp Valence 2016 Organization

2016-10-20T07:44:51Z

Cbenke: /* Attendees registration */

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
'''Dolibarr Christmas DevCamp 2016'''

2nd Devcamp in Valence after 2014, strongly technical oriented, goal to work on next 5.0 release, adding christmas gifts and chocolates ;)

== Dates ==
December 2016, 9-10-11

== Location ==
Ibis Hotel, 2-4 avenue de la Gare, Alixan (near Valence), France

== How to come ==
* Airplane: Lyon airport then train to Valence TGV
* Train: Valence TGV train station
* Car: Exit the A7 highway at Valence North or Valence South and follow TGV Station (Gare TGV)

== Main languages ==
* French / English

== Organizers ==
* Main: ATM Consulting (contact@atm-consulting.fr)
* Hosting: ATM Consulting (contact@atm-consulting.fr)
* Lodging and Catering: ATM Consulting (contact@atm-consulting.fr)

== Lodging and catering ==
Meals and bedrooms will be provided during the devcamp by the Ibis hotel. Feel free to bring sweets and beverages at your convenience.

== Food ==
We will have a cocktail on Friday evening before dinner to welcome you in Valence !

= Planning =

== Day 1 (Friday) ==
* 14:00 - Welcome

* 19.00 - Cocktail
* 20:00 - Dinner

== Day 2 (Saturday) ==
* TO BE DEFINED

== Day 3 (Sunday) ==
* TO BE DEFINED

= Topics and issues to work on =
''Open for suggestions and volunteers''
* Bugfix contest
* Accountancy module stability
* Multi-currency module stability
* Roadmap ?

= Attendees registration =

------------------------------------------
[[File:Maxime_Kohlhaas.png|40px]]
* Firstname Lastname:[[Maxime Kohlhaas]]
* Age: 29
* Coming from (town, country): Valence (26000), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 16:00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): No
* Contact email: maxime@atm-consulting.fr
------------------------------------------

------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname:[[Laurent Destailleur]]
* Age: 44
* Coming from (town, country): Pessac (33600), France
* Arrival date and hour: Friday 15:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): yes
* Contact email: eldy@destailleur.fr
------------------------------------------

------------------------------------------
* Firstname Lastname:[[Charlie Benke]]
* Age: 48
* Coming from (town, country): Lyon (69000), France
* Arrival date and hour: Friday 15:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): None
* Book hotel for me (yes/no): yes
* Contact email: charlie@benke.fr
------------------------------------------

DevCamp Genova (Italy) 2016 Organization

2016-05-11T08:23:09Z

Cbenke: /* Registration */

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
'''Title: Dolibarr DevCamp 2016'''

The event is held in Italy for the first time and will include two parts this year:
* A public event to present the project
* The usual community meeting

== Price ==
The full event is ''free'' but all participants must register ([[#Registration_template|see below]]).

== Dates ==
June 3-4-5

* Public presentation: June 3rd TBD (afternoon)
* Community meeting: June 4th-5th

=== Registrations ===
* Public event:
** Details will be available soon
* Community meeting:
** [[#Registration_template|Here on the wiki]] before '''May, 29th'''

== Location ==
Main location: CONDIVISO, Calata Andalò di Negro, 16,16126 Genova, Italia

=== Capacity ===
* Public event: ~60 people (friday afternoon)
* Community meeting: ~40 people

=== How to come ===
Airplane: see directions at goo.gl/xnxsl6
Train: take the metro and get off at "Darsena". Then walk for 500m following directions at goo.gl/fmnPuh
Car: Exit the autoroute at "Genova Ovest" than head towards city center.

== Main languages ==
* Public presentation: Italian
* Community meeting: English

== Organizers ==
* Main: Diciannove (dolibarr@19.coop)
* Hosting: CONDIVISO (info@condiviso.coop)
* Lodging and Catering: Diciannove
* Sponsoring management: Diciannove

=== Sponsors ===
(details available soon)

=== Partners ===
(details available soon)

== Lodging and catering ==
(details available soon)

=== Hotel ===
(details available soon)

=== Food ===
(details available soon)

= Planning =

== Day 1 (Friday) ==

(details available soon)
== Day 2 (Saturday) ==
(details available soon)
== Day 3 (Sunday) ==
(details available soon)

= Workshop topics =

If you plan attending the community meeting event, feel free to share the topics you'd like to see covered.
- Practical use of github for committing and share issues
- Practical use of Transifex
- How to improve module developpements : version compatibility, tests
- Technical infos on Dolibarr techniques : objects, hooks , api,
- How to build and développement efficient local communities to suport project

= Attendees registration =

== Public presentation ==

(link and facebook event available soon)

== Community meeting ==

Registration is done here, on the wiki

Please copy the template below and paste it into the registered attendees section and fill it with your data.

To be able to edit the page and register, you'll need a wiki account. If you don't have one please ask for one via email at '''contact@dolibarr.org'''.

'''Registration for Dolibarr devcamp 2016 in Genoa, Italy will close on May 29th'''

== Registration ==

------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname: [[Laurent Destailleur]]
* Age: 44
* Coming from (town, country): Pessac, France
* Arrival date and hour: ???
* Departure date and hour: ???
* Transportation (Train/Bus/Car/Plane): Plane + Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: contact@destailleur.fr
------------------------------------------

------------------------------------------
[[File:Philippe.GRAND.jpg|40px]]
* Firstname Lastname:[[Philippe Grand]]
* Age:
* Coming from (town, country): Olivet (45160), France
* Arrival date and hour: ???
* Departure date and hour: ???
* Transportation (Train/Bus/Car/Plane): Train + car
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: philippe.grand@atoo-net.com
------------------------------------------

------------------------------------------
[[File:Maxime_Kohlhaas.png|40px]]
* Firstname Lastname:[[Maxime Kohlhaas]]
* Age: 29
* Coming from (town, country): Valence (26000), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: maxime@atm-consulting.fr
------------------------------------------

------------------------------------------
[[File:Pierre-Henry_Favre.png|40px]]
* Firstname Lastname:[[Pierre-Henry Favre]]
* Age: 26
* Coming from (town, country): Valence (26000), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: phf@atm-consulting.fr
------------------------------------------

------------------------------------------
[[File:Jean_Heimburger.png|40px]]
* Firstname Lastname:[[Jean Heimburger]]
* Age: 56
* Coming from (town, country): WALSCHEID (57), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): To be defined
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): yes
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: jean.heimburger@tiaris.info
------------------------------------------

------------------------------------------
[[File:Gschratzer.png|40px]]
* Firstname Lastname: [[Gschratzer| Guido Schratzer]]
* Age: 45
* Coming from (town, country): Salzburg, Austria
* Arrival date and hour: ???
* Departure date and hour: ???
* Transportation (Train/Bus/Car/Plane): Plane + Car
* Food: N.A.
* Accommodation: booked myself Hotel Novotel Genova City
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: guido.schratzer@backbone.co.at
------------------------------------------

------------------------------------------
[[File:Lorenzo Novaro.png|40px]]
* Firstname Lastname: [[Lorenzo Novaro]]
* Age: 35
* Coming from (town, country): Genova, Italy
* Arrival date and hour: Already present
* Departure date and hour: Lives in Genova
* Transportation (Train/Bus/Car/Plane): Bike
* Food: N.A.
* Accommodation: Lives in Genova
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: novalore@19.coop
------------------------------------------

------------------------------------------
[[File:Firstname Lastname.png|40px]]
* Firstname Lastname: [[Claudio Aschieri]]
* Age: 31
* Coming from (Parma, Italy):
* Arrival date and hour: beginning of devcamp
* Departure date and hour: end of devcamp
* Transportation: Car
* Food: N.A.
* Accommodation: N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: c.aschieri@19.coop
------------------------------------------

------------------------------------------
[[File:Tommaso Basilici.png|40px]]
* Firstname Lastname: [[Tommaso Basilici]]
* Age: 37
* Coming from (Genova, Italy):
* Arrival date and hour: already present
* Departure date and hour: Lives in Genova
* Transportation:
* Food: N.A.
* Accommodation: Lives in Genova
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: t.basilici@19.coop

------------------------------------------
[[File:Firstname Lastname.png|40px]]
* Firstname Lastname: [[Paolo Selis]]
* Age: 39
* Coming from (Parma, Italy):
* Arrival date and hour: beginning of devcamp
* Departure date and hour: end of devcamp
* Transportation: Car
* Food: N.A.
* Accommodation: N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: c.aschieri@19.coop
------------------------------------------
[[File:Firstname Lastname.png|40px]]
* Firstname Lastname: [[Bogdan Dumitrasconiu]]
* Age: N.A.
* Coming from (Bucharest, Romania):
* Arrival date and hour: beginning of devcamp
* Departure date and hour: TBD
* Transportation: Plane/ Bus
* Food: N.A.
* Accommodation: N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: office@prova-nov.ro
------------------------------------------

------------------------------------------
[[File:Charles.png|40px]]
* Firstname Lastname:[[Charlène Benke]]
* Age: 47
* Coming from (town, country): Lyon (69003), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: charlie@patas-monkey.com
------------------------------------------

------------------------------------------
[[File:romain_deschamps.png|40px]]
* Firstname Lastname:[[Romain Deschamps]]
* Age: 35
* Coming from (town, country): Lyon (69004), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: r.deschamps@patas-monkey.com
------------------------------------------

== Community meeting registered attendees ==

2014-12-28T18:07:14Z

Cbenke: /* PHP Norms */

{{TemplateDocDevEn}}

This is some rules on language, syntax and norm we use into Dolibarr project:

= Versions =
* Dolibarr must works on:
# All OS (Windows, Linux, MACOS...)
# PHP {{PHPMinVersion}} (Must works with no need of complementary PHP module, except module to PHP module to access database).
# Mysql {{MySqlMinVersion}}

= Copyright Norms =
* All PHP files must start with a header that looks like
<source lang="php">
<?php
/* Copyright (C) YYYY John Doe <email@email.com>
*
* Licence information
*/
...
</source>
When you edit an existing file of project, you must add a Copyright line under others.

= PHP Norms =
* Dolibarr is written with PHP and supports all PHP version higher than {{PHPMinVersion}}. All files must end with extension .php

* Usage of superglobals PHP variables must use dedicated operators $_COOKIES, $_SERVER, $_ENV but use Dolibarr function GETPOST() to get content of $_GET or $_POST..
Other operators ($HTTP_SERVER_GET, ...) are now deprecated inside PHP, so they must no more be used. Like that code will works alos if option '''register_long_arrays''' is to off.
Moreover, the code must works when PHP option '''register_globals''' is off (recommended by PHP). It must works the same way that when option '''register_globals''' is on (by default on a lot of installations).

* Do not use '''PHP_SELF'''. Use instead $_SERVER["PHP_SELF"].

* When several variables must be initialized with same value, you must use several lines
<source lang="php">
$var1=1;$var2=1;$var3=1;
</source>
instead of
<source lang="php">
$var1=$var2=$var3=1;
</source>
that is slower.

* String must be rounded by simple quote and variable inside string must be out of the quote.
<source lang="php">
print 'My text show my '.$variable.' !';
</source>

* Comments must use the C syntax, ie a double anti-slash for a comment on one line and a slash-star to open a bloc for several lines
<source lang="php">
/* Bloc of comment
*
* End of bloc
*/

$monobjet = new MonObjet($db);
$result=$monobjet->fetch($idobject);

for ($i = 1 , $i < 2 ; $i++)
{
// comment on one line
print $i;
}

</source>

* Functions must return a value strictly higher than 0 if successful and strictly lower than 0 if error.

* No dead code (code never used) into Dolibarr core code (code used by external modules only must be included into external modules).

* Use "include_once" for anything with functions or class definitions in it (so *.class.php and *.lib.php files), use "include" for template-style php with files containing a mix of HTML and PHP (so *.inc.php and *.tpl.php files).

* Coding style to use is based on Travis CI : during pull request Travis CI verify rules of coding, if travis say OK : the coding rule is OK

= SQL rules =

== Table structures ==

* Structure of tables.
When you create a new table, it is recommended to use the same conventions as other Dolibarr tables. This means the following fields:
- rowid integer for id
- tms timestamp that will contain date of last modification (the database manages this field automatically, no need to manage it by the code, just create the field)
- import_key that will contains the import code YYYYMMDDHHMMSS if you make mass import.
Eventualy
- datec timestamp that is the creation date
- fk_user_creat integer that is the id of user making creation
- fk_user_modif integer that is the id of user making change

Note field:
- note_private text for private comment of the object
- note_pubic text for public comment of the object
or
- note text if there is no need to have private and public

* Type of fields:
Well, to be compatible with any accuracy required by any country on amounts, and with any database syntax, we will use the following type into database:
- integer for an any of foreign key
- double(24,8) for any amount
- double(6,3) for any vat rate
- real for a quantity
- varchar for a string (also if length is 1, the type char is more and more deprecated)
- timestamp for a field date+time that is automatically updated
- datetime for a field date+time
- date for a field date

* All tables has a prefix to avoid name conflicts with other projects. In current version this prefix is fixed ans can't be modified. Its value is <tt>llx_</tt>. In a future version this value should be modified during installation process.

== Primary keys ==
The primary key of a table must be called <tt>rowid</tt>.

Some old tables does not use this rule and use a primary key called <tt>id</tt> (ie [[Table llx_c_actioncomm]]), but the reason is history and this should not happens anymore.

== Foreign keys ==
A foreign key name must start with prefix <tt>fk_</tt> followed by the table name linked (this is required to avoid duplicate names in project that are not allowed even if on different tables by some DBMS like Postgresql) then the name of child field (this is to allow to have several foreign keys on same table).

Example:
''fk_facture_fourn_fk_soc'' is a foreign key on table llx_facture_fourn for field fk_soc in this table (that link to the rowid field in another table)

Note: If you develop your own external module, it must have no foreign keys that point to Dolibarr standard tables. This will break standard dolibarr upgrades, repair, backup and restore tools and may also break standard features.

== Alternative keys ==
Sometimes, we need another unique keys than primary key. We can add in this case an alternate unique key. When we need this, we can create an alternate unique key. Such an index is called by a name that start by prefix <tt>uk_</tt> followed by an underscore, then the the table name (this is required to avoid duplicate names of unique keys that may create problems for some DBMS like Postgresql) and then another string to define the key (this is to allow to have several unique keys on same table).

Example:
''uk_societe_code_client'' is a unique key on table llx_societe on field code_client.

== Index performance ==
Some fields are often used as search or order criteria, or for joins. In such case, we need to set a performance index on field to increase performances. Such indexes are named with a prefix <tt>idx_</tt> then the table name and then the field name.

Example:
''idx_societe_user_creat'' is a performance index on table llx_societe for field user_creat

== DDL file format ==
Files that contain definition of the database structure (DDL files) must be 2 per tables:
* Each table is defined by its own file whose name is <tt>llx_''mytable''.sql</tt>
A comment will be added on each field to explain its usage.
* All foreign keys, performance indexes or other constraints will be defined into another file called <tt>llx_''mytable''.key.sql</tt>

Those files must be stored into directory '''install/mysql/tables''' for all standard files or '''mymodule/tables''' for tables provided by an external module.

Example '''file of table llx_mytable.sql''':

<source lang="sql">
-- ===========================================================================
-- Copyright (C) 2013 Author <email@author.com>
--
-- This program is free software; you can redistribute it and/or modify
-- it under the terms of the GNU General Public License as published by
-- the Free Software Foundation; either version 3 of the License, or
-- (at your option) any later version.
--
-- This program is distributed in the hope that it will be useful,
-- but WITHOUT ANY WARRANTY; without even the implied warranty of
-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-- GNU General Public License for more details.
--
-- You should have received a copy of the GNU General Public License
-- along with this program. If not, see <http://www.gnu.org/licenses/>.
-- ===========================================================================

create table llx_mytable
(
rowid integer NOT NULL AUTO_INCREMENT PRIMARY KEY,
ref varchar(30) NOT NULL, -- object reference number
entity integer DEFAULT 1 NOT NULL, -- multi company id
ref_ext varchar(255),-- reference into an external system (not used by dolibarr)
field_one integer,
field_two integer NOT NULL,
fk_field integer,
field_date datetime,
datec timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,, -- creation datetime
tms timestamp, -- update time stamp
fk_user_author integer NOT NULL, -- Author, foreign key of llx_user
fk_user_mod integer NOT NULL, -- Last updater, foreign key of llx_user
import_key varchar(14) -- Use by import process
)type=innodb;
</source>

Example '''file for keys/indexs on llx_mytable.key.sql''':

<source lang="sql">
-- ===========================================================================
-- Copyright (C) 2013 Author <email@author.com>
--
-- This program is free software; you can redistribute it and/or modify
-- it under the terms of the GNU General Public License as published by
-- the Free Software Foundation; either version 3 of the License, or
-- (at your option) any later version.
--
-- This program is distributed in the hope that it will be useful,
-- but WITHOUT ANY WARRANTY; without even the implied warranty of
-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-- GNU General Public License for more details.
--
-- You should have received a copy of the GNU General Public License
-- along with this program. If not, see <http://www.gnu.org/licenses/>.
-- ===========================================================================

ALTER TABLE llx_matable ADD UNIQUE uk_matable_field(field_one, field_two);

ALTER TABLE llx_matable ADD CONSTRAINT fk_matable_fk_field FOREIGN KEY (fk_field) REFERENCES llx_matablepere (rowid);
</source>

== SQL Coding rules ==
* Alias usage/Fields naming
When doing select, we can use alias to simplify writing/reading of requests:
<source lang="sql">
select chp1, chpxxx2 as chp2 from table2 as t1, table2 as t2 where t1.chpx = t2.chpy
</source>
However, we must not used alias for update request as they are not compatible with Mysql 3.1.

* All SELECT * are forbidden ! Any SELECT must define complete list of fields to get. This avoid confusion. Example:
<source lang="sql">
SELECT field_a, field_b, field_c FROM table_1 WHERE field_d = '$id'
</source>

* Into SQL requests, you must quote fields except fields that contains amounts that must be stored as double or real type. Quotes on numbers may results in saving a different value. For example 412.62 in an insert will be saved with value 412.61999512 into database (due to implicit conversion string to numeric) if target field has type double(24,8). Only PHP see value 412.61999512. Other tools will see 412.62 giving sensation that there is no problem. But it's PHP that hase the good vision. There is really a wrong value into database. By removing quotes on numbers, no problem occurs.

Example:
<source lang="sql">
Good: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', 412.62)
Bad: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', '412.62')
</source>

Note, problem of float numbers is same problem on all langauges and not only when inserting data into database. It occurs also with any language when you work on "real" numbers, so numbers must be, as soon as they are affected, cleaned with function price2num with second parameter defined to :
'MU' (for unit prices), 'MT' (for total prices) or 'MS' (otherwise) depending on usage of number. (see function documentation)

* Functions NOW or SYSDATE are forbidden inside SQL requests. If you must use the current date into a field, value must come from the PHP and not from the database engine. This is to avoid a better portability of code and a correct management of TimeZone.

== Mysql specificities ==
* Tables must be declared with format InnoDB.
This format support foreign keys and their restrictions, and transactions integrity is also supported. This guarantee that Dolibarr events keep all data with correct values between tables even even transaction modify different tables.

* Dolibarr must works even if Mysql option '''strict''' is active.
To activate it (recommanded when developping on Dolibarr), add the following line into the config file of your Mysql server (my.cnf or my.ini)
<source lang="ini">
sql-mode="STRICT_ALL_TABLES,ONLY_FULL_GROUP_BY,NO_ZERO_DATE"
</source>

== PostgreSQL specificities ==
Only Mysql SQL files must be maintained.
Those files are converted "on the fly" by the database Dolibarr driver.

There is an exception
The SQL "UPDATE FROM" :
Syntax MySQL :
<source lang="sql">
UPDATE table_taget as target, table_source as source SET fieldtarget=source.fieldsource
WHERE source.rowid=target.rowid;
</source>

Syntax PgSQL:
<source lang="sql">
UPDATE table_taget as target SET fieldtarget=source.fieldsource
FROM table_source as source WHERE source.rowid=target.rowid;
</source>

There is no native SQL request "update from" in dolibarr core. But in your module you should do :
<source lang="php">
if ($this->db->type=='pgsql') {
$sql="UPDATE table_taget as target SET fieldtarget=source.fieldsource
FROM table_source as source WHERE source.rowid=target.rowid";
} else {
$sql= "UPDATE table_taget as target, table_source as source SET fieldtarget=source.fieldsource
WHERE source.rowid=target.rowid";
}
</source>

= HTML norms =
== Syntax rules ==
* HTML used must be HTML compliant and not XHTML. All attributes of HTML tags must be in lower case and quoted with ".

* Links href must be absolute and use the function dol_buildpath() to get absolute path from a relative path and img tag must be build using function img_picto().
For example:
<source lang="php">
print '<a href="'.dol_buildpath('/mydir/mypage.php').'">'.img_picto('Texte alt','namepictopng','').'</a>';
</source>

* HTML tables must have columns with no forced width, except for columns that contains data we know the length. For example, a column with a picto only can be forced to with="20px".
Otherwise, we must avoid forcing the column width. Reason is that, in most cases, the browser make a better works to define column width automatically than forced values, and it works whatever is the resolution.

* Javascript/ajax code and call to javascript files into php pages must be avoided. However, if you need to include javascript code, you must add a condition on "$conf->use_javascript_ajax"
<source lang="php">
if ($conf->use_javascript_ajax) {
... // php code generating javascript here
}
</source>

* Popups windows must not be used, except for tooltips (and must have a condition as explained before).

* External scripts must be written into Perl if they can't be written into PHP. Usage of another language is not forbidden but must be argue before onto development mailing-list.

== External templating framework ? ==
There is ton of frameworks to provide a templating language of an HTML page. The best and faster is just called "PHP", and because Dolibarr already depends on PHP, there is no need for depend on a third languages.

All templating frameworks are just preprocessor, BEFORE PHP. It can't be faster than PHP alone. When we say "speed, when using cache of templating framework, is increase", it is in fact the overtime spent by the framework that is reduced by cache, not the speed of processing PHP file. We should says "any templating framework has an overload over PHP, the cache of framework, just reduce the slowing effect of using it", but not "the speed is increased, it is always increased".

Above all, having a templating system is completely possible by doing a "'''.tpl.php'''" file that dos not contains any logic code, but only HTML and echo. We get same result (but faster and easier to develop because it does not need to do all the setXXX) before calling each template. All variables (known by code that include the template) are automaticaly known into a PHP template page. No risk to forget a set, and a lot of line of codes reduced, a lot of time saved.

Also, keeping a 100% isolation between code and HTML output is interesting in only 1 situation: When teams building design is complety different than team building logic code, AND if you build not too sophisticated pages, AND with no need of too many Ajax features (this need to know how code works).
And this situation is surely not the Dolibarr future (team will often be same, Ajax will be more and more present, event if I hope not too much, and screens are more and more dependent of dynamic or contextual events, difficult to have with a template without transforming the template into a page with high level of code).

There is a ton of other reasons to not use an external templating system and all arguments to use them are the best argument to use PHP as our templating system.

= Dolibarr norms and code skeleton =

== Skeleton code ==
To standardize the code, and to speed up the development of new components in Dolibarr, you'll find 4 skeletons fully prepared in the directory '''dev/skeletons'''.

* 1 that serves as an example of the module description: '''myModule.class.php'''
* 1 that serves as an example of code for creating a new class: '''skeleton_class.class.php'''
* 1 that serves as an example of code for creating a new page: '''skeleton_page.php'''
* 1 that serves as an example of code for creating a script for executing command lines: '''skeleton_script.php'''

Use it as an example.
Note that the skeletons are also used by the PHP code generator, which is described in the development chapter of Dolibarr modules, to speed up your development.

== Dates and Timezones ==
Dolibarr is an application that is multi-user and multi-location. It's therefore necessary to store dates in the right format. To avoid problems with conversions, the following rules should be applied:

* A date into memory must always be stored with Timestamp GMT format.
* A date stored into database, is the GMT Timestamp of date submitted into the request usng the PHP server timezone. This does not apply to date update automatically by database (fields '''tms''' into database).
For exemple le 1st january 1970, 3 hour at Paris (TZ=+1) = 2 hour at Greenwitch (TZ=0) will be stored into memory with value 7200 and will be submitted into a SQL request to database with the string '19700101030000' (PHP convert into its TZ hour and databse will unconvert it using its timezone too that is same than PHP).

All select methods should translate date fields, that are with format TZ of database ('19700101030000'), into a timestamp field by calling the method db->jdate. This is to store into memory a GTM Timestamp date. All insert methods must convert, during generation of SQL request, the memory date into the string by using db->idate (you may find examples into skeleton).

* Dates that are updated automatically (field '''tms''' into database) contains a GMT Timestamp GMT of date when change is done. The select will also use the db->jdate (that use PHP server TZ) to convert read data into a GMT Timestamp into memory. So if timezone of database differs from timezone of PHP server (one of them is not correctly set), you may experience differences between creation date and update date.

* Manipulation date with PHP must be done using the Dolibarr date functions: '''dol_now(), dol_mktime(), dol_stringtotime(), dol_getdate(), dol_time_plus_duree()'''. You may also find other functions available into file '''date.lib.php'''.

== UTF8/ISO encoding ==
Dolibarr stores data in the following way:
* In database, data is stored in UTF8 or ISO. It depends on the database's pagecode therefore these options are set at creation time. In any case, Dolibarr's database driver (in lib/database) deals with it to convert from/to UTF8 at insertion and readout.
* Memory data is stored in UTF8 (PHP object instances).
* Screen displayed web pages are UTF8 (for versions prior to 2.5.1, the deprecated $character_set parameter from conf.php file defines output format).

== Float numbers, amount and calculation ==
With PHP, like other languages (Java for exemple), non integer data (float, real, double) are not reliable for calculation.
Try to make for example
<source lang="php">
print 239.2 - 229.3 - 9.9;
</source>
You wont get zero but a very small decimal number. If you get zero her, you should be able to find other examples that don't work.
Problem of float is general, so a variable that is a result of a calculation using decimal numbers must ALWAYS be cleaned using the function '''price2num()''' with the econd parameter to: 'MU', 'MT' or 'MS' depending on need (see description of function).
<source lang="php">
print price2num(239.2 - 229.3 - 9.9, 'MT');
</source>
If data manipulated is not an amount, so using MU, MT, MS has no sense, so you must use the function '''round()'''.

== Creation of tables ==
Do not create tables, on the fly, during execution by a standard user, we mean, during current usage of software.
If you create a module that use its own table not available into default Dolibarr code, take a look at tutorial [[Module Development]] that will explain you how roviding new tables with your module to have the created during module activation and not during module usage.

== Logs ==
Add logs to your code using function
<source lang="php">
dol_syslog($yourmessage, LOG_INFO|LOG_DEBUG|LOG_WARNING|LOG_ERR);
</source>

== Working directory ==
If you need to create a working directory, into your code, refer to it with
'''DOL_DATA_ROOT.'/monmodule''''

The directory can be created into your code by the following fnction:
<source lang="php">
$mymoduledir=DOL_DATA_ROOT.'/monmodule';
dol_mkdir($mymoduledir);
</source>

If you need a directory to store temporary data, this directory must be '''DOL_DATA_ROOT.'/monmodule/temp''''

= Design patterns and Object programming =

== Creation design patterns (GoF) ==
Design patterns defined by the Gang Of Four (see wikipédia on [[wikipedia:Design pattern|Design patters]]).
No usage of such patterns is required. We found some objects next to Singletons or Factory but not completely compliant with syntax, this is to be compatible with PHP 4 that is not a pure object language.

== Structure design patterns (GoF) ==
Design patterns defined by the Gang Of Four (see wikipédia on [[wikipedia:Design pattern|Design patters]]).
No usage of such patterns is required.

== Behavior design patterns (GoF) ==
Design patterns defined by the Gang Of Four (see wikipédia on [[wikipedia:Design pattern|Design patters]]).
No usage of such patterns is required.

== Design patterns of enterprise (Martin Fowler) ==

=== Patterns of code organization ===
[[wikipedia:Martin Fowler|Martin Fowler]] has identified 3 ways to organize code:
* The '''Transaction Script''' (The source code is linear for each user action).
This is the old school used by all procedural languages.
Inconvenient: Redundancy of code. Need to know the physical model of data to develop.
* The '''Domain Model'''
This notion is available with object languages. It is business process (to identify before) that are used for objects classes.
Inconvenient: Model very complex to maintain.
* The '''Table Module'''
This is a mix between 2 previous where we have only one unique class for each table of database.

-> As shown in code skeletons (see previous chapter), Dolibarr use concept of '''Table Module'''.

=== Communication between business logic - data (ORM) ===

There is 3 way to make links:

* The '''Table And Row Data Gateway'''
This is the most simple. You have one class per table and each class is a link to the table with CRUD methods (Ceate, Read, Update, Delete). A class instance is a record a the table. The class contains only code to reach lines and fields of table.

Example: This mode is used by some ORM Frameworks, like '''iBatis''' (http://ibatis.apache.org/).

* The '''Active Record'''
Same than previous, but we are allowed to add some business functions into the class, if such functions are dedicated to the table or recordng into this table.

Example: This mode is used for Dolibarr development and most PHP softwares that includes their own framework and best practices.

* The '''Data Mapper'''
Classes represent entities of the problem and not the data. So you have to double, triple ... theese classes with Mapper classes to access the data.
More "purist" on paper (closer of business), this method also has the disadvantage of being more complex in practice.

Example: This is the choice if you use the ORM Framework '''Propel''' (http://propel.phpdb.org/trac/). We find this model on heavier applications, based on this ORM among others.

-> For Dolibarr development, it is recommended to use the connection mode '''Active Record''', which offers the advantages of a model close to the business without having the complexity, without obfuscating the technique. It is in this way that the development, understanding of code and technical maintenance and / or business seems the more productive (this is however an ongoing debate between the purists and the pragmatists, debate in which nobody can really be right, because it depends on the objectives).