Dolibarr ERP CRM Wiki - User contributions [en]

Setup Other

2026-09-15T07:47:22Z

Iouston: add recruitment section

[[fr:Paramétrage_Divers]]
[[es:Configuración_Varios]]
[[de:Erweiterte_Einstellungen]]
[[zh:其他设置]]


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

'''Help About Screen''': Other setup

'''Menu Path''': Home ► Setup ► Other

'''Introduction'''

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

{{warning|32px}} This page contains the list of some advanced development parameters. In most cases, they are parameters for internal usage, development, external modules, features in development not stable or that may lead to security risk. For standard usage of Dolibarr, such parameters '''SHOULD NOT''' be used. All experimental options are NOT supported. They may be removed in a future, modified at any version and break stability of your application.

To enable/override a parameter you have to define the constant name and set it to 1 (unless otherwise stated) in <code>Home ► Setup ► Other Setup</code>

The options here may not be documented since they are not stable and are unsupported (remember they are experimental or development options). The basic format of how the list is written is broken down in the example below:

UNSTABLE_OR_DEV_OPTION ► ''Description of config and goal'' ► ''(specific version information) or values''
<center>
__TOC__
</center>
=Global Options=

*'''ADD_UNSPLASH_LOGIN_BACKGROUND''' ► The background image will be refreshed on every login page refresh. Background image is pulled from the popular open source image website Unsplash. If an already saved static background image exists, then this code will override it (but not delete the saved image). Warning: Using this may allow this external website to steel your login credentials (the value to be put is the URL of the service, exemple : https://source.unsplash.com/random) ► (v10.0)
*'''MAIN_HIDE_POWERED_BY''' ► Hide the "Powered by Dolibarr" picto on public pages
*'''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 to fail by smartphone applications like [[Application Android - DoliDroid]], breaking some features when using Dolibarr from such application. If the text start with a "+", the text will be added to the standard "Dolibarr" label instead of replacing it.

*'''MAIN_AUTOFILL_DATE''' ► If this constant is defined (to something other than <code>0</code>), the date of invoice, proposal, order or payment are auto-filled with the current date. It is highly recommended to NOT ENABLE this feature. This can create a lot of input errors with data not validated by users. This leads to incorrect values saved in the database causing confusion when you have to do your accountancy reports!
*'''MAIN_AUTOFILL_DATE_PROPOSAL►'''If this constant is defined (to something other than 0), the date of proposal is auto-filled with the current date.

*'''MAIN_AUTO_TIMESTAMP_IN_PUBLIC_NOTES''' ► Add a timestamp and user automatically when editing the ''public'' note.

*'''MAIN_AUTO_TIMESTAMP_IN_PRIVATE_NOTES''' ► Add a timestamp and user automatically when editing the ''private'' note.

*'''MAIN_DEFAULT_PAYMENT_TERM_ID''' ► With ID of a payment term, will use this as default payment term each time you create a new proposal, order, invoice (customer and supplier). Deprecated. Replaced with the default setup feature instead (see French page of wiki for some exemple : [[Paramétrage Valeurs par défaut]])
*'''MAIN_DEFAULT_PAYMENT_TYPE_ID''' ► With ID of a payment type, will use this as default payment type each time you create a new proposal, order, invoice (customer and supplier). Deprecated. Replaced with the default setup feature instead (see French page of wiki for some exemple : [[Paramétrage Valeurs par défaut]])

*'''MAIN_DEFAULT_LANGUAGE_FILTER''' ► Useful if you do not want to show <code>en_US</code> language option in combo boxes (other languages can easily be removed in <code>langs</code> directory but not <code>en_US</code>) ► (v10.0)

*'''MAIN_LANGUAGES_ALLOWED''' ► Is a list of languages without spaces, example : <code>fr_FR,en_US,de_DE,it_IT</code> If defined, only those languages will appear in combos. ► (v11.0)

*'''MAIN_DISABLE_NOTES_TAB''' ► Show or hide notes tab in the card page

*'''MAIN_DISABLE_CONTACTS_TAB''' ► Show or hide contacts tab in the card page

*'''MAIN_DISABLE_FULL_SCANLIST''' ► Disables the complete scan of tables to allow the pagination to show total number of pages. May be useful to activate on systems with a very high quantity of data (tables with more than 2 000 000 records).

*'''MAIN_DISABLE_JQUERY_JNOTIFY''' ► Disable usage of <code>JNotify</code> to show confirm or error messages

*'''MAIN_DISABLE_AJAX_COMBOX''' ► If you have a large number of third parties or products, you can disable the autocomplete feature on the third parties list by setting this constant to <code>1</code> ► (v3.6.0+)
*'''MAIN_DISABLE_MULTIPLE_FILEUPLOAD''' ► Disable users to upload multiple files at once.
*'''MAIN_DISABLE_TRUNC''' ► Disable all truncings in select list. ► (v7.0+)

*'''MAIN_DISABLEDRAFTSTATUS''' ► Disable the status "Draft" for some objects (project, donation, ...) so the object is directly created with status "Validated"

*'''MAIN_DOC_USE_OBJECT_THIRDPARTY_NAME''' ► Add name of thirdparty at begin of generated document.

*'''MAIN_DOC_USE_TIMING''' ► Add a timestamp at end of generated document. Value must be format of timestamp. For example: <code>%Y%m%d%H%M</code> (only for ODT files)

*'''MAIN_DOC_UPLOAD_NOT_RENAME_BY_DEFAULT''' ► Disable the auto renaming on upload file ► (v10.0)

*'''MAIN_DOL_SCRIPTS_ROOT''' ► Define directory who contains 'scripts' directory (e.g. <code>/var/www/dolibarr</code>). Value of this variable may be requested by some external script or tools.

*'''MAIN_ENABLE_LOG_TO_HTML''' ► If this constant is defined, it is possible to have logs inside pages by adding the parameter <code>&logtohtml=1</code> into URL.

*'''MAIN_ENABLE_IMPORT_LINKED_OBJECT_LINES''' ► Allow to import lines into current document from "linked" compatible documents ► (v8.0+)

*'''MAIN_FIRST_TO_UPPER''' ► Dolibarr add uppercase to Third Parties, 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_ALL_TO_UPPER''' ► Dolibarr puts uppercase for Third Parties, 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. ► (v11.0)

*'''MAIN_ALL_TOWN_TO_UPPER''' ► Dolibarr puts uppercase for town names if not done. ► (v13.0)

*'''MAIN_FILESYSTEM_ENCODING''' ► With some PHP versions, PHP is not able to detect the page code for filesystem of the server OS. To solve this, Dolibarr assumes your OS filesystem is <code>UTF-8</code> if on Linux or OSX system, and <code>ISO-8859-1</code> if on Windows. If not, for example on a Windows server with a NTFS <code>UTF-8</code> pagecode, you can set the variable <code>MAIN_FILESYSTEM_ENCODING</code> to "<code>utf-8</code>".

*'''MAIN_FORCELANGDIR''' ► Relative path of the directory holding your custom <code>langs</code> folder.
*'''MAIN_HTML_TITLE''' ► Can be used to control how the html page title is formatted. If value contains key '<code>noapp</code>', application name will not be output. If value contains '<code>thirdpartynameonly</code>', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: '<code>noapp;thirdpartynameonly</code>'

*'''MAIN_HELPCENTER_LINKTOUSE''' ► Define the URL link to use as the target page for link "I need help" onto logon page

*'''MAIN_LOGOUT_GOTO_URL''' ► URL to which the user will be redirected after LOGOUT

*'''MAIN_MAXTABS_IN_CARD''' ► Maximum number of tabs visible. Others are grouped into a combo list.

*'''MAIN_MAXLIST_OVERLOAD''' ► Maximum number of line in space's domain.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► A warning saying setup of modules is not complete is shown if the number of enabled modules is lower or equal than this value (<code>1</code> if not defined)

*'''MAIN_NO_CONCAT_DESCRIPTION''' ► Allow to use only input custom description in lines (proposal, order, invoice) ► (v10.0) < v20.0. [ OSBOLETE since 20.0 | SEE Product module admin configuration to set the description behavior of products and services ]. This value is overwritten by PRODUCT_AUTOFILL_DESC, controled by the option in the product module admin configuration, and is no longer used. Kept in code to allow compatibility if custom modules are using it. Removed completely from v22.

*'''MAIN_OPTIMIZE_SPEED''' ► Use some speed enhancements. See page [[FAQ Increase Performance]] for more information.
*'''MAIN_PASSWORD_FORGOTLINK ►''' Change forgotten password link on login page. ► (v9.0)

*'''MAIN_PROPAGATE_CONTACTS_FROM_ORIGIN''' ► When creating an order, contract, invoice from another object, specific contacts of objects are set as specific contact of the new object when possible. ► (v4.0+)

*'''MAIN_PUBLIC_NOTE_IN_ADDRESS''' ► Show public note in address block ► (v4.0+)

*'''MAIN_REMOVE_INSTALL_WARNING''' ► Remove all security warnings that appear to administrator users if URL <code>/install</code> is public. You should solve the problem if warning occurs, instead of removing the warning! For this, create a file called <code>install.lock</code> into Dolibarr root directory. This will stop the warning but also make the page <code>/install</code> not possible to use, to protect your installation.

*'''MAIN_REPEATCONTACTONEACHTAB''' ► If added and set to <code>1</code>, this adds contacts on all tabs, not only main tab.

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

*'''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND''' ► Change way of rounding total including tax of lines, rounding first of after.

*'''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND_SUPPLIER'''► Change way of rounding total including tax of lines, rounding first of after.

*'''MAIN_SERVER_TZ''' ► If you can't set the time zone of your PHP installation, set this constant. Better is to set it to UTC. In future, this constant will be forced to '<code>UTC</code>' so PHP server time zone will not have effect any more. Examples: <code>Europe/Paris</code>, <code>auto</code>. Dolibarr will apply the timezone before saving dates in the database. Meaning that if you remove the parameter the dates saved will not change back to UTC.

*'''MAIN_SEARCH_FORM_ON_HOME_AREAS''' ► Show the search form on home page areas for core modules (Removed after v5 due to global search combo) ► (v6.0+)

*'''MAIN_SEARCHFORM_SUPPLIER_INVOICE_DISABLED''' ► Disable the supplier invoice on the search form

*'''MAIN_SEARCH_DIRECT_OPEN_IF_ONLY_ONE''' ► If only one result is found, then setting this value to <code>1</code> will take you direct to the item (default method). Setting the value to <code>0</code> will show the result in the list as a single result ► (v5.0+)

*'''MAIN_SERVICES_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country. It can have value '1' or '2'. If value 2, the VATs available to select only the ones of buying country. If '1', the VATs available to select mix the ones of selling country and the ones of buying country. ► (v18.0+)

*'''MAIN_SHOW_TUNING_INFO''' ► Add tuning information into JavaScript console. Better when xdebug is enabled.

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show also technical IDs on elements cards or some lists (not supported everywhere).

*'''MAIN_SHOWDATABASENAMEINHELPPAGESLINK''' ► Show database name in upper help menu ► (v8.0+)

*'''MAIN_USE_ALTERNATE_TRANSLATION_FOR''' ► List of fields per object that need an alternate translation. Example: <code>MAIN_USE_ALTERNATE_TRANSLATION_FOR=societe:name,town;contact:firstname,lastname</code>

*'''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_USE_JQUERY_JEDITABLE''' ► Allow to update from screen, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this feature, because it bypasses some business actions (updates on other data that should be done consistently) and ignores business controls on data you saved. Consequently this feature breaks consistency of data and possibly the stability of the 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_USE_OLD_SEARCH_FORM''' ► Display the old search form in left menu.

*'''MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS''' ► Allow to force the VAT rate to a given value (instead of higher VAT rate of country) if the VAT rate of product was not defined.

*'''MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES''' ► If we can't guess if a thirdparty is a company or individual (not VAT ID fill, no Prof ID fill, no type of thirdparty fill), then we suppose it is a company (B2B business) if 1, we suppose it is an individual (B2C business) if 0.

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► For intra CEE sales, we use by default, on proposal, order or invoice creation, a 0 VAT for customers that are companies (see MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES to change behaviour to know if a thirdparty is a company or an individual). But if the option MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL is set, we will use the 0 VAT only if a VAT ID is defined for the customer.

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_INDIVIDUAL_CUSTOMER_OUT_OF_EEC''' ► For to use the default VAT of product for individual customers that are out E.E.C. (European Economic Community) ► (v7.0+). ''There is no reason to use this.''

*'''MAIN_VIEW_LINE_NUMBER''' ► Shows a line number for each line of products/services at documents like proposal / order / invoice. Only on screen, not on PDF.

*'''MAIN_VIEW_LINE_NUMBER_IN_LIST''' ► Shows a line number in lists ► (v12.0)

*'''MAIN_VOLUME_DEFAULT_ROUND''' ► Accuracy of volume (number of decimals)

*'''MAIN_VOLUME_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''MAIN_WEIGHT_DEFAULT_ROUND''' ► Accuracy of weight (number of decimals)

*'''MAIN_WEIGHT_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''USER_HIDE_INACTIVE_IN_COMBOBOX''' ► Disable display inactive users in combobox.

*'''MAIN_DISABLE_PDF_THUMBS''' ► Disable thumbs PDF in case of imagick bug

*'''MAIN_KEEP_REF_CUSTOMER_ON_CLONING''' ► Keep the Customer Reference on cloned object (Propal/Invoice)

*'''MAIN_DONT_KEEP_NOTE_ON_CLONING''' ► Remove the object notes during cloning ► (v11.0)

*'''MAIN_DOC_SORT_FIELD''' ► Set the default sorting field on document page (name by default) ► (v11.0)

*'''MAIN_DOC_SORT_ORDER''' ► Set the default sorting order (ASC or DESC) on document page (ASC by default) ► (v11.0)

*'''MAIN_USE_ZIPTOWN_DICTIONNARY''' ► Use dictionary ZIP for create card.

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Show search in top menu with theme eldy ► (v11.0)

*'''MAIN_PHONE_SEPAR''' ► Separ phone number other space ► (v12.0)

*'''GRAPH_USE_FISCAL_YEAR''' ► Widgets uses fiscal year

*'''SHOW_SOCINFO_ON_PRINT''' ► Permit to add user company information on each printed document (when click on Dolibarr print button) ► (v12.0)

*'''MAIN_FEATURES_LEVEL''' ► Level of features to show: <code>-1=stable+deprecated</code>, <code>0=stable only (default)</code>, <code>1=stable+experimental</code>, <code>2=stable+experimental+development</code>

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show technical id for object.

*'''MAIN_HTTP_CONTENT_SECURITY_POLICY''' ► Allows you to fill in the content security rules ► (v6.0)

*'''SOCIETE_ON_SEARCH_AND_LIST_GO_ON_CUSTOMER_OR_SUPPLIER_CARD''' ► Allow to change the link of the third party to customer/supplier card instead of contact card on List.

*'''MAIN_MODULE_SETUP_ON_LIST_BY_DEFAULT''' ► If set to "common" the setup module becomes list by defaut

*'''MAIN_PAGESIZE_CHOICES''' ► Configure select field to choose number of lines displayed on listing (<code>10:10,15:15,20:20,30:30,40:40,50:50,100:100,250:250,500:500,1000:1000,5000:5000</code>).

*'''MAIN_USE_TOP_MENU_QUICKADD_DROPDOWN''' ► Add a dropdown menu with shortcuts to create new objects ► (v13.0)

*'''MAIN_EMAILCOLLECTOR_MAIL_WITHOUT_HEADER''' ► Remove the header stored by email collector ► (v13.0)

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID'''

*'''MAIN_OPTIMIZEFORTEXTBROWSER''' ► Optimise interface for a text only browser. This variable is set to 1 automatically if your browser is lynx or links

*'''MAIN_NB_OF_YEAR_IN_WIDGET_GRAPH''' ► Set the number of years visible on some graph of some widgets (2 is default value)

*'''MAIN_CREATEFROM_KEEP_LINE_ORIGIN_INFORMATION'''

*'''API_DISABLE_LOGIN_API''' ►(v14.0)

*'''MAIN_LOGIN_BADCHARUNAUTHORIZED''' ► Add possibility to define bad character unauthorized into login name REGEX expression (Default value is @<>"\') ► (v16.0)
*'''MAIN_SHOW_ALL_FILES_ON_DOCUMENT_TOOLTIP''' ► Add all files visible from the object to be visible from the list of object.
*'''MAIN_LIST_ALLOW_PUBLIC_NOTES''' ► Display public notes on list
*'''MAIN_LIST_ALLOW_PRIVATE_NOTES''' ► Display private notes on list

*'''MAIN_CHECKBOX_LEFT_COLUMN''' ► Display private check boxes on the left ► (v17.0)
*'''MAIN_STATS_GRAPHS_SHOW_N_YEARS''' ► Nb of years to shows in widget and graph ► (v14.0)
*'''MAIN_HOOK_DEBUG''' ► if >=2 the hook in the logs are more verbose ► (v18.0)

*'''MAIN_ENABLE_AJAX_TOOLTIP''' ► if 1 the tooltips are updated with AJAX request ► (v18.0)
*'''MAIN_NO_INPUT_PRICE_WITH_TAX''' ► if 1 the TTC input field is removed from propal/invoices/... ► (v17.0)

*'''MAIN_DISABLE_SELECT2_FOCUS_PROTECTION''' ► if 1 disable the focus protection ► (v17.0)
*'''MAIN_USE_ADVANCED_PERMS ►''' Add advanced user permission

*'''MAIN_FREE_PRODUCT_CHECKED_BY_DEFAULT ►''' Check "product" or "service" by default on order/invoices/propal cards (set value "product" or "service")
*'''MAIN_LINK_BY_REF ►''' Allow to link documents by choosing the type and ref from the object linked option
*'''MAIN_STORE_COMPUTED_EXTRAFIELDS ►''' when enabled, computed extrafields have their formula result evaluated and persisted to the database on save (instead of the default behavior where the formula is re-evaluated on the fly at each display and the column is left null).

'''Official supported option'''

The following options are not hidden option. They are available by default from the interface.

*'''MAIN_ONLY_LOGIN_ALLOWED ►''' Activate maintenance mode and set user that is allowed to login. Value must be user login. Available into menu Home - Admin tools - User session, it is filled with admin user when clicking on button "Block other session". Enable <code>MAIN_STORE_COMPUTED_EXTRAFIELDS</code> when you need to sort, filter, sum or report on a computed extrafield's value in SQL/lists: instead of recalculating the formula on every display (leaving the column null), it stores the result in the database on each save, at the cost of the value being a snapshot that only refreshes when the record is saved again.

[[#Top|(back to top)]]

=Security Options=

*'''MAIN_SECURITY_ANTI_SSRF_SERVER_IP''' ► Can set a complete list of IPs of server.

*'''MAIN_SECURITY_CSRF_WITH_TOKEN''' ► Activate a second anti-CSRF protection on POST (so a POST from another web site can't be done). Note there is also a default protection using test on referrer that is not reliable. This second protection uses TOKEN on forms and is more powerful. Value can be: 0=CSRF protection disabled; 1=CSRF protection is on POST URLs only (default from version Dolibarr 15.0+); 2=CSRF protection is required on POST + some GET URL that contains some white listed parameters like the parameter "action" used to request database change (default from version Dolibarr 16+), 3=CSRF protection is enabled on any POST and GET URLs (a valid CSRF token is expected whatever are the parameters, warning: can be enabled on Dolibarr but some external modules developped by thirdparty may not be ready yet with this option)

*'''MAIN_MODULES_FOR_EXTERNAL''' ► Limit available modules for external users. By default value is '<code>facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda</code>'

*'''MAIN_ALLOW_SVG_FILES_AS_IMAGES''' ► Allow to use SVG file as image files. Warning: This may introduce security vulnerability (javascript can be embedded into SVG file).

*'''MAIN_RESTRICTHTML_ONLY_VALID_HTML''' ► Refused parameter if value is not a valid HTML content. The content is also sanitized with Tidy.

*'''MAIN_RESTRICTHTML_ONLY_VALID_HTML_TIDY''' ► Refused parameter if value is not a HTML content validated by Tidy PHP library. The content is also sanitized with Tidy.

*'''MAIN_RESTRICTHTML_REMOVE_ALSO_BAD_ATTRIBUTES''' ► Sanitize also non standard attributes on HTML content.
*'''MAIN_SECURITY_SALT''' ► A salt string to base the hashing on. 8 strings length recommended.

*'''MAIN_SECURITY_MAX_IMG_IN_HTML_CONTENT''' ► Maximum number of Images on the HTML content
*'''MAIN_SECURITY_ALLOW_UNSECURED_LABELS_WITH_HTML''' ► Allow HTML tags into products label

*'''MAIN_SECURITY_FORCERP''' = "strict-origin-when-cross-origin" (default) so browser doesn't send any referrer when going into another web site domain / "same-origin" / "strict-origin"

[[#Top|(back to top)]]

=Members Module=

*'''MEMBER_NEWFORM_FORCEMORPHY''' ► Force nature of member set to "phy" for physical or to "mor" for moral ► (v12.0)
*'''MEMBER_ALLOW_CHANGE_OF_TYPE''' ► Member can edit their type on public subscription page ► (v13.0)
*'''ADHERENT_DEFAULT_CREATE_THIRDPARTY''' ► Thirdparty is created when creating a new member ► (v13.0)
*'''MEMBER_SUBSCRIPTION_SUGGEST_END_OF_MONTH''' ► If set to 1, the member subscription end date will be suggested for the end of the month ► (v18.0)
*'''MEMBER_SUBSCRIPTION_SUGGEST_END_OF_YEAR''' ► If set to 1, the member subscription end date will be suggested for the end of the year ► (v18.0)
*'''MAIN_NB_OF_YEAR_IN_MEMBERSHIP_WIDGET_GRAPH''' ► If set, it limits the number of years visible on graph and widgets of membership (empty is default value to show all) ► (v18.0)
*'''MEMBER_NO_SYNC_LINKED_THIRDPARTY ►''' If set, changes to a member will not be synchronized to a linked third party. ► (v23.0)

[[#Top|(back to top)]]

=Accounting Module=

*'''ACCOUNTANCY_COMBO_FOR_AUX''' ► Add graphic option for ACCOUNTANCY_COMBO_FOR_AUX. Having this option on may slow down and even freeze the accounting features if you have a very large number of thirdparties ► (v10.0)
*'''ACCOUNTING_DEFAULT_NOT_NOTIFIED_VALIDATION_DATE''' ► Avoid validating the lines with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*'''ACCOUNTING_DEFAULT_NOT_NOTIFIED_EXPORT_DATE''' ► Avoid flagging the lines as exported with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*'''ACCOUNTANCY_USE_PRODUCT_ACCOUNT_ON_THIRDPARTY ►''' Add 2 fields on thirdparty card which allow you to set an account for all sells products and an other for all buying products for this customer ► (v14.0)
*'''ACCOUNTING_MANAGE_ZERO''' '''►''' Allow to manage char 0 in accounting account (if enabled 1 ≠ 10) ► (v14.0)

[[#Top|(back to top)]]

=Agenda Module=

*'''AGENDA_ALL_CALENDARS''' ► Change the default view of calendar pages to see all the Agenda's (instead or yours only be default)

*'''AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS''' ► To automatically set end date of event to start date + delta on event creation page.

*'''AGENDA_DISABLE_LOCATION''' ► Disable location field in action card ► (>=v5.0)

*'''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''''').

*'''MAIN_ADD_EVENT_ON_ELEMENT_CARD''' ► Allow to create an event from a document (proposal, order, invoice)

*'''AGENDA_SUPPORT_PRIORITY_IN_EVENTS''' ► Allow to have priorities in events ► (>=v13.0)

*'''AGENDA_ADDACTIONFORPHONE''' ► Allow you to create a event from phone number ► (=<v12.0) - Need to be fix for (=>v12.0) https://github.com/Dolibarr/dolibarr/issues/22720

*'''AGENDA_ADDACTIONFOREMAIL''' ► Allow you to create a event from Email ► (=<v12.0) - Need to be fix for (=>v12.0) https://github.com/Dolibarr/dolibarr/issues/22720
*'''MAIN_ACTIONCOM_CAN_ADD_ANY_CONTACT''' ► Allow you to add any contact on events if set at 1a https://github.com/Dolibarr/dolibarr/releases/tag/18.0.0

[[#Top|(back to top)]]
=Bank Module=

*'''BANK_CAN_RECONCILIATE_CASHACCOUNT''' ► Can reconciliate cash accounts ► (v3.8)

*'''BANK_DISABLE_CHECK_DEPOSIT''' ► Disable check deposit feature

*'''BANK_ASK_PAYMENT_BANK_DURING_ORDER''' ► Ask bank account during creation of an order

*'''BANK_ASK_PAYMENT_BANK_DURING_PROPOSAL''' ► Ask bank account during creation of a proposal

*'''BANK_USE_OLD_VARIOUS_PAYMENT''' ► To allow to enter miscellaneous payments (not covered by other modules) using old method. '''''Deprecated'''''. Entering various payment is preferred ► (<=v12.0).
*'''MAIN_IBAN_IS_NEVER_MANDATORY''' ► IBAN and BIC informations not mandatory. (V15)

[[#Top|(back to top)]]

 

=BOM and MO Module=

*'''ALLOW_USE_KITS_INTO_BOM_AND_MO'''
*'''BOM_SUB_BOM''' ►Allow to add a BOM in another BOM►(v16.0)

[[#Top|(back to top)]]

 

=Bookmarks Module=

*'''BOOKMARKS_SHOW_IN_MENU''' ► Numbers of bookmark entries to be displayed (10 by default)

[[#Top|(back to top)]]

 

=Inalterable Log Module=

*'''BLOCKEDLOG_ADD_ACTIONS_SUPPORTED''' ► Can complete list of triggered action that are logged
*'''BLOCKEDLOG_USE_REMOTE_AUTHORITY''' ► URL of the remote authority for the blockchain

[[#Top|(back to top)]]

 

=Category-Tags Module=

*'''CATEGORY_SHOW_COUNTS''' ► Shows nb of object by tags in tag tree
*'''CATEGORY_EDIT_IN_MENU_NOT_IN_POPUP ►''' Display categories menu instead of managing it only from "Tools"

[[#Top|(back to top)]]

 

=Contracts=

*'''CONTRACT_SUPPORT_PRODUCTS''' ► Products are also suggested into module contract.
*'''CONTRACT_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)
*'''CONTRACT_HIDE_PLANNED_DATE_ON_PDF''' ► allows you to not display dates on pdf files.
*'''CONTRACT_HIDE_REAL_DATE_ON_PDF''' ► allows you to not display dates on pdf files.
*'''CONTRACT_HIDE_PRICE_ON_PDF''' ► allows you to not display price on pdf files.
*'''CONTRACT_HIDE_QTY_ON_PDF''' ► allows you to not quantity dates on pdf files.
*'''CONTRACT_SHOW_SIGNATURE_STATUS_WITH_SERVICE_STATUS''' ► Show signature status in contract card (Sign by all parties).► (v21.0+)

[[#Top|(back to top)]]

=Cron module=

*'''CRON_DISABLE_KEY_CHANGE''' ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*'''CRON_DISABLE_TUTORIAL_CRON''' ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*'''CRON_WARNING_DELAY_HOURS''' ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

[[#Top|(back to top)]]

 

=Direct Debit Orders=

*'''WITHDRAWAL_ALLOW_ANY_INVOICE_STATUS''' ► If this option is set, all invoices status (even already paid) may appear on the list of invoices qualified for a direct debit payment. This is the list of invoices with a payment request done, and not linked to a direct debit payment. By default, only "unpayed" invoices are used to avoid to pay twice the same invoice.

[[#Top|(back to top)]]

=Donation Module=

*'''DONATION_USE_THIRDPARTIES''' ► If this option is set, a thirdparty field appear on donation forms.

[[#Top|(back to top)]]
=Email=

*'''MAIN_COPY_FILE_IN_EVENT_AUTO''' ► Add attachment document on event auto generated by sending email from dolibarr. ► (v6.0+)

*'''MAIN_EMAIL_USE_LAYOUT'''► Enable the use of predefined layout when writing an email.

*'''MAIN_MAILFORM_DISABLE_ENTERKEY''' ► Activate JavaScript code to disable the enter key in the MAIL form. ► (>= 8.0.1)

*'''MAIN_MAIL_DEBUG''' ► Write content with header of last mail into file <code>dolibarr_mail.log</code> into directory <code>dolibarr_main_data_root</code>.

*'''MAIN_MAIL_DEBUG_ERR_WITH_DATE''' ► Use a different filename (by adding a prefix of date) for each email sent with error when MAIN_MAIL_DEBUG.

*'''MAIN_MAIL_DEBUG_LOG_WITH_DATE''' ► Use a different filename (by adding a prefix of date) to log each email sent (whatever is result) when MAIN_MAIL_DEBUG.

*'''MAIN_MAIL_FORCE_FROM''' ► (v19+) Can force the value into the From field of the SMTP header. Note that email sender is always saved into the "Reply-To".

*'''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 <code>-f</code>. This option is here to ask Dolibarr to call the function mail of PHP by adding value for the option <code>-f</code>. 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 setup or version of sendmail that ask the -f option to be mandatory or for sendmail setup that does not use by default the From of the header email to define the sender (with this option, the from can be forced on command line to avoid to have the from lost by sendmail).

*'''MAIN_MAIL_SENDMAIL_FORCE_BA''' ► On Linux 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 asks PHP to provide this parameter when sending a mail. Note that another solution is to edit the mail.force_extra_parameters=-ba into <code>php.ini</code> 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 to 1 if your recipient experience problems when opening email for example users using webmail of <code>orange.fr</code> or <code>hotmail.com</code>. Note that some users have reported that when using Exim (Exim 4), you must set this parameter to 0. Default value is 1 but may be changed to 0 in future.

*'''MAIN_MAIL_DO_NOT_USE_SIGN''' ► Do not add user signature at end of suggested pre-defined email

*'''MAIN_MAIL_FORCE_NOT_SENDING_TO''' ► If en email is defined into this variable, emails will never be sent to this email.

*'''MAIL_FORCE_DELIVERY_RECEIPT_INVOICE''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Invoice'' module.

*'''MAIL_FORCE_DELIVERY_RECEIPT_ORDER''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Order'' module.

*'''MAIL_FORCE_DELIVERY_RECEIPT_PROPAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Proposal'' module.
*'''MAIL_FORCE_DELIVERY_RECEIPT_SUPPLIER_PROPOSAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Supplier Proposal'' module.

*'''MAIN_EMAIL_SUPPORT_ACK ►''' Restore email acknowledgment checkbox on sending emails. This feature is commonly abandoned by mailers. Active from Dolibarr V17 - see [https://github.com/Dolibarr/dolibarr/blob/33744f74da1a5c20f8aa9950018ab4e549e00205/ChangeLog#L53 changelog]
*'''MAIN_EMAIL_USECCC''' ► 1 = Shows field BCC into email forms, If value is an email = Shows the BCC pre filled with the email value.

*'''MAIN_MAIL_AUTOCOPY_PROPOSAL_TO''', '''MAIN_MAIL_AUTOCOPY_ORDER_TO''', '''MAIN_MAIL_AUTOCOPY_INVOICE_TO''', '''MAIN_MAIL_AUTOCOPY_SHIPMENT_TO''', '''MAIN_MAIL_AUTOCOPY_..._TO''' ► Email to use as a BCC recipient 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 third party 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 third party or object, the email exchange is related to.

*'''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► Restrict sending of 1 email message to <code>x</code> recipients for same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include 1000 recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available.

*'''MAIN_MAIL_FORCE_CONTENT_TYPE_TO_HTML''' ► Force to send all email (event with text only content) as HTML formatted email.

*'''MAIN_MAIL_USE_MULTI_PART''' ► Forge email content using an alternate text part ► (for 5.0.2+). By default with 6.0+
*'''MAIN_INFO_SOCIETE_MAIL_ALIASES''' ► add address aliases for the from field on mail. Set his value with "Firstname Name <firstname.lastname@mydomain.tld, Otherfirstname OtherlastName <othermail@mydomain.tld>,..." ► (v5.0.0+)

*'''MAIN_MAIL_ADD_INLINE_IMAGES_IF_IN_MEDIAS''' ► If images were stored into the medias directory from CKEditor, then images into emails are replaced with "inline content". This may increase seriously risk of being detected as SPAM.

*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. You can also set the URLs where to get the IP addresses, for exemple: "https://ipv4.urltoshowip.com/_service_showmyip.php,https://ipv6.urltoshowup.com/_service_showmyip.php. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option '''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD'''.

*'''MAIN_IMAP_USE_PHPIMAP''' ► Use embedded PHP-imap library (not using the native php imap) instead of native php imap extension ► (v17.0+, available as official option in setup of emailcollector by default from v19)

*'''MAIN_MAIL_ENABLED_USER_DEST_SELECT''' ► Show also internal users into list of recipients of email in email sending form ► (v8.0+)

*'''MAIL_PREFIX_FOR_EMAIL_ID''' ► Prefix for the mails ID. Default value is <code>$_SERVER["SERVER_NAME"]</code> ► (>= 8.0.1)
*'''MAIL_MASS_ACTION_SEARCH_MOST_RECENT_FILE_IF_NOT_FOUND''' ► When sending an email from a mass action. If the path saved in DB does not point to an existing file, then search for the most recent file and use it as an attahcment.► (>= 24.0.0)

[[#Top|(back to top)]]

=Emailing Module=

*'''MAILING_PREFIX_FOR_EMAIL_ID''' ► Set the value that will be used to compose the "Email ID" into email headers. If you set this value to '<code>SERVER_NAME</code>', the virtual host of web server will be used. By default, this is not defined, so a hash key, unique to each instance, is used.

*'''MAILING_NO_USING_PHPMAIL''' ► If set, the module emailing can't be used with mail setup of "phpmail". Using a thirdparty SMTP server is required. You can complete warning message by adding an email to contact for setup help with constant <code>'''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS'''</code>.

*'''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS''' ► Contains the email of contact to show into the message visible to a user when he try to use emailing module without SMTP server and if option '''MAILING_NO_USING_PHPMAIL''' is set to on.

*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is on "phpmail". Note: The application always try to translate the message considering the message is a translation key, before showing the translation or message if translation was not found.

*'''MAILING_LIMIT_WARNING_NOPHPMAIL''' ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is something else than "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.
*'''EMAILING_USE_ADVANCED_SELECTOR''' ► Enable the advanced selector for recipients.

*'''MAILING_LIMIT_SENDBYWEB''' ► Restrict number of emails you can send in same sending session with emailing module from GUI. The value "<code>dolibarr_mailing_limit_sendbyweb</code>" if defined into config file is used in priority for this limit. A negative value means, sending by web is forbidden.

*'''MAILING_LIMIT_SENDBYCLI''' ► Restrict number of emails you can send in same sending session with emailing module from CLI script. The value "<code>dolibarr_mailing_limit_sendbycli</code>" if defined into config file is used in priority for this limit.

[[#Top|(back to top)]]

 

=Expense Report=

*'''EXPENSEREPORT_ALLOW_OVERLAPPING_PERIODS''' ► Can enter several expense reports on same or overlapping date periods. ► (v7.0+)

*'''EXPENSEREPORT_OVERRIDE_VAT''' ► Setting this constant to 1 will allow expense reports to show VAT even if the global VAT setting is off ► (v10.0)

*'''EXPENSEREPORT_USE_OLD_NUMBERING_RULE''' ► The module Expense Report use numbering rules that you can setup (like other modules do). If you need to keep the hard-coded numbering rule of expenses report used in v6.0 set this constant to 1 ► (>=v7.0+)

*'''MAIN_USE_EXPENSE_IK''' ► This feature allows you to set index kilometres against a mileage index for different types of vehicles. ► (v7.0+)

*'''MAIN_USE_EXPENSE_RULE''' ► This feature allows you to set a variety of rules per user/group/all so they can only create reports within their limits. ► (v7.0+)

[[#Top|(back to top)]]

 

=Export Module=

*'''EXPORT_CSV_SEPARATOR_TO_USE''' ► String value to use as default separator to delimit fields of exported files (by default Dolibarr uses "<code>,</code>"). Example: EXPORT_CSV_SEPARATOR_TO_USE=<code>;</code>

*'''EXPORT_CSV_FORCE_CHARSET''' ► Choose the charset used in the output file built by the CSV exporter. By default it is ISO-8859-1. Example: EXPORT_CSV_FORCE_CHARSET= <code>utf-8</code>

*'''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 (<code>"</code>).
*'''EXPORTS_SHARE_MODELS''' ► Share export models between users.

[[#Top|(back to top)]]

=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 added in front of payment cell, into the page to make online subscription.

[[#Top|(back to top)]]

 
=Holiday Module=

*'''HOLIDAY_HIDE_BALANCE''' ► Hide the user's vacation balance on the vacation request page

[https://wiki.dolibarr.org/Setup_Other#Top (back to top)]
=Interventions Module=

*'''FICHINTER_CLASSIFY_BILLED'''► Allow to classify an intervention card as "Billed". This add also trigger <code>FICHINTER_CLASSIFY_BILLED</code> into list of possible automatic event into agenda.

*'''FICHINTER_DISABLE_DETAILS'''► Disable entry of detail lines on intervention. Can validate with no line. Only one line will be shown per intervention on list.
**If set to <code>2</code> details are disabled only on intervention list ► (v21.0+)

[[#Top|(back to top)]]

=Invoice Module=

*'''MAIN_DEPOSIT_MULTI_TVA''' ► In deposits invoice, creates one line per VAT rate from the origin document ► (6.0)
*'''PDF_INVOICE_SHOW_PRICE_INCL_TAX''' ► In customer's invoice, add a column with the total including all taxes ►

*'''INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED''' ► If a credit note was partially refunded (a refund was sent to the customer), with common situation, we wait to have the remain refunded too. With this option, it is possible to convert the remain of invoice into a discount to reuse it into another invoice.

*'''SUPPLIER_INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED''' ► See INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED, but for supplier credit notes.

*'''INVOICE_CAN_BE_EDITED_EVEN_IF_PAYMENT_DONE''' ► Allow to edit invoices even if payment was started. Note: If the module "BlockedLog" is active (required in some countries for legal reasons), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change will be recorded into the archive log.

*'''INVOICE_CAN_ALWAYS_BE_REMOVED''' ► Allow to always delete invoices (even if invoice is not last one). Note: If the module "BlockedLog" is active (required by some countries for legal reason), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*'''INVOICE_CAN_NEVER_BE_EDITED''' ► Never allow to edit invoices (except draft invoices with ref like (PROV%)). See also INVOICE_CAN_NEVER_BE_REMOVED.

*'''INVOICE_CAN_NEVER_BE_REMOVED''' ► Never allow to delete invoices (except draft invoices with ref like (PROV%)). See also INVOICE_CAN_NEVER_BE_EDITED

*'''INVOICE_POSITIVE_CREDIT_NOTE''' ► All amounts on PDF credit notes are positive.

*'''FACTURE_DEPOSITS_ARE_JUST_PAYMENTS''' ► An old way to create initial payment. This treats deposit invoices as a special case and not as legal deposit invoice. 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. WARNING: In a lot of european countries, using this option is not allowed.

*'''FACTURE_SENDBYEMAIL_FOR_ALL_STATUS''' ► Can send invoice by email to customer even if invoice has status "draft".

*'''INVOICE_CREDIT_NOTE_STANDALONE''' ► Start implementation to allow a credit note even without invoice (dangerous) ► (v3.9)

*'''INVOICE_USE_SITUATION''' ► 1=Enable the "situation invoice" feature. Warning, this feature is bugged and may not be compatible with the final version of the feature once the bug will be solved. Also, using the double-entry accountancy module is not possible when this option is on (due to the same design problem). 2=Enable the "situation invoice" feature with a rewrite. This mode should be better to become a future stable feature.

*'''INVOICE_USE_SITUATION_CREDIT_NOTE''' ► Enable the "situation credit note" feature (need <code>INVOICE_USE_SITUATION</code>) ► (v8.0)
*'''INVOICE_USE_RETAINED_WARRANTY''' ► Enable the retained warranty on invoice ► (v14.0)

*'''INVOICE_DISABLE_DEPOSIT''' ► Disable deposit invoices

*'''INVOICE_DISABLE_REPLACEMENT''' ► Disable replacement invoices

*'''INVOICE_DISABLE_CREDIT_NOTE''' ► Disable credit notes

*<bdi>'''INVOICE_ADD_EXTRAFIELD_IN_NOTE''' ► Add extrafields in note for canelle template ► (v17.0+)</bdi>

*'''INVOICE_DEFAULT_NOTE_PUBLIC''' <bdi>► Default text in public note</bdi>

Note: To decode a QR image of a ZATCA code: https://www.onlinebarcodereader.com/. You can also use the mobile application https://play.google.com/store/apps/details?id=com.posbankbh.einvoiceqrreader&gl=FR

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT''' ► See PDF option

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN''' ► See PDF options

*'''WORKFLOW_BILL_ON_SHIPMENT''' ► Change label of button with suitable label when you need to create invoice on shipments

*'''INVOICE_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. Use the tag __DIRECTDOWNLOAD_URL_INVOICE__ in email template to insert it. ► (v7.0+)

*'''INVOICE_POINTOFTAX_DATE''' ► Add Point of Tax Date on invoices for country-specific legality reasons ► (v4.0+)
*'''FACTURE_ENABLE_NEGATIVE''' ► Can validate an invoice when amount is negative

*'''FACTURE_ENABLE_NEGATIVE_LINES''' ► Allows to add negative lines to an invoice ► (v8.0.2+)
*'''SUPPLIER_INVOICE_ENABLE_NEGATIVE''' ► Can validate an supplier invoice when amount is negative ► (V21 ?)
*'''SUPPLIER_INVOICE_ENABLE_NEGATIVE_LINES''' ► Allows to add negative lines to an supplier invoice ► (V21 ?)

*'''INVOICE_USE_DEFAULT_DOCUMENT''' ► Allow user to select a default invoice documents models according to invoice type. On invoice create page, the model is dynamically changed on invoice type selection. ► (v9.0+)

*'''FACTURE_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object (Proposal,...) when creating the bill.
*'''FACTUREFOURN_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object when creating the supplier bill ► (V13.0)
*'''MAIN_SHOW_FACNUMBER_IN_DISCOUNT_LIST''' ► Display the reference of credit notes in discount list when creating the bill.
*'''INVOICE_ALLOW_FREE_REF''' ► Capability to change reference of an invoice. This will be possible as long as the invoice has the status “Draft” and only if your country is not in Europe(V11)

*'''INVOICE_DISALLOW_REOPEN'''

*'''INVOICE_MAX_FUTURE_DELAY''' ► Numbers of seconds allowed for billing in the future ► (V14.0)
*'''INVOICE_AUTO_NEXT_MONTH_ON_LINES''' ► Increase start date and end date by one month, if an invoice line is a clone of a time based service AND if this services started on the first day of month and ended on the last day of month ► (V13.0.1)
*'''INVOICE_KEEP_DISCOUNT_LINES_AS_IN_ORIGIN''' ► Does not change a line with a negative price into an absolute discount when creating an invoice ► (V16 ?)
*'''INVOICEREC_SET_AUTOFILL_DATE_START''' and '''INVOICEREC_SET_AUTOFILL_DATE_END ►''' Set start and end date to yes for lines of template invoice when created from a draft invoice ► (V16)
*'''INVOICE_REC_DATE_TO_YES''' '''►''' Set start and end date to yes by default in add line form for template invoice ► (V16)
*'''INVOICE_SUBTYPE_ENABLED''' ► Extends Dolibarr standard invoice with more invoice types used in some countries. A combo box in the new invoice creation card allows the selection of "subtypes" with values from dictionary "Invoice Subtypes" ► (v19.0+)
*'''LIST_OF_QUALIFIED_INVOICES_LIMIT_DEFINED''' '''►''' Perf options to limit list of invoices for "credit note" source (on form "create a credit note"), usable for big quantities of invoices for one customer like you can have with TakePos ► (V22+)

[[#Top|(back to top)]]

=Leave=

*'''MAIN_NON_WORKING_DAYS_INCLUDE_SATURDAY''' ► Set this value to 0 if you want to have the Saturday as a working day
*'''MAIN_NON_WORKING_DAYS_INCLUDE_SUNDAY''' ► Set this value to 0 if you want to have the Sunday as a working day

=Look or Theme=

*'''MAIN_FAVICON_URL''' ► favicon url

*'''MAIN_EASTER_EGG_COMMITSTRIP''' ► Show a comic image from the CommitStrip website. Images are refreshed daily. ► (v6.0+)

*'''MAIN_INCLUDE_GLOBAL_STATS_IN_OPENED_DASHBOARD''' ► This conf will auto remove global stats box item if there are already in the new dashboard of opened elements and keep displayed stats on the opened item box (not only on mouse over) ► (v11.0+)

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Actually only for eldy theme, this conf move search input to top menu and use new design too ► (v11.0+)

*'''THEME_AGRESSIVENESS_RATIO''' ► This conf can be used to increase/decrease aggressiveness of colors. Value 0 is medium, value is between -100 (light grey colors) to +100 (very flashy colors) ► (v11.0+)

*'''THEME_SHOW_BORDER_ON_INPUT'''
*'''MAIN_DISABLE_GLOBAL_WORKBOARD''' ► Hide the work board of the main page ► (v13.0+)
*'''MAIN_DISABLE_GLOBAL_BOXSTATS''' ► Hide the Statistic Box of the main page
*'''ALLOW_THEME_JS ►''' Allow JS file in theme folder (same name as theme folder)

 

=Manifest (Progressive Web App)=

*'''MAIN_MANIFEST_APPLI_THEME_COLOR ►''' Theme color for manifest
*'''MAIN_MANIFEST_APPLI_BG_COLOR ►''' Background color for manifest
*'''MAIN_MANIFEST_APPLI_LOGO_URL ►''' Logo for manifest
*'''MAIN_MANIFEST_APPLI_LOGO_URL_SIZE ►''' Logo url size for app (150, 192, 512px) missing 3 configurations

[[#Top|(back to top)]]

=Order Module=

*'''MAIN_MASSACTION_CREATEBILLS_REDIRECT_IF_ONE''' ► If set 1, redirects to the one bill created from massaction create bills from order list ► (v20.0)

*'''MAIN_MASSACTION_CREATEBILLS_REDIRECT_IF_MANY''' ► If set to 1, redirects to the invoice list after plural invoices where generated from tho massaction create bills from order list ► (v20.0)

*'''MAIN_ORDERLIST_CREATEBILLS_ONEBYTHIRD''' ► Allow defining value for option "one by thirdparty" in massaction create bills from orders list page (no by default, yes if set to 'yes' or 1) ► (v20.0)

*'''MAIN_USE_PROPAL_REFCLIENT_FOR_ORDER''' => Copy customer reference from proposal to order. ► (v7.0+)

*'''ORDER_REQUIRE_SOURCE''' => Make the input field "Source of order" mandatory.

*'''ORDER_VALID_AFTER_CLOSE_PROPAL''' => When an order is created on a proposal close, the order is directly defined with status "Validated".

*'''ORDER_ALLOW_EXTERNAL_DOWNLOAD''' => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*'''ORDER_ENABLE_NEGATIVE''' => Can validate an order when amount is negative

*'''THIRDPARTY_PROPAGATE_EXTRAFIELDS_TO_ORDER''' => Copy also extrafields from thirdparty to order (if name match). ► (v11.0+)
*'''ORDER_DEFAULT_NOTE_PUBLIC''' ► Default text in public note
*'''MAIN_REMOVE_DROPDOWN_CREATE_BUTTONS_ON_ORDER''' => Remove the create dropdown button on order card (introduce on v19) to come back with old buttons. '''►''' (v20.0+)

[[#Top|(back to top)]]

 

=PDF Options=

*'''MAIN_ADD_PDF_BACKGROUND''' ► Define this constant with short name of a PDF file (example "<code>mypdf.pdf</code>") that must be saved into directory "<code>documents/mycompany</code>". 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_DISABLE_FORCE_SAVEAS''' ► If your browser always asks to save downloaded files on disk (like PDF), try this this option. File may be displayed directly in your browser. Values : 0= Default (file is auto downloaded), 1= For to output the file into the browser tab, 2= For to output the file into a browser tab open with target_blank

*'''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 servers with low CPU.

*'''MAIN_DISABLE_PDF_COMPRESSION''' ► Disable PDF compression.

*'''MAIN_DOCUMENTS_WITH_PICTURE_WIDTH''' ► Can change size of picture when hidden option <code>MAIN_GENERATE_PROPOSALS_WITH_PICTURE</code> is used. By default value is <code>20</code>.

*'''MAIN_GENERATE_DOCUMENTS_SHOW_FOOT_DETAILS''' ► Adding the company address at the bottom of the page. Disabled by default

*'''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer proposals.
*'''MAIN_GENERATE_ORDERS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer orders.

*'''MAIN_GENERATE_INVOICES_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer invoices.

*'''MAIN_GENERATE_SUPPLIER_PROPOSAL_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier proposals ► (v5.0.3+)
*'''MAIN_GENERATE_SUPPLIER_ORDER_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier orders

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT''' ► Disable VAT on generated documents. like for an association. (Works with crabe template)

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN''' ► Hide column with VAT information but only column not total.

*'''MAIN_INVERT_SENDER_RECIPIENT''' ► Invert sender and recipient in some PDF. Note: This option is set automatically if country if Germany.

*'''MAIN_ODT_AS_PDF''' ► Activate ODT to PDF conversion. Value can be "libreoffice" or "unoconv". Do not use value '''<nowiki/>'jodconverter'<nowiki/>''' any more, as it is declared deprecated and partly not functional, use value '''<nowiki/>'libreoffice'''' instead, it requires only '''soffice''' (OpenOffice or LibreOffice) installed on server (use '''apt install soffice libreoffice-common libreoffice-writer''').

If you got this error: javaldx failed! Warning: failed to read path from javaldx with no return to prompt when running soffice --headless -env:UserInstallation=file:"/tmp" --convert-to pdf --outdir xxx ./yyy.odt, check that directory defined into env:UserInstallation parameters exists and is writeable.

You may also have a look at this page if your server is on Windows: [[Générer automatiquement des documents PDF à partir de fichier ODT avec Doliwamp]]

*'''MAIN_ODT_AS_PDF_DEL_SOURCE''' ► For ODT generation. If set, then initial behaviour is conserved but ODT file is removed when option to convert it as PDF (see previous) is on. Disabled by default

*'''MAIN_PDF_FORCE_FONT''' ► To ignore font defined into language file and force usage of a particular font. For example "<code>DejaVuSans</code>".

*'''MAIN_PDF_FORCE_FONT_SIZE''' ► To force size of font (by default 10). For example "<code>12</code>" ► (v11.0)

*'''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: <code>220,220,200</code>

*'''MAIN_PDF_USE_LARGE_LOGO''' ► Use the original logo with its higher resolution into the PDF instead of the small thumb. This may lead to very very large PDF !

*'''MAIN_USE_BACKGROUND_ON_PDF''' ► Define this constant with short name of an image (example "<code>myimage.jpg</code>") that must be saved into directory "<code>documents/mycompany/logos</code>". This will add this background image into your generated PDF files.

*'''MAIN_USE_COMPANY_NAME_OF_CONTACT''' ► Use contact name and information rather than company

*'''MAIN_PDF_ADDALSOTARGETDETAILS''' ► If 1, add details of recipient on generated PDFs (email, fax, url and phone). Can be useful in cases where a printed order/invoice etc is given to a delivery driver/courier etc.

*'''MAIN_TVAINTRA_IN_SOURCE_ADDRESS''' ► Show VAT N° in source address of PDF to comply with legalities in certain countries. Note that VAT number should be already visible in footer of page ► (v8.0.1+)

*'''MAIN_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► Add optional esign field in pdf propal ► (v8.0+)

*'''MAIN_PROFID1_IN_SOURCE_ADDRESS''' ► Show Professional ID 1 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID2_IN_SOURCE_ADDRESS''' ► Show Professional ID 2 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID3_IN_SOURCE_ADDRESS''' ► Show Professional ID 3 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID4_IN_SOURCE_ADDRESS''' ► Show Professional ID 4 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID5_IN_SOURCE_ADDRESS''' ► Show Professional ID 5 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID6_IN_SOURCE_ADDRESS''' ► Show Professional ID 6 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

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

*'''PDF_BOLD_PRODUCT_REF_AND_PERIOD''' ► Add more visibility (bold) on product ref and period of service in desc. ► (v12.0)

*'''PDF_HIDE_PRODUCT_REF_IN_SUPPLIER_LINES''' ► Modify the use/position of Supplier Ref/Internal Ref with the item Label (name) on PDF documents.

Default (constant not set or Value <code>0</code>): Internal ref followed by supplier ref in brackets."COMPANY-REF-001 (Vendor SKU SUPPLIER-REF-001) - LABEL...".

Value <code>1</code>: Supplier ref only eg."SUPPLIER-REF-001 - LABEL...".

Value <code>2</code>: Supplier ref followed by internal ref in brackets. eg."SUPPLIER-REF-001 (InternalRef COMPANY-REF-001) - LABEL...".

*'''PDF_INCLUDE_ALIAS_IN_THIRDPARTY_NAME''' ► Include alternative/alias name into name on PDF.

*'''PDF_SECURITY_ENCRYPTION''' ► Encrypt PDF produced by dolibarr. See additional parameters :PDF_SECURITY_ENCRYPTION_RIGHTS (block 'modify' or 'copy') - '''PDF_SECURITY_ENCRYPTION_USERPASS''' - '''PDF_SECURITY_ENCRYPTION_OWNERPASS''' (random if not specified) - '''PDF_SECURITY_ENCRYPTION_STRENGTH''' (0 = RC4 40 bit; 1 = RC4 128 bit; 2 = AES 128 bit; 3 = AES 256 bit) - '''PDF_SECURITY_ENCRYPTION_PUBKEYS''' Array of recipients containing public-key certificates ('c') and permissions ('p') - For example: array(array('c' => 'file://../examples/data/cert/tcpdf.crt', 'p' => array('print'))). WARNING: if an 'encrypted PDF' provides a protection against manual change done by mistake, it does NOT provide any protection against modification of your PDF in a security point of view: A protected PDF can still be modified by any advanced PDF editors. Don't forget this: If a software can read the PDF, this software can also rebuild it differently !

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

*'''PDF_USE_ALSO_LANGUAGE_CODE''' ► The value of this constant must be a language code ('fr_FR', 'en_US', 'sa_SA', ...). If set, the PDF document will contains both language (default and the one defined by the constant).
*'''DOC_SHOW_FIRST_SALES_REP''' ► Show the sales representant on header (at least on propal azur and rubis template)
*'''MAIN_PDF_DASH_BETWEEN_LINES'''
*
*'''SHOW_SUBPRODUCT_REF_IN_PDF'''
*'''PDF_HIDE_PRODUCT_LABEL_IN_SUPPLIER_LINES''' ► hide product label in supplier order lines (V15+)
*'''SHIPPING_PDF_DISPLAY_AMOUNT_HT''' ► Show HT unit price and HT total price for lines of PDF shipment

*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_FACTURE''' ► To Hide product description in Customer Invoice
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_COMMANDE''' ► To Hide product description in Sales Order
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_ORDER_SUPPLIER''' ► To Hide product description in Purchase Order
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_INVOICE_SUPPLIER''' ► To Hide product description in Vendor Invoice

*'''PDF_PROPAL_SHOW_PRICE_INCL_TAX''' ► Display price with tax on Proposal(cyan template) (V17+)
*'''PDF_ORDER_SHOW_PRICE_INCL_TAX''' ► Display price with tax on Order(eratosthene template) (V17+)
*'''PDF_INVOICE_SHOW_PRICE_INCL_TAX''' ► Display price with tax on Invoice(sponge template) (V17+)

*'''PDF_USE_GETALIASNBPAGE_FOR_TOTAL''' ► Display the page number alias
*'''MAIN_PDF_NO_SENDER_FRAME''' ► Do not display the "sender" mention
*'''MAIN_PDF_HIDE_SENDER_NAME''' ► Do not display the sender name
*'''MAIN_PDF_NO_RECIPENT_FRAME''' ► Do not display BillTo

*'''MULTICURRENCY_SHOW_ALSO_MAIN_CURRENCY_ON_PDF''' ► Show the amount in the 2 currencies on PDF when using the MultiCurrency module
*'''MAIN_PDF_DONOTREPEAT_HEAD ►''' Do not repeat the header of document

[[#Top|(back to top)]]

=Point of Sale (POS)=

*'''CASHDESK_SHOW_KEYPAD''' ► Show a mouse key pad into the 'Simple Point of Sale' module.

*'''POS_ADDON''' ► Set this value to an existing numbering module rule (for example '<code>mod_facture_terre</code>', '<code>mod_facture_mars</code>', ...) to force the numbering module to use for invoice ref definition when invoice is created by the POS. For example setting value <code>POS_ADDON</code> to '<code>mod_facture_terre</code>' will use the numbering module '<code>terre</code>' for invoice generated from POS, whatever is the numbering rule defined into invoice module setup (you can also use POS_NUMBERING_TERRE_FORCE_PREFIX and POS_NUMBERING_MARS_FORCE_PREFIX variable to change the prefix used).

*'''TAKEPOS_ENABLE_SUMUP''' ► Enable the compatibility of TakePOS with the card reader terminal [https://SumUp.fr SumUp]
*'''TAKEPOS_CAN_FORCE_BANK_ACCOUNT_DURING_PAYMENT''' ► Possibility to force the bank account during the payment in TakePOS ► (v13.0)
*'''TAKEPOS_CONTROL_CASH_OPENING''' ► Control the cash opening
*'''TAKEPOS_NUMPAD_FORCE_PAYMENT_ICONS_LABELS'''

[[#Top|(back to top)]]

=Products Module=

*'''CATEGORY_GRAPHSTATS_ON_PRODUCTS''' ► Show graph of products with categories and totals in Products Area screen

*'''MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE''' ► Avoid customs 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.

*'''MAIN_DIRECT_STATUS_UPDATE''' ► Allows you to change the status of the product (''for sale/not for sale for purchase/not for purchase'') directly on the product page via a ''on/off'' switch button. This can be convenient for those who need to quickly disable certain statuses of products without having to go through the editing product page individually. Also can be very useful if used as a filter on the product and product search list. This option doesn't generate a MODIFY trigger, so be careful with external modules. ► (v4.0+)

*'''MAIN_SEARCH_PRODUCT_BY_FOURN_REF''' ► Allow to search a product by supplier ref in document's add line form. ► (>= 8.0)

*'''MAIN_DISABLE_FREE_LINES''' ► Disallow using free lines to add line in documents ► (>= 8.0)

*'''MAIN_SHOW_PRODUCT_ACTIVITY_TRIM''' ► Show Product and Services turnover before for all four quarters tax over recent years recent years on the product area ► (v5.0+)

*'''PRODUIT_DESC_IN_LIST''' ► Show long description of product/service into lists.

*'''PRODUCT_DISABLE_PROPAGATE_CUSTOMER_PRICES_ON_CHILD_COMPANIES''' ► Disable propagation of prices per customer from a customer to its child company.

*'''PRODUCT_DISABLE_PUBLIC_URL''' ► Disable public url in product card ► (v14.0+)
*'''PRODUCT_DISABLE_STOCK_LEVELS''' ► Disable properties of stock limits and desired optimal value on product ► (v14.0+)
*'''PRODUCT_DISABLE_NATURE''' ► Disable nature in product card ► (v14.0+)
*'''PRODUCT_DISABLE_WEIGHT''' ► Disable weight in product card ► (v14.0+)
*'''PRODUCT_DISABLE_PRICES''' ► Disable prices in product card ► (v14.0+)
*'''PRODUCT_DISABLE_ACCOUNTING''' ► Disable accounting in product card ► (v14.0+)
*'''PRODUCT_DISABLE_SIZE''' ► Disable size in product card.

*'''PRODUCT_DISABLE_LENGTH''' ► Disable length in product card ► (v4.0+)

*'''PRODUCT_DISABLE_SURFACE''' ► Disable surface in product card. ► (v4.0+)

*'''PRODUCT_DISABLE_VOLUME''' ► Disable volume in product card.

*'''PRODUCT_DISABLE_CUSTOM_INFO''' ► Disable custom info (custom code and country origin) in product/service card.

*'''PRODUIT_MULTIPRICES_USE_VAT_PER_LEVEL''' ► When option to use price per level/segment is on, this allows to also set a dedicated vat for each price level.

*'''PRODUIT_CUSTOMER_PRICES_BY_QTY''' ► If price per quantity ► ''Experimental''
*'''PRODUIT_CUSTOMER_PRICES_BY_QTY_MULTIPRICES''' ► If price per quantity and customer ► ''Experimental''

*'''PRODUCT_LOT_ENABLE_QUALITY_CONTROL''' ► Enable feature (Display fields for life time and quality control duration) for quality control on product and lot

*'''PRODUCT_MAX_LENGTH_COMBO''' ► Limit the length of the label displayed when adding lines in proposals/invoices/orders

*'''PRODUCT_MAX_VISIBLE_PHOTO''' ► Show a maximum number of product photos (as thumbnails) on the product main card. Example, setting this constant to '<code>5</code>' will show the first five product photos found on the product card.

*'''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''' ► Add other units on products (Use same dictionary as default unit feature) and propagate this unit on line of documents.
*'''MAIN_EDIT_LINE_ALLOW_ALL_UNIT_TYPE ►''' Allow the selection of other unit types when editing the document line

*'''RESOURCE_ON_PRODUCTS''' ► Allow to affect resources on products/services ► (v10.0+)
*'''RESOURCE_ON_SERVICES''' ► Allow to affect resources on products/services ► (v10.0+)
*'''PRODUCT_SHOW_ORIGIN_IN_COMBO''' ► Show origin of products when adding lines in proposals/invoices/orders ► (v12.0+)
*'''PRODUIT_ATTRIBUTES_HIDECHILD''' ► Add option hide child if variantes

*'''PRODUCT_ADD_FORM_ADD_TO''' ► Add a product to a draft proposal/order/invoice, from the product card.
*'''PRODUCT_DISABLE_SELLBY''' ► Hide the Sell by date ► (v13.0+)
*'''PRODUCT_DISABLE_EATBY''' ► Hide the Eat by date ► (v13.0+)

*'''PRODUCT_DENY_CHANGE_PRODUCT_TYPE''' ► Forbid to change the product type

*'''PRODUCT_SORT_BY_CATEGORY''' ► Sort the product by categories instead of by ID
*'''PRODUCT_ADD_NET_MEASURE''' ► Support Net Measure in product's card.php (For real weight, volume or piece; needed for some business ie fruits, vegetables....). Note brut value is already available natively, use this option only if you need 2 weights, 2 volumes, ...for each product) ► (v11.0.1+)
*'''PRODUCT_PRICE_BASE_TYPE''' ► value 'TTC' / 'HT' specify the default value of the price (with or without taxes) ► (v16.0.0+)

*'''PRODUCT_LOAD_EXTRAFIELD_INTO_OBJECTLINES''' ► Load product extrafiled on object lines

*'''PRODUCT_USE_SUB_COST_PRICES_IF_COST_PRICE_EMPTY''' : Calculate the parent product production price by child prices.
*'''PRODUCT_SEARCH_AUTO_SELECT_IF_ONLY_ONE''' : Set to 0 to disable or 1 to enable (by default) the auto select product behavior in combobox when there is only one result.(v21.0+)

[[#Top|(back to top)]]

 

=Projects Module=

*'''PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY''' ► Option related to the combo list Project on elements. It is a list of thirdparty IDs. If set, you can link an object to a project owned by one of this thirdparty in the list.

*'''PROJECT_ALLOW_COMMENT_ON_PROJECT''' ► Add comment feature on a project

*'''PROJECT_ALLOW_COMMENT_ON_TASK''' ► Add comment feature on project task
*'''PROJECT_ALWAYS_DISCARD_CLOSED_PROJECTS_IN_SELECT''' ► Discards closed projects in every select field. A closed project can't be associated to an object ► (v20.0+)

*'''PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS''' ► Option related to the combo list Project on elements. Can link a supplier element (vendor proposal, purchase order, vendor invoice, reception, ...) to any project even if object has a different supplier than the one of the project to link to. See also PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY that is different because it allows to define some given thirdparty ID to allow.

*'''PROJECT_CAN_ALWAYS_LINK_TO_ALL_CUSTOMERS''' ► Option related to the combo list Project on elements. Can link a custom element (proposal, sale order, vendor invoice, shipment, ...) to any project even if object has a different customer than the one of the project to link to.

*'''PROJECT_CREATE_ON_OVERVIEW_DISABLED''' ► Hide the "create ..." button on the overview pagec

*'''PROJECT_DISABLE_UNLINK_FROM_OVERVIEW''' ► Enable removing the button from a link in the project overview. ► (>= v8.0.1)

*'''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''' ► Hide the "link to" form on the overview page ► (v4.0)

*'''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_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_OPEN_ALWAYS_ON_TAB''' ► Set to value 'task', or 'preview' to always open the project on the given tab instead of main tab.

*'''PROJECT_ELEMENTS_FOR_MINUS_MARGIN'''

*'''TIMESPENT_ALWAYS_UPDATE_THM''' ► when it's on always check current time of user to update it in task time line ► (v17.0)

*'''PROJECT_CREATE_NO_DRAFT''' ► when you create project status will be validate ► (v19.0)

*'''PROJECT_ENABLE_SUB_PROJECT''' ► Add support for parent projects ► (v19.0)

[[#Top|(back to top)]]

=Proposals Module=

*'''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Add a picture of the product (the first one found if there are several) into the generated PDF of proposals. Note that using this will reduce the available width for the product description.

*'''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_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► add optional esign field in pdf propal ► (v8.0+)

*'''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.

*'''PROPAL_DISABLE_SIGNATURE''' ► Do no show the box for signature.
*'''PROPAL_SIGNATURE_ON_SPECIFIC_PAGE ►''' Will show the signature on which page you wanted . Set to 1 will show on first page , set to -1 will show on last second page . ( If '''PROPAL_SIGNATURE_ON_ALL_PAGES''' is enabled, the '''PROPAL_SIGNATURE_ON_SPECIFIC_PAGE''' setting will be ignored.)
*'''PROPAL_SIGNATURE_ON_ALL_PAGES ►''' Will show the signature on every pages .

*'''PRODUIT_PDF_MERGE_PROPAL''' ► When generating the proposal PDF, all PDFs linked to products linked to proposal are also included into final PDF

*'''PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*'''PROPOSAL_AUTO_ADD_AUTHOR_AS_CONTACT''' ► Add Proposal Author as user contact follow proposal

*'''PROPOSAL_PDF_HIDE_PAYMENTTERM''' ► Do not show the payment term on proposal ► (v11.0+)

*'''PROPOSAL_PDF_HIDE_PAYMENTMODE''' ► Do not show the payment mode on proposal ► (v11.0+)

*'''WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES''' ► Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.
*'''PROPAL_REOPEN_UNSIGNED_ONLY''' ► Do not allow reopening of signed (or billed) proposals. (V15)
*'''PROPOSAL_ARE_NOT_BILLABLE''' ► Disable billing button on proposals (V15)
*'''PROPAL_DEFAULT_NOTE_PUBLIC''' ► Default text in public note
*'''PROPAL_ENABLE_NEGATIVE''' ► Can validate a proposal when amount is negative

[[#Top|(back to top)]]

=Receptions=

*'''RECEPTION_STANDALONE''' ► Create a simple Reception not connected to supplier order, warehouse, stock e.t.c. (>=23.0)

[[#Top|(back to top)]]

= Recruitment =

*'''RECRUITMENT_NEWFORM_TEXT'''► Add a custom text on public recruitment page
*'''MAIN_RECRUITMENT_CSS_URL ►'''Path of custom css file for recruitment public page
*'''RECRUITMENT_IMAGE_PUBLIC_INTERFACE ►'''Path of custom image for recruitment public page

[[#Top|(back to top)]]

=Services Module=

*'''SERVICE_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country. For french speaking people, see also the page [[Loi_européenne_TVA_Vente_à_Distance_VAD_et_e-commerce_BtoC]].

*'''MAIN_FILL_SERVICE_DATES_FROM_LAST_SERVICE_LINE''' ► (v13.0) On add line form add a button to fill service dates from the last service line

[[#Top|(back to top)]]

=Shipments=

*'''STOCK_WAREHOUSE_NOT_REQUIRED_FOR_SHIPMENTS''' ► If set, you can add a shipment line, with no stock source defined. ► (>= 8.0.1)

*'''SHIPMENT_GETS_ALL_ORDER_PRODUCTS''' ► Add all order lines in shipment, including the one with 0 in quantity
*'''SHIPPING_PDF_HIDE_ORDERED''' ►Hide column quantity ordered on shipment pdf (>=15.0)
*'''STOCK_SUPPORTS_SERVICES''' ►Allow to manage services into warehouse and allow to ship services
*'''SHIPMENT_SUPPORTS_SERVICES''' ►Allow to ship services without stock (>=19.0)
*'''SHIPPING_DISPLAY_STOCK_ENTRY_DATE''' ►Display date entry stock exped and sort in date order (>=19.0)
*'''SHIPMENT_STANDALONE ►'''Create a simple shipment not connected to sales order, warehouse, stock e.t.c. (>=23.0)

[[#Top|(back to top)]]

=SMS=

*'''MAIN_SMS_DEBUG''' ► Write content of SMS sent into file <code>dolibarr_sms.log</code> into directory <code>dolibarr_main_data_root</code>.

[[#Top|(back to top)]]

=Stocks=

*'''SUPPLIER_ORDER_DISABLE_STOCK_DISPATCH_WHEN_TOTAL_REACHED''' ► Disable stock dispatch when total expected was already received

*'''STOCK_EXCLUDE_VIRTUAL_PRODUCTS''' ► If product is a virtual product, we do not manage stock for it.
*'''STOCK_ALLOW_DELETE_OF_MOVEMENT''' ► Enable massaction option to delete in movements list (be carefull !!).

*'''ENTREPOT_EXTRA_STATUS''' ► Instead of the 2 status (Closed, Open), a Warehouse has 3 status: Closed, Open (for all movements), Open (for internal movement only). Internal movement only means you can't use the warehouse to make shipment or receptions.

*'''SUPPLIER_ORDER_STATUS_FOR_VIRTUAL_STOCK''' ► For the calculation of virtual stocks, by default supplier orders with the status 3 (ordered) and 4 (partially received) are used. You can enter the list of statuses to be taken into account separated by commas for this calculation (example: 0,1,2,3)

*'''STOCK_MOVEMENT_LIST_HIDE_UNIT_PRICE''' ► to hide unit price on some pages (V15+)

*'''DISABLE_QTY_OVERWRITE''' ► Disable quantity overwrites on inventories ► (v19.0)
*'''MAIN_WAREHOUSE_LIST_DISPLAY_MODE''' ► Change warehouse select list display mode ► (v21.0) (see github pull request [https://github.com/Dolibarr/dolibarr/pull/31013 #31013] for more info)
**0 : Default behavior, display parents of warehouse
**1 : Display only current warehouse label only
**2 : Display last parent warehouse label

[[#Top|(back to top)]]

=Stripe=

*'''STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION''' ► 1 is the default mode and will use the native Stripe form for the checkout (with card only), 2 will use the native Stripe form (PaymentElement complete, multi payment modes). Note that STRIPE_USE_NEW_CHECKOUT is an abandonned alternative (so no more NEW, that does not bring real added value)

=Suppliers Module=

*'''FOURN_PRODUCT_AVAILABILITY''' ► On the Suppliers price page of the products, activate the supplier product availability. ''This is duplicate feature with delivery_delay introduced with 3.8.''

*'''RELOAD_PAGE_ON_SUPPLIER_CHANGE''' ► On creation of a supplier order/invoice, reload form with supplier-specific details when supplier is selected from drop-down list.

*'''SUPPLIER_INVOICE_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier invoice to only those with a buying price defined for that supplier. ► (v6.0+)

*'''SUPPLIER_ORDER_AUTOADD_USER_CONTACT''' ► Add user approving supplier order as a contact automatically.

*'''SUPPLIER_ORDER_DEFAULT_PAYMENT_MODE_ID''' ► Set the default payment method for suppliers (<code>rowid</code> in table <code>llx_c_paiement</code>).

*'''SUPPLIER_ORDER_USE_DISPATCH_STATUS''' ► Add a status on each dispatch order line when receiving products from suppliers ► (v4.0+)

*'''SUPPLIER_ORDER_NO_DIRECT_APPROVE''' ► No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

*'''SUPPLIER_ORDER_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier order to only those with a buying price defined for that supplier. ► (v6.0+)

*'''SUPPLIER_ORDER_EDIT_BUYINGPRICE_DURING_RECEIPT''' ► Can modify the buying price used for PMP calculation when making a stock reception on a supplier order. ► (v6.0+)
*'''SUPPLIER_PROPOSAL_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier proposal to only those with a buying price defined for that supplier. ► (v6.0+)
*'''SUPPLIER_ORDER_MORE_THAN_WISHED''' ► The supplier order status is set to "Totally received" even if there are more products received than ordered. ► (v15.0+)

*'''DISPLAY_DISCOUNTED_SUPPLIER_PRICE''' ► Allow to display discounted supplier price when searching product in supplier documents ► (v10.0)

*'''MAIN_CAN_EDIT_SUPPLIER_ON_SUPPLIER_ORDER''' ► Allow to change the supplier on a draft supplier order ► (v10.0)

*'''SUPPLIER_PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD'''

*'''SUPPLIER_ORDER_CAN_UPDATE_BUYINGPRICE_DURING_RECEIPT''' ► Allow to change price on receipt ► (v19.0)

*'''SUPPLIER_HIDE_SUPPLIER_OBJECTLINES''' ► Hide the supplier information on objectlines (invoices, etc..) ► (v19.0)

[[#Top|(back to top)]]

=Third Parties Module=

*'''COMPANY_AQUARIUM_CLEAN_REGEX''' ► Add a REGEX rule on the third parties names. It applies a regex replacement pattern on generated code if COMPANY_AQUARIUM_CLEAN_REGEX is set. Value must be a regex with parenthesis. The part into parenthesis is kept, the rest removed. For example if COMPANY_AQUARIUM_CLEAN_REGEX = '<code>^..(..)..(.*)</code>' the first char and second char are removed and the char 5 and 6 too ► (>= 8.0.1)

*'''MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES''' ► See in Global options section.

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► See in Global options section.

*'''SOCIETE_EMAIL_MANDATORY''' ► E-mail is a mandatory field when creating a thirdparty

*'''SOCIETE_DISABLE_CUSTOMERS''' ► Remove all menu and features related to customers

*'''SOCIETE_DISABLE_PROSPECTS''' ► Remove all menu and features related to prospects
*'''SOCIETE_DISABLE_PROSPECTSCUSTOMERS ►''' Remove the status "Customer/Prospect" when thirdparties creation or modification

*'''SOCIETE_DISABLE_STATE''' ► Do not use field "state/province"

*'''SOCIETE_SORT_ON_TYPEENT''' ► The combo list of "type of third party" is sorted on alphabetical order instead of the field "position" that appears into dictionary instead.

*'''SOCIETE_ASK_FOR_SHIPPING_METHOD''' ► Shipping method can be predefined on customer card and will be used as default on order creation
*'''SOCIETE_ADD_REF_IN_LIST''' ► Displays the code before the name in the lists ► Value 1 -> Code + name + alias ou Code + name if colone alias 2 -> Code + alias 3 -> Alias

*'''THIRDPARTY_CAN_HAVE_CATEGORY_EVEN_IF_NOT_CUSTOMER_PROSPECT_SUPPLIER''' ► Possible to add Categories to third parties that are not customer, prospect or supplier.

*'''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.

*'''THIRDPARTY_NOTCUSTOMERPROSPECT_BY_DEFAULT''' ► Do not set status "Customer/Prospect" to "on" when creating a new third party from menu "New third party".

*'''THIRDPARTY_INCLUDE_PARENT_IN_LINKTO''' ► Search also for elements on parent third party when using the "link to" object feature.

*'''THIRDPARTY_INCLUDE_PROJECT_THIRDPARY_IN_LINKTO''' ► Search also for elements on third party that own the project of the current element when using the "link to" object feature (if project is owned by a different thirdparty than current one).

*'''THIRDPARTY_LOGO_ALLOW_EXTERNAL_DOWNLOAD''' ► When a logo is uploaded, a share key is automatically set so the file can be downloaded using the share key.

*'''THIRDPARTY_SUGGEST_ALSO_ADDRESS_CREATION''' ► Enabled contact creation on third-party create card
*'''THIRDPARTY_QUICKSEARCH_ON_FIELDS''' ► Personalized search criteria ► Example: $conf->global->THIRDPARTY_QUICKSEARCH_ON_FIELDS = 's.nom=ThirdPartyName;s.name_alias=AliasNameShort;s.code_client=CustomerCode'
*'''MEMBER_CAN_CONVERT_CUSTOMERS_TO_MEMBERS''' ► Enabled member creation on third-party create card
*'''SOCIETE_DISABLE_PARENTCOMPANY''' ► Disables attachment to a parent company.
*'''THIRDPARTY_CUSTOMERPROSPECT_BY_DEFAULT''' ► Set the third party to customer by default
*'''THIRDPARTY_SUPPLIER_BY_DEFAULT''' ► Set the third party to supplier by default
*'''THIRDPARTY_CUSTOMERTYPE_BY_DEFAULT''' ► Set the third party type by default (3 = customer & prospect / 2 = prospect / 1 = customer )
*'''CONTACT_DISABLE_PERSONALINFO''' ► Disable Personal data on contact page
*'''SOCIETE_DISABLE_WORKFORCE''' ► Disable work force selector on society page
*'''SOCIETE_SHOW_VAT_IN_LIST''' ► display VAT number in combo list of thirdparties ► (V15+)
*'''THIRDPARTY_DEFAULT_CREATE_CONTACT''' ► When set, a contact is created at the creation of an individual third party ► (v14.0)

*'''MAIN_SUPPORT_SHARED_CONTACT_BETWEEN_THIRDPARTIES''' ► Able to share contact between several third parties
*'''THIRDPARTY_CUSTOMERCODE_EQUALS_MEMBERREF''' ► When creating third parties out of members, the customer code is set equal to the member Ref. ► (v22.0)
*'''SOCIETE_NO_SYNC_LINKED_MEMBER''' ► If set, changes to a third party will not be synchronized to a linked member. ► (v23.0)

[[#Top|(back to top)]]

=Ticket Module=

*'''TICKET_SHOW_MESSAGES_ON_CARD''' ►Display all ticket related messages on the main ticket card. ► (>= 10.0)
*'''TICKET_AUTO_ASSIGN_CONTRACT_CREATE''' ►Automatically create a contract linked to the ticket ► (>= 10.0)
*'''TICKET_AUTO_CREATE_FICHINTER_CREATE''' ►Automatically create an intervention linked to the ticket ► (>= 10.0)
*'''TICKET_AUTO_ASSIGN_USER_CREATE''' '''►''' (>= 21.0) 0=No auto assignement, 1=Auto assign current user if no user was set, 2=Auto assign current user even if another user was set.
*'''TICKET_CHECK_NOTIFY_THIRDPARTY_AT_CREATION''' ►Automatically check "notify thirdparty at creation" ( >=16)
*'''TICKETS_MESSAGE_FORCE_MAIL''' ► Pre check email sending on ticket message (>=15)
*'''TICKET_SEND_PRIVATE_EMAIL ►''' Allow a private message to be sent by mail (>=17)
*'''TICKET_LIMIT_VIEW_ASSIGNED_ONLY''' '''►''' Only display tickets assigned to the user
*'''TICKET_ADD_AUTHOR_AS_CONTACT''' '''►''' If set to 1: Automatically adds the author as internal contact. If set to 2: Automatically adds the author as external contact if external user. (>=20)
*'''TICKET_ASSIGN_CONTACT_TO_MESSAGE''' '''►''' If known, the external contact is assigned to the message. (>=19)
*'''TICKET_ALLOW_CLASSIFICATION_MODIFICATION_EVEN_IF_CLOSED''' '''►'''Allow modify ticket classification even if closed. (>=19)
*'''WORKFLOW_TICKET_CLOSE_INTERVENTION''' ►On ticket close, automatically close an intervention linked to the ticket
*'''TICKET_INCLUDE_SUSPENDED_STATUS''' ► Use ticket suspended status (>=19)
*'''TICKET_INCLUDE_LINK_TO_PUBLIC_INTERFACE_IN_MESSAGE''' ► Add a link in bottom of emails sent from ticket page with link to public ticket admin tool (>=22)

=VAT Report=

*'''MAIN_INCLUDE_ZERO_VAT_IN_REPORTS''' ► Include lines with VAT to 0% (for "auto-liquidation" in EEC) ► (v8.0.3+)

[[#Top|(back to top)]]

=Website Module=

*'''WEBSITE_USE_WEBSITE_ACCOUNTS''' ► Add a table and a tab to manage some accounts for websites to a third party
*'''WEBSITE_ALLOW_OVERWRITE_GIT_SOURCE''' ► Add a button to export a website over the GIT sources
*'''WEBSITE_ADD_CSS_TO_BODY''' ► Add a CSS class to the body tag of websites

[[#Top|(back to top)]]

 

=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 guaranteed with this. Also if the image is removed or renamed by the image hosting service, your proposal, order or invoice will be broken.
*'''FCKEDITOR_ALLOW_ANY_CONTENT''' ► Allow to enter any content. However, this will totally disable content filtering which is one of the most important CKEditor features. You can use this to keep all your tags and attributes in the html content.
*'''FCKEDITOR_ENABLE_SCAYT_AUTOSTARTUP''' ► Allow to activate the SpellCheckAsYouType (SCAYT) plugins of CKEditor i.e an automatic spell checking. The value to activate this option is 1.
*'''MAIN_ALLOW_WYSIWYG_LOCAL_MEDIAS_ON_PRIVATE_NETWORK''' ► By default, you can add medias links (img src or other) into the rich text content editor, but you can't add links like that use a local host like "https://localhost/file". If you set this option to 1, you can.
*'''MAIN_ALLOW_WYSIWYG_EVEN_ON_UNSECURED_EXTERNAL_HTTP_URL''' ► By default, you can add medias links (img src or other) into the rich text content editor, but not if the link is a unsecure "http" url (not https) and your Dolibarr is http. If you set this option to 1, you can.

[[#Top|(back to top)]]

=STRIPE Module=

*'''STRIPE_FORCE_VERSION''' ► Force the STRIPE version. For Example: "2019-09-09" (v11+)
*'''STRIPE_REUSE_EXISTING_INTENT_IF_FOUND''' ► With this, you will have idempotency key but the payment intention will be reuse and not Generate again (13+)

[[#Top|(back to top)]]

=ClickToDial Module=

*'''CLICKTODIAL_FORCENEWTARGET''' ► Open in new page.

[[#Top|(back to top)]]

 

=For SaaS / Cloud hosting integrators=

The following options are useless for a common usage of Dolibarr. But they are usefull if you plan to host / provide Dolibarr instances as Software As A Service (SAAS) to your customers.

*'''CRON_DISABLE_KEY_CHANGE''' ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*'''CRON_DISABLE_TUTORIAL_CRON''' ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*'''CRON_WARNING_DELAY_HOURS''' ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

*'''MAILING_NO_USING_PHPMAIL''' ► To avoid bad use of the emailing module, it is recommended to set this option to 1 (This option is described previously). Also you can complete the message visible by customers when they try to setup the SMTP credentials of their Dolibarr by using the constant MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS (This option is described previously). For example, you can point to a FAQ on your website.

*'''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► If you have set a system limit on number of recipients on your system, you can set also this option to match the same value, so users will be informed: So '''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' restricts sending of 1 email message to <code>x</code> recipients for the same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include a ton of recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available. Note that this is not a hard limit; it is just the quantity that will be displayed on warnings on screen. For a real limit, this must be implemented into the system.

*'''MAILING_LIMIT_SENDBYDAY''' ► This is a limit of number of emails, an instance can send. Note that this is not a hard limit; it is just the quantity that will be displayed on warnings on screen. For a real limit, this must be implemented into the system.

*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Set this value to a translation key. Then add translation keys into the instance so user will see a message when into the email setup page. For example, you can set a message to say: ''Warning: To avoid abuse, when using default setup, you are restricted to 500 emails per day for all your application (account may be suspended in case of violation of this rule. You can setup application to use your own SMTP server for sending email so you want have no restriction at all (see menu Home-Setup-Emails)''

*'''MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE''' ► If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock and remove the upgrade.unlock so the administration tools like install.php, upgrade.php and repair.php can't be used on your customer instance (until the install.lock file is deleted or the upgrade.unlock file is created).

*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted, separated by a comma. So, when your customer go into the Email setup area:
**If he has chosen mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he has chosen smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option '''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD'''.

You can also provide a list of URLs that return just an IP instead of a list of hardcoded IP. So you can for example set 1 url that contact a whoami service that return the public IP of server and another one doing the one on a IPv6 address, so on the setup page, the public IP adress of the server will always be uptodate for both ipv4 and ipv6 (Example: "https://ipv4.server.com/_service_showmyip.php,https://ipv6.server.com/_service_showmyip.php")

*'''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD''' ► Set here the string to add in the SPF record This string will be shown into a help message when the user in in the setup of email page and has choose a method using an external SMTP server.

*'''MAIN_FIRST_PING_OK_ID''' ► Set this value to "disabled" to remove completely any ping after a complete setup.

*'''MAIN_FILECHECK_LOCAL_SUFFIX''' and '''MAIN_FILECHECK_LOCAL_EXT''' ► If you offer a customized or patched version of Dolibarr, when the user will use the tool to check the integrity of files, the default xml file name used for signature checking will be the official file provided by the Dolibarr team, so it does not includes your own changes. To have the suggested signature file being your own file, you can set the constant MAIN_FILECHECK_LOCAL_SUFFIX to a suffix. For example, set this to "'''-mysaassolution'''". So, when the user will use the file integrity tool, the default file to check for signature will be "'''/install/filelist-10.0.2-mysaassolution.xml'''" instead of "'''/install/filelist-10.0.2.xml'''". All you have to do is generate the signature file '''mysaassolution''' using the tool '''build/generate_filelist_xml.php''' and put this file into the install directory of your customer instance. Doing this, your customer, and yourself, will be able to check if a file was modified without being disturbed by false alerts due to your customized files or patches (they will be included in the signature used for check). Also, if you want to zip the customized signature file into "'''/install/filelist-10.0.2-mysaassolution.xml.zip'''", you can set the constant MAIN_FILECHECK_LOCAL_EXT to '.zip'.

*'''MAIN_HIDE_WARNING_TO_ENCOURAGE_SMTP_SETUP''' ► Set to 1 by default (so warning is hidden). You can set it to 0 to show a warning to encourage admin to set its own SMTP service.

*'''MAIN_MAIL_SENDMODE_password''' ► To force the mode to send the email on the "password forgotten" page. So you can decide to use php mail or SMTP method for this specific use case.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► If set to N, the warning saying modules are not activated will be shown if number of activated module is < N (Having this variable not defined is same than having it set to 1). This may be usefull if you preinstall an application with some modules already loaded by default and you want to keep the warning to be sure the user will enable other modules he need, even if some modules are already enabed.
*'''MAIN_SETUP_MODULES_DESC''' ► If your installation is already done with activated module, the help message to explain how to enable a module on the setup page is hidden. You can keep it visible by adding this option to 1.

*'''MAIN_NO_UPGRADE_REDIRECT_ON_LEVEL_3_CHANGE''' ► The page to make the migration is not shown automatically when you deploy files of version X.Y.Z+delta over an installation with a database version X.Y.Z. The upgrade page will be shown automatically only if there is a change on value of X or Y in version.

*'''SYSLOG_DISABLE_LOGHANDLER_SYSLOG''' ► Set this to 1 to disable usage of syslog (having all customer instances logging in the same system file is not a good idea).

*'''WEBSITE_REPLACE_INFO_ABOUT_USAGE_WITH_WEBSERVER''' ► Put here a text or a translation key of a text to show when the user will use the feature "Deploy" when he want to deploy a website done with Dolibarr CMS. So you can, for example, show him a message that this feature is not part of its subscription and putting a website online may need a complementary subscription.

[[#Top|(back to top)]]

Setup Other

2026-07-27T08:05:54Z

Iouston: /* Proposals Module */ add PROPAL_ENABLE_NEGATIVE

[[fr:Paramétrage_Divers]]
[[es:Configuración_Varios]]
[[de:Erweiterte_Einstellungen]]
[[zh:其他设置]]


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

'''Help About Screen''': Other setup

'''Menu Path''': Home ► Setup ► Other

'''Introduction'''

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

{{warning|32px}} This page contains the list of some advanced development parameters. In most cases, they are parameters for internal usage, development, external modules, features in development not stable or that may lead to security risk. For standard usage of Dolibarr, such parameters '''SHOULD NOT''' be used. All experimental options are NOT supported. They may be removed in a future, modified at any version and break stability of your application.

To enable/override a parameter you have to define the constant name and set it to 1 (unless otherwise stated) in <code>Home ► Setup ► Other Setup</code>

The options here may not be documented since they are not stable and are unsupported (remember they are experimental or development options). The basic format of how the list is written is broken down in the example below:

UNSTABLE_OR_DEV_OPTION ► ''Description of config and goal'' ► ''(specific version information) or values''
<center>
__TOC__
</center>
=Global Options=

*'''ADD_UNSPLASH_LOGIN_BACKGROUND''' ► The background image will be refreshed on every login page refresh. Background image is pulled from the popular open source image website Unsplash. If an already saved static background image exists, then this code will override it (but not delete the saved image). Warning: Using this may allow this external website to steel your login credentials (the value to be put is the URL of the service, exemple : https://source.unsplash.com/random) ► (v10.0)
*'''MAIN_HIDE_POWERED_BY''' ► Hide the "Powered by Dolibarr" picto on public pages
*'''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 to fail by smartphone applications like [[Application Android - DoliDroid]], breaking some features when using Dolibarr from such application. If the text start with a "+", the text will be added to the standard "Dolibarr" label instead of replacing it.

*'''MAIN_AUTOFILL_DATE''' ► If this constant is defined (to something other than <code>0</code>), the date of invoice, proposal, order or payment are auto-filled with the current date. It is highly recommended to NOT ENABLE this feature. This can create a lot of input errors with data not validated by users. This leads to incorrect values saved in the database causing confusion when you have to do your accountancy reports!
*'''MAIN_AUTOFILL_DATE_PROPOSAL►'''If this constant is defined (to something other than 0), the date of proposal is auto-filled with the current date.

*'''MAIN_AUTO_TIMESTAMP_IN_PUBLIC_NOTES''' ► Add a timestamp and user automatically when editing the ''public'' note.

*'''MAIN_AUTO_TIMESTAMP_IN_PRIVATE_NOTES''' ► Add a timestamp and user automatically when editing the ''private'' note.

*'''MAIN_DEFAULT_PAYMENT_TERM_ID''' ► With ID of a payment term, will use this as default payment term each time you create a new proposal, order, invoice (customer and supplier). Deprecated. Replaced with the default setup feature instead (see French page of wiki for some exemple : [[Paramétrage Valeurs par défaut]])
*'''MAIN_DEFAULT_PAYMENT_TYPE_ID''' ► With ID of a payment type, will use this as default payment type each time you create a new proposal, order, invoice (customer and supplier). Deprecated. Replaced with the default setup feature instead (see French page of wiki for some exemple : [[Paramétrage Valeurs par défaut]])

*'''MAIN_DEFAULT_LANGUAGE_FILTER''' ► Useful if you do not want to show <code>en_US</code> language option in combo boxes (other languages can easily be removed in <code>langs</code> directory but not <code>en_US</code>) ► (v10.0)

*'''MAIN_LANGUAGES_ALLOWED''' ► Is a list of languages without spaces, example : <code>fr_FR,en_US,de_DE,it_IT</code> If defined, only those languages will appear in combos. ► (v11.0)

*'''MAIN_DISABLE_NOTES_TAB''' ► Show or hide notes tab in the card page

*'''MAIN_DISABLE_CONTACTS_TAB''' ► Show or hide contacts tab in the card page

*'''MAIN_DISABLE_FULL_SCANLIST''' ► Disables the complete scan of tables to allow the pagination to show total number of pages. May be useful to activate on systems with a very high quantity of data (tables with more than 2 000 000 records).

*'''MAIN_DISABLE_JQUERY_JNOTIFY''' ► Disable usage of <code>JNotify</code> to show confirm or error messages

*'''MAIN_DISABLE_AJAX_COMBOX''' ► If you have a large number of third parties or products, you can disable the autocomplete feature on the third parties list by setting this constant to <code>1</code> ► (v3.6.0+)
*'''MAIN_DISABLE_MULTIPLE_FILEUPLOAD''' ► Disable users to upload multiple files at once.
*'''MAIN_DISABLE_TRUNC''' ► Disable all truncings in select list. ► (v7.0+)

*'''MAIN_DISABLEDRAFTSTATUS''' ► Disable the status "Draft" for some objects (project, donation, ...) so the object is directly created with status "Validated"

*'''MAIN_DOC_USE_OBJECT_THIRDPARTY_NAME''' ► Add name of thirdparty at begin of generated document.

*'''MAIN_DOC_USE_TIMING''' ► Add a timestamp at end of generated document. Value must be format of timestamp. For example: <code>%Y%m%d%H%M</code> (only for ODT files)

*'''MAIN_DOC_UPLOAD_NOT_RENAME_BY_DEFAULT''' ► Disable the auto renaming on upload file ► (v10.0)

*'''MAIN_DOL_SCRIPTS_ROOT''' ► Define directory who contains 'scripts' directory (e.g. <code>/var/www/dolibarr</code>). Value of this variable may be requested by some external script or tools.

*'''MAIN_ENABLE_LOG_TO_HTML''' ► If this constant is defined, it is possible to have logs inside pages by adding the parameter <code>&logtohtml=1</code> into URL.

*'''MAIN_ENABLE_IMPORT_LINKED_OBJECT_LINES''' ► Allow to import lines into current document from "linked" compatible documents ► (v8.0+)

*'''MAIN_FIRST_TO_UPPER''' ► Dolibarr add uppercase to Third Parties, 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_ALL_TO_UPPER''' ► Dolibarr puts uppercase for Third Parties, 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. ► (v11.0)

*'''MAIN_ALL_TOWN_TO_UPPER''' ► Dolibarr puts uppercase for town names if not done. ► (v13.0)

*'''MAIN_FILESYSTEM_ENCODING''' ► With some PHP versions, PHP is not able to detect the page code for filesystem of the server OS. To solve this, Dolibarr assumes your OS filesystem is <code>UTF-8</code> if on Linux or OSX system, and <code>ISO-8859-1</code> if on Windows. If not, for example on a Windows server with a NTFS <code>UTF-8</code> pagecode, you can set the variable <code>MAIN_FILESYSTEM_ENCODING</code> to "<code>utf-8</code>".

*'''MAIN_FORCELANGDIR''' ► Relative path of the directory holding your custom <code>langs</code> folder.
*'''MAIN_HTML_TITLE''' ► Can be used to control how the html page title is formatted. If value contains key '<code>noapp</code>', application name will not be output. If value contains '<code>thirdpartynameonly</code>', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: '<code>noapp;thirdpartynameonly</code>'

*'''MAIN_HELPCENTER_LINKTOUSE''' ► Define the URL link to use as the target page for link "I need help" onto logon page

*'''MAIN_LOGOUT_GOTO_URL''' ► URL to which the user will be redirected after LOGOUT

*'''MAIN_MAXTABS_IN_CARD''' ► Maximum number of tabs visible. Others are grouped into a combo list.

*'''MAIN_MAXLIST_OVERLOAD''' ► Maximum number of line in space's domain.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► A warning saying setup of modules is not complete is shown if the number of enabled modules is lower or equal than this value (<code>1</code> if not defined)

*'''MAIN_NO_CONCAT_DESCRIPTION''' ► Allow to use only input custom description in lines (proposal, order, invoice) ► (v10.0) < v20.0. [ OSBOLETE since 20.0 | SEE Product module admin configuration to set the description behavior of products and services ]. This value is overwritten by PRODUCT_AUTOFILL_DESC, controled by the option in the product module admin configuration, and is no longer used. Kept in code to allow compatibility if custom modules are using it. Removed completely from v22.

*'''MAIN_OPTIMIZE_SPEED''' ► Use some speed enhancements. See page [[FAQ Increase Performance]] for more information.
*'''MAIN_PASSWORD_FORGOTLINK ►''' Change forgotten password link on login page. ► (v9.0)

*'''MAIN_PROPAGATE_CONTACTS_FROM_ORIGIN''' ► When creating an order, contract, invoice from another object, specific contacts of objects are set as specific contact of the new object when possible. ► (v4.0+)

*'''MAIN_PUBLIC_NOTE_IN_ADDRESS''' ► Show public note in address block ► (v4.0+)

*'''MAIN_REMOVE_INSTALL_WARNING''' ► Remove all security warnings that appear to administrator users if URL <code>/install</code> is public. You should solve the problem if warning occurs, instead of removing the warning! For this, create a file called <code>install.lock</code> into Dolibarr root directory. This will stop the warning but also make the page <code>/install</code> not possible to use, to protect your installation.

*'''MAIN_REPEATCONTACTONEACHTAB''' ► If added and set to <code>1</code>, this adds contacts on all tabs, not only main tab.

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

*'''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND''' ► Change way of rounding total including tax of lines, rounding first of after.

*'''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND_SUPPLIER'''► Change way of rounding total including tax of lines, rounding first of after.

*'''MAIN_SERVER_TZ''' ► If you can't set the time zone of your PHP installation, set this constant. Better is to set it to UTC. In future, this constant will be forced to '<code>UTC</code>' so PHP server time zone will not have effect any more. Examples: <code>Europe/Paris</code>, <code>auto</code>. Dolibarr will apply the timezone before saving dates in the database. Meaning that if you remove the parameter the dates saved will not change back to UTC.

*'''MAIN_SEARCH_FORM_ON_HOME_AREAS''' ► Show the search form on home page areas for core modules (Removed after v5 due to global search combo) ► (v6.0+)

*'''MAIN_SEARCHFORM_SUPPLIER_INVOICE_DISABLED''' ► Disable the supplier invoice on the search form

*'''MAIN_SEARCH_DIRECT_OPEN_IF_ONLY_ONE''' ► If only one result is found, then setting this value to <code>1</code> will take you direct to the item (default method). Setting the value to <code>0</code> will show the result in the list as a single result ► (v5.0+)

*'''MAIN_SERVICES_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country. It can have value '1' or '2'. If value 2, the VATs available to select only the ones of buying country. If '1', the VATs available to select mix the ones of selling country and the ones of buying country. ► (v18.0+)

*'''MAIN_SHOW_TUNING_INFO''' ► Add tuning information into JavaScript console. Better when xdebug is enabled.

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show also technical IDs on elements cards or some lists (not supported everywhere).

*'''MAIN_SHOWDATABASENAMEINHELPPAGESLINK''' ► Show database name in upper help menu ► (v8.0+)

*'''MAIN_USE_ALTERNATE_TRANSLATION_FOR''' ► List of fields per object that need an alternate translation. Example: <code>MAIN_USE_ALTERNATE_TRANSLATION_FOR=societe:name,town;contact:firstname,lastname</code>

*'''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_USE_JQUERY_JEDITABLE''' ► Allow to update from screen, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this feature, because it bypasses some business actions (updates on other data that should be done consistently) and ignores business controls on data you saved. Consequently this feature breaks consistency of data and possibly the stability of the 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_USE_OLD_SEARCH_FORM''' ► Display the old search form in left menu.

*'''MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS''' ► Allow to force the VAT rate to a given value (instead of higher VAT rate of country) if the VAT rate of product was not defined.

*'''MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES''' ► If we can't guess if a thirdparty is a company or individual (not VAT ID fill, no Prof ID fill, no type of thirdparty fill), then we suppose it is a company (B2B business) if 1, we suppose it is an individual (B2C business) if 0.

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► For intra CEE sales, we use by default, on proposal, order or invoice creation, a 0 VAT for customers that are companies (see MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES to change behaviour to know if a thirdparty is a company or an individual). But if the option MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL is set, we will use the 0 VAT only if a VAT ID is defined for the customer.

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_INDIVIDUAL_CUSTOMER_OUT_OF_EEC''' ► For to use the default VAT of product for individual customers that are out E.E.C. (European Economic Community) ► (v7.0+). ''There is no reason to use this.''

*'''MAIN_VIEW_LINE_NUMBER''' ► Shows a line number for each line of products/services at documents like proposal / order / invoice. Only on screen, not on PDF.

*'''MAIN_VIEW_LINE_NUMBER_IN_LIST''' ► Shows a line number in lists ► (v12.0)

*'''MAIN_VOLUME_DEFAULT_ROUND''' ► Accuracy of volume (number of decimals)

*'''MAIN_VOLUME_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''MAIN_WEIGHT_DEFAULT_ROUND''' ► Accuracy of weight (number of decimals)

*'''MAIN_WEIGHT_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''USER_HIDE_INACTIVE_IN_COMBOBOX''' ► Disable display inactive users in combobox.

*'''MAIN_DISABLE_PDF_THUMBS''' ► Disable thumbs PDF in case of imagick bug

*'''MAIN_KEEP_REF_CUSTOMER_ON_CLONING''' ► Keep the Customer Reference on cloned object (Propal/Invoice)

*'''MAIN_DONT_KEEP_NOTE_ON_CLONING''' ► Remove the object notes during cloning ► (v11.0)

*'''MAIN_DOC_SORT_FIELD''' ► Set the default sorting field on document page (name by default) ► (v11.0)

*'''MAIN_DOC_SORT_ORDER''' ► Set the default sorting order (ASC or DESC) on document page (ASC by default) ► (v11.0)

*'''MAIN_USE_ZIPTOWN_DICTIONNARY''' ► Use dictionary ZIP for create card.

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Show search in top menu with theme eldy ► (v11.0)

*'''MAIN_PHONE_SEPAR''' ► Separ phone number other space ► (v12.0)

*'''GRAPH_USE_FISCAL_YEAR''' ► Widgets uses fiscal year

*'''SHOW_SOCINFO_ON_PRINT''' ► Permit to add user company information on each printed document (when click on Dolibarr print button) ► (v12.0)

*'''MAIN_FEATURES_LEVEL''' ► Level of features to show: <code>-1=stable+deprecated</code>, <code>0=stable only (default)</code>, <code>1=stable+experimental</code>, <code>2=stable+experimental+development</code>

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show technical id for object.

*'''MAIN_HTTP_CONTENT_SECURITY_POLICY''' ► Allows you to fill in the content security rules ► (v6.0)

*'''SOCIETE_ON_SEARCH_AND_LIST_GO_ON_CUSTOMER_OR_SUPPLIER_CARD''' ► Allow to change the link of the third party to customer/supplier card instead of contact card on List.

*'''MAIN_MODULE_SETUP_ON_LIST_BY_DEFAULT''' ► If set to "common" the setup module becomes list by defaut

*'''MAIN_PAGESIZE_CHOICES''' ► Configure select field to choose number of lines displayed on listing (<code>10:10,15:15,20:20,30:30,40:40,50:50,100:100,250:250,500:500,1000:1000,5000:5000</code>).

*'''MAIN_USE_TOP_MENU_QUICKADD_DROPDOWN''' ► Add a dropdown menu with shortcuts to create new objects ► (v13.0)

*'''MAIN_EMAILCOLLECTOR_MAIL_WITHOUT_HEADER''' ► Remove the header stored by email collector ► (v13.0)

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID'''

*'''MAIN_OPTIMIZEFORTEXTBROWSER''' ► Optimise interface for a text only browser. This variable is set to 1 automatically if your browser is lynx or links

*'''MAIN_NB_OF_YEAR_IN_WIDGET_GRAPH''' ► Set the number of years visible on some graph of some widgets (2 is default value)

*'''MAIN_CREATEFROM_KEEP_LINE_ORIGIN_INFORMATION'''

*'''API_DISABLE_LOGIN_API''' ►(v14.0)

*'''MAIN_LOGIN_BADCHARUNAUTHORIZED''' ► Add possibility to define bad character unauthorized into login name REGEX expression (Default value is @<>"\') ► (v16.0)
*'''MAIN_SHOW_ALL_FILES_ON_DOCUMENT_TOOLTIP''' ► Add all files visible from the object to be visible from the list of object.
*'''MAIN_LIST_ALLOW_PUBLIC_NOTES''' ► Display public notes on list
*'''MAIN_LIST_ALLOW_PRIVATE_NOTES''' ► Display private notes on list

*'''MAIN_CHECKBOX_LEFT_COLUMN''' ► Display private check boxes on the left ► (v17.0)
*'''MAIN_STATS_GRAPHS_SHOW_N_YEARS''' ► Nb of years to shows in widget and graph ► (v14.0)
*'''MAIN_HOOK_DEBUG''' ► if >=2 the hook in the logs are more verbose ► (v18.0)

*'''MAIN_ENABLE_AJAX_TOOLTIP''' ► if 1 the tooltips are updated with AJAX request ► (v18.0)
*'''MAIN_NO_INPUT_PRICE_WITH_TAX''' ► if 1 the TTC input field is removed from propal/invoices/... ► (v17.0)

*'''MAIN_DISABLE_SELECT2_FOCUS_PROTECTION''' ► if 1 disable the focus protection ► (v17.0)
*'''MAIN_USE_ADVANCED_PERMS ►''' Add advanced user permission

*'''MAIN_FREE_PRODUCT_CHECKED_BY_DEFAULT ►''' Check "product" or "service" by default on order/invoices/propal cards (set value "product" or "service")
*'''MAIN_LINK_BY_REF ►''' Allow to link documents by choosing the type and ref from the object linked option
*'''MAIN_STORE_COMPUTED_EXTRAFIELDS ►''' when enabled, computed extrafields have their formula result evaluated and persisted to the database on save (instead of the default behavior where the formula is re-evaluated on the fly at each display and the column is left null).

'''Official supported option'''

The following options are not hidden option. They are available by default from the interface.

*'''MAIN_ONLY_LOGIN_ALLOWED ►''' Activate maintenance mode and set user that is allowed to login. Value must be user login. Available into menu Home - Admin tools - User session, it is filled with admin user when clicking on button "Block other session". Enable <code>MAIN_STORE_COMPUTED_EXTRAFIELDS</code> when you need to sort, filter, sum or report on a computed extrafield's value in SQL/lists: instead of recalculating the formula on every display (leaving the column null), it stores the result in the database on each save, at the cost of the value being a snapshot that only refreshes when the record is saved again.

[[#Top|(back to top)]]

=Security Options=

*'''MAIN_SECURITY_ANTI_SSRF_SERVER_IP''' ► Can set a complete list of IPs of server.

*'''MAIN_SECURITY_CSRF_WITH_TOKEN''' ► Activate a second anti-CSRF protection on POST (so a POST from another web site can't be done). Note there is also a default protection using test on referrer that is not reliable. This second protection uses TOKEN on forms and is more powerful. Value can be: 0=CSRF protection disabled; 1=CSRF protection is on POST URLs only (default from version Dolibarr 15.0+); 2=CSRF protection is required on POST + some GET URL that contains some white listed parameters like the parameter "action" used to request database change (default from version Dolibarr 16+), 3=CSRF protection is enabled on any POST and GET URLs (a valid CSRF token is expected whatever are the parameters, warning: can be enabled on Dolibarr but some external modules developped by thirdparty may not be ready yet with this option)

*'''MAIN_MODULES_FOR_EXTERNAL''' ► Limit available modules for external users. By default value is '<code>facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda</code>'

*'''MAIN_ALLOW_SVG_FILES_AS_IMAGES''' ► Allow to use SVG file as image files. Warning: This may introduce security vulnerability (javascript can be embedded into SVG file).

*'''MAIN_RESTRICTHTML_ONLY_VALID_HTML''' ► Refused parameter if value is not a valid HTML content. The content is also sanitized with Tidy.

*'''MAIN_RESTRICTHTML_ONLY_VALID_HTML_TIDY''' ► Refused parameter if value is not a HTML content validated by Tidy PHP library. The content is also sanitized with Tidy.

*'''MAIN_RESTRICTHTML_REMOVE_ALSO_BAD_ATTRIBUTES''' ► Sanitize also non standard attributes on HTML content.
*'''MAIN_SECURITY_SALT''' ► A salt string to base the hashing on. 8 strings length recommended.

*'''MAIN_SECURITY_MAX_IMG_IN_HTML_CONTENT''' ► Maximum number of Images on the HTML content
*'''MAIN_SECURITY_ALLOW_UNSECURED_LABELS_WITH_HTML''' ► Allow HTML tags into products label

*'''MAIN_SECURITY_FORCERP''' = "strict-origin-when-cross-origin" (default) so browser doesn't send any referrer when going into another web site domain / "same-origin" / "strict-origin"

[[#Top|(back to top)]]

=Members Module=

*'''MEMBER_NEWFORM_FORCEMORPHY''' ► Force nature of member set to "phy" for physical or to "mor" for moral ► (v12.0)
*'''MEMBER_ALLOW_CHANGE_OF_TYPE''' ► Member can edit their type on public subscription page ► (v13.0)
*'''ADHERENT_DEFAULT_CREATE_THIRDPARTY''' ► Thirdparty is created when creating a new member ► (v13.0)
*'''MEMBER_SUBSCRIPTION_SUGGEST_END_OF_MONTH''' ► If set to 1, the member subscription end date will be suggested for the end of the month ► (v18.0)
*'''MEMBER_SUBSCRIPTION_SUGGEST_END_OF_YEAR''' ► If set to 1, the member subscription end date will be suggested for the end of the year ► (v18.0)
*'''MAIN_NB_OF_YEAR_IN_MEMBERSHIP_WIDGET_GRAPH''' ► If set, it limits the number of years visible on graph and widgets of membership (empty is default value to show all) ► (v18.0)
*'''MEMBER_NO_SYNC_LINKED_THIRDPARTY ►''' If set, changes to a member will not be synchronized to a linked third party. ► (v23.0)

[[#Top|(back to top)]]

=Accounting Module=

*'''ACCOUNTANCY_COMBO_FOR_AUX''' ► Add graphic option for ACCOUNTANCY_COMBO_FOR_AUX. Having this option on may slow down and even freeze the accounting features if you have a very large number of thirdparties ► (v10.0)
*'''ACCOUNTING_DEFAULT_NOT_NOTIFIED_VALIDATION_DATE''' ► Avoid validating the lines with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*'''ACCOUNTING_DEFAULT_NOT_NOTIFIED_EXPORT_DATE''' ► Avoid flagging the lines as exported with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*'''ACCOUNTANCY_USE_PRODUCT_ACCOUNT_ON_THIRDPARTY ►''' Add 2 fields on thirdparty card which allow you to set an account for all sells products and an other for all buying products for this customer ► (v14.0)
*'''ACCOUNTING_MANAGE_ZERO''' '''►''' Allow to manage char 0 in accounting account (if enabled 1 ≠ 10) ► (v14.0)

[[#Top|(back to top)]]

=Agenda Module=

*'''AGENDA_ALL_CALENDARS''' ► Change the default view of calendar pages to see all the Agenda's (instead or yours only be default)

*'''AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS''' ► To automatically set end date of event to start date + delta on event creation page.

*'''AGENDA_DISABLE_LOCATION''' ► Disable location field in action card ► (>=v5.0)

*'''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''''').

*'''MAIN_ADD_EVENT_ON_ELEMENT_CARD''' ► Allow to create an event from a document (proposal, order, invoice)

*'''AGENDA_SUPPORT_PRIORITY_IN_EVENTS''' ► Allow to have priorities in events ► (>=v13.0)

*'''AGENDA_ADDACTIONFORPHONE''' ► Allow you to create a event from phone number ► (=<v12.0) - Need to be fix for (=>v12.0) https://github.com/Dolibarr/dolibarr/issues/22720

*'''AGENDA_ADDACTIONFOREMAIL''' ► Allow you to create a event from Email ► (=<v12.0) - Need to be fix for (=>v12.0) https://github.com/Dolibarr/dolibarr/issues/22720
*'''MAIN_ACTIONCOM_CAN_ADD_ANY_CONTACT''' ► Allow you to add any contact on events if set at 1a https://github.com/Dolibarr/dolibarr/releases/tag/18.0.0

[[#Top|(back to top)]]
=Bank Module=

*'''BANK_CAN_RECONCILIATE_CASHACCOUNT''' ► Can reconciliate cash accounts ► (v3.8)

*'''BANK_DISABLE_CHECK_DEPOSIT''' ► Disable check deposit feature

*'''BANK_ASK_PAYMENT_BANK_DURING_ORDER''' ► Ask bank account during creation of an order

*'''BANK_ASK_PAYMENT_BANK_DURING_PROPOSAL''' ► Ask bank account during creation of a proposal

*'''BANK_USE_OLD_VARIOUS_PAYMENT''' ► To allow to enter miscellaneous payments (not covered by other modules) using old method. '''''Deprecated'''''. Entering various payment is preferred ► (<=v12.0).
*'''MAIN_IBAN_IS_NEVER_MANDATORY''' ► IBAN and BIC informations not mandatory. (V15)

[[#Top|(back to top)]]

 

=BOM and MO Module=

*'''ALLOW_USE_KITS_INTO_BOM_AND_MO'''
*'''BOM_SUB_BOM''' ►Allow to add a BOM in another BOM►(v16.0)

[[#Top|(back to top)]]

 

=Bookmarks Module=

*'''BOOKMARKS_SHOW_IN_MENU''' ► Numbers of bookmark entries to be displayed (10 by default)

[[#Top|(back to top)]]

 

=Inalterable Log Module=

*'''BLOCKEDLOG_ADD_ACTIONS_SUPPORTED''' ► Can complete list of triggered action that are logged
*'''BLOCKEDLOG_USE_REMOTE_AUTHORITY''' ► URL of the remote authority for the blockchain

[[#Top|(back to top)]]

 

=Category-Tags Module=

*'''CATEGORY_SHOW_COUNTS''' ► Shows nb of object by tags in tag tree
*'''CATEGORY_EDIT_IN_MENU_NOT_IN_POPUP ►''' Display categories menu instead of managing it only from "Tools"

[[#Top|(back to top)]]

 

=Contracts=

*'''CONTRACT_SUPPORT_PRODUCTS''' ► Products are also suggested into module contract.
*'''CONTRACT_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)
*'''CONTRACT_HIDE_PLANNED_DATE_ON_PDF''' ► allows you to not display dates on pdf files.
*'''CONTRACT_HIDE_REAL_DATE_ON_PDF''' ► allows you to not display dates on pdf files.
*'''CONTRACT_HIDE_PRICE_ON_PDF''' ► allows you to not display price on pdf files.
*'''CONTRACT_HIDE_QTY_ON_PDF''' ► allows you to not quantity dates on pdf files.
*'''CONTRACT_SHOW_SIGNATURE_STATUS_WITH_SERVICE_STATUS''' ► Show signature status in contract card (Sign by all parties).► (v21.0+)

[[#Top|(back to top)]]

=Cron module=

*'''CRON_DISABLE_KEY_CHANGE''' ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*'''CRON_DISABLE_TUTORIAL_CRON''' ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*'''CRON_WARNING_DELAY_HOURS''' ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

[[#Top|(back to top)]]

 

=Direct Debit Orders=

*'''WITHDRAWAL_ALLOW_ANY_INVOICE_STATUS''' ► If this option is set, all invoices status (even already paid) may appear on the list of invoices qualified for a direct debit payment. This is the list of invoices with a payment request done, and not linked to a direct debit payment. By default, only "unpayed" invoices are used to avoid to pay twice the same invoice.

[[#Top|(back to top)]]

=Donation Module=

*'''DONATION_USE_THIRDPARTIES''' ► If this option is set, a thirdparty field appear on donation forms.

[[#Top|(back to top)]]
=Email=

*'''MAIN_COPY_FILE_IN_EVENT_AUTO''' ► Add attachment document on event auto generated by sending email from dolibarr. ► (v6.0+)

*'''MAIN_EMAIL_USE_LAYOUT'''► Enable the use of predefined layout when writing an email.

*'''MAIN_MAILFORM_DISABLE_ENTERKEY''' ► Activate JavaScript code to disable the enter key in the MAIL form. ► (>= 8.0.1)

*'''MAIN_MAIL_DEBUG''' ► Write content with header of last mail into file <code>dolibarr_mail.log</code> into directory <code>dolibarr_main_data_root</code>.

*'''MAIN_MAIL_DEBUG_ERR_WITH_DATE''' ► Use a different filename (by adding a prefix of date) for each email sent with error when MAIN_MAIL_DEBUG.

*'''MAIN_MAIL_DEBUG_LOG_WITH_DATE''' ► Use a different filename (by adding a prefix of date) to log each email sent (whatever is result) when MAIN_MAIL_DEBUG.

*'''MAIN_MAIL_FORCE_FROM''' ► (v19+) Can force the value into the From field of the SMTP header. Note that email sender is always saved into the "Reply-To".

*'''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 <code>-f</code>. This option is here to ask Dolibarr to call the function mail of PHP by adding value for the option <code>-f</code>. 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 setup or version of sendmail that ask the -f option to be mandatory or for sendmail setup that does not use by default the From of the header email to define the sender (with this option, the from can be forced on command line to avoid to have the from lost by sendmail).

*'''MAIN_MAIL_SENDMAIL_FORCE_BA''' ► On Linux 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 asks PHP to provide this parameter when sending a mail. Note that another solution is to edit the mail.force_extra_parameters=-ba into <code>php.ini</code> 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 to 1 if your recipient experience problems when opening email for example users using webmail of <code>orange.fr</code> or <code>hotmail.com</code>. Note that some users have reported that when using Exim (Exim 4), you must set this parameter to 0. Default value is 1 but may be changed to 0 in future.

*'''MAIN_MAIL_DO_NOT_USE_SIGN''' ► Do not add user signature at end of suggested pre-defined email

*'''MAIN_MAIL_FORCE_NOT_SENDING_TO''' ► If en email is defined into this variable, emails will never be sent to this email.

*'''MAIL_FORCE_DELIVERY_RECEIPT_INVOICE''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Invoice'' module.

*'''MAIL_FORCE_DELIVERY_RECEIPT_ORDER''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Order'' module.

*'''MAIL_FORCE_DELIVERY_RECEIPT_PROPAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Proposal'' module.
*'''MAIL_FORCE_DELIVERY_RECEIPT_SUPPLIER_PROPOSAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Supplier Proposal'' module.

*'''MAIN_EMAIL_SUPPORT_ACK ►''' Restore email acknowledgment checkbox on sending emails. This feature is commonly abandoned by mailers. Active from Dolibarr V17 - see [https://github.com/Dolibarr/dolibarr/blob/33744f74da1a5c20f8aa9950018ab4e549e00205/ChangeLog#L53 changelog]
*'''MAIN_EMAIL_USECCC''' ► 1 = Shows field BCC into email forms, If value is an email = Shows the BCC pre filled with the email value.

*'''MAIN_MAIL_AUTOCOPY_PROPOSAL_TO''', '''MAIN_MAIL_AUTOCOPY_ORDER_TO''', '''MAIN_MAIL_AUTOCOPY_INVOICE_TO''', '''MAIN_MAIL_AUTOCOPY_SHIPMENT_TO''', '''MAIN_MAIL_AUTOCOPY_..._TO''' ► Email to use as a BCC recipient 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 third party 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 third party or object, the email exchange is related to.

*'''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► Restrict sending of 1 email message to <code>x</code> recipients for same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include 1000 recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available.

*'''MAIN_MAIL_FORCE_CONTENT_TYPE_TO_HTML''' ► Force to send all email (event with text only content) as HTML formatted email.

*'''MAIN_MAIL_USE_MULTI_PART''' ► Forge email content using an alternate text part ► (for 5.0.2+). By default with 6.0+
*'''MAIN_INFO_SOCIETE_MAIL_ALIASES''' ► add address aliases for the from field on mail. Set his value with "Firstname Name <firstname.lastname@mydomain.tld, Otherfirstname OtherlastName <othermail@mydomain.tld>,..." ► (v5.0.0+)

*'''MAIN_MAIL_ADD_INLINE_IMAGES_IF_IN_MEDIAS''' ► If images were stored into the medias directory from CKEditor, then images into emails are replaced with "inline content". This may increase seriously risk of being detected as SPAM.

*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. You can also set the URLs where to get the IP addresses, for exemple: "https://ipv4.urltoshowip.com/_service_showmyip.php,https://ipv6.urltoshowup.com/_service_showmyip.php. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option '''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD'''.

*'''MAIN_IMAP_USE_PHPIMAP''' ► Use embedded PHP-imap library (not using the native php imap) instead of native php imap extension ► (v17.0+, available as official option in setup of emailcollector by default from v19)

*'''MAIN_MAIL_ENABLED_USER_DEST_SELECT''' ► Show also internal users into list of recipients of email in email sending form ► (v8.0+)

*'''MAIL_PREFIX_FOR_EMAIL_ID''' ► Prefix for the mails ID. Default value is <code>$_SERVER["SERVER_NAME"]</code> ► (>= 8.0.1)
*'''MAIL_MASS_ACTION_SEARCH_MOST_RECENT_FILE_IF_NOT_FOUND''' ► When sending an email from a mass action. If the path saved in DB does not point to an existing file, then search for the most recent file and use it as an attahcment.► (>= 24.0.0)

[[#Top|(back to top)]]

=Emailing Module=

*'''MAILING_PREFIX_FOR_EMAIL_ID''' ► Set the value that will be used to compose the "Email ID" into email headers. If you set this value to '<code>SERVER_NAME</code>', the virtual host of web server will be used. By default, this is not defined, so a hash key, unique to each instance, is used.

*'''MAILING_NO_USING_PHPMAIL''' ► If set, the module emailing can't be used with mail setup of "phpmail". Using a thirdparty SMTP server is required. You can complete warning message by adding an email to contact for setup help with constant <code>'''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS'''</code>.

*'''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS''' ► Contains the email of contact to show into the message visible to a user when he try to use emailing module without SMTP server and if option '''MAILING_NO_USING_PHPMAIL''' is set to on.

*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is on "phpmail". Note: The application always try to translate the message considering the message is a translation key, before showing the translation or message if translation was not found.

*'''MAILING_LIMIT_WARNING_NOPHPMAIL''' ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is something else than "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.
*'''EMAILING_USE_ADVANCED_SELECTOR''' ► Enable the advanced selector for recipients.

*'''MAILING_LIMIT_SENDBYWEB''' ► Restrict number of emails you can send in same sending session with emailing module from GUI. The value "<code>dolibarr_mailing_limit_sendbyweb</code>" if defined into config file is used in priority for this limit. A negative value means, sending by web is forbidden.

*'''MAILING_LIMIT_SENDBYCLI''' ► Restrict number of emails you can send in same sending session with emailing module from CLI script. The value "<code>dolibarr_mailing_limit_sendbycli</code>" if defined into config file is used in priority for this limit.

[[#Top|(back to top)]]

 

=Expense Report=

*'''EXPENSEREPORT_ALLOW_OVERLAPPING_PERIODS''' ► Can enter several expense reports on same or overlapping date periods. ► (v7.0+)

*'''EXPENSEREPORT_OVERRIDE_VAT''' ► Setting this constant to 1 will allow expense reports to show VAT even if the global VAT setting is off ► (v10.0)

*'''EXPENSEREPORT_USE_OLD_NUMBERING_RULE''' ► The module Expense Report use numbering rules that you can setup (like other modules do). If you need to keep the hard-coded numbering rule of expenses report used in v6.0 set this constant to 1 ► (>=v7.0+)

*'''MAIN_USE_EXPENSE_IK''' ► This feature allows you to set index kilometres against a mileage index for different types of vehicles. ► (v7.0+)

*'''MAIN_USE_EXPENSE_RULE''' ► This feature allows you to set a variety of rules per user/group/all so they can only create reports within their limits. ► (v7.0+)

[[#Top|(back to top)]]

 

=Export Module=

*'''EXPORT_CSV_SEPARATOR_TO_USE''' ► String value to use as default separator to delimit fields of exported files (by default Dolibarr uses "<code>,</code>"). Example: EXPORT_CSV_SEPARATOR_TO_USE=<code>;</code>

*'''EXPORT_CSV_FORCE_CHARSET''' ► Choose the charset used in the output file built by the CSV exporter. By default it is ISO-8859-1. Example: EXPORT_CSV_FORCE_CHARSET= <code>utf-8</code>

*'''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 (<code>"</code>).
*'''EXPORTS_SHARE_MODELS''' ► Share export models between users.

[[#Top|(back to top)]]

=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 added in front of payment cell, into the page to make online subscription.

[[#Top|(back to top)]]

 
=Holiday Module=

*'''HOLIDAY_HIDE_BALANCE''' ► Hide the user's vacation balance on the vacation request page

[https://wiki.dolibarr.org/Setup_Other#Top (back to top)]
=Interventions Module=

*'''FICHINTER_CLASSIFY_BILLED'''► Allow to classify an intervention card as "Billed". This add also trigger <code>FICHINTER_CLASSIFY_BILLED</code> into list of possible automatic event into agenda.

*'''FICHINTER_DISABLE_DETAILS'''► Disable entry of detail lines on intervention. Can validate with no line. Only one line will be shown per intervention on list.
**If set to <code>2</code> details are disabled only on intervention list ► (v21.0+)

[[#Top|(back to top)]]

=Invoice Module=

*'''MAIN_DEPOSIT_MULTI_TVA''' ► In deposits invoice, creates one line per VAT rate from the origin document ► (6.0)
*'''PDF_INVOICE_SHOW_PRICE_INCL_TAX''' ► In customer's invoice, add a column with the total including all taxes ►

*'''INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED''' ► If a credit note was partially refunded (a refund was sent to the customer), with common situation, we wait to have the remain refunded too. With this option, it is possible to convert the remain of invoice into a discount to reuse it into another invoice.

*'''SUPPLIER_INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED''' ► See INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED, but for supplier credit notes.

*'''INVOICE_CAN_BE_EDITED_EVEN_IF_PAYMENT_DONE''' ► Allow to edit invoices even if payment was started. Note: If the module "BlockedLog" is active (required in some countries for legal reasons), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change will be recorded into the archive log.

*'''INVOICE_CAN_ALWAYS_BE_REMOVED''' ► Allow to always delete invoices (even if invoice is not last one). Note: If the module "BlockedLog" is active (required by some countries for legal reason), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*'''INVOICE_CAN_NEVER_BE_EDITED''' ► Never allow to edit invoices (except draft invoices with ref like (PROV%)). See also INVOICE_CAN_NEVER_BE_REMOVED.

*'''INVOICE_CAN_NEVER_BE_REMOVED''' ► Never allow to delete invoices (except draft invoices with ref like (PROV%)). See also INVOICE_CAN_NEVER_BE_EDITED

*'''INVOICE_POSITIVE_CREDIT_NOTE''' ► All amounts on PDF credit notes are positive.

*'''FACTURE_DEPOSITS_ARE_JUST_PAYMENTS''' ► An old way to create initial payment. This treats deposit invoices as a special case and not as legal deposit invoice. 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. WARNING: In a lot of european countries, using this option is not allowed.

*'''FACTURE_SENDBYEMAIL_FOR_ALL_STATUS''' ► Can send invoice by email to customer even if invoice has status "draft".

*'''INVOICE_CREDIT_NOTE_STANDALONE''' ► Start implementation to allow a credit note even without invoice (dangerous) ► (v3.9)

*'''INVOICE_USE_SITUATION''' ► 1=Enable the "situation invoice" feature. Warning, this feature is bugged and may not be compatible with the final version of the feature once the bug will be solved. Also, using the double-entry accountancy module is not possible when this option is on (due to the same design problem). 2=Enable the "situation invoice" feature with a rewrite. This mode should be better to become a future stable feature.

*'''INVOICE_USE_SITUATION_CREDIT_NOTE''' ► Enable the "situation credit note" feature (need <code>INVOICE_USE_SITUATION</code>) ► (v8.0)
*'''INVOICE_USE_RETAINED_WARRANTY''' ► Enable the retained warranty on invoice ► (v14.0)

*'''INVOICE_DISABLE_DEPOSIT''' ► Disable deposit invoices

*'''INVOICE_DISABLE_REPLACEMENT''' ► Disable replacement invoices

*'''INVOICE_DISABLE_CREDIT_NOTE''' ► Disable credit notes

*<bdi>'''INVOICE_ADD_EXTRAFIELD_IN_NOTE''' ► Add extrafields in note for canelle template ► (v17.0+)</bdi>

*'''INVOICE_DEFAULT_NOTE_PUBLIC''' <bdi>► Default text in public note</bdi>

Note: To decode a QR image of a ZATCA code: https://www.onlinebarcodereader.com/. You can also use the mobile application https://play.google.com/store/apps/details?id=com.posbankbh.einvoiceqrreader&gl=FR

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT''' ► See PDF option

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN''' ► See PDF options

*'''WORKFLOW_BILL_ON_SHIPMENT''' ► Change label of button with suitable label when you need to create invoice on shipments

*'''INVOICE_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. Use the tag __DIRECTDOWNLOAD_URL_INVOICE__ in email template to insert it. ► (v7.0+)

*'''INVOICE_POINTOFTAX_DATE''' ► Add Point of Tax Date on invoices for country-specific legality reasons ► (v4.0+)
*'''FACTURE_ENABLE_NEGATIVE''' ► Can validate an invoice when amount is negative

*'''FACTURE_ENABLE_NEGATIVE_LINES''' ► Allows to add negative lines to an invoice ► (v8.0.2+)
*'''SUPPLIER_INVOICE_ENABLE_NEGATIVE''' ► Can validate an supplier invoice when amount is negative ► (V21 ?)
*'''SUPPLIER_INVOICE_ENABLE_NEGATIVE_LINES''' ► Allows to add negative lines to an supplier invoice ► (V21 ?)

*'''INVOICE_USE_DEFAULT_DOCUMENT''' ► Allow user to select a default invoice documents models according to invoice type. On invoice create page, the model is dynamically changed on invoice type selection. ► (v9.0+)

*'''FACTURE_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object (Proposal,...) when creating the bill.
*'''FACTUREFOURN_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object when creating the supplier bill ► (V13.0)
*'''MAIN_SHOW_FACNUMBER_IN_DISCOUNT_LIST''' ► Display the reference of credit notes in discount list when creating the bill.
*'''INVOICE_ALLOW_FREE_REF''' ► Capability to change reference of an invoice. This will be possible as long as the invoice has the status “Draft” and only if your country is not in Europe(V11)

*'''INVOICE_DISALLOW_REOPEN'''

*'''INVOICE_MAX_FUTURE_DELAY''' ► Numbers of seconds allowed for billing in the future ► (V14.0)
*'''INVOICE_AUTO_NEXT_MONTH_ON_LINES''' ► Increase start date and end date by one month, if an invoice line is a clone of a time based service AND if this services started on the first day of month and ended on the last day of month ► (V13.0.1)
*'''INVOICE_KEEP_DISCOUNT_LINES_AS_IN_ORIGIN''' ► Does not change a line with a negative price into an absolute discount when creating an invoice ► (V16 ?)
*'''INVOICEREC_SET_AUTOFILL_DATE_START''' and '''INVOICEREC_SET_AUTOFILL_DATE_END ►''' Set start and end date to yes for lines of template invoice when created from a draft invoice ► (V16)
*'''INVOICE_REC_DATE_TO_YES''' '''►''' Set start and end date to yes by default in add line form for template invoice ► (V16)
*'''INVOICE_SUBTYPE_ENABLED''' ► Extends Dolibarr standard invoice with more invoice types used in some countries. A combo box in the new invoice creation card allows the selection of "subtypes" with values from dictionary "Invoice Subtypes" ► (v19.0+)
*'''LIST_OF_QUALIFIED_INVOICES_LIMIT_DEFINED''' '''►''' Perf options to limit list of invoices for "credit note" source (on form "create a credit note"), usable for big quantities of invoices for one customer like you can have with TakePos ► (V22+)

[[#Top|(back to top)]]

=Leave=

*'''MAIN_NON_WORKING_DAYS_INCLUDE_SATURDAY''' ► Set this value to 0 if you want to have the Saturday as a working day
*'''MAIN_NON_WORKING_DAYS_INCLUDE_SUNDAY''' ► Set this value to 0 if you want to have the Sunday as a working day

=Look or Theme=

*'''MAIN_FAVICON_URL''' ► favicon url

*'''MAIN_EASTER_EGG_COMMITSTRIP''' ► Show a comic image from the CommitStrip website. Images are refreshed daily. ► (v6.0+)

*'''MAIN_INCLUDE_GLOBAL_STATS_IN_OPENED_DASHBOARD''' ► This conf will auto remove global stats box item if there are already in the new dashboard of opened elements and keep displayed stats on the opened item box (not only on mouse over) ► (v11.0+)

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Actually only for eldy theme, this conf move search input to top menu and use new design too ► (v11.0+)

*'''THEME_AGRESSIVENESS_RATIO''' ► This conf can be used to increase/decrease aggressiveness of colors. Value 0 is medium, value is between -100 (light grey colors) to +100 (very flashy colors) ► (v11.0+)

*'''THEME_SHOW_BORDER_ON_INPUT'''
*'''MAIN_DISABLE_GLOBAL_WORKBOARD''' ► Hide the work board of the main page ► (v13.0+)
*'''MAIN_DISABLE_GLOBAL_BOXSTATS''' ► Hide the Statistic Box of the main page
*'''ALLOW_THEME_JS ►''' Allow JS file in theme folder (same name as theme folder)

 

=Manifest (Progressive Web App)=

*'''MAIN_MANIFEST_APPLI_THEME_COLOR ►''' Theme color for manifest
*'''MAIN_MANIFEST_APPLI_BG_COLOR ►''' Background color for manifest
*'''MAIN_MANIFEST_APPLI_LOGO_URL ►''' Logo for manifest
*'''MAIN_MANIFEST_APPLI_LOGO_URL_SIZE ►''' Logo url size for app (150, 192, 512px) missing 3 configurations

[[#Top|(back to top)]]

=Order Module=

*'''MAIN_MASSACTION_CREATEBILLS_REDIRECT_IF_ONE''' ► If set 1, redirects to the one bill created from massaction create bills from order list ► (v20.0)

*'''MAIN_MASSACTION_CREATEBILLS_REDIRECT_IF_MANY''' ► If set to 1, redirects to the invoice list after plural invoices where generated from tho massaction create bills from order list ► (v20.0)

*'''MAIN_ORDERLIST_CREATEBILLS_ONEBYTHIRD''' ► Allow defining value for option "one by thirdparty" in massaction create bills from orders list page (no by default, yes if set to 'yes' or 1) ► (v20.0)

*'''MAIN_USE_PROPAL_REFCLIENT_FOR_ORDER''' => Copy customer reference from proposal to order. ► (v7.0+)

*'''ORDER_REQUIRE_SOURCE''' => Make the input field "Source of order" mandatory.

*'''ORDER_VALID_AFTER_CLOSE_PROPAL''' => When an order is created on a proposal close, the order is directly defined with status "Validated".

*'''ORDER_ALLOW_EXTERNAL_DOWNLOAD''' => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*'''ORDER_ENABLE_NEGATIVE''' => Can validate an order when amount is negative

*'''THIRDPARTY_PROPAGATE_EXTRAFIELDS_TO_ORDER''' => Copy also extrafields from thirdparty to order (if name match). ► (v11.0+)
*'''ORDER_DEFAULT_NOTE_PUBLIC''' ► Default text in public note
*'''MAIN_REMOVE_DROPDOWN_CREATE_BUTTONS_ON_ORDER''' => Remove the create dropdown button on order card (introduce on v19) to come back with old buttons. '''►''' (v20.0+)

[[#Top|(back to top)]]

 

=PDF Options=

*'''MAIN_ADD_PDF_BACKGROUND''' ► Define this constant with short name of a PDF file (example "<code>mypdf.pdf</code>") that must be saved into directory "<code>documents/mycompany</code>". 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_DISABLE_FORCE_SAVEAS''' ► If your browser always asks to save downloaded files on disk (like PDF), try this this option. File may be displayed directly in your browser. Values : 0= Default (file is auto downloaded), 1= For to output the file into the browser tab, 2= For to output the file into a browser tab open with target_blank

*'''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 servers with low CPU.

*'''MAIN_DISABLE_PDF_COMPRESSION''' ► Disable PDF compression.

*'''MAIN_DOCUMENTS_WITH_PICTURE_WIDTH''' ► Can change size of picture when hidden option <code>MAIN_GENERATE_PROPOSALS_WITH_PICTURE</code> is used. By default value is <code>20</code>.

*'''MAIN_GENERATE_DOCUMENTS_SHOW_FOOT_DETAILS''' ► Adding the company address at the bottom of the page. Disabled by default

*'''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer proposals.
*'''MAIN_GENERATE_ORDERS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer orders.

*'''MAIN_GENERATE_INVOICES_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer invoices.

*'''MAIN_GENERATE_SUPPLIER_PROPOSAL_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier proposals ► (v5.0.3+)
*'''MAIN_GENERATE_SUPPLIER_ORDER_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier orders

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT''' ► Disable VAT on generated documents. like for an association. (Works with crabe template)

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN''' ► Hide column with VAT information but only column not total.

*'''MAIN_INVERT_SENDER_RECIPIENT''' ► Invert sender and recipient in some PDF. Note: This option is set automatically if country if Germany.

*'''MAIN_ODT_AS_PDF''' ► Activate ODT to PDF conversion. Value can be "libreoffice" or "unoconv". Do not use value '''<nowiki/>'jodconverter'<nowiki/>''' any more, as it is declared deprecated and partly not functional, use value '''<nowiki/>'libreoffice'''' instead, it requires only '''soffice''' (OpenOffice or LibreOffice) installed on server (use '''apt install soffice libreoffice-common libreoffice-writer''').

If you got this error: javaldx failed! Warning: failed to read path from javaldx with no return to prompt when running soffice --headless -env:UserInstallation=file:"/tmp" --convert-to pdf --outdir xxx ./yyy.odt, check that directory defined into env:UserInstallation parameters exists and is writeable.

You may also have a look at this page if your server is on Windows: [[Générer automatiquement des documents PDF à partir de fichier ODT avec Doliwamp]]

*'''MAIN_ODT_AS_PDF_DEL_SOURCE''' ► For ODT generation. If set, then initial behaviour is conserved but ODT file is removed when option to convert it as PDF (see previous) is on. Disabled by default

*'''MAIN_PDF_FORCE_FONT''' ► To ignore font defined into language file and force usage of a particular font. For example "<code>DejaVuSans</code>".

*'''MAIN_PDF_FORCE_FONT_SIZE''' ► To force size of font (by default 10). For example "<code>12</code>" ► (v11.0)

*'''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: <code>220,220,200</code>

*'''MAIN_PDF_USE_LARGE_LOGO''' ► Use the original logo with its higher resolution into the PDF instead of the small thumb. This may lead to very very large PDF !

*'''MAIN_USE_BACKGROUND_ON_PDF''' ► Define this constant with short name of an image (example "<code>myimage.jpg</code>") that must be saved into directory "<code>documents/mycompany/logos</code>". This will add this background image into your generated PDF files.

*'''MAIN_USE_COMPANY_NAME_OF_CONTACT''' ► Use contact name and information rather than company

*'''MAIN_PDF_ADDALSOTARGETDETAILS''' ► If 1, add details of recipient on generated PDFs (email, fax, url and phone). Can be useful in cases where a printed order/invoice etc is given to a delivery driver/courier etc.

*'''MAIN_TVAINTRA_IN_SOURCE_ADDRESS''' ► Show VAT N° in source address of PDF to comply with legalities in certain countries. Note that VAT number should be already visible in footer of page ► (v8.0.1+)

*'''MAIN_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► Add optional esign field in pdf propal ► (v8.0+)

*'''MAIN_PROFID1_IN_SOURCE_ADDRESS''' ► Show Professional ID 1 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID2_IN_SOURCE_ADDRESS''' ► Show Professional ID 2 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID3_IN_SOURCE_ADDRESS''' ► Show Professional ID 3 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID4_IN_SOURCE_ADDRESS''' ► Show Professional ID 4 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID5_IN_SOURCE_ADDRESS''' ► Show Professional ID 5 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID6_IN_SOURCE_ADDRESS''' ► Show Professional ID 6 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

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

*'''PDF_BOLD_PRODUCT_REF_AND_PERIOD''' ► Add more visibility (bold) on product ref and period of service in desc. ► (v12.0)

*'''PDF_HIDE_PRODUCT_REF_IN_SUPPLIER_LINES''' ► Modify the use/position of Supplier Ref/Internal Ref with the item Label (name) on PDF documents.

Default (constant not set or Value <code>0</code>): Internal ref followed by supplier ref in brackets."COMPANY-REF-001 (Vendor SKU SUPPLIER-REF-001) - LABEL...".

Value <code>1</code>: Supplier ref only eg."SUPPLIER-REF-001 - LABEL...".

Value <code>2</code>: Supplier ref followed by internal ref in brackets. eg."SUPPLIER-REF-001 (InternalRef COMPANY-REF-001) - LABEL...".

*'''PDF_INCLUDE_ALIAS_IN_THIRDPARTY_NAME''' ► Include alternative/alias name into name on PDF.

*'''PDF_SECURITY_ENCRYPTION''' ► Encrypt PDF produced by dolibarr. See additional parameters :PDF_SECURITY_ENCRYPTION_RIGHTS (block 'modify' or 'copy') - '''PDF_SECURITY_ENCRYPTION_USERPASS''' - '''PDF_SECURITY_ENCRYPTION_OWNERPASS''' (random if not specified) - '''PDF_SECURITY_ENCRYPTION_STRENGTH''' (0 = RC4 40 bit; 1 = RC4 128 bit; 2 = AES 128 bit; 3 = AES 256 bit) - '''PDF_SECURITY_ENCRYPTION_PUBKEYS''' Array of recipients containing public-key certificates ('c') and permissions ('p') - For example: array(array('c' => 'file://../examples/data/cert/tcpdf.crt', 'p' => array('print'))). WARNING: if an 'encrypted PDF' provides a protection against manual change done by mistake, it does NOT provide any protection against modification of your PDF in a security point of view: A protected PDF can still be modified by any advanced PDF editors. Don't forget this: If a software can read the PDF, this software can also rebuild it differently !

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

*'''PDF_USE_ALSO_LANGUAGE_CODE''' ► The value of this constant must be a language code ('fr_FR', 'en_US', 'sa_SA', ...). If set, the PDF document will contains both language (default and the one defined by the constant).
*'''DOC_SHOW_FIRST_SALES_REP''' ► Show the sales representant on header (at least on propal azur and rubis template)
*'''MAIN_PDF_DASH_BETWEEN_LINES'''
*
*'''SHOW_SUBPRODUCT_REF_IN_PDF'''
*'''PDF_HIDE_PRODUCT_LABEL_IN_SUPPLIER_LINES''' ► hide product label in supplier order lines (V15+)
*'''SHIPPING_PDF_DISPLAY_AMOUNT_HT''' ► Show HT unit price and HT total price for lines of PDF shipment

*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_FACTURE''' ► To Hide product description in Customer Invoice
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_COMMANDE''' ► To Hide product description in Sales Order
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_ORDER_SUPPLIER''' ► To Hide product description in Purchase Order
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_INVOICE_SUPPLIER''' ► To Hide product description in Vendor Invoice

*'''PDF_PROPAL_SHOW_PRICE_INCL_TAX''' ► Display price with tax on Proposal(cyan template) (V17+)
*'''PDF_ORDER_SHOW_PRICE_INCL_TAX''' ► Display price with tax on Order(eratosthene template) (V17+)
*'''PDF_INVOICE_SHOW_PRICE_INCL_TAX''' ► Display price with tax on Invoice(sponge template) (V17+)

*'''PDF_USE_GETALIASNBPAGE_FOR_TOTAL''' ► Display the page number alias
*'''MAIN_PDF_NO_SENDER_FRAME''' ► Do not display the "sender" mention
*'''MAIN_PDF_HIDE_SENDER_NAME''' ► Do not display the sender name
*'''MAIN_PDF_NO_RECIPENT_FRAME''' ► Do not display BillTo

*'''MULTICURRENCY_SHOW_ALSO_MAIN_CURRENCY_ON_PDF''' ► Show the amount in the 2 currencies on PDF when using the MultiCurrency module
*'''MAIN_PDF_DONOTREPEAT_HEAD ►''' Do not repeat the header of document

[[#Top|(back to top)]]

=Point of Sale (POS)=

*'''CASHDESK_SHOW_KEYPAD''' ► Show a mouse key pad into the 'Simple Point of Sale' module.

*'''POS_ADDON''' ► Set this value to an existing numbering module rule (for example '<code>mod_facture_terre</code>', '<code>mod_facture_mars</code>', ...) to force the numbering module to use for invoice ref definition when invoice is created by the POS. For example setting value <code>POS_ADDON</code> to '<code>mod_facture_terre</code>' will use the numbering module '<code>terre</code>' for invoice generated from POS, whatever is the numbering rule defined into invoice module setup (you can also use POS_NUMBERING_TERRE_FORCE_PREFIX and POS_NUMBERING_MARS_FORCE_PREFIX variable to change the prefix used).

*'''TAKEPOS_ENABLE_SUMUP''' ► Enable the compatibility of TakePOS with the card reader terminal [https://SumUp.fr SumUp]
*'''TAKEPOS_CAN_FORCE_BANK_ACCOUNT_DURING_PAYMENT''' ► Possibility to force the bank account during the payment in TakePOS ► (v13.0)
*'''TAKEPOS_CONTROL_CASH_OPENING''' ► Control the cash opening
*'''TAKEPOS_NUMPAD_FORCE_PAYMENT_ICONS_LABELS'''

[[#Top|(back to top)]]

=Products Module=

*'''CATEGORY_GRAPHSTATS_ON_PRODUCTS''' ► Show graph of products with categories and totals in Products Area screen

*'''MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE''' ► Avoid customs 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.

*'''MAIN_DIRECT_STATUS_UPDATE''' ► Allows you to change the status of the product (''for sale/not for sale for purchase/not for purchase'') directly on the product page via a ''on/off'' switch button. This can be convenient for those who need to quickly disable certain statuses of products without having to go through the editing product page individually. Also can be very useful if used as a filter on the product and product search list. This option doesn't generate a MODIFY trigger, so be careful with external modules. ► (v4.0+)

*'''MAIN_SEARCH_PRODUCT_BY_FOURN_REF''' ► Allow to search a product by supplier ref in document's add line form. ► (>= 8.0)

*'''MAIN_DISABLE_FREE_LINES''' ► Disallow using free lines to add line in documents ► (>= 8.0)

*'''MAIN_SHOW_PRODUCT_ACTIVITY_TRIM''' ► Show Product and Services turnover before for all four quarters tax over recent years recent years on the product area ► (v5.0+)

*'''PRODUIT_DESC_IN_LIST''' ► Show long description of product/service into lists.

*'''PRODUCT_DISABLE_PROPAGATE_CUSTOMER_PRICES_ON_CHILD_COMPANIES''' ► Disable propagation of prices per customer from a customer to its child company.

*'''PRODUCT_DISABLE_PUBLIC_URL''' ► Disable public url in product card ► (v14.0+)
*'''PRODUCT_DISABLE_STOCK_LEVELS''' ► Disable properties of stock limits and desired optimal value on product ► (v14.0+)
*'''PRODUCT_DISABLE_NATURE''' ► Disable nature in product card ► (v14.0+)
*'''PRODUCT_DISABLE_WEIGHT''' ► Disable weight in product card ► (v14.0+)
*'''PRODUCT_DISABLE_PRICES''' ► Disable prices in product card ► (v14.0+)
*'''PRODUCT_DISABLE_ACCOUNTING''' ► Disable accounting in product card ► (v14.0+)
*'''PRODUCT_DISABLE_SIZE''' ► Disable size in product card.

*'''PRODUCT_DISABLE_LENGTH''' ► Disable length in product card ► (v4.0+)

*'''PRODUCT_DISABLE_SURFACE''' ► Disable surface in product card. ► (v4.0+)

*'''PRODUCT_DISABLE_VOLUME''' ► Disable volume in product card.

*'''PRODUCT_DISABLE_CUSTOM_INFO''' ► Disable custom info (custom code and country origin) in product/service card.

*'''PRODUIT_MULTIPRICES_USE_VAT_PER_LEVEL''' ► When option to use price per level/segment is on, this allows to also set a dedicated vat for each price level.

*'''PRODUIT_CUSTOMER_PRICES_BY_QTY''' ► If price per quantity ► ''Experimental''
*'''PRODUIT_CUSTOMER_PRICES_BY_QTY_MULTIPRICES''' ► If price per quantity and customer ► ''Experimental''

*'''PRODUCT_LOT_ENABLE_QUALITY_CONTROL''' ► Enable feature (Display fields for life time and quality control duration) for quality control on product and lot

*'''PRODUCT_MAX_LENGTH_COMBO''' ► Limit the length of the label displayed when adding lines in proposals/invoices/orders

*'''PRODUCT_MAX_VISIBLE_PHOTO''' ► Show a maximum number of product photos (as thumbnails) on the product main card. Example, setting this constant to '<code>5</code>' will show the first five product photos found on the product card.

*'''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''' ► Add other units on products (Use same dictionary as default unit feature) and propagate this unit on line of documents.
*'''MAIN_EDIT_LINE_ALLOW_ALL_UNIT_TYPE ►''' Allow the selection of other unit types when editing the document line

*'''RESOURCE_ON_PRODUCTS''' ► Allow to affect resources on products/services ► (v10.0+)
*'''RESOURCE_ON_SERVICES''' ► Allow to affect resources on products/services ► (v10.0+)
*'''PRODUCT_SHOW_ORIGIN_IN_COMBO''' ► Show origin of products when adding lines in proposals/invoices/orders ► (v12.0+)
*'''PRODUIT_ATTRIBUTES_HIDECHILD''' ► Add option hide child if variantes

*'''PRODUCT_ADD_FORM_ADD_TO''' ► Add a product to a draft proposal/order/invoice, from the product card.
*'''PRODUCT_DISABLE_SELLBY''' ► Hide the Sell by date ► (v13.0+)
*'''PRODUCT_DISABLE_EATBY''' ► Hide the Eat by date ► (v13.0+)

*'''PRODUCT_DENY_CHANGE_PRODUCT_TYPE''' ► Forbid to change the product type

*'''PRODUCT_SORT_BY_CATEGORY''' ► Sort the product by categories instead of by ID
*'''PRODUCT_ADD_NET_MEASURE''' ► Support Net Measure in product's card.php (For real weight, volume or piece; needed for some business ie fruits, vegetables....). Note brut value is already available natively, use this option only if you need 2 weights, 2 volumes, ...for each product) ► (v11.0.1+)
*'''PRODUCT_PRICE_BASE_TYPE''' ► value 'TTC' / 'HT' specify the default value of the price (with or without taxes) ► (v16.0.0+)

*'''PRODUCT_LOAD_EXTRAFIELD_INTO_OBJECTLINES''' ► Load product extrafiled on object lines

*'''PRODUCT_USE_SUB_COST_PRICES_IF_COST_PRICE_EMPTY''' : Calculate the parent product production price by child prices.
*'''PRODUCT_SEARCH_AUTO_SELECT_IF_ONLY_ONE''' : Set to 0 to disable or 1 to enable (by default) the auto select product behavior in combobox when there is only one result.(v21.0+)

[[#Top|(back to top)]]

 

=Projects Module=

*'''PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY''' ► Option related to the combo list Project on elements. It is a list of thirdparty IDs. If set, you can link an object to a project owned by one of this thirdparty in the list.

*'''PROJECT_ALLOW_COMMENT_ON_PROJECT''' ► Add comment feature on a project

*'''PROJECT_ALLOW_COMMENT_ON_TASK''' ► Add comment feature on project task
*'''PROJECT_ALWAYS_DISCARD_CLOSED_PROJECTS_IN_SELECT''' ► Discards closed projects in every select field. A closed project can't be associated to an object ► (v20.0+)

*'''PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS''' ► Option related to the combo list Project on elements. Can link a supplier element (vendor proposal, purchase order, vendor invoice, reception, ...) to any project even if object has a different supplier than the one of the project to link to. See also PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY that is different because it allows to define some given thirdparty ID to allow.

*'''PROJECT_CAN_ALWAYS_LINK_TO_ALL_CUSTOMERS''' ► Option related to the combo list Project on elements. Can link a custom element (proposal, sale order, vendor invoice, shipment, ...) to any project even if object has a different customer than the one of the project to link to.

*'''PROJECT_CREATE_ON_OVERVIEW_DISABLED''' ► Hide the "create ..." button on the overview pagec

*'''PROJECT_DISABLE_UNLINK_FROM_OVERVIEW''' ► Enable removing the button from a link in the project overview. ► (>= v8.0.1)

*'''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''' ► Hide the "link to" form on the overview page ► (v4.0)

*'''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_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_OPEN_ALWAYS_ON_TAB''' ► Set to value 'task', or 'preview' to always open the project on the given tab instead of main tab.

*'''PROJECT_ELEMENTS_FOR_MINUS_MARGIN'''

*'''TIMESPENT_ALWAYS_UPDATE_THM''' ► when it's on always check current time of user to update it in task time line ► (v17.0)

*'''PROJECT_CREATE_NO_DRAFT''' ► when you create project status will be validate ► (v19.0)

*'''PROJECT_ENABLE_SUB_PROJECT''' ► Add support for parent projects ► (v19.0)

[[#Top|(back to top)]]

=Proposals Module=

*'''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Add a picture of the product (the first one found if there are several) into the generated PDF of proposals. Note that using this will reduce the available width for the product description.

*'''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_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► add optional esign field in pdf propal ► (v8.0+)

*'''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.

*'''PROPAL_DISABLE_SIGNATURE''' ► Do no show the box for signature.
*'''PROPAL_SIGNATURE_ON_SPECIFIC_PAGE ►''' Will show the signature on which page you wanted . Set to 1 will show on first page , set to -1 will show on last second page . ( If '''PROPAL_SIGNATURE_ON_ALL_PAGES''' is enabled, the '''PROPAL_SIGNATURE_ON_SPECIFIC_PAGE''' setting will be ignored.)
*'''PROPAL_SIGNATURE_ON_ALL_PAGES ►''' Will show the signature on every pages .

*'''PRODUIT_PDF_MERGE_PROPAL''' ► When generating the proposal PDF, all PDFs linked to products linked to proposal are also included into final PDF

*'''PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*'''PROPOSAL_AUTO_ADD_AUTHOR_AS_CONTACT''' ► Add Proposal Author as user contact follow proposal

*'''PROPOSAL_PDF_HIDE_PAYMENTTERM''' ► Do not show the payment term on proposal ► (v11.0+)

*'''PROPOSAL_PDF_HIDE_PAYMENTMODE''' ► Do not show the payment mode on proposal ► (v11.0+)

*'''WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES''' ► Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.
*'''PROPAL_REOPEN_UNSIGNED_ONLY''' ► Do not allow reopening of signed (or billed) proposals. (V15)
*'''PROPOSAL_ARE_NOT_BILLABLE''' ► Disable billing button on proposals (V15)
*'''PROPAL_DEFAULT_NOTE_PUBLIC''' ► Default text in public note
*'''PROPAL_ENABLE_NEGATIVE''' ► Can validate a proposal when amount is negative

[[#Top|(back to top)]]

=Receptions=

*'''RECEPTION_STANDALONE''' ► Create a simple Reception not connected to supplier order, warehouse, stock e.t.c. (>=23.0)

[[#Top|(back to top)]]

=Services Module=

*'''SERVICE_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country. For french speaking people, see also the page [[Loi_européenne_TVA_Vente_à_Distance_VAD_et_e-commerce_BtoC]].

*'''MAIN_FILL_SERVICE_DATES_FROM_LAST_SERVICE_LINE''' ► (v13.0) On add line form add a button to fill service dates from the last service line

[[#Top|(back to top)]]

=Shipments=

*'''STOCK_WAREHOUSE_NOT_REQUIRED_FOR_SHIPMENTS''' ► If set, you can add a shipment line, with no stock source defined. ► (>= 8.0.1)

*'''SHIPMENT_GETS_ALL_ORDER_PRODUCTS''' ► Add all order lines in shipment, including the one with 0 in quantity
*'''SHIPPING_PDF_HIDE_ORDERED''' ►Hide column quantity ordered on shipment pdf (>=15.0)
*'''STOCK_SUPPORTS_SERVICES''' ►Allow to manage services into warehouse and allow to ship services
*'''SHIPMENT_SUPPORTS_SERVICES''' ►Allow to ship services without stock (>=19.0)
*'''SHIPPING_DISPLAY_STOCK_ENTRY_DATE''' ►Display date entry stock exped and sort in date order (>=19.0)
*'''SHIPMENT_STANDALONE ►'''Create a simple shipment not connected to sales order, warehouse, stock e.t.c. (>=23.0)

[[#Top|(back to top)]]

=SMS=

*'''MAIN_SMS_DEBUG''' ► Write content of SMS sent into file <code>dolibarr_sms.log</code> into directory <code>dolibarr_main_data_root</code>.

[[#Top|(back to top)]]

=Stocks=

*'''SUPPLIER_ORDER_DISABLE_STOCK_DISPATCH_WHEN_TOTAL_REACHED''' ► Disable stock dispatch when total expected was already received

*'''STOCK_EXCLUDE_VIRTUAL_PRODUCTS''' ► If product is a virtual product, we do not manage stock for it.
*'''STOCK_ALLOW_DELETE_OF_MOVEMENT''' ► Enable massaction option to delete in movements list (be carefull !!).

*'''ENTREPOT_EXTRA_STATUS''' ► Instead of the 2 status (Closed, Open), a Warehouse has 3 status: Closed, Open (for all movements), Open (for internal movement only). Internal movement only means you can't use the warehouse to make shipment or receptions.

*'''SUPPLIER_ORDER_STATUS_FOR_VIRTUAL_STOCK''' ► For the calculation of virtual stocks, by default supplier orders with the status 3 (ordered) and 4 (partially received) are used. You can enter the list of statuses to be taken into account separated by commas for this calculation (example: 0,1,2,3)

*'''STOCK_MOVEMENT_LIST_HIDE_UNIT_PRICE''' ► to hide unit price on some pages (V15+)

*'''DISABLE_QTY_OVERWRITE''' ► Disable quantity overwrites on inventories ► (v19.0)
*'''MAIN_WAREHOUSE_LIST_DISPLAY_MODE''' ► Change warehouse select list display mode ► (v21.0) (see github pull request [https://github.com/Dolibarr/dolibarr/pull/31013 #31013] for more info)
**0 : Default behavior, display parents of warehouse
**1 : Display only current warehouse label only
**2 : Display last parent warehouse label

[[#Top|(back to top)]]

=Stripe=

*'''STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION''' ► 1 is the default mode and will use the native Stripe form for the checkout (with card only), 2 will use the native Stripe form (PaymentElement complete, multi payment modes). Note that STRIPE_USE_NEW_CHECKOUT is an abandonned alternative (so no more NEW, that does not bring real added value)

=Suppliers Module=

*'''FOURN_PRODUCT_AVAILABILITY''' ► On the Suppliers price page of the products, activate the supplier product availability. ''This is duplicate feature with delivery_delay introduced with 3.8.''

*'''RELOAD_PAGE_ON_SUPPLIER_CHANGE''' ► On creation of a supplier order/invoice, reload form with supplier-specific details when supplier is selected from drop-down list.

*'''SUPPLIER_INVOICE_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier invoice to only those with a buying price defined for that supplier. ► (v6.0+)

*'''SUPPLIER_ORDER_AUTOADD_USER_CONTACT''' ► Add user approving supplier order as a contact automatically.

*'''SUPPLIER_ORDER_DEFAULT_PAYMENT_MODE_ID''' ► Set the default payment method for suppliers (<code>rowid</code> in table <code>llx_c_paiement</code>).

*'''SUPPLIER_ORDER_USE_DISPATCH_STATUS''' ► Add a status on each dispatch order line when receiving products from suppliers ► (v4.0+)

*'''SUPPLIER_ORDER_NO_DIRECT_APPROVE''' ► No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

*'''SUPPLIER_ORDER_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier order to only those with a buying price defined for that supplier. ► (v6.0+)

*'''SUPPLIER_ORDER_EDIT_BUYINGPRICE_DURING_RECEIPT''' ► Can modify the buying price used for PMP calculation when making a stock reception on a supplier order. ► (v6.0+)
*'''SUPPLIER_PROPOSAL_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier proposal to only those with a buying price defined for that supplier. ► (v6.0+)
*'''SUPPLIER_ORDER_MORE_THAN_WISHED''' ► The supplier order status is set to "Totally received" even if there are more products received than ordered. ► (v15.0+)

*'''DISPLAY_DISCOUNTED_SUPPLIER_PRICE''' ► Allow to display discounted supplier price when searching product in supplier documents ► (v10.0)

*'''MAIN_CAN_EDIT_SUPPLIER_ON_SUPPLIER_ORDER''' ► Allow to change the supplier on a draft supplier order ► (v10.0)

*'''SUPPLIER_PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD'''

*'''SUPPLIER_ORDER_CAN_UPDATE_BUYINGPRICE_DURING_RECEIPT''' ► Allow to change price on receipt ► (v19.0)

*'''SUPPLIER_HIDE_SUPPLIER_OBJECTLINES''' ► Hide the supplier information on objectlines (invoices, etc..) ► (v19.0)

[[#Top|(back to top)]]

=Third Parties Module=

*'''COMPANY_AQUARIUM_CLEAN_REGEX''' ► Add a REGEX rule on the third parties names. It applies a regex replacement pattern on generated code if COMPANY_AQUARIUM_CLEAN_REGEX is set. Value must be a regex with parenthesis. The part into parenthesis is kept, the rest removed. For example if COMPANY_AQUARIUM_CLEAN_REGEX = '<code>^..(..)..(.*)</code>' the first char and second char are removed and the char 5 and 6 too ► (>= 8.0.1)

*'''MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES''' ► See in Global options section.

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► See in Global options section.

*'''SOCIETE_EMAIL_MANDATORY''' ► E-mail is a mandatory field when creating a thirdparty

*'''SOCIETE_DISABLE_CUSTOMERS''' ► Remove all menu and features related to customers

*'''SOCIETE_DISABLE_PROSPECTS''' ► Remove all menu and features related to prospects
*'''SOCIETE_DISABLE_PROSPECTSCUSTOMERS ►''' Remove the status "Customer/Prospect" when thirdparties creation or modification

*'''SOCIETE_DISABLE_STATE''' ► Do not use field "state/province"

*'''SOCIETE_SORT_ON_TYPEENT''' ► The combo list of "type of third party" is sorted on alphabetical order instead of the field "position" that appears into dictionary instead.

*'''SOCIETE_ASK_FOR_SHIPPING_METHOD''' ► Shipping method can be predefined on customer card and will be used as default on order creation
*'''SOCIETE_ADD_REF_IN_LIST''' ► Displays the code before the name in the lists ► Value 1 -> Code + name + alias ou Code + name if colone alias 2 -> Code + alias 3 -> Alias

*'''THIRDPARTY_CAN_HAVE_CATEGORY_EVEN_IF_NOT_CUSTOMER_PROSPECT_SUPPLIER''' ► Possible to add Categories to third parties that are not customer, prospect or supplier.

*'''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.

*'''THIRDPARTY_NOTCUSTOMERPROSPECT_BY_DEFAULT''' ► Do not set status "Customer/Prospect" to "on" when creating a new third party from menu "New third party".

*'''THIRDPARTY_INCLUDE_PARENT_IN_LINKTO''' ► Search also for elements on parent third party when using the "link to" object feature.

*'''THIRDPARTY_INCLUDE_PROJECT_THIRDPARY_IN_LINKTO''' ► Search also for elements on third party that own the project of the current element when using the "link to" object feature (if project is owned by a different thirdparty than current one).

*'''THIRDPARTY_LOGO_ALLOW_EXTERNAL_DOWNLOAD''' ► When a logo is uploaded, a share key is automatically set so the file can be downloaded using the share key.

*'''THIRDPARTY_SUGGEST_ALSO_ADDRESS_CREATION''' ► Enabled contact creation on third-party create card
*'''THIRDPARTY_QUICKSEARCH_ON_FIELDS''' ► Personalized search criteria ► Example: $conf->global->THIRDPARTY_QUICKSEARCH_ON_FIELDS = 's.nom=ThirdPartyName;s.name_alias=AliasNameShort;s.code_client=CustomerCode'
*'''MEMBER_CAN_CONVERT_CUSTOMERS_TO_MEMBERS''' ► Enabled member creation on third-party create card
*'''SOCIETE_DISABLE_PARENTCOMPANY''' ► Disables attachment to a parent company.
*'''THIRDPARTY_CUSTOMERPROSPECT_BY_DEFAULT''' ► Set the third party to customer by default
*'''THIRDPARTY_SUPPLIER_BY_DEFAULT''' ► Set the third party to supplier by default
*'''THIRDPARTY_CUSTOMERTYPE_BY_DEFAULT''' ► Set the third party type by default (3 = customer & prospect / 2 = prospect / 1 = customer )
*'''CONTACT_DISABLE_PERSONALINFO''' ► Disable Personal data on contact page
*'''SOCIETE_DISABLE_WORKFORCE''' ► Disable work force selector on society page
*'''SOCIETE_SHOW_VAT_IN_LIST''' ► display VAT number in combo list of thirdparties ► (V15+)
*'''THIRDPARTY_DEFAULT_CREATE_CONTACT''' ► When set, a contact is created at the creation of an individual third party ► (v14.0)

*'''MAIN_SUPPORT_SHARED_CONTACT_BETWEEN_THIRDPARTIES''' ► Able to share contact between several third parties
*'''THIRDPARTY_CUSTOMERCODE_EQUALS_MEMBERREF''' ► When creating third parties out of members, the customer code is set equal to the member Ref. ► (v22.0)
*'''SOCIETE_NO_SYNC_LINKED_MEMBER''' ► If set, changes to a third party will not be synchronized to a linked member. ► (v23.0)

[[#Top|(back to top)]]

=Ticket Module=

*'''TICKET_SHOW_MESSAGES_ON_CARD''' ►Display all ticket related messages on the main ticket card. ► (>= 10.0)
*'''TICKET_AUTO_ASSIGN_CONTRACT_CREATE''' ►Automatically create a contract linked to the ticket ► (>= 10.0)
*'''TICKET_AUTO_CREATE_FICHINTER_CREATE''' ►Automatically create an intervention linked to the ticket ► (>= 10.0)
*'''TICKET_AUTO_ASSIGN_USER_CREATE''' '''►''' (>= 21.0) 0=No auto assignement, 1=Auto assign current user if no user was set, 2=Auto assign current user even if another user was set.
*'''TICKET_CHECK_NOTIFY_THIRDPARTY_AT_CREATION''' ►Automatically check "notify thirdparty at creation" ( >=16)
*'''TICKETS_MESSAGE_FORCE_MAIL''' ► Pre check email sending on ticket message (>=15)
*'''TICKET_SEND_PRIVATE_EMAIL ►''' Allow a private message to be sent by mail (>=17)
*'''TICKET_LIMIT_VIEW_ASSIGNED_ONLY''' '''►''' Only display tickets assigned to the user
*'''TICKET_ADD_AUTHOR_AS_CONTACT''' '''►''' If set to 1: Automatically adds the author as internal contact. If set to 2: Automatically adds the author as external contact if external user. (>=20)
*'''TICKET_ASSIGN_CONTACT_TO_MESSAGE''' '''►''' If known, the external contact is assigned to the message. (>=19)
*'''TICKET_ALLOW_CLASSIFICATION_MODIFICATION_EVEN_IF_CLOSED''' '''►'''Allow modify ticket classification even if closed. (>=19)
*'''WORKFLOW_TICKET_CLOSE_INTERVENTION''' ►On ticket close, automatically close an intervention linked to the ticket
*'''TICKET_INCLUDE_SUSPENDED_STATUS''' ► Use ticket suspended status (>=19)
*'''TICKET_INCLUDE_LINK_TO_PUBLIC_INTERFACE_IN_MESSAGE''' ► Add a link in bottom of emails sent from ticket page with link to public ticket admin tool (>=22)

=VAT Report=

*'''MAIN_INCLUDE_ZERO_VAT_IN_REPORTS''' ► Include lines with VAT to 0% (for "auto-liquidation" in EEC) ► (v8.0.3+)

[[#Top|(back to top)]]

=Website Module=

*'''WEBSITE_USE_WEBSITE_ACCOUNTS''' ► Add a table and a tab to manage some accounts for websites to a third party
*'''WEBSITE_ALLOW_OVERWRITE_GIT_SOURCE''' ► Add a button to export a website over the GIT sources
*'''WEBSITE_ADD_CSS_TO_BODY''' ► Add a CSS class to the body tag of websites

[[#Top|(back to top)]]

 

=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 guaranteed with this. Also if the image is removed or renamed by the image hosting service, your proposal, order or invoice will be broken.
*'''FCKEDITOR_ALLOW_ANY_CONTENT''' ► Allow to enter any content. However, this will totally disable content filtering which is one of the most important CKEditor features. You can use this to keep all your tags and attributes in the html content.
*'''FCKEDITOR_ENABLE_SCAYT_AUTOSTARTUP''' ► Allow to activate the SpellCheckAsYouType (SCAYT) plugins of CKEditor i.e an automatic spell checking. The value to activate this option is 1.
*'''MAIN_ALLOW_WYSIWYG_LOCAL_MEDIAS_ON_PRIVATE_NETWORK''' ► By default, you can add medias links (img src or other) into the rich text content editor, but you can't add links like that use a local host like "https://localhost/file". If you set this option to 1, you can.
*'''MAIN_ALLOW_WYSIWYG_EVEN_ON_UNSECURED_EXTERNAL_HTTP_URL''' ► By default, you can add medias links (img src or other) into the rich text content editor, but not if the link is a unsecure "http" url (not https) and your Dolibarr is http. If you set this option to 1, you can.

[[#Top|(back to top)]]

=STRIPE Module=

*'''STRIPE_FORCE_VERSION''' ► Force the STRIPE version. For Example: "2019-09-09" (v11+)
*'''STRIPE_REUSE_EXISTING_INTENT_IF_FOUND''' ► With this, you will have idempotency key but the payment intention will be reuse and not Generate again (13+)

[[#Top|(back to top)]]

=ClickToDial Module=

*'''CLICKTODIAL_FORCENEWTARGET''' ► Open in new page.

[[#Top|(back to top)]]

 

=For SaaS / Cloud hosting integrators=

The following options are useless for a common usage of Dolibarr. But they are usefull if you plan to host / provide Dolibarr instances as Software As A Service (SAAS) to your customers.

*'''CRON_DISABLE_KEY_CHANGE''' ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*'''CRON_DISABLE_TUTORIAL_CRON''' ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*'''CRON_WARNING_DELAY_HOURS''' ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

*'''MAILING_NO_USING_PHPMAIL''' ► To avoid bad use of the emailing module, it is recommended to set this option to 1 (This option is described previously). Also you can complete the message visible by customers when they try to setup the SMTP credentials of their Dolibarr by using the constant MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS (This option is described previously). For example, you can point to a FAQ on your website.

*'''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► If you have set a system limit on number of recipients on your system, you can set also this option to match the same value, so users will be informed: So '''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' restricts sending of 1 email message to <code>x</code> recipients for the same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include a ton of recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available. Note that this is not a hard limit; it is just the quantity that will be displayed on warnings on screen. For a real limit, this must be implemented into the system.

*'''MAILING_LIMIT_SENDBYDAY''' ► This is a limit of number of emails, an instance can send. Note that this is not a hard limit; it is just the quantity that will be displayed on warnings on screen. For a real limit, this must be implemented into the system.

*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Set this value to a translation key. Then add translation keys into the instance so user will see a message when into the email setup page. For example, you can set a message to say: ''Warning: To avoid abuse, when using default setup, you are restricted to 500 emails per day for all your application (account may be suspended in case of violation of this rule. You can setup application to use your own SMTP server for sending email so you want have no restriction at all (see menu Home-Setup-Emails)''

*'''MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE''' ► If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock and remove the upgrade.unlock so the administration tools like install.php, upgrade.php and repair.php can't be used on your customer instance (until the install.lock file is deleted or the upgrade.unlock file is created).

*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted, separated by a comma. So, when your customer go into the Email setup area:
**If he has chosen mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he has chosen smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option '''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD'''.

You can also provide a list of URLs that return just an IP instead of a list of hardcoded IP. So you can for example set 1 url that contact a whoami service that return the public IP of server and another one doing the one on a IPv6 address, so on the setup page, the public IP adress of the server will always be uptodate for both ipv4 and ipv6 (Example: "https://ipv4.server.com/_service_showmyip.php,https://ipv6.server.com/_service_showmyip.php")

*'''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD''' ► Set here the string to add in the SPF record This string will be shown into a help message when the user in in the setup of email page and has choose a method using an external SMTP server.

*'''MAIN_FIRST_PING_OK_ID''' ► Set this value to "disabled" to remove completely any ping after a complete setup.

*'''MAIN_FILECHECK_LOCAL_SUFFIX''' and '''MAIN_FILECHECK_LOCAL_EXT''' ► If you offer a customized or patched version of Dolibarr, when the user will use the tool to check the integrity of files, the default xml file name used for signature checking will be the official file provided by the Dolibarr team, so it does not includes your own changes. To have the suggested signature file being your own file, you can set the constant MAIN_FILECHECK_LOCAL_SUFFIX to a suffix. For example, set this to "'''-mysaassolution'''". So, when the user will use the file integrity tool, the default file to check for signature will be "'''/install/filelist-10.0.2-mysaassolution.xml'''" instead of "'''/install/filelist-10.0.2.xml'''". All you have to do is generate the signature file '''mysaassolution''' using the tool '''build/generate_filelist_xml.php''' and put this file into the install directory of your customer instance. Doing this, your customer, and yourself, will be able to check if a file was modified without being disturbed by false alerts due to your customized files or patches (they will be included in the signature used for check). Also, if you want to zip the customized signature file into "'''/install/filelist-10.0.2-mysaassolution.xml.zip'''", you can set the constant MAIN_FILECHECK_LOCAL_EXT to '.zip'.

*'''MAIN_HIDE_WARNING_TO_ENCOURAGE_SMTP_SETUP''' ► Set to 1 by default (so warning is hidden). You can set it to 0 to show a warning to encourage admin to set its own SMTP service.

*'''MAIN_MAIL_SENDMODE_password''' ► To force the mode to send the email on the "password forgotten" page. So you can decide to use php mail or SMTP method for this specific use case.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► If set to N, the warning saying modules are not activated will be shown if number of activated module is < N (Having this variable not defined is same than having it set to 1). This may be usefull if you preinstall an application with some modules already loaded by default and you want to keep the warning to be sure the user will enable other modules he need, even if some modules are already enabed.
*'''MAIN_SETUP_MODULES_DESC''' ► If your installation is already done with activated module, the help message to explain how to enable a module on the setup page is hidden. You can keep it visible by adding this option to 1.

*'''MAIN_NO_UPGRADE_REDIRECT_ON_LEVEL_3_CHANGE''' ► The page to make the migration is not shown automatically when you deploy files of version X.Y.Z+delta over an installation with a database version X.Y.Z. The upgrade page will be shown automatically only if there is a change on value of X or Y in version.

*'''SYSLOG_DISABLE_LOGHANDLER_SYSLOG''' ► Set this to 1 to disable usage of syslog (having all customer instances logging in the same system file is not a good idea).

*'''WEBSITE_REPLACE_INFO_ABOUT_USAGE_WITH_WEBSERVER''' ► Put here a text or a translation key of a text to show when the user will use the feature "Deploy" when he want to deploy a website done with Dolibarr CMS. So you can, for example, show him a message that this feature is not part of its subscription and putting a website online may need a complementary subscription.

[[#Top|(back to top)]]

Setup Other

2026-01-05T22:44:14Z

Iouston: /* PDF Options */ add main_pdf_donotrepeat_head

[[fr:Paramétrage_Divers]]
[[es:Configuración_Varios]]
[[de:Erweiterte_Einstellungen]]
[[zh:其他设置]]


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

'''Help About Screen''': Other setup

'''Menu Path''': Home ► Setup ► Other

'''Introduction'''

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

{{warning|32px}} This page contains the list of some advanced development parameters. In most cases, they are parameters for internal usage, development, external modules, features in development not stable or that may lead to security risk. For standard usage of Dolibarr, such parameters '''SHOULD NOT''' be used. All experimental options are NOT supported. They may be removed in a future, modified at any version and break stability of your application.

To enable/override a parameter you have to define the constant name and set it to 1 (unless otherwise stated) in <code>Home ► Setup ► Other Setup</code>

The options here may not be documented since they are not stable and are unsupported (remember they are experimental or development options). The basic format of how the list is written is broken down in the example below:

UNSTABLE_OR_DEV_OPTION ► ''Description of config and goal'' ► ''(specific version information) or values''
<center>
__TOC__
</center>
=Global Options=

*'''ADD_UNSPLASH_LOGIN_BACKGROUND''' ► The background image will be refreshed on every login page refresh. Background image is pulled from the popular open source image website Unsplash. If an already saved static background image exists, then this code will override it (but not delete the saved image). Warning: Using this may allow this external website to steel your login credentials (the value to be put is the URL of the service, exemple : https://source.unsplash.com/random) ► (v10.0)
*'''MAIN_HIDE_POWERED_BY''' ► Hide the "Powered by Dolibarr" picto on public pages
*'''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 to fail by smartphone applications like [[Application Android - DoliDroid]], breaking some features when using Dolibarr from such application. If the text start with a "+", the text will be added to the standard "Dolibarr" label instead of replacing it.

*'''MAIN_AUTOFILL_DATE''' ► If this constant is defined (to something other than <code>0</code>), the date of invoice, proposal, order or payment are auto-filled with the current date. It is highly recommended to NOT ENABLE this feature. This can create a lot of input errors with data not validated by users. This leads to incorrect values saved in the database causing confusion when you have to do your accountancy reports!
*'''MAIN_AUTOFILL_DATE_PROPOSAL►'''If this constant is defined (to something other than 0), the date of proposal is auto-filled with the current date.

*'''MAIN_AUTO_TIMESTAMP_IN_PUBLIC_NOTES''' ► Add a timestamp and user automatically when editing the ''public'' note.

*'''MAIN_AUTO_TIMESTAMP_IN_PRIVATE_NOTES''' ► Add a timestamp and user automatically when editing the ''private'' note.

*'''MAIN_DEFAULT_PAYMENT_TERM_ID''' ► With ID of a payment term, will use this as default payment term each time you create a new proposal, order, invoice (customer and supplier). Deprecated. Replaced with the default setup feature instead (see French page of wiki for some exemple : [[Paramétrage Valeurs par défaut]])
*'''MAIN_DEFAULT_PAYMENT_TYPE_ID''' ► With ID of a payment type, will use this as default payment type each time you create a new proposal, order, invoice (customer and supplier). Deprecated. Replaced with the default setup feature instead (see French page of wiki for some exemple : [[Paramétrage Valeurs par défaut]])

*'''MAIN_DEFAULT_LANGUAGE_FILTER''' ► Useful if you do not want to show <code>en_US</code> language option in combo boxes (other languages can easily be removed in <code>langs</code> directory but not <code>en_US</code>) ► (v10.0)

*'''MAIN_LANGUAGES_ALLOWED''' ► Is a list of languages without spaces, example : <code>fr_FR,en_US,de_DE,it_IT</code> If defined, only those languages will appear in combos. ► (v11.0)

*'''MAIN_DISABLE_NOTES_TAB''' ► Show or hide notes tab in the card page

*'''MAIN_DISABLE_CONTACTS_TAB''' ► Show or hide contacts tab in the card page

*'''MAIN_DISABLE_FULL_SCANLIST''' ► Disables the complete scan of tables to allow the pagination to show total number of pages. May be useful to activate on systems with a very high quantity of data (tables with more than 2 000 000 records).

*'''MAIN_DISABLE_JQUERY_JNOTIFY''' ► Disable usage of <code>JNotify</code> to show confirm or error messages

*'''MAIN_DISABLE_AJAX_COMBOX''' ► If you have a large number of third parties or products, you can disable the autocomplete feature on the third parties list by setting this constant to <code>1</code> ► (v3.6.0+)
*'''MAIN_DISABLE_MULTIPLE_FILEUPLOAD''' ► Disable users to upload multiple files at once.
*'''MAIN_DISABLE_TRUNC''' ► Disable all truncings in select list. ► (v7.0+)

*'''MAIN_DISABLEDRAFTSTATUS''' ► Disable the status "Draft" for some objects (project, donation, ...) so the object is directly created with status "Validated"

*'''MAIN_DOC_USE_OBJECT_THIRDPARTY_NAME''' ► Add name of thirdparty at begin of generated document.

*'''MAIN_DOC_USE_TIMING''' ► Add a timestamp at end of generated document. Value must be format of timestamp. For example: <code>%Y%m%d%H%M</code> (only for ODT files)

*'''MAIN_DOC_UPLOAD_NOT_RENAME_BY_DEFAULT''' ► Disable the auto renaming on upload file ► (v10.0)

*'''MAIN_DOL_SCRIPTS_ROOT''' ► Define directory who contains 'scripts' directory (e.g. <code>/var/www/dolibarr</code>). Value of this variable may be requested by some external script or tools.

*'''MAIN_ENABLE_LOG_TO_HTML''' ► If this constant is defined, it is possible to have logs inside pages by adding the parameter <code>&logtohtml=1</code> into URL.

*'''MAIN_ENABLE_IMPORT_LINKED_OBJECT_LINES''' ► Allow to import lines into current document from "linked" compatible documents ► (v8.0+)

*'''MAIN_FIRST_TO_UPPER''' ► Dolibarr add uppercase to Third Parties, 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_ALL_TO_UPPER''' ► Dolibarr puts uppercase for Third Parties, 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. ► (v11.0)

*'''MAIN_ALL_TOWN_TO_UPPER''' ► Dolibarr puts uppercase for town names if not done. ► (v13.0)

*'''MAIN_FILESYSTEM_ENCODING''' ► With some PHP versions, PHP is not able to detect the page code for filesystem of the server OS. To solve this, Dolibarr assumes your OS filesystem is <code>UTF-8</code> if on Linux or OSX system, and <code>ISO-8859-1</code> if on Windows. If not, for example on a Windows server with a NTFS <code>UTF-8</code> pagecode, you can set the variable <code>MAIN_FILESYSTEM_ENCODING</code> to "<code>utf-8</code>".

*'''MAIN_FORCELANGDIR''' ► Relative path of the directory holding your custom <code>langs</code> folder.
*'''MAIN_HTML_TITLE''' ► Can be used to control how the html page title is formatted. If value contains key '<code>noapp</code>', application name will not be output. If value contains '<code>thirdpartynameonly</code>', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: '<code>noapp;thirdpartynameonly</code>'

*'''MAIN_HELPCENTER_LINKTOUSE''' ► Define the URL link to use as the target page for link "I need help" onto logon page

*'''MAIN_LOGOUT_GOTO_URL''' ► URL to which the user will be redirected after LOGOUT

*'''MAIN_MAXTABS_IN_CARD''' ► Maximum number of tabs visible. Others are grouped into a combo list.

*'''MAIN_MAXLIST_OVERLOAD''' ► Maximum number of line in space's domain.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► A warning saying setup of modules is not complete is shown if the number of enabled modules is lower or equal than this value (<code>1</code> if not defined)

*'''MAIN_NO_CONCAT_DESCRIPTION''' ► Allow to use only input custom description in lines (proposal, order, invoice) ► (v10.0) < v20.0. [ OSBOLETE since 20.0 | SEE Product module admin configuration to set the description behavior of products and services ]. This value is overwritten by PRODUCT_AUTOFILL_DESC, controled by the option in the product module admin configuration, and is no longer used. Kept in code to allow compatibility if custom modules are using it. Removed completely from v22.

*'''MAIN_OPTIMIZE_SPEED''' ► Use some speed enhancements. See page [[FAQ Increase Performance]] for more information.
*'''MAIN_PASSWORD_FORGOTLINK ►''' Change forgotten password link on login page. ► (v9.0)

*'''MAIN_PROPAGATE_CONTACTS_FROM_ORIGIN''' ► When creating an order, contract, invoice from another object, specific contacts of objects are set as specific contact of the new object when possible. ► (v4.0+)

*'''MAIN_PUBLIC_NOTE_IN_ADDRESS''' ► Show public note in address block ► (v4.0+)

*'''MAIN_REMOVE_INSTALL_WARNING''' ► Remove all security warnings that appear to administrator users if URL <code>/install</code> is public. You should solve the problem if warning occurs, instead of removing the warning! For this, create a file called <code>install.lock</code> into Dolibarr root directory. This will stop the warning but also make the page <code>/install</code> not possible to use, to protect your installation.

*'''MAIN_REPEATCONTACTONEACHTAB''' ► If added and set to <code>1</code>, this adds contacts on all tabs, not only main tab.

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

*'''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND''' ► Change way of rounding total including tax of lines, rounding first of after.

*'''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND_SUPPLIER'''► Change way of rounding total including tax of lines, rounding first of after.

*'''MAIN_SERVER_TZ''' ► If you can't set the time zone of your PHP installation, set this constant. Better is to set it to UTC. In future, this constant will be forced to '<code>UTC</code>' so PHP server time zone will not have effect any more. Examples: <code>Europe/Paris</code>, <code>auto</code>.

*'''MAIN_SEARCH_FORM_ON_HOME_AREAS''' ► Show the search form on home page areas for core modules (Removed after v5 due to global search combo) ► (v6.0+)

*'''MAIN_SEARCHFORM_SUPPLIER_INVOICE_DISABLED''' ► Disable the supplier invoice on the search form

*'''MAIN_SEARCH_DIRECT_OPEN_IF_ONLY_ONE''' ► If only one result is found, then setting this value to <code>1</code> will take you direct to the item (default method). Setting the value to <code>0</code> will show the result in the list as a single result ► (v5.0+)

*'''MAIN_SERVICES_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country. It can have value '1' or '2'. If value 2, the VATs available to select only the ones of buying country. If '1', the VATs available to select mix the ones of selling country and the ones of buying country. ► (v18.0+)

*'''MAIN_SHOW_TUNING_INFO''' ► Add tuning information into JavaScript console. Better when xdebug is enabled.

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show also technical IDs on elements cards or some lists (not supported everywhere).

*'''MAIN_SHOWDATABASENAMEINHELPPAGESLINK''' ► Show database name in upper help menu ► (v8.0+)

*'''MAIN_USE_ALTERNATE_TRANSLATION_FOR''' ► List of fields per object that need an alternate translation. Example: <code>MAIN_USE_ALTERNATE_TRANSLATION_FOR=societe:name,town;contact:firstname,lastname</code>

*'''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_USE_JQUERY_JEDITABLE''' ► Allow to update from screen, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this feature, because it bypasses some business actions (updates on other data that should be done consistently) and ignores business controls on data you saved. Consequently this feature breaks consistency of data and possibly the stability of the 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_USE_OLD_SEARCH_FORM''' ► Display the old search form in left menu.

*'''MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS''' ► Allow to force the VAT rate to a given value (instead of higher VAT rate of country) if the VAT rate of product was not defined.

*'''MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES''' ► If we can't guess if a thirdparty is a company or individual (not VAT ID fill, no Prof ID fill, no type of thirdparty fill), then we suppose it is a company (B2B business) if 1, we suppose it is an individual (B2C business) if 0.

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► For intra CEE sales, we use by default, on proposal, order or invoice creation, a 0 VAT for customers that are companies (see MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES to change behaviour to know if a thirdparty is a company or an individual). But if the option MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL is set, we will use the 0 VAT only if a VAT ID is defined for the customer.

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_INDIVIDUAL_CUSTOMER_OUT_OF_EEC''' ► For to use the default VAT of product for individual customers that are out E.E.C. (European Economic Community) ► (v7.0+). ''There is no reason to use this.''

*'''MAIN_VIEW_LINE_NUMBER''' ► Shows a line number for each line of products/services at documents like proposal / order / invoice. Only on screen, not on PDF.

*'''MAIN_VIEW_LINE_NUMBER_IN_LIST''' ► Shows a line number in lists ► (v12.0)

*'''MAIN_VOLUME_DEFAULT_ROUND''' ► Accuracy of volume (number of decimals)

*'''MAIN_VOLUME_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''MAIN_WEIGHT_DEFAULT_ROUND''' ► Accuracy of weight (number of decimals)

*'''MAIN_WEIGHT_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''USER_HIDE_INACTIVE_IN_COMBOBOX''' ► Disable display inactive users in combobox.

*'''MAIN_DISABLE_PDF_THUMBS''' ► Disable thumbs PDF in case of imagick bug

*'''MAIN_KEEP_REF_CUSTOMER_ON_CLONING''' ► Keep the Customer Reference on cloned object (Propal/Invoice)

*'''MAIN_DONT_KEEP_NOTE_ON_CLONING''' ► Remove the object notes during cloning ► (v11.0)

*'''MAIN_DOC_SORT_FIELD''' ► Set the default sorting field on document page (name by default) ► (v11.0)

*'''MAIN_DOC_SORT_ORDER''' ► Set the default sorting order (ASC or DESC) on document page (ASC by default) ► (v11.0)

*'''MAIN_USE_ZIPTOWN_DICTIONNARY''' ► Use dictionary ZIP for create card.

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Show search in top menu with theme eldy ► (v11.0)

*'''MAIN_PHONE_SEPAR''' ► Separ phone number other space ► (v12.0)

*'''GRAPH_USE_FISCAL_YEAR''' ► Widgets uses fiscal year

*'''SHOW_SOCINFO_ON_PRINT''' ► Permit to add user company information on each printed document (when click on Dolibarr print button) ► (v12.0)

*'''MAIN_FEATURES_LEVEL''' ► Level of features to show: <code>-1=stable+deprecated</code>, <code>0=stable only (default)</code>, <code>1=stable+experimental</code>, <code>2=stable+experimental+development</code>

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show technical id for object.

*'''MAIN_HTTP_CONTENT_SECURITY_POLICY''' ► Allows you to fill in the content security rules ► (v6.0)

*'''SOCIETE_ON_SEARCH_AND_LIST_GO_ON_CUSTOMER_OR_SUPPLIER_CARD''' ► Allow to change the link of the third party to customer/supplier card instead of contact card on List.

*'''MAIN_MODULE_SETUP_ON_LIST_BY_DEFAULT''' ► If set to "common" the setup module becomes list by defaut

*'''MAIN_PAGESIZE_CHOICES''' ► Configure select field to choose number of lines displayed on listing (<code>10:10,15:15,20:20,30:30,40:40,50:50,100:100,250:250,500:500,1000:1000,5000:5000</code>).

*'''MAIN_USE_TOP_MENU_QUICKADD_DROPDOWN''' ► Add a dropdown menu with shortcuts to create new objects ► (v13.0)

*'''MAIN_EMAILCOLLECTOR_MAIL_WITHOUT_HEADER''' ► Remove the header stored by email collector ► (v13.0)

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID'''

*'''MAIN_OPTIMIZEFORTEXTBROWSER''' ► Optimise interface for a text only browser. This variable is set to 1 automatically if your browser is lynx or links

*'''MAIN_NB_OF_YEAR_IN_WIDGET_GRAPH''' ► Set the number of years visible on some graph of some widgets (2 is default value)

*'''MAIN_CREATEFROM_KEEP_LINE_ORIGIN_INFORMATION'''

*'''API_DISABLE_LOGIN_API''' ►(v14.0)

*'''MAIN_LOGIN_BADCHARUNAUTHORIZED''' ► Add possibility to define bad character unauthorized into login name REGEX expression (Default value is @<>"\') ► (v16.0)
*'''MAIN_SHOW_ALL_FILES_ON_DOCUMENT_TOOLTIP''' ► Add all files visible from the object to be visible from the list of object.
*'''MAIN_LIST_ALLOW_PUBLIC_NOTES''' ► Display public notes on list
*'''MAIN_LIST_ALLOW_PRIVATE_NOTES''' ► Display private notes on list

*'''MAIN_CHECKBOX_LEFT_COLUMN''' ► Display private check boxes on the left ► (v17.0)
*'''MAIN_STATS_GRAPHS_SHOW_N_YEARS''' ► Nb of years to shows in widget and graph ► (v14.0)
*'''MAIN_HOOK_DEBUG''' ► if >=2 the hook in the logs are more verbose ► (v18.0)

*'''MAIN_ENABLE_AJAX_TOOLTIP''' ► if 1 the tooltips are updated with AJAX request ► (v18.0)
*'''MAIN_NO_INPUT_PRICE_WITH_TAX''' ► if 1 the TTC input field is removed from propal/invoices/... ► (v17.0)

*'''MAIN_DISABLE_SELECT2_FOCUS_PROTECTION''' ► if 1 disable the focus protection ► (v17.0)
*'''MAIN_USE_ADVANCED_PERMS ►''' Add advanced user permission

*'''MAIN_FREE_PRODUCT_CHECKED_BY_DEFAULT ►''' Check "product" or "service" by default on order/invoices/propal cards (set value "product" or "service")
*'''MAIN_LINK_BY_REF ►''' Allow to link documents by choosing the type and ref from the object linked option

'''Official supported option'''

The following options are not hidden option. They are available by default from the interface.

*'''MAIN_ONLY_LOGIN_ALLOWED ►''' Activate maintenance mode and set user that is allowed to login. Value must be user login. Available into menu Home - Admin tools - User session, it is filled with admin user when clicking on button "Block other session".

[[#Top|(back to top)]]

=Security Options=

*'''MAIN_SECURITY_ANTI_SSRF_SERVER_IP''' ► Can set a complete list of IPs of server.

*'''MAIN_SECURITY_CSRF_WITH_TOKEN''' ► Activate a second anti-CSRF protection on POST (so a POST from another web site can't be done). Note there is also a default protection using test on referrer that is not reliable. This second protection uses TOKEN on forms and is more powerful. Value can be: 0=CSRF protection disabled; 1=CSRF protection is on POST URLs only (default from version Dolibarr 15.0+); 2=CSRF protection is required on POST + some GET URL that contains some white listed parameters like the parameter "action" used to request database change (default from version Dolibarr 16+), 3=CSRF protection is enabled on any POST and GET URLs (a valid CSRF token is expected whatever are the parameters, warning: can be enabled on Dolibarr but some external modules developped by thirdparty may not be ready yet with this option)

*'''MAIN_MODULES_FOR_EXTERNAL''' ► Limit available modules for external users. By default value is '<code>facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda</code>'

*'''MAIN_ALLOW_SVG_FILES_AS_IMAGES''' ► Allow to use SVG file as image files. Warning: This may introduce security vulnerability (javascript can be embedded into SVG file).

*'''MAIN_RESTRICTHTML_ONLY_VALID_HTML''' ► Refused parameter if value is not a valid HTML content. The content is also sanitized with Tidy.

*'''MAIN_RESTRICTHTML_ONLY_VALID_HTML_TIDY''' ► Refused parameter if value is not a HTML content validated by Tidy PHP library. The content is also sanitized with Tidy.

*'''MAIN_RESTRICTHTML_REMOVE_ALSO_BAD_ATTRIBUTES''' ► Sanitize also non standard attributes on HTML content.
*'''MAIN_SECURITY_SALT''' ► A salt string to base the hashing on. 8 strings length recommended.

*'''MAIN_SECURITY_MAX_IMG_IN_HTML_CONTENT''' ► Maximum number of Images on the HTML content
*'''MAIN_SECURITY_ALLOW_UNSECURED_LABELS_WITH_HTML''' ► Allow HTML tags into products label

*'''MAIN_SECURITY_FORCERP''' = "strict-origin-when-cross-origin" (default) so browser doesn't send any referrer when going into another web site domain / "same-origin" / "strict-origin"

[[#Top|(back to top)]]

=Members Module=

*'''MEMBER_NEWFORM_FORCEMORPHY''' ► Force nature of member set to "phy" for physical or to "mor" for moral ► (v12.0)
*'''MEMBER_ALLOW_CHANGE_OF_TYPE''' ► Member can edit their type on public subscription page ► (v13.0)
*'''ADHERENT_DEFAULT_CREATE_THIRDPARTY''' ► Thirdparty is created when creating a new member ► (v13.0)
*'''MEMBER_SUBSCRIPTION_SUGGEST_END_OF_MONTH''' ► If set to 1, the member subscription end date will be suggested for the end of the month ► (v18.0)
*'''MEMBER_SUBSCRIPTION_SUGGEST_END_OF_YEAR''' ► If set to 1, the member subscription end date will be suggested for the end of the year ► (v18.0)
*'''MAIN_NB_OF_YEAR_IN_MEMBERSHIP_WIDGET_GRAPH''' ► If set, it limits the number of years visible on graph and widgets of membership (empty is default value to show all) ► (v18.0)
*'''MEMBER_NO_SYNC_LINKED_THIRDPARTY ►''' If set, changes to a member will not be synchronized to a linked third party. ► (v23.0)

[[#Top|(back to top)]]

=Accounting Module=

*'''ACCOUNTANCY_COMBO_FOR_AUX''' ► Add graphic option for ACCOUNTANCY_COMBO_FOR_AUX. Having this option on may slow down and even freeze the accounting features if you have a very large number of thirdparties ► (v10.0)
*'''ACCOUNTING_DEFAULT_NOT_NOTIFIED_VALIDATION_DATE''' ► Avoid validating the lines with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*'''ACCOUNTING_DEFAULT_NOT_NOTIFIED_EXPORT_DATE''' ► Avoid flagging the lines as exported with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*'''ACCOUNTANCY_USE_PRODUCT_ACCOUNT_ON_THIRDPARTY ►''' Add 2 fields on thirdparty card which allow you to set an account for all sells products and an other for all buying products for this customer ► (v14.0)
*'''ACCOUNTING_MANAGE_ZERO''' '''►''' Allow to manage char 0 in accounting account (if enabled 1 ≠ 10) ► (v14.0)

[[#Top|(back to top)]]

=Agenda Module=

*'''AGENDA_ALL_CALENDARS''' ► Change the default view of calendar pages to see all the Agenda's (instead or yours only be default)

*'''AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS''' ► To automatically set end date of event to start date + delta on event creation page.

*'''AGENDA_DISABLE_LOCATION''' ► Disable location field in action card ► (>=v5.0)

*'''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''''').

*'''MAIN_ADD_EVENT_ON_ELEMENT_CARD''' ► Allow to create an event from a document (proposal, order, invoice)

*'''AGENDA_SUPPORT_PRIORITY_IN_EVENTS''' ► Allow to have priorities in events ► (>=v13.0)

*'''AGENDA_ADDACTIONFORPHONE''' ► Allow you to create a event from phone number ► (=<v12.0) - Need to be fix for (=>v12.0) https://github.com/Dolibarr/dolibarr/issues/22720

*'''AGENDA_ADDACTIONFOREMAIL''' ► Allow you to create a event from Email ► (=<v12.0) - Need to be fix for (=>v12.0) https://github.com/Dolibarr/dolibarr/issues/22720
*'''MAIN_ACTIONCOM_CAN_ADD_ANY_CONTACT''' ► Allow you to add any contact on events if set at 1a https://github.com/Dolibarr/dolibarr/releases/tag/18.0.0

[[#Top|(back to top)]]
=Bank Module=

*'''BANK_CAN_RECONCILIATE_CASHACCOUNT''' ► Can reconciliate cash accounts ► (v3.8)

*'''BANK_DISABLE_CHECK_DEPOSIT''' ► Disable check deposit feature

*'''BANK_ASK_PAYMENT_BANK_DURING_ORDER''' ► Ask bank account during creation of an order

*'''BANK_ASK_PAYMENT_BANK_DURING_PROPOSAL''' ► Ask bank account during creation of a proposal

*'''BANK_USE_OLD_VARIOUS_PAYMENT''' ► To allow to enter miscellaneous payments (not covered by other modules) using old method. '''''Deprecated'''''. Entering various payment is preferred ► (<=v12.0).
*'''MAIN_IBAN_IS_NEVER_MANDATORY''' ► IBAN and BIC informations not mandatory. (V15)

[[#Top|(back to top)]]

 

=BOM and MO Module=

*'''ALLOW_USE_KITS_INTO_BOM_AND_MO'''
*'''BOM_SUB_BOM''' ►Allow to add a BOM in another BOM►(v16.0)

[[#Top|(back to top)]]

 

=Bookmarks Module=

*'''BOOKMARKS_SHOW_IN_MENU''' ► Numbers of bookmark entries to be displayed (10 by default)

[[#Top|(back to top)]]

 

=Inalterable Log Module=

*'''BLOCKEDLOG_ADD_ACTIONS_SUPPORTED''' ► Can complete list of triggered action that are logged
*'''BLOCKEDLOG_USE_REMOTE_AUTHORITY''' ► URL of the remote authority for the blockchain

[[#Top|(back to top)]]

 

=Category-Tags Module=

*'''CATEGORY_SHOW_COUNTS''' ► Shows nb of object by tags in tag tree
*'''CATEGORY_EDIT_IN_MENU_NOT_IN_POPUP ►''' Display categories menu instead of managing it only from "Tools"

[[#Top|(back to top)]]

 

=Contracts=

*'''CONTRACT_SUPPORT_PRODUCTS''' ► Products are also suggested into module contract.
*'''CONTRACT_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)
*'''CONTRACT_HIDE_PLANNED_DATE_ON_PDF''' ► allows you to not display dates on pdf files.
*'''CONTRACT_HIDE_REAL_DATE_ON_PDF''' ► allows you to not display dates on pdf files.
*'''CONTRACT_HIDE_PRICE_ON_PDF''' ► allows you to not display price on pdf files.
*'''CONTRACT_HIDE_QTY_ON_PDF''' ► allows you to not quantity dates on pdf files.
*'''CONTRACT_SHOW_SIGNATURE_STATUS_WITH_SERVICE_STATUS''' ► Show signature status in contract card (Sign by all parties).► (v21.0+)

[[#Top|(back to top)]]

=Cron module=

*'''CRON_DISABLE_KEY_CHANGE''' ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*'''CRON_DISABLE_TUTORIAL_CRON''' ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*'''CRON_WARNING_DELAY_HOURS''' ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

[[#Top|(back to top)]]

 

=Direct Debit Orders=

*'''WITHDRAWAL_ALLOW_ANY_INVOICE_STATUS''' ► If this option is set, all invoices status (even already paid) may appear on the list of invoices qualified for a direct debit payment. This is the list of invoices with a payment request done, and not linked to a direct debit payment. By default, only "unpayed" invoices are used to avoid to pay twice the same invoice.

[[#Top|(back to top)]]

=Donation Module=

*'''DONATION_USE_THIRDPARTIES''' ► If this option is set, a thirdparty field appear on donation forms.

[[#Top|(back to top)]]
=Email=

*'''MAIN_COPY_FILE_IN_EVENT_AUTO''' ► Add attachment document on event auto generated by sending email from dolibarr. ► (v6.0+)

*'''MAIN_EMAIL_USE_LAYOUT'''► Enable the use of predefined layout when writing an email.

*'''MAIN_MAILFORM_DISABLE_ENTERKEY''' ► Activate JavaScript code to disable the enter key in the MAIL form. ► (>= 8.0.1)

*'''MAIN_MAIL_DEBUG''' ► Write content with header of last mail into file <code>dolibarr_mail.log</code> into directory <code>dolibarr_main_data_root</code>.

*'''MAIN_MAIL_DEBUG_ERR_WITH_DATE''' ► Use a different filename (by adding a prefix of date) for each email sent with error when MAIN_MAIL_DEBUG.

*'''MAIN_MAIL_DEBUG_LOG_WITH_DATE''' ► Use a different filename (by adding a prefix of date) to log each email sent (whatever is result) when MAIN_MAIL_DEBUG.

*'''MAIN_MAIL_FORCE_FROM''' ► (v19+) Can force the value into the From field of the SMTP header. Note that email sender is always saved into the "Reply-To".

*'''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 <code>-f</code>. This option is here to ask Dolibarr to call the function mail of PHP by adding value for the option <code>-f</code>. 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 setup or version of sendmail that ask the -f option to be mandatory or for sendmail setup that does not use by default the From of the header email to define the sender (with this option, the from can be forced on command line to avoid to have the from lost by sendmail).

*'''MAIN_MAIL_SENDMAIL_FORCE_BA''' ► On Linux 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 asks PHP to provide this parameter when sending a mail. Note that another solution is to edit the mail.force_extra_parameters=-ba into <code>php.ini</code> 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 <code>orange.fr</code> or <code>hotmail.com</code>

*'''MAIN_MAIL_DO_NOT_USE_SIGN''' ► Do not add user signature at end of suggested pre-defined email

*'''MAIN_MAIL_FORCE_NOT_SENDING_TO''' ► If en email is defined into this variable, emails will never be sent to this email.

*'''MAIL_FORCE_DELIVERY_RECEIPT_INVOICE''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Invoice'' module.

*'''MAIL_FORCE_DELIVERY_RECEIPT_ORDER''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Order'' module.

*'''MAIL_FORCE_DELIVERY_RECEIPT_PROPAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Proposal'' module.
*'''MAIL_FORCE_DELIVERY_RECEIPT_SUPPLIER_PROPOSAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Supplier Proposal'' module.

*'''MAIN_EMAIL_SUPPORT_ACK ►''' Restore email acknowledgment checkbox on sending emails. This feature is commonly abandoned by mailers. Active from Dolibarr V17 - see [https://github.com/Dolibarr/dolibarr/blob/33744f74da1a5c20f8aa9950018ab4e549e00205/ChangeLog#L53 changelog]
*'''MAIN_EMAIL_USECCC''' ► 1 = Shows field BCC into email forms, If value is an email = Shows the BCC pre filled with the email value.

*'''MAIN_MAIL_AUTOCOPY_PROPOSAL_TO''', '''MAIN_MAIL_AUTOCOPY_ORDER_TO''', '''MAIN_MAIL_AUTOCOPY_INVOICE_TO''', '''MAIN_MAIL_AUTOCOPY_SHIPMENT_TO''', '''MAIN_MAIL_AUTOCOPY_..._TO''' ► Email to use as a BCC recipient 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 third party 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 third party or object, the email exchange is related to.

*'''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► Restrict sending of 1 email message to <code>x</code> recipients for same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include 1000 recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available.

*'''MAIN_MAIL_FORCE_CONTENT_TYPE_TO_HTML''' ► Force to send all email (event with text only content) as HTML formatted email.

*'''MAIN_MAIL_USE_MULTI_PART''' ► Forge email content using an alternate text part ► (for 5.0.2+). By default with 6.0+
*'''MAIN_INFO_SOCIETE_MAIL_ALIASES''' ► add address aliases for the from field on mail. Set his value with "Firstname Name <firstname.lastname@mydomain.tld, Otherfirstname OtherlastName <othermail@mydomain.tld>,..." ► (v5.0.0+)

*'''MAIN_MAIL_ADD_INLINE_IMAGES_IF_IN_MEDIAS''' ► If images were stored into the medias directory from CKEditor, then images into emails are replaced with "inline content". This may increase seriously risk of being detected as SPAM.

*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. You can also set the URLs where to get the IP addresses, for exemple: "https://ipv4.urltoshowip.com/_service_showmyip.php,https://ipv6.urltoshowup.com/_service_showmyip.php. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option '''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD'''.

*'''MAIN_IMAP_USE_PHPIMAP''' ► Use embedded PHP-imap library (not using the native php imap) instead of native php imap extension ► (v17.0+, available as official option in setup of emailcollector by default from v19)

*'''MAIN_MAIL_ENABLED_USER_DEST_SELECT''' ► Show also internal users into list of recipients of email in email sending form ► (v8.0+)

*'''MAIL_PREFIX_FOR_EMAIL_ID''' ► Prefix for the mails ID. Default value is <code>$_SERVER["SERVER_NAME"]</code> ► (>= 8.0.1)

[[#Top|(back to top)]]

=SMS=

*'''MAIN_SMS_DEBUG''' ► Write content of SMS sent into file <code>dolibarr_sms.log</code> into directory <code>dolibarr_main_data_root</code>.

[[#Top|(back to top)]]

=Emailing Module=

*'''MAILING_PREFIX_FOR_EMAIL_ID''' ► Set the value that will be used to compose the "Email ID" into email headers. If you set this value to '<code>SERVER_NAME</code>', the virtual host of web server will be used. By default, this is not defined, so a hash key, unique to each instance, is used.

*'''MAILING_NO_USING_PHPMAIL''' ► If set, the module emailing can't be used with mail setup of "phpmail". Using a thirdparty SMTP server is required. You can complete warning message by adding an email to contact for setup help with constant <code>'''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS'''</code>.

*'''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS''' ► Contains the email of contact to show into the message visible to a user when he try to use emailing module without SMTP server and if option '''MAILING_NO_USING_PHPMAIL''' is set to on.

*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is on "phpmail". Note: The application always try to translate the message considering the message is a translation key, before showing the translation or message if translation was not found.

*'''MAILING_LIMIT_WARNING_NOPHPMAIL''' ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is something else than "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.
*'''EMAILING_USE_ADVANCED_SELECTOR''' ► Enable the advanced selector for recipients.

*'''MAILING_LIMIT_SENDBYWEB''' ► Restrict number of emails you can send in same sending session with emailing module from GUI. The value "<code>dolibarr_mailing_limit_sendbyweb</code>" if defined into config file is used in priority for this limit. A negative value means, sending by web is forbidden.

*'''MAILING_LIMIT_SENDBYCLI''' ► Restrict number of emails you can send in same sending session with emailing module from CLI script. The value "<code>dolibarr_mailing_limit_sendbycli</code>" if defined into config file is used in priority for this limit.

[[#Top|(back to top)]]

 

=Expense Report=

*'''EXPENSEREPORT_ALLOW_OVERLAPPING_PERIODS''' ► Can enter several expense reports on same or overlapping date periods. ► (v7.0+)

*'''EXPENSEREPORT_OVERRIDE_VAT''' ► Setting this constant to 1 will allow expense reports to show VAT even if the global VAT setting is off ► (v10.0)

*'''EXPENSEREPORT_USE_OLD_NUMBERING_RULE''' ► The module Expense Report use numbering rules that you can setup (like other modules do). If you need to keep the hard-coded numbering rule of expenses report used in v6.0 set this constant to 1 ► (>=v7.0+)

*'''MAIN_USE_EXPENSE_IK''' ► This feature allows you to set index kilometres against a mileage index for different types of vehicles. ► (v7.0+)

*'''MAIN_USE_EXPENSE_RULE''' ► This feature allows you to set a variety of rules per user/group/all so they can only create reports within their limits. ► (v7.0+)

[[#Top|(back to top)]]

 

=Export Module=

*'''EXPORT_CSV_SEPARATOR_TO_USE''' ► String value to use as default separator to delimit fields of exported files (by default Dolibarr uses "<code>,</code>"). Example: EXPORT_CSV_SEPARATOR_TO_USE=<code>;</code>

*'''EXPORT_CSV_FORCE_CHARSET''' ► Choose the charset used in the output file built by the CSV exporter. By default it is ISO-8859-1. Example: EXPORT_CSV_FORCE_CHARSET= <code>utf-8</code>

*'''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 (<code>"</code>).
*'''EXPORTS_SHARE_MODELS''' ► Share export models between users.

[[#Top|(back to top)]]

=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 added in front of payment cell, into the page to make online subscription.

[[#Top|(back to top)]]

 
=Holiday Module=

*'''HOLIDAY_HIDE_BALANCE''' ► Hide the user's vacation balance on the vacation request page

[https://wiki.dolibarr.org/Setup_Other#Top (back to top)]
=Interventions Module=

*'''FICHINTER_CLASSIFY_BILLED'''► Allow to classify an intervention card as "Billed". This add also trigger <code>FICHINTER_CLASSIFY_BILLED</code> into list of possible automatic event into agenda.

*'''FICHINTER_DISABLE_DETAILS'''► Disable entry of detail lines on intervention. Can validate with no line. Only one line will be shown per intervention on list.
**If set to <code>2</code> details are disabled only on intervention list ► (v21.0+)

[[#Top|(back to top)]]

=Invoice Module=

*'''MAIN_DEPOSIT_MULTI_TVA''' ► In deposits invoice, creates one line per VAT rate from the origin document ► (6.0)

*'''INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED''' ► If a credit note was partially refunded (a refund was sent to the customer), with common situation, we wait to have the remain refunded too. With this option, it is possible to convert the remain of invoice into a discount to reuse it into another invoice.

*'''SUPPLIER_INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED''' ► See INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED, but for supplier credit notes.

*'''INVOICE_CAN_BE_EDITED_EVEN_IF_PAYMENT_DONE''' ► Allow to edit invoices even if payment was started. Note: If the module "BlockedLog" is active (required in some countries for legal reasons), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change will be recorded into the archive log.

*'''INVOICE_CAN_ALWAYS_BE_REMOVED''' ► Allow to always delete invoices (even if invoice is not last one). Note: If the module "BlockedLog" is active (required by some countries for legal reason), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*'''INVOICE_CAN_NEVER_BE_EDITED''' ► Never allow to edit invoices (except draft invoices with ref like (PROV%)). See also INVOICE_CAN_NEVER_BE_REMOVED.

*'''INVOICE_CAN_NEVER_BE_REMOVED''' ► Never allow to delete invoices (except draft invoices with ref like (PROV%)). See also INVOICE_CAN_NEVER_BE_EDITED

*'''INVOICE_POSITIVE_CREDIT_NOTE''' ► All amounts on PDF credit notes are positive.

*'''FACTURE_DEPOSITS_ARE_JUST_PAYMENTS''' ► An old way to create initial payment. This treats deposit invoices as a special case and not as legal deposit invoice. 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. WARNING: In a lot of european countries, using this option is not allowed.

*'''FACTURE_SENDBYEMAIL_FOR_ALL_STATUS''' ► Can send invoice by email to customer even if invoice has status "draft".

*'''INVOICE_CREDIT_NOTE_STANDALONE''' ► Start implementation to allow a credit note even without invoice (dangerous) ► (v3.9)

*'''INVOICE_USE_SITUATION''' ► 1=Enable the "situation invoice" feature. Warning, this feature is bugged and may not be compatible with the final version of the feature once the bug will be solved. Also, using the double-entry accountancy module is not possible when this option is on (due to the same design problem). 2=Enable the "situation invoice" feature with a rewrite. This mode should be better to become a future stable feature.

*'''INVOICE_USE_SITUATION_CREDIT_NOTE''' ► Enable the "situation credit note" feature (need <code>INVOICE_USE_SITUATION</code>) ► (v8.0)
*'''INVOICE_USE_RETAINED_WARRANTY''' ► Enable the retained warranty on invoice ► (v14.0)

*'''INVOICE_DISABLE_DEPOSIT''' ► Disable deposit invoices

*'''INVOICE_DISABLE_REPLACEMENT''' ► Disable replacement invoices

*'''INVOICE_DISABLE_CREDIT_NOTE''' ► Disable credit notes

*<bdi>'''INVOICE_ADD_EXTRAFIELD_IN_NOTE''' ► Add extrafields in note for canelle template ► (v17.0+)</bdi>

*'''INVOICE_DEFAULT_NOTE_PUBLIC''' <bdi>► Default text in public note</bdi>

Note: To decode a QR image of a ZATCA code: https://www.onlinebarcodereader.com/. You can also use the mobile application https://play.google.com/store/apps/details?id=com.posbankbh.einvoiceqrreader&gl=FR

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT''' ► See PDF option

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN''' ► See PDF options

*'''WORKFLOW_BILL_ON_SHIPMENT''' ► Change label of button with suitable label when you need to create invoice on shipments

*'''INVOICE_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. Use the tag __DIRECTDOWNLOAD_URL_INVOICE__ in email template to insert it. ► (v7.0+)

*'''INVOICE_POINTOFTAX_DATE''' ► Add Point of Tax Date on invoices for country-specific legality reasons ► (v4.0+)
*'''FACTURE_ENABLE_NEGATIVE''' ► Can validate an invoice when amount is negative

*'''FACTURE_ENABLE_NEGATIVE_LINES''' ► Allows to add negative lines to an invoice ► (v8.0.2+)
*'''SUPPLIER_INVOICE_ENABLE_NEGATIVE''' ► Can validate an supplier invoice when amount is negative ► (V21 ?)
*'''SUPPLIER_INVOICE_ENABLE_NEGATIVE_LINES''' ► Allows to add negative lines to an supplier invoice ► (V21 ?)

*'''INVOICE_USE_DEFAULT_DOCUMENT''' ► Allow user to select a default invoice documents models according to invoice type. On invoice create page, the model is dynamically changed on invoice type selection. ► (v9.0+)

*'''FACTURE_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object (Proposal,...) when creating the bill.
*'''FACTUREFOURN_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object when creating the supplier bill ► (V13.0)
*'''MAIN_SHOW_FACNUMBER_IN_DISCOUNT_LIST''' ► Display the reference of credit notes in discount list when creating the bill.
*'''INVOICE_ALLOW_FREE_REF''' ► Capability to change reference of an invoice. This will be possible as long as the invoice has the status “Draft” and only if your country is not in Europe(V11)

*'''INVOICE_DISALLOW_REOPEN'''

*'''INVOICE_MAX_FUTURE_DELAY''' ► Numbers of seconds allowed for billing in the future ► (V14.0)
*'''INVOICE_AUTO_NEXT_MONTH_ON_LINES''' ► Increase start date and end date by one month, if an invoice line is a clone of a time based service AND if this services started on the first day of month and ended on the last day of month ► (V13.0.1)
*'''INVOICE_KEEP_DISCOUNT_LINES_AS_IN_ORIGIN''' ► Does not change a line with a negative price into an absolute discount when creating an invoice ► (V16 ?)
*'''INVOICEREC_SET_AUTOFILL_DATE_START''' and '''INVOICEREC_SET_AUTOFILL_DATE_END ►''' Set start and end date to yes for lines of template invoice when created from a draft invoice ► (V16)
*'''INVOICE_REC_DATE_TO_YES''' '''►''' Set start and end date to yes by default in add line form for template invoice ► (V16)
*'''INVOICE_SUBTYPE_ENABLED''' ► Extends Dolibarr standard invoice with more invoice types used in some countries. A combo box in the new invoice creation card allows the selection of "subtypes" with values from dictionary "Invoice Subtypes" ► (v19.0+)
*'''LIST_OF_QUALIFIED_INVOICES_LIMIT_DEFINED''' '''►''' Perf options to limit list of invoices for "credit note" source (on form "create a credit note"), usable for big quantities of invoices for one customer like you can have with TakePos ► (V22+)

[[#Top|(back to top)]]

=Leave=

*'''MAIN_NON_WORKING_DAYS_INCLUDE_SATURDAY''' ► Set this value to 0 if you want to have the Saturday as a working day
*'''MAIN_NON_WORKING_DAYS_INCLUDE_SUNDAY''' ► Set this value to 0 if you want to have the Sunday as a working day

=Look or Theme=

*'''MAIN_FAVICON_URL''' ► favicon url

*'''MAIN_EASTER_EGG_COMMITSTRIP''' ► Show a comic image from the CommitStrip website. Images are refreshed daily. ► (v6.0+)

*'''MAIN_INCLUDE_GLOBAL_STATS_IN_OPENED_DASHBOARD''' ► This conf will auto remove global stats box item if there are already in the new dashboard of opened elements and keep displayed stats on the opened item box (not only on mouse over) ► (v11.0+)

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Actually only for eldy theme, this conf move search input to top menu and use new design too ► (v11.0+)

*'''THEME_AGRESSIVENESS_RATIO''' ► This conf can be used to increase/decrease aggressiveness of colors. Value 0 is medium, value is between -100 (light grey colors) to +100 (very flashy colors) ► (v11.0+)

*'''THEME_SHOW_BORDER_ON_INPUT'''
*'''MAIN_DISABLE_GLOBAL_WORKBOARD''' ► Hide the work board of the main page ► (v13.0+)
*'''MAIN_DISABLE_GLOBAL_BOXSTATS''' ► Hide the Statistic Box of the main page
*'''ALLOW_THEME_JS ►''' Allow JS file in theme folder (same name as theme folder)

 

=Manifest (Progressive Web App)=

*'''MAIN_MANIFEST_APPLI_THEME_COLOR ►''' Theme color for manifest
*'''MAIN_MANIFEST_APPLI_BG_COLOR ►''' Background color for manifest
*'''MAIN_MANIFEST_APPLI_LOGO_URL ►''' Logo for manifest
*'''MAIN_MANIFEST_APPLI_LOGO_URL_SIZE ►''' Logo url size for app (150, 192, 512px) missing 3 configurations

[[#Top|(back to top)]]

=Order Module=

*'''MAIN_MASSACTION_CREATEBILLS_REDIRECT_IF_ONE''' ► If set 1, redirects to the one bill created from massaction create bills from order list ► (v20.0)

*'''MAIN_MASSACTION_CREATEBILLS_REDIRECT_IF_MANY''' ► If set to 1, redirects to the invoice list after plural invoices where generated from tho massaction create bills from order list ► (v20.0)

*'''MAIN_ORDERLIST_CREATEBILLS_ONEBYTHIRD''' ► Allow defining value for option "one by thirdparty" in massaction create bills from orders list page (no by default, yes if set to 'yes' or 1) ► (v20.0)

*'''MAIN_USE_PROPAL_REFCLIENT_FOR_ORDER''' => Copy customer reference from proposal to order. ► (v7.0+)

*'''ORDER_REQUIRE_SOURCE''' => Make the input field "Source of order" mandatory.

*'''ORDER_VALID_AFTER_CLOSE_PROPAL''' => When an order is created on a proposal close, the order is directly defined with status "Validated".

*'''ORDER_ALLOW_EXTERNAL_DOWNLOAD''' => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*'''ORDER_ENABLE_NEGATIVE''' => Can validate an order when amount is negative

*'''THIRDPARTY_PROPAGATE_EXTRAFIELDS_TO_ORDER''' => Copy also extrafields from thirdparty to order (if name match). ► (v11.0+)
*'''ORDER_DEFAULT_NOTE_PUBLIC''' ► Default text in public note
*'''MAIN_REMOVE_DROPDOWN_CREATE_BUTTONS_ON_ORDER''' => Remove the create dropdown button on order card (introduce on v19) to come back with old buttons. '''►''' (v20.0+)

[[#Top|(back to top)]]

 

=PDF Options=

*'''MAIN_ADD_PDF_BACKGROUND''' ► Define this constant with short name of a PDF file (example "<code>mypdf.pdf</code>") that must be saved into directory "<code>documents/mycompany</code>". 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_DISABLE_FORCE_SAVEAS''' ► If your browser always asks to save downloaded files on disk (like PDF), try this this option. File may be displayed directly in your browser. Values : 0= Default (file is auto downloaded), 1= For to output the file into the browser tab, 2= For to output the file into a browser tab open with target_blank

*'''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 servers with low CPU.

*'''MAIN_DISABLE_PDF_COMPRESSION''' ► Disable PDF compression.

*'''MAIN_DOCUMENTS_WITH_PICTURE_WIDTH''' ► Can change size of picture when hidden option <code>MAIN_GENERATE_PROPOSALS_WITH_PICTURE</code> is used. By default value is <code>20</code>.

*'''MAIN_GENERATE_DOCUMENTS_SHOW_FOOT_DETAILS''' ► Adding the company address at the bottom of the page. Disabled by default

*'''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer proposals.
*'''MAIN_GENERATE_ORDERS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer orders.

*'''MAIN_GENERATE_INVOICES_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer invoices.

*'''MAIN_GENERATE_SUPPLIER_PROPOSAL_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier proposals ► (v5.0.3+)
*'''MAIN_GENERATE_SUPPLIER_ORDER_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier orders

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT''' ► Disable VAT on generated documents. like for an association. (Works with crabe template)

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN''' ► Hide column with VAT information but only column not total.

*'''MAIN_INVERT_SENDER_RECIPIENT''' ► Invert sender and recipient in some PDF. Note: This option is set automatically if country if Germany.

*'''MAIN_ODT_AS_PDF''' ► Activate ODT to PDF conversion. Value can be "libreoffice" or "unoconv". Do not use value '''<nowiki/>'jodconverter'<nowiki/>''' any more, as it is declared deprecated and partly not functional, use value '''<nowiki/>'libreoffice'''' instead, it requires only '''soffice''' (OpenOffice or LibreOffice) installed on server (use '''apt install soffice libreoffice-common libreoffice-writer''').

If you got this error: javaldx failed! Warning: failed to read path from javaldx with no return to prompt when running soffice --headless -env:UserInstallation=file:"/tmp" --convert-to pdf --outdir xxx ./yyy.odt, check that directory defined into env:UserInstallation parameters exists and is writeable.

You may also have a look at this page if your server is on Windows: [[Générer automatiquement des documents PDF à partir de fichier ODT avec Doliwamp]]

*'''MAIN_ODT_AS_PDF_DEL_SOURCE''' ► For ODT generation. If set, then initial behaviour is conserved but ODT file is removed when option to convert it as PDF (see previous) is on. Disabled by default

*'''MAIN_PDF_FORCE_FONT''' ► To ignore font defined into language file and force usage of a particular font. For example "<code>DejaVuSans</code>".

*'''MAIN_PDF_FORCE_FONT_SIZE''' ► To force size of font (by default 10). For example "<code>12</code>" ► (v11.0)

*'''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: <code>220,220,200</code>

*'''MAIN_PDF_USE_LARGE_LOGO''' ► Use the original logo with its higher resolution into the PDF instead of the small thumb. This may lead to very very large PDF !

*'''MAIN_USE_BACKGROUND_ON_PDF''' ► Define this constant with short name of an image (example "<code>myimage.jpg</code>") that must be saved into directory "<code>documents/mycompany/logos</code>". This will add this background image into your generated PDF files.

*'''MAIN_USE_COMPANY_NAME_OF_CONTACT''' ► Use contact name and information rather than company

*'''MAIN_PDF_ADDALSOTARGETDETAILS''' ► If 1, add details of recipient on generated PDFs (email, fax, url and phone). Can be useful in cases where a printed order/invoice etc is given to a delivery driver/courier etc.

*'''MAIN_TVAINTRA_IN_SOURCE_ADDRESS''' ► Show VAT N° in source address of PDF to comply with legalities in certain countries. Note that VAT number should be already visible in footer of page ► (v8.0.1+)

*'''MAIN_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► Add optional esign field in pdf propal ► (v8.0+)

*'''MAIN_PROFID1_IN_SOURCE_ADDRESS''' ► Show Professional ID 1 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID2_IN_SOURCE_ADDRESS''' ► Show Professional ID 2 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID3_IN_SOURCE_ADDRESS''' ► Show Professional ID 3 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID4_IN_SOURCE_ADDRESS''' ► Show Professional ID 4 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID5_IN_SOURCE_ADDRESS''' ► Show Professional ID 5 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID6_IN_SOURCE_ADDRESS''' ► Show Professional ID 6 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

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

*'''PDF_BOLD_PRODUCT_REF_AND_PERIOD''' ► Add more visibility (bold) on product ref and period of service in desc. ► (v12.0)

*'''PDF_HIDE_PRODUCT_REF_IN_SUPPLIER_LINES''' ► Modify the use/position of Supplier Ref/Internal Ref with the item Label (name) on PDF documents.

Default (constant not set or Value <code>0</code>): Internal ref followed by supplier ref in brackets."COMPANY-REF-001 (Vendor SKU SUPPLIER-REF-001) - LABEL...".

Value <code>1</code>: Supplier ref only eg."SUPPLIER-REF-001 - LABEL...".

Value <code>2</code>: Supplier ref followed by internal ref in brackets. eg."SUPPLIER-REF-001 (InternalRef COMPANY-REF-001) - LABEL...".

*'''PDF_INCLUDE_ALIAS_IN_THIRDPARTY_NAME''' ► Include alternative/alias name into name on PDF.

*'''PDF_SECURITY_ENCRYPTION''' ► Encrypt PDF produced by dolibarr. See additional parameters :PDF_SECURITY_ENCRYPTION_RIGHTS (block 'modify' or 'copy') - '''PDF_SECURITY_ENCRYPTION_USERPASS''' - '''PDF_SECURITY_ENCRYPTION_OWNERPASS''' (random if not specified) - '''PDF_SECURITY_ENCRYPTION_STRENGTH''' (0 = RC4 40 bit; 1 = RC4 128 bit; 2 = AES 128 bit; 3 = AES 256 bit) - '''PDF_SECURITY_ENCRYPTION_PUBKEYS''' Array of recipients containing public-key certificates ('c') and permissions ('p') - For example: array(array('c' => 'file://../examples/data/cert/tcpdf.crt', 'p' => array('print'))). WARNING: if an 'encrypted PDF' provides a protection against manual change done by mistake, it does NOT provide any protection against modification of your PDF in a security point of view: A protected PDF can still be modified by any advanced PDF editors. Don't forget this: If a software can read the PDF, this software can also rebuild it differently !

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

*'''PDF_USE_ALSO_LANGUAGE_CODE''' ► The value of this constant must be a language code ('fr_FR', 'en_US', 'sa_SA', ...). If set, the PDF document will contains both language (default and the one defined by the constant).
*'''DOC_SHOW_FIRST_SALES_REP''' ► Show the sales representant on header (at least on propal azur and rubis template)
*'''MAIN_PDF_DASH_BETWEEN_LINES'''
*
*'''SHOW_SUBPRODUCT_REF_IN_PDF'''
*'''PDF_HIDE_PRODUCT_LABEL_IN_SUPPLIER_LINES''' ► hide product label in supplier order lines (V15+)
*'''SHIPPING_PDF_DISPLAY_AMOUNT_HT''' ► Show HT unit price and HT total price for lines of PDF shipment

*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_FACTURE''' ► To Hide product description in Customer Invoice
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_COMMANDE''' ► To Hide product description in Sales Order
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_ORDER_SUPPLIER''' ► To Hide product description in Purchase Order
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_INVOICE_SUPPLIER''' ► To Hide product description in Vendor Invoice

*'''PDF_PROPAL_SHOW_PRICE_INCL_TAX''' ► Display price with tax on Proposal(cyan template), Order(eratosthene template), Bill(sponge template) (V17+)

*'''PDF_USE_GETALIASNBPAGE_FOR_TOTAL''' ► Display the page number alias
*'''MAIN_PDF_NO_SENDER_FRAME''' ► Do not display the "sender" mention
*'''MAIN_PDF_HIDE_SENDER_NAME''' ► Do not display the sender name
*'''MAIN_PDF_NO_RECIPENT_FRAME''' ► Do not display BillTo

*'''MULTICURRENCY_SHOW_ALSO_MAIN_CURRENCY_ON_PDF''' ► Show the amount in the 2 currencies on PDF when using the MultiCurrency module
*'''MAIN_PDF_DONOTREPEAT_HEAD ►''' Do not repeat the header of document

[[#Top|(back to top)]]

=Point of Sale (POS)=

*'''CASHDESK_SHOW_KEYPAD''' ► Show a mouse key pad into the 'Simple Point of Sale' module.

*'''POS_ADDON''' ► Set this value to an existing numbering module rule (for example '<code>mod_facture_terre</code>', '<code>mod_facture_mars</code>', ...) to force the numbering module to use for invoice ref definition when invoice is created by the POS. For example setting value <code>POS_ADDON</code> to '<code>mod_facture_terre</code>' will use the numbering module '<code>terre</code>' for invoice generated from POS, whatever is the numbering rule defined into invoice module setup (you can also use POS_NUMBERING_TERRE_FORCE_PREFIX and POS_NUMBERING_MARS_FORCE_PREFIX variable to change the prefix used).

*'''TAKEPOS_ENABLE_SUMUP''' ► Enable the compatibility of TakePOS with the card reader terminal [https://SumUp.fr SumUp]
*'''TAKEPOS_CAN_FORCE_BANK_ACCOUNT_DURING_PAYMENT''' ► Possibility to force the bank account during the payment in TakePOS ► (v13.0)
*'''TAKEPOS_CONTROL_CASH_OPENING''' ► Control the cash opening
*'''TAKEPOS_NUMPAD_FORCE_PAYMENT_ICONS_LABELS'''

[[#Top|(back to top)]]

=Products Module=

*'''CATEGORY_GRAPHSTATS_ON_PRODUCTS''' ► Show graph of products with categories and totals in Products Area screen

*'''MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE''' ► Avoid customs 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.

*'''MAIN_DIRECT_STATUS_UPDATE''' ► Allows you to change the status of the product (''for sale/not for sale for purchase/not for purchase'') directly on the product page via a ''on/off'' switch button. This can be convenient for those who need to quickly disable certain statuses of products without having to go through the editing product page individually. Also can be very useful if used as a filter on the product and product search list. This option doesn't generate a MODIFY trigger, so be careful with external modules. ► (v4.0+)

*'''MAIN_SEARCH_PRODUCT_BY_FOURN_REF''' ► Allow to search a product by supplier ref in document's add line form. ► (>= 8.0)

*'''MAIN_DISABLE_FREE_LINES''' ► Disallow using free lines to add line in documents ► (>= 8.0)

*'''MAIN_SHOW_PRODUCT_ACTIVITY_TRIM''' ► Show Product and Services turnover before for all four quarters tax over recent years recent years on the product area ► (v5.0+)

*'''PRODUIT_DESC_IN_LIST''' ► Show long description of product/service into lists.

*'''PRODUCT_DISABLE_PROPAGATE_CUSTOMER_PRICES_ON_CHILD_COMPANIES''' ► Disable propagation of prices per customer from a customer to its child company.

*'''PRODUCT_DISABLE_PUBLIC_URL''' ► Disable public url in product card ► (v14.0+)
*'''PRODUCT_DISABLE_STOCK_LEVELS''' ► Disable properties of stock limits and desired optimal value on product ► (v14.0+)
*'''PRODUCT_DISABLE_NATURE''' ► Disable nature in product card ► (v14.0+)
*'''PRODUCT_DISABLE_WEIGHT''' ► Disable weight in product card ► (v14.0+)
*'''PRODUCT_DISABLE_PRICES''' ► Disable prices in product card ► (v14.0+)
*'''PRODUCT_DISABLE_ACCOUNTING''' ► Disable accounting in product card ► (v14.0+)
*'''PRODUCT_DISABLE_SIZE''' ► Disable size in product card.

*'''PRODUCT_DISABLE_LENGTH''' ► Disable length in product card ► (v4.0+)

*'''PRODUCT_DISABLE_SURFACE''' ► Disable surface in product card. ► (v4.0+)

*'''PRODUCT_DISABLE_VOLUME''' ► Disable volume in product card.

*'''PRODUCT_DISABLE_CUSTOM_INFO''' ► Disable custom info (custom code and country origin) in product/service card.

*'''PRODUIT_MULTIPRICES_USE_VAT_PER_LEVEL''' ► When option to use price per level/segment is on, this allows to also set a dedicated vat for each price level.

*'''PRODUIT_CUSTOMER_PRICES_BY_QTY''' ► If price per quantity ► ''Experimental''
*'''PRODUIT_CUSTOMER_PRICES_BY_QTY_MULTIPRICES''' ► If price per quantity and customer ► ''Experimental''

*'''PRODUCT_LOT_ENABLE_QUALITY_CONTROL''' ► Enable feature (Display fields for life time and quality control duration) for quality control on product and lot

*'''PRODUCT_MAX_LENGTH_COMBO''' ► Limit the length of the label displayed when adding lines in proposals/invoices/orders

*'''PRODUCT_MAX_VISIBLE_PHOTO''' ► Show a maximum number of product photos (as thumbnails) on the product main card. Example, setting this constant to '<code>5</code>' will show the first five product photos found on the product card.

*'''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''' ► Add other units on products (Use same dictionary as default unit feature) and propagate this unit on line of documents.
*'''MAIN_EDIT_LINE_ALLOW_ALL_UNIT_TYPE ►''' Allow the selection of other unit types when editing the document line

*'''RESOURCE_ON_PRODUCTS''' ► Allow to affect resources on products/services ► (v10.0+)
*'''RESOURCE_ON_SERVICES''' ► Allow to affect resources on products/services ► (v10.0+)
*'''PRODUCT_SHOW_ORIGIN_IN_COMBO''' ► Show origin of products when adding lines in proposals/invoices/orders ► (v12.0+)
*'''PRODUIT_ATTRIBUTES_HIDECHILD''' ► Add option hide child if variantes

*'''PRODUCT_ADD_FORM_ADD_TO''' ► Add a product to a draft proposal/order/invoice, from the product card.
*'''PRODUCT_DISABLE_SELLBY''' ► Hide the Sell by date ► (v13.0+)
*'''PRODUCT_DISABLE_EATBY''' ► Hide the Eat by date ► (v13.0+)

*'''PRODUCT_DENY_CHANGE_PRODUCT_TYPE''' ► Forbid to change the product type

*'''PRODUCT_SORT_BY_CATEGORY''' ► Sort the product by categories instead of by ID
*'''PRODUCT_ADD_NET_MEASURE''' ► Support Net Measure in product's card.php (For real weight, volume or piece; needed for some business ie fruits, vegetables....). Note brut value is already available natively, use this option only if you need 2 weights, 2 volumes, ...for each product) ► (v11.0.1+)
*'''PRODUCT_PRICE_BASE_TYPE''' ► value 'TTC' / 'HT' specify the default value of the price (with or without taxes) ► (v16.0.0+)

*'''PRODUCT_LOAD_EXTRAFIELD_INTO_OBJECTLINES''' ► Load product extrafiled on object lines

*'''PRODUCT_USE_SUB_COST_PRICES_IF_COST_PRICE_EMPTY''' : Calculate the parent product production price by child prices.
*'''PRODUCT_SEARCH_AUTO_SELECT_IF_ONLY_ONE''' : Set to 0 to disable or 1 to enable (by default) the auto select product behavior in combobox when there is only one result.(v21.0+)

[[#Top|(back to top)]]

 

=Projects Module=

*'''PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY''' ► Option related to the combo list Project on elements. It is a list of thirdparty IDs. If set, you can link an object to a project owned by one of this thirdparty in the list.

*'''PROJECT_ALLOW_COMMENT_ON_PROJECT''' ► Add comment feature on a project

*'''PROJECT_ALLOW_COMMENT_ON_TASK''' ► Add comment feature on project task
*'''PROJECT_ALWAYS_DISCARD_CLOSED_PROJECTS_IN_SELECT''' ► Discards closed projects in every select field. A closed project can't be associated to an object ► (v20.0+)

*'''PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS''' ► Option related to the combo list Project on elements. Can link a supplier element (vendor proposal, purchase order, vendor invoice, reception, ...) to any project even if object has a different supplier than the one of the project to link to. See also PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY that is different because it allows to define some given thirdparty ID to allow.

*'''PROJECT_CAN_ALWAYS_LINK_TO_ALL_CUSTOMERS''' ► Option related to the combo list Project on elements. Can link a custom element (proposal, sale order, vendor invoice, shipment, ...) to any project even if object has a different customer than the one of the project to link to.

*'''PROJECT_CREATE_ON_OVERVIEW_DISABLED''' ► Hide the "create ..." button on the overview pagec

*'''PROJECT_DISABLE_UNLINK_FROM_OVERVIEW''' ► Enable removing the button from a link in the project overview. ► (>= v8.0.1)

*'''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''' ► Hide the "link to" form on the overview page ► (v4.0)

*'''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_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_OPEN_ALWAYS_ON_TAB''' ► Set to value 'task', or 'preview' to always open the project on the given tab instead of main tab.

*'''PROJECT_ELEMENTS_FOR_MINUS_MARGIN'''

*'''TIMESPENT_ALWAYS_UPDATE_THM''' ► when it's on always check current time of user to update it in task time line ► (v17.0)

*'''PROJECT_CREATE_NO_DRAFT''' ► when you create project status will be validate ► (v19.0)

*'''PROJECT_ENABLE_SUB_PROJECT''' ► Add support for parent projects ► (v19.0)

[[#Top|(back to top)]]

=Proposals Module=

*'''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Add a picture of the product (the first one found if there are several) into the generated PDF of proposals. Note that using this will reduce the available width for the product description.

*'''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_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► add optional esign field in pdf propal ► (v8.0+)

*'''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.

*'''PROPAL_DISABLE_SIGNATURE''' ► Do no show the box for signature.
*'''PROPAL_SIGNATURE_ON_SPECIFIC_PAGE ►''' Will show the signature on which page you wanted . Set to 1 will show on first page , set to -1 will show on last second page . ( If '''PROPAL_SIGNATURE_ON_ALL_PAGES''' is enabled, the '''PROPAL_SIGNATURE_ON_SPECIFIC_PAGE''' setting will be ignored.)
*'''PROPAL_SIGNATURE_ON_ALL_PAGES ►''' Will show the signature on every pages .

*'''PRODUIT_PDF_MERGE_PROPAL''' ► When generating the proposal PDF, all PDFs linked to products linked to proposal are also included into final PDF

*'''PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*'''PROPOSAL_AUTO_ADD_AUTHOR_AS_CONTACT''' ► Add Proposal Author as user contact follow proposal

*'''PROPOSAL_PDF_HIDE_PAYMENTTERM''' ► Do not show the payment term on proposal ► (v11.0+)

*'''PROPOSAL_PDF_HIDE_PAYMENTMODE''' ► Do not show the payment mode on proposal ► (v11.0+)

*'''WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES''' ► Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.
*'''PROPAL_REOPEN_UNSIGNED_ONLY''' ► Do not allow reopening of signed (or billed) proposals. (V15)
*'''PROPOSAL_ARE_NOT_BILLABLE''' ► Disable billing button on proposals (V15)
*'''PROPAL_DEFAULT_NOTE_PUBLIC''' ► Default text in public note

[[#Top|(back to top)]]

 

=Services Module=

*'''SERVICE_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country. For french speaking people, see also the page [[Loi_européenne_TVA_Vente_à_Distance_VAD_et_e-commerce_BtoC]].

*'''MAIN_FILL_SERVICE_DATES_FROM_LAST_SERVICE_LINE''' ► (v13.0) On add line form add a button to fill service dates from the last service line

[[#Top|(back to top)]]

=Shipments=

*'''STOCK_WAREHOUSE_NOT_REQUIRED_FOR_SHIPMENTS''' ► If set, you can add a shipment line, with no stock source defined. ► (>= 8.0.1)

*'''SHIPMENT_GETS_ALL_ORDER_PRODUCTS''' ► Add all order lines in shipment, including the one with 0 in quantity
*'''SHIPPING_PDF_HIDE_ORDERED''' ►Hide column quantity ordered on shipment pdf (>=15.0)
*'''STOCK_SUPPORTS_SERVICES''' ►Allow to manage services into warehouse and allow to ship services
*'''SHIPMENT_SUPPORTS_SERVICES''' ►Allow to ship services without stock (>=19.0)
*'''SHIPPING_DISPLAY_STOCK_ENTRY_DATE''' ►Display date entry stock exped and sort in date order (>=19.0)

[[#Top|(back to top)]]

=Stocks=

*'''SUPPLIER_ORDER_DISABLE_STOCK_DISPATCH_WHEN_TOTAL_REACHED''' ► Disable stock dispatch when total expected was already received

*'''STOCK_EXCLUDE_VIRTUAL_PRODUCTS''' ► If product is a virtual product, we do not manage stock for it.
*'''STOCK_ALLOW_DELETE_OF_MOVEMENT''' ► Enable massaction option to delete in movements list (be carefull !!).

*'''ENTREPOT_EXTRA_STATUS''' ► Instead of the 2 status (Closed, Open), a Warehouse has 3 status: Closed, Open (for all movements), Open (for internal movement only). Internal movement only means you can't use the warehouse to make shipment or receptions.

*'''SUPPLIER_ORDER_STATUS_FOR_VIRTUAL_STOCK''' ► For the calculation of virtual stocks, by default supplier orders with the status 3 (ordered) and 4 (partially received) are used. You can enter the list of statuses to be taken into account separated by commas for this calculation (example: 0,1,2,3)

*'''STOCK_MOVEMENT_LIST_HIDE_UNIT_PRICE''' ► to hide unit price on some pages (V15+)

*'''DISABLE_QTY_OVERWRITE''' ► Disable quantity overwrites on inventories ► (v19.0)
*'''MAIN_WAREHOUSE_LIST_DISPLAY_MODE''' ► Change warehouse select list display mode ► (v21.0) (see github pull request [https://github.com/Dolibarr/dolibarr/pull/31013 #31013] for more info)
**0 : Default behavior, display parents of warehouse
**1 : Display only current warehouse label only
**2 : Display last parent warehouse label

[[#Top|(back to top)]]

=Suppliers Module=

*'''FOURN_PRODUCT_AVAILABILITY''' ► On the Suppliers price page of the products, activate the supplier product availability. ''This is duplicate feature with delivery_delay introduced with 3.8.''

*'''RELOAD_PAGE_ON_SUPPLIER_CHANGE''' ► On creation of a supplier order/invoice, reload form with supplier-specific details when supplier is selected from drop-down list.

*'''SUPPLIER_INVOICE_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier invoice to only those with a buying price defined for that supplier. ► (v6.0+)

*'''SUPPLIER_ORDER_AUTOADD_USER_CONTACT''' ► Add user approving supplier order as a contact automatically.

*'''SUPPLIER_ORDER_DEFAULT_PAYMENT_MODE_ID''' ► Set the default payment method for suppliers (<code>rowid</code> in table <code>llx_c_paiement</code>).

*'''SUPPLIER_ORDER_USE_DISPATCH_STATUS''' ► Add a status on each dispatch order line when receiving products from suppliers ► (v4.0+)

*'''SUPPLIER_ORDER_NO_DIRECT_APPROVE''' ► No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

*'''SUPPLIER_ORDER_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier order to only those with a buying price defined for that supplier. ► (v6.0+)

*'''SUPPLIER_ORDER_EDIT_BUYINGPRICE_DURING_RECEIPT''' ► Can modify the buying price used for PMP calculation when making a stock reception on a supplier order. ► (v6.0+)
*'''SUPPLIER_PROPOSAL_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier proposal to only those with a buying price defined for that supplier. ► (v6.0+)
*'''SUPPLIER_ORDER_MORE_THAN_WISHED''' ► The supplier order status is set to "Totally received" even if there are more products received than ordered. ► (v15.0+)

*'''DISPLAY_DISCOUNTED_SUPPLIER_PRICE''' ► Allow to display discounted supplier price when searching product in supplier documents ► (v10.0)

*'''MAIN_CAN_EDIT_SUPPLIER_ON_SUPPLIER_ORDER''' ► Allow to change the supplier on a draft supplier order ► (v10.0)

*'''SUPPLIER_PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD'''

*'''SUPPLIER_ORDER_CAN_UPDATE_BUYINGPRICE_DURING_RECEIPT''' ► Allow to change price on receipt ► (v19.0)

*'''SUPPLIER_HIDE_SUPPLIER_OBJECTLINES''' ► Hide the supplier information on objectlines (invoices, etc..) ► (v19.0)

[[#Top|(back to top)]]

=Third Parties Module=

*'''COMPANY_AQUARIUM_CLEAN_REGEX''' ► Add a REGEX rule on the third parties names. It applies a regex replacement pattern on generated code if COMPANY_AQUARIUM_CLEAN_REGEX is set. Value must be a regex with parenthesis. The part into parenthesis is kept, the rest removed. For example if COMPANY_AQUARIUM_CLEAN_REGEX = '<code>^..(..)..(.*)</code>' the first char and second char are removed and the char 5 and 6 too ► (>= 8.0.1)

*'''MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES''' ► See in Global options section.

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► See in Global options section.

*'''SOCIETE_EMAIL_MANDATORY''' ► E-mail is a mandatory field when creating a thirdparty

*'''SOCIETE_DISABLE_CUSTOMERS''' ► Remove all menu and features related to customers

*'''SOCIETE_DISABLE_PROSPECTS''' ► Remove all menu and features related to prospects
*'''SOCIETE_DISABLE_PROSPECTSCUSTOMERS ►''' Remove the status "Customer/Prospect" when thirdparties creation or modification

*'''SOCIETE_DISABLE_STATE''' ► Do not use field "state/province"

*'''SOCIETE_SORT_ON_TYPEENT''' ► The combo list of "type of third party" is sorted on alphabetical order instead of the field "position" that appears into dictionary instead.

*'''SOCIETE_ASK_FOR_SHIPPING_METHOD''' ► Shipping method can be predefined on customer card and will be used as default on order creation
*'''SOCIETE_ADD_REF_IN_LIST''' ► Displays the code before the name in the lists ► Value 1 -> Code + name + alias ou Code + name if colone alias 2 -> Code + alias 3 -> Alias

*'''THIRDPARTY_CAN_HAVE_CATEGORY_EVEN_IF_NOT_CUSTOMER_PROSPECT_SUPPLIER''' ► Possible to add Categories to third parties that are not customer, prospect or supplier.

*'''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.

*'''THIRDPARTY_NOTCUSTOMERPROSPECT_BY_DEFAULT''' ► Do not set status "Customer/Prospect" to "on" when creating a new third party from menu "New third party".

*'''THIRDPARTY_INCLUDE_PARENT_IN_LINKTO''' ► Search also for elements on parent third party when using the "link to" object feature.

*'''THIRDPARTY_INCLUDE_PROJECT_THIRDPARY_IN_LINKTO''' ► Search also for elements on third party that own the project of the current element when using the "link to" object feature (if project is owned by a different thirdparty than current one).

*'''THIRDPARTY_LOGO_ALLOW_EXTERNAL_DOWNLOAD''' ► When a logo is uploaded, a share key is automatically set so the file can be downloaded using the share key.

*'''THIRDPARTY_SUGGEST_ALSO_ADDRESS_CREATION''' ► Enabled contact creation on third-party create card
*'''THIRDPARTY_QUICKSEARCH_ON_FIELDS''' ► Personalized search criteria ► Example: $conf->global->THIRDPARTY_QUICKSEARCH_ON_FIELDS = 's.nom=ThirdPartyName;s.name_alias=AliasNameShort;s.code_client=CustomerCode'
*'''MEMBER_CAN_CONVERT_CUSTOMERS_TO_MEMBERS''' ► Enabled member creation on third-party create card
*'''SOCIETE_DISABLE_PARENTCOMPANY''' ► Disables attachment to a parent company.
*'''THIRDPARTY_CUSTOMERPROSPECT_BY_DEFAULT''' ► Set the third party to customer by default
*'''THIRDPARTY_SUPPLIER_BY_DEFAULT''' ► Set the third party to supplier by default
*'''THIRDPARTY_CUSTOMERTYPE_BY_DEFAULT''' ► Set the third party type by default (3 = customer & prospect / 2 = prospect / 1 = customer )
*'''CONTACT_DISABLE_PERSONALINFO''' ► Disable Personal data on contact page
*'''SOCIETE_DISABLE_WORKFORCE''' ► Disable work force selector on society page
*'''SOCIETE_SHOW_VAT_IN_LIST''' ► display VAT number in combo list of thirdparties ► (V15+)
*'''THIRDPARTY_DEFAULT_CREATE_CONTACT''' ► When set, a contact is created at the creation of an individual third party ► (v14.0)

*'''MAIN_SUPPORT_SHARED_CONTACT_BETWEEN_THIRDPARTIES''' ► Able to share contact between several third parties
*'''THIRDPARTY_CUSTOMERCODE_EQUALS_MEMBERREF''' ► When creating third parties out of members, the customer code is set equal to the member Ref. ► (v22.0)
*'''SOCIETE_NO_SYNC_LINKED_MEMBER''' ► If set, changes to a third party will not be synchronized to a linked member. ► (v23.0)

[[#Top|(back to top)]]

=Ticket Module=

*'''TICKET_SHOW_MESSAGES_ON_CARD''' ►Display all ticket related messages on the main ticket card. ► (>= 10.0)
*'''TICKET_AUTO_ASSIGN_CONTRACT_CREATE''' ►Automatically create a contract linked to the ticket ► (>= 10.0)
*'''TICKET_AUTO_CREATE_FICHINTER_CREATE''' ►Automatically create an intervention linked to the ticket ► (>= 10.0)
*'''TICKET_AUTO_ASSIGN_USER_CREATE''' '''►''' (>= 21.0) 0=No auto assignement, 1=Auto assign current user if no user was set, 2=Auto assign current user even if another user was set.
*'''TICKET_CHECK_NOTIFY_THIRDPARTY_AT_CREATION''' ►Automatically check "notify thirdparty at creation" ( >=16)
*'''TICKETS_MESSAGE_FORCE_MAIL''' ► Pre check email sending on ticket message (>=15)
*'''TICKET_SEND_PRIVATE_EMAIL ►''' Allow a private message to be sent by mail (>=17)
*'''TICKET_LIMIT_VIEW_ASSIGNED_ONLY''' '''►''' Only display tickets assigned to the user
*'''TICKET_ADD_AUTHOR_AS_CONTACT''' '''►''' If set to 1: Automatically adds the author as internal contact. If set to 2: Automatically adds the author as external contact if external user. (>=20)
*'''TICKET_ASSIGN_CONTACT_TO_MESSAGE''' '''►''' If known, the external contact is assigned to the message. (>=19)
*'''TICKET_ALLOW_CLASSIFICATION_MODIFICATION_EVEN_IF_CLOSED''' '''►'''Allow modify ticket classification even if closed. (>=19)
*'''WORKFLOW_TICKET_CLOSE_INTERVENTION''' ►On ticket close, automatically close an intervention linked to the ticket
*'''TICKET_INCLUDE_SUSPENDED_STATUS''' ► Use ticket suspended status (>=19)
*'''TICKET_INCLUDE_LINK_TO_PUBLIC_INTERFACE_IN_MESSAGE''' ► Add a link in bottom of emails sent from ticket page with link to public ticket admin tool (>=22)

=VAT Report=

*'''MAIN_INCLUDE_ZERO_VAT_IN_REPORTS''' ► Include lines with VAT to 0% (for "auto-liquidation" in EEC) ► (v8.0.3+)

[[#Top|(back to top)]]

=Website Module=

*'''WEBSITE_USE_WEBSITE_ACCOUNTS''' ► Add a table and a tab to manage some accounts for websites to a third party
*'''WEBSITE_ALLOW_OVERWRITE_GIT_SOURCE''' ► Add a button to export a website over the GIT sources
*'''WEBSITE_ADD_CSS_TO_BODY''' ► Add a CSS class to the body tag of websites

[[#Top|(back to top)]]

 

=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 guaranteed with this. Also if the image is removed or renamed by the image hosting service, your proposal, order or invoice will be broken.
*'''FCKEDITOR_ALLOW_ANY_CONTENT''' ► Allow to enter any content. However, this will totally disable content filtering which is one of the most important CKEditor features. You can use this to keep all your tags and attributes in the html content.
*'''FCKEDITOR_ENABLE_SCAYT_AUTOSTARTUP''' ► Allow to activate the SpellCheckAsYouType (SCAYT) plugins of CKEditor i.e an automatic spell checking. The value to activate this option is 1.
*'''MAIN_ALLOW_WYSIWYG_LOCAL_MEDIAS_ON_PRIVATE_NETWORK''' ► By default, you can add medias links (img src or other) into the rich text content editor, but you can't add links like that use a local host like "https://localhost/file". If you set this option to 1, you can.
*'''MAIN_ALLOW_WYSIWYG_EVEN_ON_UNSECURED_EXTERNAL_HTTP_URL''' ► By default, you can add medias links (img src or other) into the rich text content editor, but not if the link is a unsecure "http" url (not https) and your Dolibarr is http. If you set this option to 1, you can.

[[#Top|(back to top)]]

=STRIPE Module=

*'''STRIPE_FORCE_VERSION''' ► Force the STRIPE version. For Example: "2019-09-09" (v11+)
*'''STRIPE_REUSE_EXISTING_INTENT_IF_FOUND''' ► With this, you will have idempotency key but the payment intention will be reuse and not Generate again (13+)

[[#Top|(back to top)]]

=ClickToDial Module=

*'''CLICKTODIAL_FORCENEWTARGET''' ► Open in new page.

[[#Top|(back to top)]]

 

=For SaaS / Cloud hosting integrators=

The following options are useless for a common usage of Dolibarr. But they are usefull if you plan to host / provide Dolibarr instances as Software As A Service (SAAS) to your customers.

*'''CRON_DISABLE_KEY_CHANGE''' ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*'''CRON_DISABLE_TUTORIAL_CRON''' ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*'''CRON_WARNING_DELAY_HOURS''' ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

*'''MAILING_NO_USING_PHPMAIL''' ► To avoid bad use of the emailing module, it is recommended to set this option to 1 (This option is described previously). Also you can complete the message visible by customers when they try to setup the SMTP credentials of their Dolibarr by using the constant MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS (This option is described previously). For example, you can point to a FAQ on your website.

*'''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► If you have set a system limit on number of recipients on your system, you can set also this option to match the same value, so users will be informed: So '''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' restricts sending of 1 email message to <code>x</code> recipients for the same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include a ton of recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available. Note that this is not a hard limit; it is just the quantity that will be displayed on warnings on screen. For a real limit, this must be implemented into the system.

*'''MAILING_LIMIT_SENDBYDAY''' ► This is a limit of number of emails, an instance can send. Note that this is not a hard limit; it is just the quantity that will be displayed on warnings on screen. For a real limit, this must be implemented into the system.

*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Set this value to a translation key. Then add translation keys into the instance so user will see a message when into the email setup page. For example, you can set a message to say: ''Warning: To avoid abuse, when using default setup, you are restricted to 500 emails per day for all your application (account may be suspended in case of violation of this rule. You can setup application to use your own SMTP server for sending email so you want have no restriction at all (see menu Home-Setup-Emails)''

*'''MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE''' ► If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock and remove the upgrade.unlock so the administration tools like install.php, upgrade.php and repair.php can't be used on your customer instance (until the install.lock file is deleted or the upgrade.unlock file is created).

*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted, separated by a comma. So, when your customer go into the Email setup area:
**If he has chosen mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he has chosen smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option '''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD'''.

You can also provide a list of URLs that return just an IP instead of a list of hardcoded IP. So you can for example set 1 url that contact a whoami service that return the public IP of server and another one doing the one on a IPv6 address, so on the setup page, the public IP adress of the server will always be uptodate for both ipv4 and ipv6 (Example: "https://ipv4.server.com/_service_showmyip.php,https://ipv6.server.com/_service_showmyip.php")

*'''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD''' ► Set here the string to add in the SPF record This string will be shown into a help message when the user in in the setup of email page and has choose a method using an external SMTP server.

*'''MAIN_FIRST_PING_OK_ID''' ► Set this value to "disabled" to remove completely any ping after a complete setup.

*'''MAIN_FILECHECK_LOCAL_SUFFIX''' and '''MAIN_FILECHECK_LOCAL_EXT''' ► If you offer a customized or patched version of Dolibarr, when the user will use the tool to check the integrity of files, the default xml file name used for signature checking will be the official file provided by the Dolibarr team, so it does not includes your own changes. To have the suggested signature file being your own file, you can set the constant MAIN_FILECHECK_LOCAL_SUFFIX to a suffix. For example, set this to "'''-mysaassolution'''". So, when the user will use the file integrity tool, the default file to check for signature will be "'''/install/filelist-10.0.2-mysaassolution.xml'''" instead of "'''/install/filelist-10.0.2.xml'''". All you have to do is generate the signature file '''mysaassolution''' using the tool '''build/generate_filelist_xml.php''' and put this file into the install directory of your customer instance. Doing this, your customer, and yourself, will be able to check if a file was modified without being disturbed by false alerts due to your customized files or patches (they will be included in the signature used for check). Also, if you want to zip the customized signature file into "'''/install/filelist-10.0.2-mysaassolution.xml.zip'''", you can set the constant MAIN_FILECHECK_LOCAL_EXT to '.zip'.

*'''MAIN_HIDE_WARNING_TO_ENCOURAGE_SMTP_SETUP''' ► Set to 1 by default (so warning is hidden). You can set it to 0 to show a warning to encourage admin to set its own SMTP service.

*'''MAIN_MAIL_SENDMODE_password''' ► To force the mode to send the email on the "password forgotten" page. So you can decide to use php mail or SMTP method for this specific use case.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► If set to N, the warning saying modules are not activated will be shown if number of activated module is < N (Having this variable not defined is same than having it set to 1). This may be usefull if you preinstall an application with some modules already loaded by default and you want to keep the warning to be sure the user will enable other modules he need, even if some modules are already enabed.
*'''MAIN_SETUP_MODULES_DESC''' ► If your installation is already done with activated module, the help message to explain how to enable a module on the setup page is hidden. You can keep it visible by adding this option to 1.

*'''MAIN_NO_UPGRADE_REDIRECT_ON_LEVEL_3_CHANGE''' ► The page to make the migration is not shown automatically when you deploy files of version X.Y.Z+delta over an installation with a database version X.Y.Z. The upgrade page will be shown automatically only if there is a change on value of X or Y in version.

*'''SYSLOG_DISABLE_LOGHANDLER_SYSLOG''' ► Set this to 1 to disable usage of syslog (having all customer instances logging in the same system file is not a good idea).

*'''WEBSITE_REPLACE_INFO_ABOUT_USAGE_WITH_WEBSERVER''' ► Put here a text or a translation key of a text to show when the user will use the feature "Deploy" when he want to deploy a website done with Dolibarr CMS. So you can, for example, show him a message that this feature is not part of its subscription and putting a website online may need a complementary subscription.

[[#Top|(back to top)]]

Verticaux Dolibarr

2025-11-28T15:44:37Z

Iouston: /* Sciences - Recherche */ mise en page

{{TemplateDocDevFr}}
{{TemplateDocUtil}}

<div class="opacitymedium">Le but de cette page est de recenser les différents solutions "Verticales" (solutions ultra spécialisées couvrant les besoins d'un métier en particulier) et basée sur Dolibarr, que ce soit sous son propre nom ou simplement en tant que module complémentaires.</div>

=Médical - Santé=
==DoliMed==
DoliMed est un module transformant Dolibarr pour gérer un cabinet médical, à destination du ou des médecins, kiné, infirmières, ...

Site Web: [https://www.dolimed.com DoliMed]

Lien vers le module: https://www.dolistore.com/product.php?id=1764&title=cabinet-medical

=Gestion des risques - Document unique=
==DiGiRisk==
Site web: [https://www.digirisk.com/ DigiRisk]

Lien vers lemodule: https://www.dolistore.com/product.php?id=1034&title=digirisk

=Gestion de Garage=
==Garage==
Lien vers le module: https://www.dolistore.com/product.php?id=2553

=Gestion de locations immobiliaires=
==UltimateImmo==
Module permettant la gestion des biens immobiliers, suivi des locations, ...

Lien vers le module: https://www.dolistore.com/product.php?id=2488&title=ultimateimmo-22-0-0

=Gestion de locations de matériel=
==DoliRent==
Module permettant la gestion de location de matériel.

Lien vers le module: https://www.dolistore.com/product.php?id=448

=Agence de location de véhicule=
==Gestion des véhicules==
Lien vers le module: https://www.dolistore.com/product.php?id=747

=Centre de formation=
==AgeFodd==
Site web: https://solutions.atm-consulting.fr/dolibarr-module/agefodd-gestion-de-formations

Lien vers le module: https://www.dolistore.com/product.php?id=2379

=Sciences - Recherche=

== Signalement tique | Tiquothèque ==
Recensement contextualisé des signalement de piqûres de tiques sur les humains et les animaux dans le cadre d'un programme de recherche participative citoyenne, gestion des échantillons de tiques piqueuses dans le cadre de la bio banque pour fournir aux chercheurs le contexte de la piqûre et la tique responsable de la piqûre.

Site web : https://www.citique.fr

Verticaux Dolibarr

2025-11-28T15:43:48Z

Iouston: /* Sciences - Recherche */

{{TemplateDocDevFr}}
{{TemplateDocUtil}}

<div class="opacitymedium">Le but de cette page est de recenser les différents solutions "Verticales" (solutions ultra spécialisées couvrant les besoins d'un métier en particulier) et basée sur Dolibarr, que ce soit sous son propre nom ou simplement en tant que module complémentaires.</div>

=Médical - Santé=
==DoliMed==
DoliMed est un module transformant Dolibarr pour gérer un cabinet médical, à destination du ou des médecins, kiné, infirmières, ...

Site Web: [https://www.dolimed.com DoliMed]

Lien vers le module: https://www.dolistore.com/product.php?id=1764&title=cabinet-medical

=Gestion des risques - Document unique=
==DiGiRisk==
Site web: [https://www.digirisk.com/ DigiRisk]

Lien vers lemodule: https://www.dolistore.com/product.php?id=1034&title=digirisk

=Gestion de Garage=
==Garage==
Lien vers le module: https://www.dolistore.com/product.php?id=2553

=Gestion de locations immobiliaires=
==UltimateImmo==
Module permettant la gestion des biens immobiliers, suivi des locations, ...

Lien vers le module: https://www.dolistore.com/product.php?id=2488&title=ultimateimmo-22-0-0

=Gestion de locations de matériel=
==DoliRent==
Module permettant la gestion de location de matériel.

Lien vers le module: https://www.dolistore.com/product.php?id=448

=Agence de location de véhicule=
==Gestion des véhicules==
Lien vers le module: https://www.dolistore.com/product.php?id=747

=Centre de formation=
==AgeFodd==
Site web: https://solutions.atm-consulting.fr/dolibarr-module/agefodd-gestion-de-formations

Lien vers le module: https://www.dolistore.com/product.php?id=2379

=Sciences - Recherche=
Signalement tique : Recensement contextualisé des signalement de piqûres de tiques sur les humains et les animaux dans le cadre d'un programme de recherche participative citoyenne, gestion des échantillons de tiques piqueuses dans le cadre de la bio banque pour fournir aux chercheurs le contexte de la piqûre et la tique responsable de la piqûre.

Site web : https://www.citique.fr /

Verticaux Dolibarr

2025-11-28T15:43:04Z

Iouston: Ajout de la section science et recherche avec signalement tique / citique

{{TemplateDocDevFr}}
{{TemplateDocUtil}}

<div class="opacitymedium">Le but de cette page est de recenser les différents solutions "Verticales" (solutions ultra spécialisées couvrant les besoins d'un métier en particulier) et basée sur Dolibarr, que ce soit sous son propre nom ou simplement en tant que module complémentaires.</div>

=Médical - Santé=
==DoliMed==
DoliMed est un module transformant Dolibarr pour gérer un cabinet médical, à destination du ou des médecins, kiné, infirmières, ...

Site Web: [https://www.dolimed.com DoliMed]

Lien vers le module: https://www.dolistore.com/product.php?id=1764&title=cabinet-medical

=Gestion des risques - Document unique=
==DiGiRisk==
Site web: [https://www.digirisk.com/ DigiRisk]

Lien vers lemodule: https://www.dolistore.com/product.php?id=1034&title=digirisk

=Gestion de Garage=
==Garage==
Lien vers le module: https://www.dolistore.com/product.php?id=2553

=Gestion de locations immobiliaires=
==UltimateImmo==
Module permettant la gestion des biens immobiliers, suivi des locations, ...

Lien vers le module: https://www.dolistore.com/product.php?id=2488&title=ultimateimmo-22-0-0

=Gestion de locations de matériel=
==DoliRent==
Module permettant la gestion de location de matériel.

Lien vers le module: https://www.dolistore.com/product.php?id=448

=Agence de location de véhicule=
==Gestion des véhicules==
Lien vers le module: https://www.dolistore.com/product.php?id=747

=Centre de formation=
==AgeFodd==
Site web: https://solutions.atm-consulting.fr/dolibarr-module/agefodd-gestion-de-formations

Lien vers le module: https://www.dolistore.com/product.php?id=2379

== Sciences - Recherche ==
Signalement tique : Recensement contextualisé des signalement de piqûres de tiques sur les humains et les animaux dans le cadre d'un programme de recherche participative citoyenne, gestion des échantillons de tiques piqueuses dans le cadre de la bio banque pour fournir aux chercheurs le contexte de la piqûre et la tique responsable de la piqûre.

Site web : https://www.citique.fr /

Système de substitution de variables

2025-07-17T07:39:13Z

Iouston: add an example for mymodule_completesubstitutionarray() function

[[en:Variable_substitution_system]]
[[zh:变量替换系统]]


{{TemplateDocUtil}}
{{TemplateDocDev}}

Les variables de substitutions sont des mots clés qui peuvent être utilisés à de nombreux endroits dans Dolibarr pour être remplacés ultérieurement.
On s'en sert par exemple dans les modèles d'emails ou de texte de configuration pour qu'un texte soit personnalisé au moment de son affichage ou de son envoi pour les emails.

=Variables de substitution disponibles=

*

{| class="wikitable sortable"
|+
!Variable
!Valeur Affichée
!Note
!Dolibarr Mini
|-
|__USER_SIGNATURE__
|Ma super signature
|Signature de l'utilisateur
|
|-
|__USER_ID__
|1
|ID de l'utilisateur
|
|-
|__USER_LOGIN__
|doli9
|Login de l'utilisateur
|
|-
|__USER_LASTNAME__
|Admin
|Nom de l'utilisateur
|
|-
|__USER_FIRSTNAME__
|Super
|Prénom de l'utilisateur
|
|-
|__USER_FULLNAME__
|SuperAdmin
|Nom complet de l'utilisateur
|
|-
|__USER_SUPERVISOR_ID__
|1
|ID du superviseur
|
|-
|__USER_REMOTE_IP__
|xxx.xxx.xxx.xxx
|IP de l'utilisateur
|
|-
|__MYCOMPANY_NAME__
|Ma petite entreprise
|Nom de l'entreprise
|
|-
|__MYCOMPANY_EMAIL__
|contact@monentreprise.fr
|Adresse email de contact de mon entreprise
|
|-
|__MYCOMPANY_PROFID1__
|12345678
|Id. prof. 1 (TIN)
|
|-
|__MYCOMPANY_PROFID2__
|12345678
|Id. prof. 2 (PAN)
|
|-
|__MYCOMPANY_PROFID3__
|12345678
|Id. prof. 3 (SRVC TAX)
|
|-
|__MYCOMPANY_PROFID4__
|12345678
|Id. prof. 4
|
|-
|__MYCOMPANY_PROFID5__
|12345678
|Id. prof. 5
|
|-
|__MYCOMPANY_PROFID6__
|FR12345678
|Numéro de TVA
|
|-
|__MYCOMPANY_CAPITAL__
|10000
|Capital de mon entreprise
|
|-
|__MYCOMPANY_FULLADDRESS__
|12 rue laurent 75001 Paris France
|Adresse complète de mon entreprise
|
|-
|__MYCOMPANY_ADDRESS__
|12 rue laurent
|Rue et numéro de rue de mon entreprise
|
|-
|__MYCOMPANY_ZIP__
|75001
|Code postale de mon entreprise
|
|-
|__MYCOMPANY_TOWN__
|Paris
|Ville de mon entreprise
|
|-
|__MYCOMPANY_COUNTRY__
|France
|Pays de mon entreprise
|
|-
|__MYCOMPANY_COUNTRY_ID__
|1
|Identifiant du pays de mon entreprise
|
|-
|__MYCOMPANY_CURRENCY_CODE__
|EUR
|Devise principale de mon entreprise
|
|-
|__ID__
|1
|ID de l'object
|
|-
|__REF__
|1234
|Référence de l'objet
|
|-
|__REF_CLIENT__
|1234
|Référence client de l'objet
|
|-
|__REF_SUPPLIER__
|1234
|Référence fournisseur de l'objet
|
|-
|__EXTRAFIELD_XXX__
|?????
|Attribut supplémentaire de l'object (XXX doit être remplacé par le code de l'attribut)
|
|-
|__THIRDPARTY_ID__
|1
|ID du tiers
|
|-
|__THIRDPARTY_NAME__
|MonClient
|Nom du tiers
|
|-
|__THIRDPARTY_NAME_ALIAS__
|MonC
|Alias du tiers
|
|-
|__THIRDPARTY_EMAIL__
|contact@monclient.com
|Adresse email du tiers
|
|-
|__CONTACT_NAME_CUSTOMER__
|civilité prénom nom
|Genre prénom et nom du contact de type 'contact suivi proposition' d'une proposition commerciale
|
|-
|__PROJECT_ID__
|1
|ID du projet de l'objet
|
|-
|__PROJECT_REF__
|1234
|Référence du projet de l'objet
|
|-
|__PROJECT_NAME__
|MonProjet
|Nom du projet de l'objet
|
|-
|__CONTRACT_HIGHEST_PLANNED_START_DATE__
|01/01/2020
|Date la plus tardive prévue pour le démarrage du contrat
|
|-
|__CONTRACT_HIGHEST_PLANNED_START_DATETIME__
|1/1/2020 13h
|Date et heure la plus tardive prévue pour le démarrage du contrat
|
|-
|__CONTRACT_LOWEST_EXPIRATION_DATE__
|01/01/2020
|Date la plus proche pour l'expiration du contrat
|
|-
|__CONTRACT_LOWEST_EXPIRATION_DATETIME__
|1/1/2020 13h
|Date et heure la plus proche pour l'expiration du contrat
|
|-
|__ONLINE_PAYMENT_URL__
|<nowiki>https://mondoli.com/payment</nowiki>
|Adresse du paiement en ligne (si applicable)
|
|-
|__ONLINE_PAYMENT_TEXT_AND_URL__
|Cliquez pour payer
|Texte et adresse du paiement en ligne (si applicable)
|
|-
|__SECUREKEYPAYMENT__
|
|Clé de sécurité pour le paiement (si la clé n'est pas unique par enregistrement)
|
|-
|__SECUREKEYPAYMENT_MEMBER__
|
|Clé de sécurité pour le paiement de l'abonnement d'un membre (une clé par membre)
|
|-
|__SECUREKEYPAYMENT_ORDER__
|
|Clé de sécurité pour le paiement d'une commande
|
|-
|__SECUREKEYPAYMENT_INVOICE__
|
|Clé de sécurité pour le paiement d'une facture
|
|-
|__SECUREKEYPAYMENT_CONTRACTLINE__
|
|Clé de sécurité pour le paiement d'un contrat
|
|-
|__DIRECTDOWNLOAD_URL_PROPOSAL__
|<nowiki>https://mondoli.com/devis.pdf</nowiki>
|URL de téléchargement direct d'un devis
|
|-
|__DIRECTDOWNLOAD_URL_ORDER__
|<nowiki>http://mondoli.com/commande.pdf</nowiki>
|URL de téléchargement direct d'une commande
|
|-
|__DIRECTDOWNLOAD_URL_INVOICE__
|<nowiki>http://mondoli.com/facture.pdf</nowiki>
|URL de téléchargement direct d'une facture. Pour cela, il faut que le paramètre INVOICE_ALLOW_EXTERNAL_DOWNLOAD soit configuré pour permettre de générer le lien.
|
|-
|__SHIPPINGTRACKNUM__
|XXXXX
|Numéro de suivi du colis
|
|-
|__SHIPPINGTRACKNUMURL__
|<nowiki>http://trackingcompagny.com/XXXXX</nowiki>
|URL de suivi du colis
|
|-
|__DATE_YMD__
|01/01/2020
|Date d'aujourd'hui
|
|-
|__DATE_DUE_YMD__
|01/01/2020
|Date d'échéance
|
|-
|__AMOUNT__ ->
|1243,34
|Montant total
|
|-
|__AMOUNT_EXCL_TAX__ -> __AMOUNT_EXCL_TAX__
|1234,45
|Montant total hors taxe
|
|-
|__AMOUNT_VAT__ -> __AMOUNT_VAT__
|123,4
|Montant TVA
|
|-
|__AMOUNT_FORMATED__
|1243,34 €
|Montant total formaté
|
|-
|__AMOUNT_EXCL_TAX_FORMATED__
|1234,45 €
|Montant total hors taxe formaté
|
|-
|__AMOUNT_VAT_FORMATED__ -> __AMOUNT_VAT_FORMATED__
|123,4 €
|Montant TVA formaté
|
|-
|__DAY__
|12
|Jours actuel (chiffre)
|
|-
|__DAY_TEXT__
|Mardi
|Jours actuel (texte)
|
|-
|__DAY_TEXT_SHORT__
|Ma
|Jours actuel en texte abrégé
|
|-
|__DAY_TEXT_MIN__
|M
|Jours actuel en texte en une lettre
|
|-
|__MONTH__
|3
|Mois actuel (chiffre)
|
|-
|__MONTH_TEXT__
|Mars
|Mois actuel (texte)
|
|-
|__MONTH_TEXT_SHORT__
|Ma.
|Mois actuel en texte abrégé
|
|-
|__MONTH_TEXT_MIN__
|M
|Mois actuel en texte en une lettre
|
|-
|__YEAR__
|2020
|Année actuelle
|
|-
|__PREVIOUS_DAY__
|11
|Hier (chiffre)
|
|-
|__PREVIOUS_MONTH__
|2
|Mois précédent (chiffre)
|
|-
|__PREVIOUS_YEAR__
|2019
|Année précédente
|
|-
|__NEXT_DAY__
|13
|Demain (chiffre)
|
|-
|__NEXT_MONTH__
|4
|Mois prochain
|
|-
|__NEXT_YEAR__
|2021
|Année prochaine
|
|-
|__DOL_MAIN_URL_ROOT__
|<nowiki>http://mondolibarr.fr/htdocs</nowiki>
|Adresse de mon dolibarr
|
|-
|__(Clédetraduction)__
|Clé traduite
|N'importe qu'elle clé de traduction
|
|-
|__[constante]__
|Valeure de la constante
|N'importe qu'elle constante
|
|-
|__DATE_DELIVERY__
|21/09/1974
|Date de livraison de la Propal
|V14
|-
|__CONTACT_NAME_XXX__
|Mr T
|Civilité/titre prénom et nom du contact
XXX est le type de contact défini dans Accueil>configuration>dictionnaires>Types de contacts/adresses (par exemple : __CONTACT_NAME_BILLING__ pour le contact client désigné comme responsable de la facturation sur une facture)
|
|-
|__CONTACT_LASTNAME_XXX__
|Nom patronymique du contact
|Nom du contact

XXX est le type de contact défini dans Accueil>configuration>dictionnaires>Types de contacts/adresses (par exemple : __CONTACT_NAME_BILLING__ pour le contact client désigné comme responsable de la facturation sur une facture)
|
|-
|__CONTACT_FIRSTNAME_XXX__
|Prénom du contact
|Prénom du contact

XXX est le type de contact défini dans Accueil>configuration>dictionnaires>Types de contacts/adresses (par exemple : __CONTACT_NAME_BILLING__ pour le contact client désigné comme responsable de la facturation sur une facture)
|
|-
|__CONTACT_TITLE_XXX__
|Titre de civilité du contact
|Titre/civilité du contact

XXX est le type de contact défini dans Accueil>configuration>dictionnaires>Types de contacts/adresses (par exemple : __CONTACT_NAME_BILLING__ pour le contact client désigné comme responsable de la facturation sur une facture)
|
|-
|__UNSUBSCRIBE__
|
|Lien de désinscription dans les emailings. Insère le terme "Désinscription" dans l'emailing avec un lien pour enregistrer une désinscription. Le texte peut être modifié via les traductions des clés
- MailUnsubcribe = la mention de désinscription insérée dans l'email

- YourMailUnsubcribeOK = la mention qui s'affiche sur la page web de confirmation de la désinscription
|
|-
|__CHECK_READ__
|
|Dans les emailings, insère une fonction permettant le comptage des emails lus (en anglais "blank image with a callback URL to Dolibarr (/public/emailing/mailing-read.php?tag=)"
|
|}

=Variables de substitution Personnalisées de modules externes=

Un module peut ajouter ses propres variables de substitutions.
Pour cela, le module doit embarquer un fichier avec le nom '''monmodule/core/substitutions/functions_monmodule.lib.php''' et en définissant le

<code>$this->module_parts['substitutions'] = 1 </code>

dans le descripteur de module.

Le fichier '''functions_monmodule.lib.php''' doit contenir une fonction nommée

où la variable $substitutionarray['_NOM_DE_MA_VAR_DE_SUBSTITUTION__'] = 'sa valeur';

ce qui peut donner quelque chose comme :
function monmodule_completesubstitutionarray(&$substitutionarray,$outputlangs,$object,$parameters){

$substitutionarray['_NOM_DE_MA_VARIABLE_DE_SUBSTITUTION__'] = 'sa valeur';

return 1;

}

Développement module

2025-02-20T08:27:21Z

Iouston: ajout d'un lien vers la page du fichier de conf pour mettre en avant la variable $dolibarr_allow_download_external_modules

[[en:Module_development]]
[[es:Desarrollo_de_un_módulo]]
[[de:Modul_Entwicklung]]
[[zh:模块开发]]
[[ja:モジュール_開発]]


[[Category:Noyau]]
{{TemplateDocDev}}
Pour créer un nouveau module, il existe plusieurs étapes. Ce didacticiel a pour but de vous décrire chacune d'elles afin d'ajouter un module permettant d'étendre les possibilités de Dolibarr, comme par exemple ajouter une ou plusieurs des fonctionnalités suivantes:

*Ajouter de nouvelles tables en base.
*Ajouter vos propres entrées dans les menus.
*Ajouter des objets et des écrans de saisie/consultation de nouvelle tables.
*Ajouter ou supprimer des onglets sur les pages de vues/édition des objets (facture, produit, commande, événement, ...)
*Ajouter des exports prédéfinis pour la fonction export.
*Ajouter de nouvelles boites/widgets pour la home page.
*Ajouter des variables de substitution.
*Définir de nouvelles permissions.
*Déclencher du code automatiquement sur une action Dolibarr particulière.
*Insérer votre code aux emplacements hooks de Dolibarr
*Ajouter un modèle de numérotation de la référence des objets créés.
*Ajouter un modèle de document PDF.
*Ajouter un nouveau thème.

Les chapitres suivants vous présentent comment réaliser tout cela en manuel de manière simple.

=[[File:Art.png]] Création de Module avec le générateur de module=
Depuis Dolibarr 9.0 il est possible de créer les fichiers principaux de votre module avec le "Générateur de module" (aussi appelé "Module Builder"). Pour l'activer :

*Activez le module "Générateur de Module" (ou "Module builder") dans la section "Outils multi-modules" de Configuration > Modules/Applications

[[File:Mod_builder_2.png|400px]]

*Puis cliquez sur l’icône "bug" qui est apparue dans la barre de menu en haut à droite

[[File:Mod_builder_3.png|400px]]

=[[File:Art.png]] Exemple de modèle de module externe=
Un bon modèle/squelette de module externe Dolibarr est disponible ici : [https://github.com/Dolibarr/dolibarr/tree/develop/htdocs/modulebuilder/template GitHub Dolibarr Module Modèle]

Vous trouverez aussi un exemple de réalisation de module via un cas pratique : la création d'un module afin de créer un calendrier des commandes fournisseurs : [[Exemple de cas pratique de Module Builder]]

=[[File:Art.png]] Créer un module=
Les sous chapitres suivant décrivent les actions à faire pour créer un module Dolibarr. Les premiers chapitres sont obligatoires quelle que soit la vocation du module, les suivants dépendront de ce que doit faire le module.

==Créer un descripteur de Module (obligatoire)==
'''Quand''' : Obligatoire dès qu'une extension est développée, quelle que soit sa vocation.
'''Depuis Dolibarr 9.0, il est possible de créer le descripteur de votre module avec le "Générateur de module"'''. Cet outil est encore encours de développement et de maturité mais peut d'ores et déjà être utilisé.

===Créer votre descripteur avec le générateur de module===

*Lancez le générateur de module en cliquant sur l’icône "bug"

[[File:Mod_builder_3.png|400px]]

*Entrez le nom de votre module sans espaces (le nom de votre module NE DOIT PAS CONTENIR le caractère underscore ou tiret bas : _) et cliquez sur Créer.

[[File:Mod_builder_4.png|400px]]

*Un module avec ses premiers fichiers a été initialisé. Vous pouvez alors modifier les paramètres du descripteur du module :

[[File:Mod_builder_5.png|400px]]

===Alternative : créer votre descripteur manuellement (sans utiliser le générateur de module)===
La première étape est donc de créer un fichier de description du module (descripteur). Pour cela:

*Créez le répertoire '''/htdocs/''monmodule''/core/modules'''. Puis, allez dans le répertoire '''dev/skeletons''' et recopiez le fichier modMyModule.class.php dans ce répertoire '''htdocs/''monmodule''/core/modules'''.
*Renommez le fichier mod'''MyModule'''.class.php en modifiant seulement la partie '''MyModule''' (le fichier doit commencer par mod)

Ensuite, modifiez le contenu de ce fichier afin de remplacer :

*les ''modMyModule'' en une valeur qui corresponde à la vocation de votre module. Cette valeur doit toujours commencer par '<nowiki/>'''mod'''' et ne contenir que des '''caractères alphabétiques'''.
*$this->numero = ''100000'' par un numéro de module libre. Pour éviter tout conflit, vous pouvez consulter la page suivante pour retrouver les numéros déjà alloués : [[List of modules id|Liste des id de modules]].
*Modifier éventuellement les autres variables définies dans le constructeurs (Voir le commentaire dans le code du squelette pour leur signification).

Le descripteur de votre module est alors en place.

===Tester votre descripteur===

Lancez Dolibarr et allez sur la page '''Configuration->module''', vous devez voir apparaître une nouvelle ligne avec votre nouveau module et la possibilité de l'activer ou non (parcourez tous les onglets de chaque catégories de modules jusqu'à le retrouver).
C'est la valeur de $this->special qui détermine dans quel onglet se trouve votre module.

===Nom de module===

Le nom de votre module NE DOIT PAS CONTENIR le caractère underscore ou tiret bas : _

==Arborescence d'un nouveau module==
Voici l'arborescence à respecter pour l'organisation des fichiers d'un module (cette arborescence sera celle prise d'office si vous générer les fichiers à l'aide de ModuleBuilder).

{{TemplateModuleTreeSimple}}

Un bon modèle/squelette de module externe Dolibarr est disponible ici : [https://github.com/Dolibarr/dolibarr/tree/develop/htdocs/modulebuilder/template GitHub Dolibarr Module Modèle]

==Créer vos tables SQL et les classes PHP DAO (optionnel)==
'''Quand''' : Si votre module a besoin de gérer des données qui lui sont propres

===Créer vos fichiers .sql===
Si votre module a vocation à gérer des données bien à lui, qui n'existent pas en base dans la version standard de Dolibarr, il est nécessaire de définir des tables SQL pour stocker ces données.

Créer un sous-répertoire '''sql''' dans le répertoire de votre module ('''monmodule/sql''') afin d'y placer les scripts sql que vous allez créer (Avec ModuleBuilder cette étape sera réalisée automatiquement suite à la création d'un nouvel Objet depuis l'onglet Objet).

Ensuite, vérifiez dans votre fichier descripteur de module, dans la fonction '''init''' que la ligne

<source lang="php">$this->_load_tables('/mymodule/sql/');</source>

n'est pas commentée.

''Règles à respecter:''

*Ajoutez les fichiers d'ordre de création de vos tables sur le principe de 1 fichier par table, nommé '''llx_matable.sql''' (pour la table), accompagné éventuellement du fichier '''llx_matable.key.sql''' (pour les index ou clé étrangères). Voir les exemples dans les fichiers existants dans '''install/mysql/tables''' pour exemple.
*Les types et noms recommandés pour les champs SQL sont définis sur la page [[https://wiki.dolibarr.org/index.php/Langages_et_normes#R.C3.A8gles_de_codage_SQL]].
*Pour ce qui est des commandes permettant d'ajouter/manipuler des données, elles doivent toutes se trouver dans un fichier nommé '''data.sql''' situé dans le même répertoire '''/monmodule/sql/'''.
*N'utilisez pas "chaine" mais 'chaine' car les guillemets doubles (") ont une signification particulière en PostGreSQL

Exemple de contenu de fichier data.sql
<source lang="sql">
delete from llx_const where name='MONMODULE_IT_WORKS' and entity='__ENTITY__';
insert into llx_const (name, value, type, note, visible, entity) values ('MONMODULE_IT_WORKS','1','chaine','A constant for my module',1,'__ENTITY__');
</source>

Les ordres SQL des fichiers doivent être opérationnels pour la base de données '''mysql'''.
Rem: Les fichiers des autres types de bases ne sont pas à maintenir. Ils sont lus et convertis à la volée par le driver de la base de données.

===Tester vos fichiers .sql===

Une fois les fichiers prêts, vous pouvez retourner dans l'écran de gestion des modules de Dolibarr puis désactiver le module, dropper les tables en base (si elles existent déjà) et réactiver le module.
Les tables doivent alors être recréées par l'activation du module.
Si tel n'est pas le cas, vérifiez vos scripts en les passant à la main, ou consultez les logs Dolibarr.

===Générer la classe PHP DAO d'accès aux tables===

Le fichier de classe DAO PHP d'un object est généré automatiquement avec ModuleBuilder lors de la création d'un Object.

À défaut d'utiliser le générateur de module, vous trouverez des exemples dans le squelette de module, fichier '''htdocs/modulebuilder/templates/class/myobject.class.php'''.

Dans cette classe, se trouvent des méthodes CRUD (Create/Read/Update/Delete) déjà opérationnelles pour faire un insert, un fetch (select), un update, un delete d'une ligne de la table. Éditer le fichier pour utiliser le bon nom de module, de tables et placer ce fichier dans le sous-répertoire de '''class''' du module. Le Module Builder permet de faire cela en quelques clics de souris.

==Affichage des onglets (optionnel)==

===Ajouter ou supprimer des onglets sur les fiches objets===
'''Quand''' : Pour ajouter votre propre onglet parmi les onglets d'un object standard (facture, commande, proposition commercial, adhérent...)

Pour cela, allez dans le fichier descripteur de module précédemment créé et modifiez le tableau $this->tabs:
<source lang="php">
// Array to add new pages in new tabs or remove existing one
$this->tabs = array('objecttype:+tabname1:Title1:mylangfile@monmodule:$user->rights->monmodule->read:/monmodule/mapagetab1.php?id=__ID__' // To add a new tab identified by code tabname1
'objecttype:+tabname2:Title2:mylangfile@monmodule:$user->rights->monmodule->read:/monmodule/mapagetab2.php?id=__ID__', // To add a new tab identified by code tabname2
'objecttype:-tabname'); // To remove an existing tab identified by code tabname
</source>

Le tableau doit contenir une liste de chaîne, chaque chaîne représentant un nouvel onglet.
Le format de la chaîne étant composé de 6 parties séparées par ":"

*Partie 1 : le type d'élément (objecttype) dans lequel doit apparaître l'onglet qui est une valeur parmi celle-ci:
{{TemplateModuleTabs-fr}}

*Partie 2 : nom de code pour l'onglet à ajouter (commence par +) ou à enlever (commence par -)
*Partie 3 : le titre de l'onglet. Cela peut être un libellé en dur ou mieux un code traduction présent dans un fichier lang.
*Partie 4 : le nom du fichier .lang (sans l'extension .lang) qui contient la correspondance entre le code traduction et le libellé à afficher. Si ce com est suivi de @monmodule, Dolibarr cherche le fichier dans le répertoire lang propre au module, c'est à dire htdocs/monmodule/langs/code_CODE/monmodule.lang, sinon Dolibarr cherche le fichier traduction dans htdocs/langs/code_CODE/mylangfile.lang
*Partie 5 : une condition à tester pour savoir si l'onglet doit être visible ou pas. Mettre '1' pour qu'il soit toujours visible.
*Partie 6 : l'url de la page à afficher quand on clique sur l'onglet. La chaine __ID__ sera remplacée automatiquement par l'Id de l'entité concernée.

Pour que la déclaration soit effective, il faut désactiver et réactiver le module.

Pour alimenter le contenu de l'onglet avec des données issues de la base, voir le chapitre suivant.

===Ajouter les onglets standard d'un objet sur sa propre page d'onglet===
'''Quand''' : Pour afficher les onglets existant d'un objet standard (produit, tiers, etc.) sur votre nouvelle page onglet.

Il faut appliquer la procédure suivante :

'''1. Inclure les fichiers définissant les fonctions utiles dans vos fichiers'''

Pour chaque fiche entité, il y a deux fichiers à inclure avec l'instruction
<source lang="php">require_once($url_fichier) ;</source>

Voici quelques exemples de fichiers à inclure (DOL_DOCUMENT_ROOT correspond au dossier dolibarr/htdocs/) :

*Entité tiers (thirdparty) :
**DOL_DOCUMENT_ROOT/societe/class/societe.class.php
**DOL_DOCUMENT_ROOT/core/lib/company.lib.php
*Entité produit (product) :
**DOL_DOCUMENT_ROOT/product/class/product.class.php
**DOL_DOCUMENT_ROOT/core/lib/product.lib.php
*Entité facture (invoice) :
**DOL_DOCUMENT_ROOT/compta/facture/facture.class.php
**DOL_DOCUMENT_ROOT/core/lib/invoice.lib.php

'''2. Créer et charger l'objet à afficher dans votre onglet'''

Créez l'objet de la classe voulue, et récupérez les données de l'objet à partir de la base de données. Pour cela il faut utiliser les fonctions fetch() de la classe correspondante, en passant en paramètre l'identifiant de l'objet que vous récupérez depuis l'url (ex : /mononglet.php?id=1).

''Exemple :''
<source lang="php">
$id=GETPOST('id','int');
$ref=GETPOST('ref','alpha');
$product = new Product($db) ;
$result = $product->fetch($id, $ref) ; //Tester $result pour vérifier que l'accès à la base s'est bien passée
</source>

'''3. Récupérer la liste des onglets correspondant à l'entité choisie'''

Utilisez la fonction XXX_prepare_head($obj), ou XXX est le nom de l'entité, permettant de créer un tableau contenant les définitions des onglets à afficher. Le paramètre à passer est l'objet pour lequel vous voulez afficher les onglets.

Le tableau retourné est composé de la façon suivante :
<source lang="php">
$head // Tableau des onglets
$head[$h] // Élément décrivant un onglet. Il y aura autant de $h que d'onglets à afficher
$head[$h][0] // Url de la page affichée quand on clique sur l'onglet
$head[$h][1] // Titre de l’onglet
$head[$h][2] // Code de l'onglet, à utiliser pour choisir quel onglet sera 'actif' (voir paragraphe suivant)
</source>

''Exemple :''
<source lang="php">
$head = product_prepare_head($product, $user) ; //le paramètre $user n'est pas présent sur certaines fonctions
</source>

'''4. Afficher les onglets sur votre page onglet'''

Utilisez la fonction dol_fiche_head() qui affiche les onglets contenus dans le tableau $head retourné par XX_prepare_head().

<source lang="php">
dol_fiche_head($links, $active='0', $title='', $notab=0, $picto='')
//$links // Tableau des onglets, appelé $head plus haut.
//$active // Onglet actif (mettre le nom de l'onglet défini dans votre fichier de module, ou un nom contenu dans $head[$h][2]). Cet onglet sera mis en surbrillance
//$title // ?
//$notab // Mettre ce paramètre à 1 permet de ne pas afficher de zone bleue en dessous des onglets.
//$picto // Nom de l'image à utiliser au début de la barre des onglet. Les choix suivant sont possibles :
// product
// service
// company
</source>

Cette fonction affiche les onglets voulus et ouvre un élément ''< div class="" >'' qui correspond à la zone bleue sous les onglets (si paramètre $notab = 0). Pour fermer la zone bleue, il suffit de fermer l'élément ''< /div >'' dans le code PHP.

''Remarque'' :
Pour plus de détail, se référer à la [http://www.dolibarr.fr/doxygen/ documentation Doxygen] ou directement au code de Dolibarr.

==Créer vos pages écran PHP (optionnel)==
'''Quand''' : Si l'objet de votre module est d'ajouter des fonctionnalités qui nécessitent de nouveaux écrans.

===Créer une page écran PHP brute===
Vous pouvez ensuite créer vos pages PHP, qui se basent sur les données de vos tables, en utilisant les squelettes fournis comme exemple dans le répertoire '''modulebuilder''' (Pour le développement d'un script en ligne de commande, voir [[Développement de scripts]]). La encore, si vous avez utilisez ModuleBuilder, des cas de pages (liste, page de création, onglet notes, etc...) auront été créés automatiquement lors de l'initialisation de l'objet.

Pour créer une nouvelle page écran utilisateur, créez un sous-répertoire de '''htdocs''' (si non déjà fait) propre à votre module (Dans '''htdocs/monmodule''' par exemple) afin d'y placer les pages que vous allez créer.

Y recopier le fichier '''myobject_page.php''' qui va servir de point de départ.
Modifiez le fichier afin que le main.inc.php soit trouvé
<source lang="php">
// Load Dolibarr environment
$res=0;
// Try main.inc.php into web root known defined into CONTEXT_DOCUMENT_ROOT (not always defined)
if (! $res && ! empty($_SERVER["CONTEXT_DOCUMENT_ROOT"])) $res=@include($_SERVER["CONTEXT_DOCUMENT_ROOT"]."/main.inc.php");
// Try main.inc.php into web root detected using web root calculated from SCRIPT_FILENAME
$tmp=empty($_SERVER['SCRIPT_FILENAME'])?'':$_SERVER['SCRIPT_FILENAME'];$tmp2=realpath(__FILE__); $i=strlen($tmp)-1; $j=strlen($tmp2)-1;
while($i > 0 && $j > 0 && isset($tmp[$i]) && isset($tmp2[$j]) && $tmp[$i]==$tmp2[$j]) { $i--; $j--; }
if (! $res && $i > 0 && file_exists(substr($tmp, 0, ($i+1))."/main.inc.php")) $res=@include(substr($tmp, 0, ($i+1))."/main.inc.php");
if (! $res && $i > 0 && file_exists(dirname(substr($tmp, 0, ($i+1)))."/main.inc.php")) $res=@include(dirname(substr($tmp, 0, ($i+1)))."/main.inc.php");
// Try main.inc.php using relative path
if (! $res && file_exists("../main.inc.php")) $res=@include("../main.inc.php");
if (! $res && file_exists("../../main.inc.php")) $res=@include("../../main.inc.php");
if (! $res && file_exists("../../../main.inc.php")) $res=@include("../../../main.inc.php");
if (! $res) die("Include of main fails");
</source>
Comme vous pouvez le constater, plusieurs tentatives de chargement du fichier main.inc.php (ou master.inc.php) ont été tentées. Le but est de réussir dans le plus grand nombre de cas possibles. Le minimum est de 2 lignes: une pour essayer de charger le fichier master / main.inc.php dans le répertoire racine de dolibarr et une autre pour essayer de charger le fichier afin de prendre en charge le cas où le module est déployé dans le répertoire "custom". Mais vous pouvez avoir à gérer plus de situations. L'exemple fourni devrait pouvoir charger le fichier main / master.inc.php dans presque toutes les situations / configurations.

Notez que vous pouvez ajouter plus "../" en fonction de la profondeur du fichier par rapport à l'arborescence de votre module.

C'est dans le main qu'est chargé l'environnement technique ainsi que les habilitations. Les variables objets suivantes sont alors positionnées:

*$user L'objet qui contient les caractéristiques de l'utilisateur + ses droits.
*$conf L'objet qui contient la configuration de Dolibarr.
*$db L'objet qui contient le handler de connexion à la base de données.
*$langs L'objet qui contient la langue de l'utilisateur.

*L'inclusion d'une classe ou librairie dédiée au module, sans savoir d'où le fichier sera appelé, se fait en utilisant une fonction de Dolibarr (et non en utilisant directement le include_once)

''Exemple :''
<source lang="php">
dol_include_once('/monmodule/class/maclasse.class.php', 'MaClasse');
</source>

*L'appel des classes fournies en standard avec Dolibarr se fera par contre par le require_once directe avec la syntaxe suivante:

''Exemple :''
<source lang="php">
require_once DOL_DOCUMENT_ROOT.'/core/class/doli.class.php';
</source>
La raison est que si le dol_include_once est pratique car il scanne chaque répertoire de chemin alternatif pour trouver le fichier, il est aussi moins performant car génère des accès et recherches disque à chaque appel (en effet, PHP intègre un cache des fichiers lus mais n'intègre pas un cache des fichiers "non trouvés". Et comme un fichier donné n'est que dans une seule arborescence, il y a toujours une arborescence alternative où il ne se trouve pas et qui génère des accès superflus au disque dur, pénalisant en terme de performance. Comme pour les fichiers internes à Dolibarr, on connait toujours le chemin exacte, le require_once avec ce chemin direct doit être préféré).

===Accès à la base===
Si vous avez besoin de réaliser des modifications en base dans votre propre table ajoutée, utilisez la classe générée plus haut qui contient les méthodes pour cela.

Si toutefois vous voulez faire des accès dans des tables sans objet PHP dédié, ceci reste possible (par exemple pour récupérer une liste d'enregistrement). Dans ce cas, pensez à suivre ces exemples:

Pour un insert, update ou delete :

<source lang="php">
$db->begin(); // Debut transaction
$db->query("Ma requete insert, update ou delete");
$db->commit(); // Valide
ou $db->rollback() // Annule
</source>

Pour une lecture :

<source lang="php">
$resql=$db->query("Ma requete select");
if ($resql)
{
$num = $db->num_rows($resql);
$i = 0;
if ($num)
{
while ($i < $num)
{
$obj = $db->fetch_object($resql);
if ($obj)
{
// You can use here results
print $obj->field1;
print $obj->field2;
}
$i++;
}
}
}
</source>

===Définition du style===
Pour que le look de la page soit aligné avec le thème Dolibarr, il est nécessaire d'utiliser les styles des CSS de Dolibarr.

Par exemple :

*class="'''liste_titre'''" sur les balises ''tr'' et ''td'' pour une ligne de titre de tableau.
*class="'''pair'''" ou class="'''impair'''" sur les balises ''tr'' et ''td'' des lignes de données de tableau.
*class="'''flat'''" sur tous les champs de saisie (''input, select, textarea''...).
*class="'''button'''" sur les objets de type ''input type="submit"''.

===Utilisez le sélecteur de date de Dolibarr===
Si vous le désirez, vous pouvez profiter du sélecteur de date dans des écrans Dolibarr. Pour cela, utilisez la ligne suivante:
<source lang="php">
$form=new Form($db);
$form->select_date('','mykey',0,0,0,"myform");
</source>
La chaîne mykey identifie la zone date. Il faut y mettre une valeur différente s'il y a plusieurs zones.
La chaine myform est le nom de la zone FORM (dans form name="myform" de la page HTML).
L'affichage d'un sélecteur de date doit donc être intégré dans une zone FORM Html.

Pour récupérer la valeur, à l'issu du POST, la commande est:
<source lang="php">
$mydate = dol_mktime(12, 0 , 0, GETPOST('mykeymonth', 'int'), GETPOST('mykeyday', 'int'), GETPOST('mykeyyear', 'int'));
print strftime('%A %d %B %Y', $mydate);
</source>

==Définir votre page de configuration (optionnel)==
'''Quand''' : si votre module offre plusieurs options paramétrables.

===Créez votre page d'édition de configuration===
Si votre module offre plusieurs options paramétrables, il est nécessaire de créer une page PHP pour éditer les options (qui sont stockées dans la [[Table llx_const|table '''llx_const''']]).
Créez une page PHP nommée '''monmodule_setupapage.php''' qui affiche les options possibles et les met à jour.
Il est nécessaire de prendre exemple sur une page dans '''/admin''' qui vous montre la méthode pour lire ou sauvegarder en base votre option.
Placez cette page de configuration dans le répertoire '''/admin''' également.
Ensuite dans le descripteur de module, modifiez la variable pour indiquer le nom de cette page PHP (sans le chemin qui n'est pas nécessaire, la page étant forcément dans le rep admin).
<source lang="php">
$this->config_page_url = array("setup.php@mymodule");
</source>

===Testez votre page===
Allez sur la page '''Configuration->module''', vous devez voir apparaître une icône qui permet d'accéder à la page de configuration et vous devez être capable de modifier ces options et les voir conservées en base.

==Définir vos entrées de menu (optionnel)==
'''Quand''' : si vous avez créé des pages PHP, il est nécessaire que ces écrans soient accessibles depuis le menu Dolibarr.

===Définissez vos entrées menus===
Pour cela, il vous faut définir dans le fichier descripteur de module, le tableau this->menu qui déclare les menus.
Ce tableau contient toutes les entrées qui apparaîtront dans les menus une fois le module activé.
Le fichier de descripteur de module exemple '''modMonModule.class.php''' possède un exemple de déclaration de menu haut ainsi que de ses entrées menu gauche associées.

Voici un exemple de déclaration d'entrées de menu dans le fichier descripteur:
<source lang="php">
// Main menu entries
$this->menu = array(); // List of menus to add
$r=0;

// Add here entries to declare new menus
// Example to declare the Top Menu entry:
$this->menu[$r]=array( 'fk_menu'=>0, // Put 0 if this is a top menu
'type'=>'top', // This is a Top menu entry
'titre'=>'MonModule top menu',
'mainmenu'=>'monmodule',
'leftmenu'=>'monmodule',
'url'=>'/monmodule/pagetop.php',
'langs'=>'mylangfile', // Lang file to use (without .lang) by module. File must be in langs/code_CODE/ directory.
'position'=>100,
'enabled'=>'1', // Define condition to show or hide menu entry. Use '$conf->monmodule->enabled' if entry must be visible if module is enabled.
'perms'=>'1', // Use 'perms'=>'$user->rights->monmodule->level1->level2' if you want your menu with a permission rules
'target'=>'',
'user'=>2); // 0=Menu for internal users, 1=external users, 2=both
$r++;

// Example to declare a Left Menu entry:
$this->menu[$r]=array( 'fk_menu'=>'fk_mainmenu=xxx', // Use 'fk_mainmenu=xxx' or 'fk_mainmenu=xxx,fk_leftmenu=yyy' where xxx is mainmenucode and yyy is a leftmenucode of parent menu
'type'=>'left', // This is a Left menu entry
'titre'=>'MonModule left menu 1',
'mainmenu'=>'xxx',
'leftmenu'=>'yyy',
'url'=>'/monmodule/pagelevel1.php',
'langs'=>'mylangfile', // Lang file to use (without .lang) by module. File must be in langs/code_CODE/ directory.
'position'=>100,
'enabled'=>'1', // Define condition to show or hide menu entry. Use '$conf->monmodule->enabled' if entry must be visible if module is enabled.
'perms'=>'1', // Use 'perms'=>'$user->rights->monmodule->level1->level2' if you want your menu with a permission rules
'target'=>'',
'user'=>2); // 0=Menu for internal users,1=external users, 2=both
$r++;
</source>

Pour conditionner l'accès au menu selon des permission, modifier la propriété '''perms''' du tableau. Voir le chapitre sur les permissions un peu plus loin pour savoir comment ajouter des permissions.

===Testez vos entrées menus===
Désactiver et réactiver votre module sous Dolibarr, les entrées menus doivent alors apparaître (si la condition dans 'enabled' est vraie).

==Définir vos propres permissions (optionnel)==
'''Quand''' : Si vous voulez ajouter de nouvelles permissions.

La définition des permissions que gérera votre module se fait dans le fichier descripteur créé dans la première étape.
Modifier la ligne
<source lang="php">
$this->rights_class = 'monmodule'
</source>
pour y mettre la bonne valeur de monmodule.

Ensuite remplissez le tableau $this->rights avec autant d'entrées que de permissions différentes à gérer.

<source lang="php">
$this->rights[$r][0] = 10001;
$this->rights[$r][1] = 'Libelle par défaut de ma permission';
$this->rights[$r][3] = 1;
$this->rights[$r][4] = 'action';
$this->rights[$r][5] = 'sousaction';
$r++;
</source>

Dans $this->rights[$r][0], mettre un id de permission non déjà pris (Voir dans le menu '''Infos Système''' sur une installation de Dolibarr opérationnelle pour connaître les id déjà utilisés.
Dans $this->rights[$r][3], mettre 1 si cette permission est attribué d'office par défaut quand un utilisateur est créé.
Dans $this->rights[$r][1], mettre un libellé par défaut (il sera affiché si aucune traduction n'est trouvé pour votre permission dans le fichier '''admin.lang'''. La clé de traduction dit être "Permission10001=Description de ma super permission'''"''').
Dans $this->rights[$r][4] et $this->rights[$r][5], mettre une chaîne action et sous action sans espace. Vous pourrez alors tester dans le code PHP si un utilisateurs a bien les droits par la séquence suivante :

<source lang="php">
if ($user->rights->monmodule->action->sousaction) ...
</source>

==Définir vos propres box/widgets (optionnel)==
'''Quand''' : si votre module amène avec lui une ou plusieurs Boxes.

===Définissez vos box===
Pour cela, modifiez les tableaux $this->boxes du fichier descripteur de module.
Il suffit d'ajouter 2 lignes par fichier box que vous allez créer dans le répertoire '''htdocs/monmodule/core/boxes'''

''Exemple :''
<source lang="php">
$this->boxes[0]['file']='mabox0.php@monmodule'
$this->boxes[0]['note']='Ma box 0'
...
$this->boxes[n]['file']='maboxn.php@monmodule'
$this->boxes[n]['note']='Ma box n'
</source>

Ensuite créez les fichiers '''htdocs/monmodule/core/boxes/mabox0.php''', '''htdocs/monmodule/core/boxes/maboxn.php'''... en prenant exemple sur des box existantes (exemple dans le répertoire '''htdocs/core/boxes''')

===Testez la présence de vos box dans Dolibarr===
Désactivez et réactivez le module.

Allez dans le menu '''Accueil - Configuration - Widgets'''.

Vos box doivent apparaître dans la liste des box activables. Activez les puis allez sur la page d'accueil et vérifiez qu'elles s'affichent correctement.

==Définir vos propres exports (optionnel)==
'''Quand''' : si votre module amène avec lui des exports prédéfinis de données (pour ces propres tables ou des tables déjà existantes d'un autre module de Dolibarr).

===Définissez l'export===
Pour cela, décommentez et modifiez les tableaux $this->export_xxx du votre fichier descripteur de module.

===Testez votre export===
Allez dans le menu outils -> export de Dolibarr. Votre export doit apparaitre dans la liste des exports prédéfinis disponibles (si votre module est bien activé).
Le choisir, vous devez alors voir les champs possibles définis dans le tableau à l'étape précédente.
Choissez quelques champs et tentez une génération du fichier export.

==Définir vos styles CSS (optionnel)==
'''Quand''' : lorsque dans vos écrans PHP, vous utiliser des classes de styles qui ne sont pas celle des thèmes de Dolibarr (non recommandé).

Cette fonctionnalité est décrite mais pas encore opérationnel en 2.4

===Créez et déclarez votre feuille de style===
Créez un fichier de style css nommé '''monmodule.css''' ou '''monmodule.css.php''' et placez le dans le répertoire '''''monmodule''''' dans '''htdocs'''. Il ne peut y avoir qu'un fichier css propre à chaque module.
Rappelons qu'il vaut mieux utiliser les styles déjà existant de Dolibarr (le fichier css utilisé par Dolibarr étant le fichier '''themes/nomtheme/''nomtheme''.css.php'''). Ne créez un fichier css propre à votre module que si vous devez absolument gérer des styles non déjà existants.
Une fois votre feuille de style prête, déclarez la dans votre fichier descripteur de module en modifiant la propriété '''$this->module_parts'''.
La valeur à renseigner ici doit être le chemin relatif de l'URL de votre fichier css.
Par exemple
<source lang="php">
$this->module_parts = array('css' => array('/monmodule/css/monmodule.css.php'));
</source>

===Testez votre feuille de style===
Désactivez et réactivez votre module.

Appelez la page d'accueil de Dolibarr. Affichez la source de la page HTML.

Vous devriez voir dans l'entête HTML, une ligne déclarant votre feuille de style.

==Définir vos fonctions Javascript (optionnel)==
'''Quand''' : lorsque dans vos écrans PHP, vous utiliser des fonctions javascript non dispo en standard (fichier lib_head.js)

Si dans vos écrans PHP, vous utilisez des fonctions javascript, il est nécessaire de faire en sorte que vos fonctions déclarées dans un fichier javascript '''htdocs/monmodule/js/monmodule.js''' soit chargées dans l'entête head html.
Pour demander à Dolibarr qui gère la génération de la section header d'inclure un de vos fichiers javascript, il est nécessaire de fournir en paramètre de la fonction llxHeader() appelée au début de votre page, d'inclure le paramètre qui contient l'URL vers le js à inclure.

Exemple pour la page /htdocs/monmodule/mapage.php :
<source lang="php">
require('../main.inc.php');
$morejs=array("/monmodule/js/monmodule.js");
llxHeader('','Titre','','','','',$morejs,'',0,0);
</source>

==Déclencher du code sur un évènement Dolibarr (optionnel)==
'''Quand''' : lorsque vous voulez que des actions particulières s'exécutent suite au déclenchement d'actions standards de Dolibarr (exemple : je veux mettre à jour une table de mon module quand une facture se crée dans Dolibarr), il vous faut créer un fichier de '''triggers'''.

Voir aussi [[Interfaces_Dolibarr_vers_exterieur|Interfaces de Dolibarr vers l'exterieur]]
et [[Interfaces_Exterieur_vers_Dolibarr|Interfaces exterieures vers Dolibarr]]

==Insérer votre code aux emplacement hooks de Dolibarr (optionnel)==
'''Quand''' : lorsque vous voulez modifier ou ajouter du code autrement que lors d'un événement métier (voir le chapitre précédent pour cela).

Voir la page [[Système de Hooks]].

==Ajouter un module de numérotation (optionnel)==
'''Quand''' : lorsque vous voulez ajouter une règle de numérotation non couverte par les modules par défaut.

Voir la page [[Créer un module de numérotation]].

==Ajouter un nouveau modèle de document (optionnel)==
'''Quand''' : lorsque vous voulez ajouter un nouveau modèle de document.

La documentation au sujet de la génération de documents depuis des modèles est disponible sur la page [[Créer un modèle de document PDF]] ou [[Créer un modèle de document ODT]].

==Ajouter un thème (optionnel)==
'''Quand''': Lorsque vous voulez une interface aux couleurs personnalisées à votre cas.

Voir la page [[Themes]].

==Ajouter un bouton (optionnel)==
Si vous souhaitez ajouter des boutons à vos enregistrements.

Voir la page [[Création de boutons]].

=[[File:Art.png]] Quelques règles de codage et fonctions pour développeurs=
Les règles de codage à suivre sont définis dans la [[Documentation Développeur|Documentation développeur]], rubrique "Informations Générales - Langage et normes de développement".

De nombreuses fonctions prédéfinies pour les développeurs sont disponibles et décrites sur la page [[Documentation Développeur|Documentation développeur]] sous la section "Les couches techniques de Dolibarr".

=[[File:Art.png]] Créer un package pour livrer et installer votre module=
Cette procédure doit être utilisée pour fabriquer un package afin de le soumettre sur la place de marché http://www.dolistore.com.
Mais vous pouvez aussi l'utiliser pour distribuer facillement votre module via votre propre réseau de distribution.

*Allez dans le répertoire '''/build''' et recopiez le fichier '''makepack-dolibarrmodules.conf''' en '''makepack-monmodule.conf'''. Attention, ce répertoire peut ne pas être fourni dans les packages de versions stables. Si c'est le cas, il peut être récupéré dans le snapshot disponible en téléchargement sur le site web Dolibarr dans la rubrique Version de développement (prenez dans ce cas tout le répertoire build qui est un répertoire autonome et indépendant de la version).

Saisissez dans ce fichier la liste des noms des nouveaux fichiers que vous avez créé pour votre module (descripteur de module, nouveaux fichiers sql de tables, page php, images, etc...)

*Lancer le script via Perl (besoin de la version Perl 5.0 ou +):

<source lang="bash">
perl makepack-dolibarrmodule.pl
</source>
Le script vous demande le nom de votre module, sa version majeure et mineure.
Un fichier '''monmodule.zip''' va alors être fabriqué contenant votre module prêt pour être déployé.

*La personne qui reçoit votre module doit alors placer le fichier dans son répertoire racine d'installation de Dolibarr et réaliser la commande :

<source lang="bash">
tar -xvf monmodule.zip
</source>

*Si vous désirez que votre module profite à tous, vous pouvez le soumettre (le fichier zip) sur la place de marché des modules complémentaires: {{LinkToPluginDownload}} (vous devez avoir créé un compte auparavant et utiliser le lien "Soumettre un module/produit").
**Si votre module a été fabriqué correctement, le fichier sera validé rapidement.
**Si la qualité est suffisante, que la licence le permet et que la fonctionnalité du module s'avère être d'un intérêt général, le code pourra être ajouté au code source de Dolibarr (sauf si vous ne le désirez pas).

Il également possible récupérer votre module au format .zip en ayant activé la variable [[Fichier de configuration|$dolibarr_allow_download_external_modules à 1 dans le fichier conf.php]].

=[[File:Art.png]] Dépôt et validation du module externe sur Dolistore=

Voir [[Module_Dolistore_Validation_Regles|Règles de Validation]]

Setup Other

2024-09-05T04:04:01Z

Iouston: add holiday module section

[[fr:Paramétrage_Divers]]
[[es:Configuración_Varios]]
[[de:Erweiterte_Einstellungen]]
[[zh:其他设置]]


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

'''Help About Screen''': Other setup

'''Menu Path''': Home ► Setup ► Other

'''Introduction'''

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

{{warning|32px}} This page contains the list of some advanced development parameters. In most cases, it is parameters for internal usage, development, external modules, features in development not stable or that may lead to security risk. For standard usage of Dolibarr, such parameters '''SHOULD NOT''' be used. All experimental options are NOT supported. They may be removed in a future, modified at any version and break stability of your application.

To enable/override a parameter you have to define the constant name and set it to 1 (unless otherwise stated) in <code>Home ► Setup ► Other Setup</code>

The options here may not be documented since they are not stable and are unsupported (remember they are experimental or development options). The basic format of how the list is written is broken down in the example below:

UNSTABLE_OR_DEV_OPTION ► ''Description of config and goal'' ► ''(specific version information) or values''
<center>
__TOC__
</center>
=Global Options=

*'''ADD_UNSPLASH_LOGIN_BACKGROUND''' ► The background image will be refreshed on every login page refresh. Background image is pulled from the popular open source image website Unsplash. If an already saved static background image exists, then this code will override it (but not delete the saved image). Warning: Using this may allow this external website to steel your login credentials (the value to be put is the URL of the service, exemple : https://source.unsplash.com/random) ► (v10.0)
*'''MAIN_HIDE_POWERED_BY''' ► Hide the "Powered by Dolibarr" picto on public pages
*'''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 fail by smartphone applications like [[Application Android - DoliDroid]] breaking some features when using Dolibarr from this application.

*'''MAIN_AUTOFILL_DATE''' ► If this constant is defined (to something other than <code>0</code>), the date of invoice, proposal, order or payment are auto-filled with the current date. It is highly recommended to NOT ENABLE this feature. This can create a lot of input errors with data not validated by users. This leads to incorrect values saved in the database causing confusion when you have to do your accountancy reports!

*'''MAIN_AUTO_TIMESTAMP_IN_PUBLIC_NOTES''' ► Add a timestamp and user automatically when editing the ''public'' note.

*'''MAIN_AUTO_TIMESTAMP_IN_PRIVATE_NOTES''' ► Add a timestamp and user automatically when editing the ''private'' note.

*'''MAIN_COUNTRIES_IN_EEC''' ► Country list in European Area (For VAT purpose) ► (v10.0-v13.0). From v14, do not use this any more (remove the constant if you set it and instead set if the country is in Europe or not from the DB for V14 - V15 and from dictionary of countries in V16 and more).

*'''MAIN_DEFAULT_PAYMENT_TERM_ID''' ► With ID of a payment term, will use this as default payment term each time you create a new proposal, order, invoice (customer and supplier). Deprecated. Replaced with the default setup feature instead.
*'''MAIN_DEFAULT_PAYMENT_TYPE_ID''' ► With ID of a payment type, will use this as default payment type each time you create a new proposal, order, invoice (customer and supplier). Deprecated. Replaced with the default setup feature instead.

*'''MAIN_DEFAULT_LANGUAGE_FILTER''' ► Useful if you do not want to show <code>en_US</code> language option in combo boxes (other languages can easily be removed in <code>langs</code> directory but not <code>en_US</code>) ► (v10.0)

*'''MAIN_LANGUAGES_ALLOWED''' ► Is a list of languages without spaces, example : <code>fr_FR,en_US,de_DE,it_IT</code> If defined, only those languages will appear in combos. ► (v11.0)

*'''MAIN_DISABLE_NOTES_TAB''' ► Show or hide notes tab in the card page

*'''MAIN_DISABLE_CONTACTS_TAB''' ► Show or hide contacts tab in the card page

*'''MAIN_DISABLE_FULL_SCANLIST''' ► Disables the complete scan of tables to allow the pagination to show total number of pages. May be useful to activate on systems with a very high quantity of data (tables with more than 2 000 000 records).

*'''MAIN_DISABLE_JQUERY_JNOTIFY''' ► Disable usage of <code>JNotify</code> to show confirm or error messages

*'''MAIN_DISABLE_AJAX_COMBOX''' ► If you have a large number of third parties or products, you can disable the autocomplete feature on the third parties list by setting this constant to <code>1</code> ► (v3.6.0+)
*'''MAIN_DISABLE_MULTIPLE_FILEUPLOAD''' ► Disable users to upload multiple files at once.
*'''MAIN_DISABLE_TRUNC''' ► Disable all truncings in select list. ► (v7.0+)

*'''MAIN_DISABLEDRAFTSTATUS''' ► Disable the status "Draft" for some objects (project, donation, ...) so the object is directly created with status "Validated"

*'''MAIN_DOC_USE_OBJECT_THIRDPARTY_NAME''' ► Add name of thirdparty at begin of generated document.

*'''MAIN_DOC_USE_TIMING''' ► Add a timestamp at end of generated document. Value must be format of timestamp. For example: <code>%Y%m%d%H%M</code> (only for ODT files)

*'''MAIN_DOC_UPLOAD_NOT_RENAME_BY_DEFAULT''' ► Disable the auto renaming on upload file ► (v10.0)

*'''MAIN_DOL_SCRIPTS_ROOT''' ► Define directory who contains 'scripts' directory (e.g. <code>/var/www/dolibarr</code>). Value of this variable may be requested by some external script or tools.

*'''MAIN_ENABLE_LOG_TO_HTML''' ► If this constant is defined, it is possible to have logs inside pages by adding the parameter <code>&logtohtml=1</code> into URL.

*'''MAIN_ENABLE_IMPORT_LINKED_OBJECT_LINES''' ► Allow to import lines into current document from "linked" compatible documents ► (v8.0+)

*'''MAIN_FIRST_TO_UPPER''' ► Dolibarr add uppercase to Third Parties, 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_ALL_TO_UPPER''' ► Dolibarr puts uppercase for Third Parties, 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. ► (v11.0)

*'''MAIN_ALL_TOWN_TO_UPPER''' ► Dolibarr puts uppercase for town names if not done. ► (v13.0)

*'''MAIN_FILESYSTEM_ENCODING''' ► With some PHP versions, PHP is not able to detect the page code for filesystem of the server OS. To solve this, Dolibarr assumes your OS filesystem is <code>UTF-8</code> if on Linux or OSX system, and <code>ISO-8859-1</code> if on Windows. If not, for example on a Windows server with a NTFS <code>UTF-8</code> pagecode, you can set the variable <code>MAIN_FILESYSTEM_ENCODING</code> to "<code>utf-8</code>".

*'''MAIN_FORCELANGDIR''' ► Relative path of the directory holding your custom <code>langs</code> folder.

*'''MAIN_HTML_TITLE''' ► Can be used to control how the html page title is formatted. If value contains key '<code>noapp</code>', application name will not be output. If value contains '<code>thirdpartynameonly</code>', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: '<code>noapp;thirdpartynameonly</code>'

*'''MAIN_HELPCENTER_LINKTOUSE''' ► Define the URL link to use as the target page for link "I need help" onto logon page

*'''MAIN_LOGOUT_GOTO_URL''' ► URL to which the user will be redirected after LOGOUT

*'''MAIN_MAXTABS_IN_CARD''' ► Maximum number of tabs visible. Others are grouped into a combo list.

*'''MAIN_MAXLIST_OVERLOAD''' ► Maximum number of line in space's domain.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► A warning saying setup of modules is not complete is shown if the number of enabled modules is lower or equal than this value (<code>1</code> if not defined)

*'''MAIN_NO_CONCAT_DESCRIPTION''' ► Allow to use only input custom description in lines (proposal, order, invoice) ► (v10.0)

*'''MAIN_OPTIMIZE_SPEED''' ► Use some speed enhancements. See page [[FAQ Increase Performance]] for more information.

*'''MAIN_PROPAGATE_CONTACTS_FROM_ORIGIN''' ► When creating an order, contract, invoice from another object, specific contacts of objects are set as specific contact of the new object when possible. ► (v4.0+)

*'''MAIN_PUBLIC_NOTE_IN_ADDRESS''' ► Show public note in address block ► (v4.0+)

*'''MAIN_REMOVE_INSTALL_WARNING''' ► Remove all security warnings that appear to administrator users if URL <code>/install</code> is public. You should solve the problem if warning occurs, instead of removing the warning! For this, create a file called <code>install.lock</code> into Dolibarr root directory. This will stop the warning but also make the page <code>/install</code> not possible to use, to protect your installation.

*'''MAIN_REPEATCONTACTONEACHTAB''' ► If added and set to <code>1</code>, this adds contacts on all tabs, not only main tab.

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

*'''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND''' ► Change way of rounding total TTC lines, rounding first of after.

*'''MAIN_SERVER_TZ''' ► If you can't set the time zone of your PHP installation, set this constant. Better is to set it to UTC. In future, this constant will be forced to '<code>UTC</code>' so PHP server time zone will not have effect any more. Examples: <code>Europe/Paris</code>, <code>auto</code>.

*'''MAIN_SEARCH_FORM_ON_HOME_AREAS''' ► Show the search form on home page areas for core modules (Removed after v5 due to global search combo) ► (v6.0+)

*'''MAIN_SEARCHFORM_SUPPLIER_INVOICE_DISABLED''' ► Disable the supplier invoice on the search form

*'''MAIN_SEARCH_DIRECT_OPEN_IF_ONLY_ONE''' ► If only one result is found, then setting this value to <code>1</code> will take you direct to the item (default method). Setting the value to <code>0</code> will show the result in the list as a single result ► (v5.0+)

*'''MAIN_SERVICES_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country.

*'''MAIN_SHOW_TUNING_INFO''' ► Add tuning information into JavaScript console. Better when xdebug is enabled.

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show also technical IDs on elements cards or some lists (not supported everywhere).

*'''MAIN_SHOWDATABASENAMEINHELPPAGESLINK''' ► Show database name in upper help menu ► (v8.0+)

*'''MAIN_USE_ALTERNATE_TRANSLATION_FOR''' ► List of fields per object that need an alternate translation. Example: <code>MAIN_USE_ALTERNATE_TRANSLATION_FOR=societe:name,town;contact:firstname,lastname</code>

*'''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_USE_JQUERY_JEDITABLE''' ► Allow to update from screen, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this feature, because it bypasses some business actions (updates on other data that should be done consistently) and ignores business controls on data you saved. Consequently this feature breaks consistency of data and possibly the stability of the 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_USE_OLD_SEARCH_FORM''' ► Display the old search form in left menu.

*'''MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS''' ► Allow to force the VAT rate to a given value (instead of higher VAT rate of country) if the VAT rate of product was not defined.

*'''MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES''' ► If we can't guess if a thirdparty is a company or individual (not VAT ID fill, no Prof ID fill, no type of thirdparty fill), then we suppose it is a company (B2B business) instead of an individual (B2C business).

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► For intra CEE sales, we use by default, on proposal, order or invoice creation, a 0 VAT for customers that are companies (see MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES to change behaviour to know if a thirdparty is a company or an individual). But if the option MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL is set, we will use the 0 VAT only if a VAT ID is defined for the customer.

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_INDIVIDUAL_CUSTOMER_OUT_OF_EEC''' ► For to use the default VAT of product for individual customers that are out E.E.C. (European Economic Community) ► (v7.0+). ''There is no reason to use this.''

*'''MAIN_VIEW_LINE_NUMBER''' ► Shows a line number for each line of products/services at documents like proposal / order / invoice. Only on screen, not on PDF.

*'''MAIN_VIEW_LINE_NUMBER_IN_LIST''' ► Shows a line number in lists ► (v12.0)

*'''MAIN_VOLUME_DEFAULT_ROUND''' ► Accuracy of volume (number of decimals)

*'''MAIN_VOLUME_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''MAIN_WEIGHT_DEFAULT_ROUND''' ► Accuracy of weight (number of decimals)

*'''MAIN_WEIGHT_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''USER_HIDE_INACTIVE_IN_COMBOBOX''' ► Disable display inactive users in combobox.

*'''MAIN_DISABLE_PDF_THUMBS''' ► Disable thumbs PDF in case of imagick bug

*'''MAIN_KEEP_REF_CUSTOMER_ON_CLONING''' ► Keep the Customer Reference on cloned object (Propal/Invoice)

*'''MAIN_DONT_KEEP_NOTE_ON_CLONING''' ► Remove the object notes during cloning ► (v11.0)

*'''MAIN_DOC_SORT_FIELD''' ► Set the default sorting field on document page (name by default) ► (v11.0)

*'''MAIN_DOC_SORT_ORDER''' ► Set the default sorting order (ASC or DESC) on document page (ASC by default) ► (v11.0)

*'''MAIN_USE_ZIPTOWN_DICTIONNARY''' ► Use dictionary ZIP for create card.

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Show search in top menu with theme eldy ► (v11.0)

*'''MAIN_PHONE_SEPAR''' ► Separ phone number other space ► (v12.0)

*'''GRAPH_USE_FISCAL_YEAR''' ► Widgets uses fiscal year

*'''SHOW_SOCINFO_ON_PRINT''' ► Permit to add user company information on each printed document (when click on Dolibarr print button) ► (v12.0)

*'''MAIN_FEATURES_LEVEL''' ► Level of features to show: <code>-1=stable+deprecated</code>, <code>0=stable only (default)</code>, <code>1=stable+experimental</code>, <code>2=stable+experimental+development</code>

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show technical id for object.

*'''MAIN_HTTP_CONTENT_SECURITY_POLICY''' ► Allows you to fill in the content security rules ► (v6.0)

*'''SOCIETE_ON_SEARCH_AND_LIST_GO_ON_CUSTOMER_OR_SUPPLIER_CARD''' ► Allow to change the link of the third party to customer/supplier card instead of contact card on List.

*'''MAIN_MODULE_SETUP_ON_LIST_BY_DEFAULT''' ► If set to "common" the setup module becomes list by defaut

*'''MAIN_PAGESIZE_CHOICES''' ► Configure select field to choose number of lines displayed on listing (<code>10:10,15:15,20:20,30:30,40:40,50:50,100:100,250:250,500:500,1000:1000,5000:5000</code>).

*'''MAIN_USE_TOP_MENU_QUICKADD_DROPDOWN''' ► Add a dropdown menu with shortcuts to create new objects ► (v13.0)

*'''MAIN_EMAILCOLLECTOR_MAIL_WITHOUT_HEADER''' ► Remove the header stored by email collector ► (v13.0)

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID'''

*'''MAIN_OPTIMIZEFORTEXTBROWSER''' ► Optimise interface for a text only browser. This variable is set to 1 automatically if your browser is lynx or links

*'''MAIN_NB_OF_YEAR_IN_WIDGET_GRAPH''' ► Set the number of years visible on some graph of some widgets (2 is default value)

*'''MAIN_CREATEFROM_KEEP_LINE_ORIGIN_INFORMATION'''

*'''API_DISABLE_LOGIN_API''' ►(v14.0)

*'''MAIN_LOGIN_BADCHARUNAUTHORIZED''' ► Add possibility to define bad character unauthorized into login name REGEX expression (Default value is @<>"\') ► (v16.0)
*'''MAIN_SHOW_ALL_FILES_ON_DOCUMENT_TOOLTIP''' ► Add all files visible from the object to be visible from the list of object.
*'''MAIN_LIST_ALLOW_PUBLIC_NOTES''' ► Display public notes on list
*'''MAIN_LIST_ALLOW_PRIVATE_NOTES''' ► Display private notes on list

*'''MAIN_CHECKBOX_LEFT_COLUMN''' ► Display private check boxes on the left ► (v17.0)
*'''MAIN_STATS_GRAPHS_SHOW_N_YEARS''' ► Nb of years to shows in widget and graph ► (v14.0)
*'''MAIN_HOOK_DEBUG''' ► if >=2 the hook in the logs are more verbose ► (v18.0)

*'''MAIN_ENABLE_AJAX_TOOLTIP''' ► if 1 the tooltips are updated with AJAX request ► (v18.0)
*'''MAIN_NO_INPUT_PRICE_WITH_TAX''' ► if 1 the TTC input field is removed from propal/invoices/... ► (v17.0)

*'''MAIN_DISABLE_SELECT2_FOCUS_PROTECTION''' ► if 1 disable the focus protection ► (v17.0)
*'''MAIN_USE_ADVANCED_PERMS ►''' Add advanced user permission

*'''MAIN_FREE_PRODUCT_CHECKED_BY_DEFAULT ►''' Check "product" or "service" by default on order/invoices/propal cards (set value "product" or "service")

[[#Top|(back to top)]]

=Security Options=

*'''MAIN_SECURITY_ANTI_SSRF_SERVER_IP''' ► Can set a complete list of IPs of server.

*'''MAIN_SECURITY_CSRF_WITH_TOKEN''' ► Activate a second anti-CSRF protection on POST (so 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 more powerful. ► (v5.0+)

*'''MAIN_MODULES_FOR_EXTERNAL''' ► Limit available modules for external users. By default value is '<code>facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda</code>'

*'''MAIN_ALLOW_SVG_FILES_AS_IMAGES''' ► Allow to use SVG file as image files. Warning: This may introduce security vulnerability (javascript can be embedded into SVG file).

*'''MAIN_RESTRICTHTML_ONLY_VALID_HTML''' ► Refused parameter if value is not a valid HTML content.

*'''MAIN_RESTRICTHTML_REMOVE_ALSO_BAD_ATTRIBUTES''' ► Sanitize also non standard attributes on HTML content.
*'''MAIN_SECURITY_SALT''' ► A salt string to base the hashing on. 8 strings length recommended.

*'''MAIN_SECURITY_MAX_IMG_IN_HTML_CONTENT''' ► Maximum number of Images on the HTML content
*'''MAIN_SECURITY_ALLOW_UNSECURED_LABELS_WITH_HTML''' ► Allow HTML tags into products label

*'''MAIN_SECURITY_FORCERP''' = "strict-origin-when-cross-origin" (default) so browser doesn't send any referrer when going into another web site domain / "same-origin" / "strict-origin"

[[#Top|(back to top)]]

=Adherent Module=

*'''MEMBER_NEWFORM_FORCEMORPHY''' ► Force nature of member set to "phy" for physical or to "mor" for moral ► (v12.0)
*'''MEMBER_ALLOW_CHANGE_OF_TYPE''' ► Member can edit their type on public subscription page ► (v13.0)
*'''ADHERENT_DEFAULT_CREATE_THIRDPARTY''' ► Thirdparty is created when creating a new member ► (v13.0)
*'''MEMBER_SUBSCRIPTION_SUGGEST_END_OF_MONTH''' ► If set to 1, the member subscription end date will be suggested for the end of the month ► (v18.0)
*'''MEMBER_SUBSCRIPTION_SUGGEST_END_OF_YEAR''' ► If set to 1, the member subscription end date will be suggested for the end of the year ► (v18.0)
*'''MAIN_NB_OF_YEAR_IN_MEMBERSHIP_WIDGET_GRAPH''' ► If set, it limits the number of years visible on graph and widgets of membership (empty is default value to show all) ► (v18.0)

[[#Top|(back to top)]]

=Accountancy Module=

*'''ACCOUNTANCY_COMBO_FOR_AUX''' ► Add graphic option for ACCOUNTANCY_COMBO_FOR_AUX. Having this option on may slow down and even freeze the accounting features if you have a very large number of thirdparties ► (v10.0)
*'''ACCOUNTING_DEFAULT_NOT_NOTIFIED_VALIDATION_DATE''' ► Avoid validating the lines with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*'''ACCOUNTING_DEFAULT_NOT_NOTIFIED_EXPORT_DATE''' ► Avoid flagging the lines as exported with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*'''ACCOUNTANCY_USE_PRODUCT_ACCOUNT_ON_THIRDPARTY ►''' Add 2 fields on thirdparty card which allow you to set an account for all sells products and an other for all buying products for this customer ► (v14.0)

[[#Top|(back to top)]]

=Agenda Module=

*'''AGENDA_ALL_CALENDARS''' ► Change the default view of calendar pages to see all the Agenda's (instead or yours only be default)

*'''AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS''' ► To automatically set end date of event to start date + delta on event creation page.

*'''AGENDA_DISABLE_LOCATION''' ► Disable location field in action card ► (>=v5.0)

*'''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''''').

*'''MAIN_ADD_EVENT_ON_ELEMENT_CARD''' ► Allow to create an event from a document (proposal, order, invoice)

*'''AGENDA_SUPPORT_PRIORITY_IN_EVENTS''' ► Allow to have priorities in events ► (>=v13.0)

*'''AGENDA_ADDACTIONFORPHONE''' ► Allow you to create a event from phone number ► (=<v12.0) - Need to be fix for (=>v12.0) https://github.com/Dolibarr/dolibarr/issues/22720

*'''AGENDA_ADDACTIONFOREMAIL''' ► Allow you to create a event from Email ► (=<v12.0) - Need to be fix for (=>v12.0) https://github.com/Dolibarr/dolibarr/issues/22720

[[#Top|(back to top)]]
=Bank Module=

*'''BANK_CAN_RECONCILIATE_CASHACCOUNT''' ► Can reconciliate cash accounts ► (v3.8)

*'''BANK_DISABLE_CHECK_DEPOSIT''' ► Disable check deposit feature

*'''BANK_ASK_PAYMENT_BANK_DURING_ORDER''' ► Ask bank account during creation of an order

*'''BANK_ASK_PAYMENT_BANK_DURING_PROPOSAL''' ► Ask bank account during creation of a proposal

*'''BANK_USE_OLD_VARIOUS_PAYMENT''' ► To allow to enter miscellaneous payments (not covered by other modules) using old method. '''''Deprecated'''''. Entering various payment is preferred ► (<=v12.0).
*'''MAIN_IBAN_IS_NEVER_MANDATORY''' ► IBAN and BIC informations not mandatory. (V15)

[[#Top|(back to top)]]

 

=BOM and MO Module=

*'''ALLOW_USE_KITS_INTO_BOM_AND_MO'''
*'''BOM_SUB_BOM''' ►Allow to add a BOM in another BOM►(v16.0)

[[#Top|(back to top)]]

 

=Bookmarks Module=

*'''BOOKMARKS_SHOW_IN_MENU''' ► Numbers of bookmark entries to be displayed (10 by default)

[[#Top|(back to top)]]

 

=Inalterable Log Module=

*'''BLOCKEDLOG_ADD_ACTIONS_SUPPORTED''' ► Can complete list of triggered action that are logged

[[#Top|(back to top)]]

 

=Category-Tags Module=

*'''CATEGORY_SHOW_COUNTS''' ► Shows nb of object by tags in tag tree

[[#Top|(back to top)]]

 

=Contracts=

*'''CONTRACT_SUPPORT_PRODUCTS''' ► Products are also suggested into module contract.
*'''CONTRACT_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)
*'''CONTRACT_HIDE_PLANNED_DATE_ON_PDF''' ► allows you to not display dates on pdf files.
*'''CONTRACT_HIDE_REAL_DATE_ON_PDF''' ► allows you to not display dates on pdf files.
*'''CONTRACT_HIDE_PRICE_ON_PDF''' ► allows you to not display price on pdf files.
*'''CONTRACT_HIDE_QTY_ON_PDF''' ► allows you to not quantity dates on pdf files.

[[#Top|(back to top)]]

=Cron module=

*'''CRON_DISABLE_KEY_CHANGE''' ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*'''CRON_DISABLE_TUTORIAL_CRON''' ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*'''CRON_WARNING_DELAY_HOURS''' ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

[[#Top|(back to top)]]

 

=Direct Debit Orders=

*'''WITHDRAWAL_ALLOW_ANY_INVOICE_STATUS''' ► If this option is set, all invoices status (even already paid) may appear on the list of invoices qualified for a direct debit payment. This is the list of invoices with a payment request done, and not linked to a direct debit payment. By default, only "unpayed" invoices are used to avoid to pay twice the same invoice.

[[#Top|(back to top)]]

=Donation Module=

*'''DONATION_USE_THIRDPARTIES''' ► If this option is set, a thirdparty field appear on donation forms.

[[#Top|(back to top)]]
=Email=

*'''MAIN_COPY_FILE_IN_EVENT_AUTO''' ► Add attachment document on event auto generated by sending email from dolibarr. ► (v6.0+)

*'''MAIN_EMAIL_USE_LAYOUT'''► Enable the use of predefined layout when writing an email.

*'''MAIN_MAILFORM_DISABLE_ENTERKEY''' ► Activate JavaScript code to disable the enter key in the MAIL form. ► (>= 8.0.1)

*'''MAIN_MAIL_DEBUG''' ► Write content with header of last mail into file <code>dolibarr_mail.log</code> into directory <code>dolibarr_main_data_root</code>.

*'''MAIN_MAIL_DEBUG_ERR_WITH_DATE''' ► Use a different filename (by adding a prefix of date) for each email sent with error when MAIN_MAIL_DEBUG.

*'''MAIN_MAIL_DEBUG_LOG_WITH_DATE''' ► Use a different filename (by adding a prefix of date) to log each email sent (whatever is result) when MAIN_MAIL_DEBUG.

*'''MAIN_MAIL_FORCE_FROM''' ► (v19+) Can force the value into the From field of the SMTP header. Note that email sender is always saved into the "Reply-To".

*'''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 <code>-f</code>. This option is here to ask Dolibarr to call the function mail of PHP by adding value for the option <code>-f</code>. 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 setup or version of sendmail that ask the -f option to be mandatory or for sendmail setup that does not use by default the From of the header email to define the sender (with this option, the from can be forced on command line to avoid to have the from lost by sendmail).

*'''MAIN_MAIL_SENDMAIL_FORCE_BA''' ► On Linux 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 asks PHP to provide this parameter when sending a mail. Note that another solution is to edit the mail.force_extra_parameters=-ba into <code>php.ini</code> 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 <code>orange.fr</code> or <code>hotmail.com</code>

*'''MAIN_MAIL_DO_NOT_USE_SIGN''' ► Do not add user signature at end of suggested pre-defined email

*'''MAIN_MAIL_FORCE_NOT_SENDING_TO''' ► If en email is defined into this variable, emails will never be sent to this email.

*'''MAIL_FORCE_DELIVERY_RECEIPT_INVOICE''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Invoice'' module.

*'''MAIL_FORCE_DELIVERY_RECEIPT_ORDER''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Order'' module.

*'''MAIL_FORCE_DELIVERY_RECEIPT_PROPAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Proposal'' module.
*'''MAIL_FORCE_DELIVERY_RECEIPT_SUPPLIER_PROPOSAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Supplier Proposal'' module.

*'''MAIN_EMAIL_SUPPORT_ACK ►''' Restore email acknowledgment checkbox on sending emails. This feature is commonly abandoned by mailers. Active from Dolibarr V17 - see [https://github.com/Dolibarr/dolibarr/blob/33744f74da1a5c20f8aa9950018ab4e549e00205/ChangeLog#L53 changelog]
*'''MAIN_EMAIL_USECCC''' ► 1 = Shows field BCC into email forms, If value is an email = Shows the BCC pre filled with the email value.

*'''MAIN_MAIL_AUTOCOPY_PROPOSAL_TO''', '''MAIN_MAIL_AUTOCOPY_ORDER_TO''', '''MAIN_MAIL_AUTOCOPY_INVOICE_TO''', '''MAIN_MAIL_AUTOCOPY_SHIPMENT_TO''', '''MAIN_MAIL_AUTOCOPY_..._TO''' ► Email to use as a BCC recipient 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 third party 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 third party or object, the email exchange is related to.

*'''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► Restrict sending of 1 email message to <code>x</code> recipients for same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include 1000 recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available.

*'''MAIN_MAIL_FORCE_CONTENT_TYPE_TO_HTML''' ► Force to send all email (event with text only content) as HTML formatted email.

*'''MAIN_MAIL_USE_MULTI_PART''' ► Forge email content using an alternate text part ► (for 5.0.2+). By default with 6.0+
*'''MAIN_INFO_SOCIETE_MAIL_ALIASES''' ► add address aliases for the from field on mail. Set his value with "Firstname Name <firstname.lastname@mydomain.tld, Otherfirstname OtherlastName <othermail@mydomain.tld>,..." ► (v5.0.0+)

*'''MAIN_MAIL_ADD_INLINE_IMAGES_IF_IN_MEDIAS''' ► If images were stored into the medias directory from CKEditor, then images into emails are replaced with "inline content". This may increase seriously risk of being detected as SPAM.

*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option '''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD'''.

*'''MAIN_IMAP_USE_PHPIMAP''' ► Use embedded PHP-imap library (not using the native php imap) instead of native php imap extension ► (v17.0+, available as official option in setup of emailcollector by default from v19)

*'''MAIN_MAIL_ENABLED_USER_DEST_SELECT''' ► Show also internal users into list of recipients of email in email sending form ► (v8.0+)

*'''MAIL_PREFIX_FOR_EMAIL_ID''' ► Prefix for the mails ID. Default value is <code>$_SERVER["SERVER_NAME"]</code> ► (>= 8.0.1)

[[#Top|(back to top)]]

=SMS=

*'''MAIN_SMS_DEBUG''' ► Write content of SMS sent into file <code>dolibarr_sms.log</code> into directory <code>dolibarr_main_data_root</code>.

[[#Top|(back to top)]]

=Emailing Module=

*'''MAILING_PREFIX_FOR_EMAIL_ID''' ► Set the value that will be used to compose the "Email ID" into email headers. If you set this value to '<code>SERVER_NAME</code>', the virtual host of web server will be used. By default, this is not defined, so a hash key, unique to each instance, is used.

*'''MAILING_NO_USING_PHPMAIL''' ► If set, the module emailing can't be used with mail setup of "phpmail". Using a thirdparty SMTP server is required. You can complete warning message by adding an email to contact for setup help with constant <code>'''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS'''</code>.

*'''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS''' ► Contains the email of contact to show into the message visible to a user when he try to use emailing module without SMTP server and if option '''MAILING_NO_USING_PHPMAIL''' is set to on.

*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is on "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.

*'''MAILING_LIMIT_WARNING_NOPHPMAIL''' ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is something else than "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.
*'''EMAILING_USE_ADVANCED_SELECTOR''' ► Enable the advanced selector for recipients.

*'''MAILING_LIMIT_SENDBYWEB''' ► Restrict number of emails you can send in same sending session with emailing module from GUI. The value "<code>dolibarr_mailing_limit_sendbyweb</code>" if defined into config file is used in priority for this limit. A negative value means, sending by web is forbidden.

*'''MAILING_LIMIT_SENDBYCLI''' ► Restrict number of emails you can send in same sending session with emailing module from CLI script. The value "<code>dolibarr_mailing_limit_sendbycli</code>" if defined into config file is used in priority for this limit.

[[#Top|(back to top)]]

 

=Expense Report=

*'''EXPENSEREPORT_ALLOW_OVERLAPPING_PERIODS''' ► Can enter several expense reports on same or overlapping date periods. ► (v7.0+)

*'''EXPENSEREPORT_OVERRIDE_VAT''' ► Setting this constant to 1 will allow expense reports to show VAT even if the global VAT setting is off ► (v10.0)

*'''EXPENSEREPORT_USE_OLD_NUMBERING_RULE''' ► The module Expense Report use numbering rules that you can setup (like other modules do). If you need to keep the hard-coded numbering rule of expenses report used in v6.0 set this constant to 1 ► (>=v7.0+)

*'''MAIN_USE_EXPENSE_IK''' ► This feature allows you to set index kilometres against a mileage index for different types of vehicles. ► (v7.0+)

*'''MAIN_USE_EXPENSE_RULE''' ► This feature allows you to set a variety of rules per user/group/all so they can only create reports within their limits. ► (v7.0+)

[[#Top|(back to top)]]

 

=Export Module=

*'''EXPORT_CSV_SEPARATOR_TO_USE''' ► String value to use as default separator to delimit fields of exported files (by default Dolibarr uses "<code>,</code>"). Example: EXPORT_CSV_SEPARATOR_TO_USE=<code>;</code>

*'''EXPORT_CSV_FORCE_CHARSET''' ► Choose the charset used in the output file built by the CSV exporter. By default it is ISO-8859-1. Example: EXPORT_CSV_FORCE_CHARSET= <code>utf-8</code>

*'''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 (<code>"</code>).
*'''EXPORTS_SHARE_MODELS''' ► Share export models between users.

[[#Top|(back to top)]]

=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 added in front of payment cell, into the page to make online subscription.

[[#Top|(back to top)]]

 
=Holiday Module=

*'''HOLIDAY_HIDE_BALANCE''' ► Hide the user's vacation balance on the vacation request page

[https://wiki.dolibarr.org/Setup_Other#Top (back to top)]
=Interventions Module=

*'''FICHINTER_CLASSIFY_BILLED'''► Allow to classify an intervention card as "Billed". This add also trigger <code>FICHINTER_CLASSIFY_BILLED</code> into list of possible automatic event into agenda.

*'''FICHINTER_DISABLE_DETAILS'''► Disable entry of details line on intervention. Can validate with no line.

[[#Top|(back to top)]]

=Invoice Module=

*'''MAIN_DEPOSIT_MULTI_TVA''' ► In deposits invoice, creates one line per VAT rate from the origin document ► (6.0)

*'''INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED''' ► If a credit note was partially refunded (a refund was sent to the customer), with common situation, we wait to have the remain refunded too. With this option, it is possible to convert the remain of invoice into a discount to reuse it into another invoice.

*'''SUPPLIER_INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED''' ► See INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED, but for supplier credit notes.

*'''INVOICE_CAN_ALWAYS_BE_EDITED''' changed in version 15 or 16 to '''INVOICE_CAN_BE_EDITED_EVEN_IF_PAYMENT_DONE''' ► Allow to edit invoices even if payment was started. Note: If the module "BlockedLog" is active (required in some countries for legal reasons), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*'''INVOICE_CAN_ALWAYS_BE_REMOVED''' ► Allow to always delete invoices (even if invoice is not last one). Note: If the module "BlockedLog" is active (required by some countries for legal reason), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*'''INVOICE_CAN_NEVER_BE_REMOVED''' ► Never allow to delete invoices (except draft invoices with ref like (PROV%)).

*'''INVOICE_POSITIVE_CREDIT_NOTE''' ► All amounts on PDF credit notes are positive.

*'''FACTURE_DEPOSITS_ARE_JUST_PAYMENTS''' ► An old way to create initial payment. This treats deposit invoices as a special case and not as legal deposit invoice. 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. WARNING: In a lot of european countries, using this option is not allowed.

*'''FACTURE_SENDBYEMAIL_FOR_ALL_STATUS''' ► Can send invoice by email to customer even if invoice has status "draft".

*'''INVOICE_CREDIT_NOTE_STANDALONE''' ► Start implementation to allow a credit note even without invoice (dangerous) ► (v3.9)

*'''INVOICE_USE_SITUATION''' ► 1=Enable the "situation invoice" feature. Warning, this feature is bugged and may not be compatible with the final version of the feature once the bug will be solved. Also, using the double-entry accountancy module is not possible when this option is on (due to the same design problem). 2=Enable the "situation invoice" feature with a rewrite. This mode should be better to become a future stable feature.

*'''INVOICE_USE_SITUATION_CREDIT_NOTE''' ► Enable the "situation credit note" feature (need <code>INVOICE_USE_SITUATION</code>) ► (v8.0)
*'''INVOICE_USE_RETAINED_WARRANTY''' ► Enable the retained warranty on invoice ► (v14.0)

*'''INVOICE_DISABLE_DEPOSIT''' ► Disable deposit invoices

*'''INVOICE_DISABLE_REPLACEMENT''' ► Disable replacement invoices

*'''INVOICE_DISABLE_CREDIT_NOTE''' ► Disable credit notes

*'''INVOICE_ADD_ZATCA_QR_CODE''' ► Add a QR code with format ZATCA (for Saudi Arabia) on PDF of invoices.
*<bdi>'''INVOICE_ADD_EXTRAFIELD_IN_NOTE''' ► Add extrafields in note for canelle template ► (v17.0+)</bdi>
*'''INVOICE_DEFAULT_NOTE_PUBLIC''' <bdi>► Default text in public note</bdi>

Note: To decode a QR image of a ZATCA code: https://www.onlinebarcodereader.com/. You can also use the mobile application https://play.google.com/store/apps/details?id=com.posbankbh.einvoiceqrreader&gl=FR

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT''' ► See PDF option

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN''' ► See PDF options

*'''WORKFLOW_BILL_ON_SHIPMENT''' ► Change label of button with suitable label when you need to create invoice on shipments

*'''INVOICE_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. Use the tag __DIRECTDOWNLOAD_URL_INVOICE__ in email template to insert it. ► (v7.0+)

*'''INVOICE_POINTOFTAX_DATE''' ► Add Point of Tax Date on invoices for country-specific legality reasons ► (v4.0+)
*'''FACTURE_ENABLE_NEGATIVE''' ► Can validate an invoice when amount is negative

*'''FACTURE_ENABLE_NEGATIVE_LINES''' ► Allows to add negative lines to an invoice ► (v8.0.2+)

*'''INVOICE_USE_DEFAULT_DOCUMENT''' ► Allow user to select a default invoice documents models according to invoice type. On invoice create page, the model is dynamically changed on invoice type selection. ► (v9.0+)

*'''FACTURE_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object (Proposal,...) when creating the bill.
*'''FACTUREFOURN_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object when creating the supplier bill ► (V13.0)
*'''MAIN_SHOW_FACNUMBER_IN_DISCOUNT_LIST''' ► Display the reference of credit notes in discount list when creating the bill.
*'''INVOICE_ALLOW_FREE_REF''' ► Capability to change reference of an invoice. This will be possible as long as the invoice has the status “Draft” and only if your country is not in Europe(V11)

*'''INVOICE_DISALLOW_REOPEN'''

*'''INVOICE_MAX_FUTURE_DELAY''' ► Numbers of seconds allowed for billing in the future ► (V14.0)
*'''INVOICE_AUTO_NEXT_MONTH_ON_LINES''' ► Increase start date and end date by one month, if an invoice line is a clone of a time based service AND if this services started on the first day of month and ended on the last day of month ► (V13.0.1)
*'''INVOICE_KEEP_DISCOUNT_LINES_AS_IN_ORIGIN''' ► Does not change a line with a negative price into an absolute discount when creating an invoice ► (V16 ?)
*'''INVOICEREC_SET_AUTOFILL_DATE_START''' and '''INVOICEREC_SET_AUTOFILL_DATE_END ►''' Set start and end date to yes for lines of template invoice when created from a draft invoice ► (V16)
*'''INVOICE_REC_DATE_TO_YES''' '''►''' Set start and end date to yes by default in add line form for template invoice ► (V16)
*'''INVOICE_SUBTYPE_ENABLED''' ► Extends Dolibarr standard invoice with more invoice types used in some countries. A combo box in the new invoice creation card allows the selection of "subtypes" with values from dictionary "Invoice Subtypes" ► (v19.0+)

[[#Top|(back to top)]]

=Leave=

*'''MAIN_NON_WORKING_DAYS_INCLUDE_SATURDAY''' ► Set this value to 0 if you want to have the Saturday as a working day
*'''MAIN_NON_WORKING_DAYS_INCLUDE_SUNDAY''' ► Set this value to 0 if you want to have the Sunday as a working day

=Look or Theme=

*'''MAIN_FAVICON_URL''' ► favicon url

*'''MAIN_EASTER_EGG_COMMITSTRIP''' ► Show a comic image from the CommitStrip website. Images are refreshed daily. ► (v6.0+)

*'''MAIN_STATUS_USES_CSS''' ► Change status design using new style ► (v10.0+)

*'''MAIN_INCLUDE_GLOBAL_STATS_IN_OPENED_DASHBOARD''' ► This conf will auto remove global stats box item if there are already in the new dashboard of opened elements and keep displayed stats on the opened item box (not only on mouse over) ► (v11.0+)

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Actually only for eldy theme, this conf move search input to top menu and use new design too ► (v11.0+)

*'''THEME_AGRESSIVENESS_RATIO''' ► This conf can be used to increase/decrease aggressiveness of colors. Value 0 is medium, value is between -100 (light grey colors) to +100 (very flashy colors) ► (v11.0+)

*'''THEME_SHOW_BORDER_ON_INPUT'''
*'''MAIN_DISABLE_GLOBAL_WORKBOARD''' ► Hide the work board of the main page ► (v13.0+)
*'''MAIN_DISABLE_GLOBAL_BOXSTATS''' ► Hide the Statistic Box of the main page
*'''ALLOW_THEME_JS ►''' Allow JS file in theme folder (same name as theme folder)

 

=Manifest (Progressive Web App)=

*'''MAIN_MANIFEST_APPLI_THEME_COLOR ►''' Theme color for manifest
*'''MAIN_MANIFEST_APPLI_BG_COLOR ►''' Background color for manifest
*'''MAIN_MANIFEST_APPLI_LOGO_URL ►''' Logo for manifest
*'''MAIN_MANIFEST_APPLI_LOGO_URL_SIZE ►''' Logo url size for app (150, 192, 512px) missing 3 configurations

[[#Top|(back to top)]]

=Order Module=

*'''MAIN_MASSACTION_CREATEBILLS_REDIRECT_IF_ONE''' ► If set 1, redirects to the one bill created from massaction create bills from order list ► (v20.0)

*'''MAIN_MASSACTION_CREATEBILLS_REDIRECT_IF_MANY''' ► If set to 1, redirects to the invoice list after plural invoices where generated from tho massaction create bills from order list ► (v20.0)

*'''MAIN_ORDERLIST_CREATEBILLS_ONEBYTHIRD''' ► Allow defining value for option "one by thirdparty" in massaction create bills from orders list page (no by default, yes if set to 'yes' or 1) ► (v20.0)

*'''MAIN_USE_PROPAL_REFCLIENT_FOR_ORDER''' => Copy customer reference from proposal to order. ► (v7.0+)

*'''ORDER_REQUIRE_SOURCE''' => Make the input field "Source of order" mandatory.

*'''ORDER_VALID_AFTER_CLOSE_PROPAL''' => When an order is created on a proposal close, the order is directly defined with status "Validated".

*'''ORDER_ALLOW_EXTERNAL_DOWNLOAD''' => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*'''ORDER_ENABLE_NEGATIVE''' => Can validate an order when amount is negative

*'''THIRDPARTY_PROPAGATE_EXTRAFIELDS_TO_ORDER''' => Copy also extrafields from thirdparty to order (if name match). ► (v11.0+)
*'''MAIN_REMOVE_DROPDOWN_CREATE_BUTTONS_ON_ORDER''' => Remove the create dropdown button on order card (introduce on v19) to come back with old buttons. '''►''' (v20.0+)

[[#Top|(back to top)]]

 

=PDF Options=

*'''MAIN_ADD_PDF_BACKGROUND''' ► Define this constant with short name of a PDF file (example "<code>mypdf.pdf</code>") that must be saved into directory "<code>documents/mycompany</code>". 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_DISABLE_FORCE_SAVEAS''' ► If your browser always asks to save downloaded files on disk (like PDF), try this this option. File may be displayed directly in your browser. Values : 0= Default (file is auto downloaded), 1= For to output the file into the browser tab, 2= For to output the file into a browser tab open with target_blank

*'''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 servers with low CPU.

*'''MAIN_DISABLE_PDF_COMPRESSION''' ► Disable PDF compression.

*'''MAIN_DOCUMENTS_WITH_PICTURE_WIDTH''' ► Can change size of picture when hidden option <code>MAIN_GENERATE_PROPOSALS_WITH_PICTURE</code> is used. By default value is <code>20</code>.

*'''MAIN_GENERATE_DOCUMENTS_SHOW_FOOT_DETAILS''' ► Adding the company address at the bottom of the page. Disabled by default

*'''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer proposals.
*'''MAIN_GENERATE_ORDERS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer orders.

*'''MAIN_GENERATE_INVOICES_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer invoices.

*'''MAIN_GENERATE_SUPPLIER_PROPOSAL_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier proposals ► (v5.0.3+)
*'''MAIN_GENERATE_SUPPLIER_ORDER_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier orders

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT''' ► Disable VAT on generated documents. like for an association. (Works with crabe template)

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN''' ► Hide column with VAT information but only column not total.

*'''MAIN_INVERT_SENDER_RECIPIENT''' ► Invert sender and recipient in some PDF. Note: This option is set automatically if country if Germany.

*'''MAIN_ODT_AS_PDF''' ► Activate ODT to PDF conversion. Value can be "libreoffice" or "unoconv". Do not use value '''<nowiki/>'jodconverter'<nowiki/>''' any more, as it is declared deprecated and partly not functional, use value '''<nowiki/>'libreoffice'''' instead, it requires only '''soffice''' (OpenOffice or LibreOffice) installed on server (use '''apt install soffice libreoffice-common libreoffice-writer''').

If you got this error: javaldx failed! Warning: failed to read path from javaldx with no return to prompt when running soffice --headless -env:UserInstallation=file:"/tmp" --convert-to pdf --outdir xxx ./yyy.odt, check that directory defined into env:UserInstallation parameters exists and is writeable.

You may also have a look at this page if your server is on Windows: [[Générer automatiquement des documents PDF à partir de fichier ODT avec Doliwamp]]

*'''MAIN_ODT_AS_PDF_DEL_SOURCE''' ► For ODT generation. If set, then initial behaviour is conserved but ODT file is removed when option to convert it as PDF (see previous) is on. Disabled by default

*'''MAIN_PDF_FORCE_FONT''' ► To ignore font defined into language file and force usage of a particular font. For example "<code>DejaVuSans</code>".

*'''MAIN_PDF_FORCE_FONT_SIZE''' ► To force size of font (by default 10). For example "<code>12</code>" ► (v11.0)

*'''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: <code>220,220,200</code>

*'''MAIN_PDF_USE_LARGE_LOGO''' ► Use the original logo with its higher resolution into the PDF instead of the small thumb. This may lead to very very large PDF !

*'''MAIN_USE_BACKGROUND_ON_PDF''' ► Define this constant with short name of an image (example "<code>myimage.jpg</code>") that must be saved into directory "<code>documents/mycompany/logos</code>". This will add this background image into your generated PDF files.

*'''MAIN_USE_COMPANY_NAME_OF_CONTACT''' ► Use contact name and information rather than company

*'''MAIN_PDF_ADDALSOTARGETDETAILS''' ► If 1, add details of recipient on generated PDFs (email, fax, url and phone). Can be useful in cases where a printed order/invoice etc is given to a delivery driver/courier etc.

*'''MAIN_TVAINTRA_IN_SOURCE_ADDRESS''' ► Show VAT N° in source address of PDF to comply with legalities in certain countries. Note that VAT number should be already visible in footer of page ► (v8.0.1+)

*'''MAIN_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► Add optional esign field in pdf propal ► (v8.0+)

*'''MAIN_PROFID1_IN_SOURCE_ADDRESS''' ► Show Professional ID 1 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID2_IN_SOURCE_ADDRESS''' ► Show Professional ID 2 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID3_IN_SOURCE_ADDRESS''' ► Show Professional ID 3 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID4_IN_SOURCE_ADDRESS''' ► Show Professional ID 4 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID5_IN_SOURCE_ADDRESS''' ► Show Professional ID 5 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID6_IN_SOURCE_ADDRESS''' ► Show Professional ID 6 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

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

*'''PDF_BOLD_PRODUCT_REF_AND_PERIOD''' ► Add more visibility (bold) on product ref and period of service in desc. ► (v12.0)

*'''PDF_HIDE_PRODUCT_REF_IN_SUPPLIER_LINES''' ► Modify the use/position of Supplier Ref/Internal Ref with the item Label (name) on PDF documents.

Default (constant not set or Value <code>0</code>): Internal ref followed by supplier ref in brackets."COMPANY-REF-001 (Vendor SKU SUPPLIER-REF-001) - LABEL...".

Value <code>1</code>: Supplier ref only eg."SUPPLIER-REF-001 - LABEL...".

Value <code>2</code>: Supplier ref followed by internal ref in brackets. eg."SUPPLIER-REF-001 (InternalRef COMPANY-REF-001) - LABEL...".

*'''PDF_INCLUDE_ALIAS_IN_THIRDPARTY_NAME''' ► Include alternative/alias name into name on PDF.

*'''PDF_SECURITY_ENCRYPTION''' ► Encrypt PDF produced by dolibarr ► (v?) . See additional parameters :PDF_SECURITY_ENCRYPTION_RIGHTS (block 'modify' or 'copy') - '''PDF_SECURITY_ENCRYPTION_USERPASS''' - '''PDF_SECURITY_ENCRYPTION_OWNERPASS''' (random if not specified) - '''PDF_SECURITY_ENCRYPTION_STRENGTH''' (0 = RC4 40 bit; 1 = RC4 128 bit; 2 = AES 128 bit; 3 = AES 256 bit) - '''PDF_SECURITY_ENCRYPTION_PUBKEYS''' Array of recipients containing public-key certificates ('c') and permissions ('p') - For example: array(array('c' => 'file://../examples/data/cert/tcpdf.crt', 'p' => array('print')))

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

*'''PDF_USE_ALSO_LANGUAGE_CODE''' ► The value of this constant must be a language code ('fr_FR', 'en_US', 'sa_SA', ...). If set, the PDF document will contains both language (default and the one defined by the constant).
*'''DOC_SHOW_FIRST_SALES_REP''' ► Show the sales representant on header (at least on propal azur and rubis template)
*'''MAIN_PDF_DASH_BETWEEN_LINES'''
*
*'''SHOW_SUBPRODUCT_REF_IN_PDF'''
*'''PDF_HIDE_PRODUCT_LABEL_IN_SUPPLIER_LINES''' ► hide product label in supplier order lines (V15+)
*'''SHIPPING_PDF_DISPLAY_AMOUNT_HT''' ► Show HT unit price and HT total price for lines of PDF shipment

*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_FACTURE''' ► To Hide product description in Customer Invoice
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_COMMANDE''' ► To Hide product description in Sales Order
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_ORDER_SUPPLIER''' ► To Hide product description in Purchase Order
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_INVOICE_SUPPLIER''' ► To Hide product description in Vendor Invoice

*'''PDF_PROPAL_SHOW_PRICE_INCL_TAX''' ► Display price with tax on Proposal(cyan template), Order(eratosthene template), Bill(sponge template) (V17+)

[[#Top|(back to top)]]

=Point of Sale (POS)=

*'''CASHDESK_SHOW_KEYPAD''' ► Show a mouse key pad into the 'Simple Point of Sale' module.

*'''POS_ADDON''' ► Set this value to an existing numbering module rule (for example '<code>mod_facture_terre</code>', '<code>mod_facture_mars</code>', ...) to force the numbering module to use for invoice ref definition when invoice is created by the POS. For example setting value <code>POS_ADDON</code> to '<code>mod_facture_terre</code>' will use the numbering module '<code>terre</code>' for invoice generated from POS, whatever is the numbering rule defined into invoice module setup (you can also use POS_NUMBERING_TERRE_FORCE_PREFIX and POS_NUMBERING_MARS_FORCE_PREFIX variable to change the prefix used).

*'''TAKEPOS_ENABLE_SUMUP''' ► Enable the compatibility of TakePOS with the card reader terminal [https://SumUp.fr SumUp]
*'''TAKEPOS_CAN_FORCE_BANK_ACCOUNT_DURING_PAYMENT''' ► Possibility to force the bank account during the payment in TakePOS ► (v13.0)
*'''TAKEPOS_CONTROL_CASH_OPENING''' ► Control the cash opening
*'''TAKEPOS_NUMPAD_FORCE_PAYMENT_ICONS_LABELS'''

[[#Top|(back to top)]]

=Products Module=

*'''CATEGORY_GRAPHSTATS_ON_PRODUCTS''' ► Show graph of products with categories and totals in Products Area screen

*'''MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE''' ► Avoid customs 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.

*'''MAIN_DIRECT_STATUS_UPDATE''' ► Allows you to change the status of the product (''for sale/not for sale for purchase/not for purchase'') directly on the product page via a ''on/off'' switch button. This can be convenient for those who need to quickly disable certain statuses of products without having to go through the editing product page individually. Also can be very useful if used as a filter on the product and product search list. This option doesn't generate a MODIFY trigger, so be careful with external modules. ► (v4.0+)

*'''MAIN_SEARCH_PRODUCT_BY_FOURN_REF''' ► Allow to search a product by supplier ref in document's add line form. ► (>= 8.0)

*'''MAIN_DISABLE_FREE_LINES''' ► Disallow using free lines to add line in documents ► (>= 8.0)

*'''MAIN_SHOW_PRODUCT_ACTIVITY_TRIM''' ► Show Product and Services turnover before for all four quarters tax over recent years recent years on the product area ► (v5.0+)

*'''PRODUIT_DESC_IN_LIST''' ► Show long description of product/service into lists.

*'''PRODUCT_DISABLE_PROPAGATE_CUSTOMER_PRICES_ON_CHILD_COMPANIES''' ► Disable propagation of prices per customer from a customer to its child company.

*'''PRODUCT_DISABLE_PUBLIC_URL''' ► Disable public url in product card ► (v14.0+)
*'''PRODUCT_DISABLE_STOCK_LEVELS''' ► Disable properties of stock limits and desired optimal value on product ► (v14.0+)
*'''PRODUCT_DISABLE_NATURE''' ► Disable nature in product card ► (v14.0+)
*'''PRODUCT_DISABLE_WEIGHT''' ► Disable weight in product card ► (v14.0+)
*'''PRODUCT_DISABLE_PRICES''' ► Disable prices in product card ► (v14.0+)
*'''PRODUCT_DISABLE_ACCOUNTING''' ► Disable accounting in product card ► (v14.0+)
*'''PRODUCT_DISABLE_SIZE''' ► Disable size in product card.

*'''PRODUCT_DISABLE_LENGTH''' ► Disable length in product card ► (v4.0+)

*'''PRODUCT_DISABLE_SURFACE''' ► Disable surface in product card. ► (v4.0+)

*'''PRODUCT_DISABLE_VOLUME''' ► Disable volume in product card.

*'''PRODUCT_DISABLE_CUSTOM_INFO''' ► Disable custom info (custom code and country origin) in product/service card.

*'''PRODUIT_MULTIPRICES_USE_VAT_PER_LEVEL''' ► When option to use price per level/segment is on, this allows to also set a dedicated vat for each price level.

*'''PRODUIT_CUSTOMER_PRICES_BY_QTY''' ► If price per quantity ► ''Experimental''
*'''PRODUIT_CUSTOMER_PRICES_BY_QTY_MULTIPRICES''' ► If price per quantity and customer ► ''Experimental''

*'''PRODUCT_LOT_ENABLE_QUALITY_CONTROL''' ► Enable feature (Display fields for life time and quality control duration) for quality control on product and lot

*'''PRODUCT_MAX_LENGTH_COMBO''' ► Limit the length of the label displayed when adding lines in proposals/invoices/orders

*'''PRODUCT_MAX_VISIBLE_PHOTO''' ► Show a maximum number of product photos (as thumbnails) on the product main card. Example, setting this constant to '<code>5</code>' will show the first five product photos found on the product card.

*'''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''' ► Add other units on products (Use same dictionary as default unit feature) and propagate this unit on line of documents.
*'''MAIN_EDIT_LINE_ALLOW_ALL_UNIT_TYPE ►''' Allow the selection of other unit types when editing the document line

*'''RESOURCE_ON_PRODUCTS''' ► Allow to affect resources on products/services ► (v10.0+)
*'''RESOURCE_ON_SERVICES''' ► Allow to affect resources on products/services ► (v10.0+)
*'''PRODUCT_SHOW_ORIGIN_IN_COMBO''' ► Show origin of products when adding lines in proposals/invoices/orders ► (v12.0+)
*'''PRODUIT_ATTRIBUTES_HIDECHILD''' ► Add option hide child if variantes

*'''PRODUCT_ADD_FORM_ADD_TO''' ► Add a product to a draft proposal/order/invoice, from the product card.
*'''PRODUCT_DISABLE_SELLBY''' ► Hide the Sell by date ► (v13.0+)
*'''PRODUCT_DISABLE_EATBY''' ► Hide the Eat by date ► (v13.0+)

*'''PRODUCT_DENY_CHANGE_PRODUCT_TYPE''' ► Forbid to change the product type

*'''PRODUCT_SORT_BY_CATEGORY''' ► Sort the product by categories instead of by ID
*'''PRODUCT_ADD_NET_MEASURE''' ► Support Net Measure in product's card.php (For real weight, volume or piece; needed for some business ie fruits, vegetables....). Note brut value is already available natively, use this option only if you need 2 weights, 2 volumes, ...for each product) ► (v11.0.1+)
*'''PRODUCT_PRICE_BASE_TYPE''' ► value 'TTC' / 'HT' specify the default value of the price (with or without taxes) ► (v16.0.0+)

*'''PRODUCT_LOAD_EXTRAFIELD_INTO_OBJECTLINES''' ► Load product extrafiled on object lines

*'''PRODUCT_USE_SUB_COST_PRICES_IF_COST_PRICE_EMPTY''' : Calculate the parent product production price by child prices.

[[#Top|(back to top)]]

 

=Projects Module=

*'''PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY''' ► Option related to the combo list Project on elements. It is a list of thirdparty IDs. If set, you can link an object to a project owned by one of this thirdparty in the list.

*'''PROJECT_ALLOW_COMMENT_ON_PROJECT''' ► Add comment feature on a project

*'''PROJECT_ALLOW_COMMENT_ON_TASK''' ► Add comment feature on project task
*'''PROJECT_ALWAYS_DISCARD_CLOSED_PROJECTS_IN_SELECT''' ► Discards closed projects in every select field. A closed project can't be associated to an object ► (v20.0+)

*'''PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS''' ► Option related to the combo list Project on elements. Can link an element (purhcase invoice, purchase order, reception, ...) to any project even if object has a different supplier than the one of the project to link to. See also PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY that is different because it allows to define some given thirdparty ID to allow.

*'''PROJECT_CREATE_ON_OVERVIEW_DISABLED''' ► Hide the "create ..." button on the overview pagec

*'''PROJECT_DISABLE_UNLINK_FROM_OVERVIEW''' ► Enable removing the button from a link in the project overview. ► (>= v8.0.1)

*'''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''' ► Hide the "link to" form on the overview page ► (v4.0)

*'''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_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_OPEN_ALWAYS_ON_TAB''' ► Set to value 'task', or 'preview' to always open the project on the given tab instead of main tab.

*'''PROJECT_ELEMENTS_FOR_MINUS_MARGIN'''

*'''TIMESPENT_ALWAYS_UPDATE_THM''' ► when it's on always check current time of user to update it in task time line ► (v17.0)

[[#Top|(back to top)]]

=Proposals Module=

*'''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Add a picture of the product (the first one found if there are several) into the generated PDF of proposals. Note that using this will reduce the available width for the product description.

*'''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_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► add optional esign field in pdf propal ► (v8.0+)

*'''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.

*'''PROPAL_DISABLE_SIGNATURE''' ► Do no show the box for signature.

*'''PRODUIT_PDF_MERGE_PROPAL''' ► When generating the proposal PDF, all PDFs linked to products linked to proposal are also included into final PDF

*'''PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*'''PROPOSAL_AUTO_ADD_AUTHOR_AS_CONTACT''' ► Add Proposal Author as user contact follow proposal

*'''PROPOSAL_PDF_HIDE_PAYMENTTERM''' ► Do not show the payment term on proposal ► (v11.0+)

*'''PROPOSAL_PDF_HIDE_PAYMENTMODE''' ► Do not show the payment mode on proposal ► (v11.0+)

*'''WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES''' ► Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.
*'''PROPAL_REOPEN_UNSIGNED_ONLY''' ► Do not allow reopening of signed (or billed) proposals. (V15)
*'''PROPOSAL_ARE_NOT_BILLABLE''' ► Disable billing button on proposals (V15)
*'''PROPAL_DEFAULT_NOTE_PUBLIC''' ► Default text in public note

[[#Top|(back to top)]]

 

=Services Module=

*'''SERVICE_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country. For french speaking people, see also the page [[Loi_européenne_TVA_Vente_à_Distance_VAD_et_e-commerce_BtoC]].

*'''MAIN_FILL_SERVICE_DATES_FROM_LAST_SERVICE_LINE''' ► (v13.0) On add line form add a button to fill service dates from the last service line

[[#Top|(back to top)]]

=Shipments=

*'''STOCK_WAREHOUSE_NOT_REQUIRED_FOR_SHIPMENTS''' ► If set, you can add a shipment line, with no stock source defined. ► (>= 8.0.1)

*'''SHIPMENT_GETS_ALL_ORDER_PRODUCTS''' ► Add all order lines in shipment, including the one with 0 in quantity
*'''SHIPPING_PDF_HIDE_ORDERED''' ►Hide column quantity ordered on shipment pdf (>=15.0)
*'''STOCK_SUPPORTS_SERVICES''' ►Allow to manage services into warehouse and allow to ship services
*'''SHIPMENT_SUPPORTS_SERVICES''' ►Allow to ship services without stock (>=19.0)
*'''SHIPPING_DISPLAY_STOCK_ENTRY_DATE''' ►Display date entry stock exped and sort in date order (>=19.0)

[[#Top|(back to top)]]

=Stocks=

*'''SUPPLIER_ORDER_DISABLE_STOCK_DISPATCH_WHEN_TOTAL_REACHED''' ► Disable stock dispatch when total expected was already received

*'''STOCK_EXCLUDE_VIRTUAL_PRODUCTS''' ► If product is a virtual product, we do not manage stock for it.

*'''ENTREPOT_EXTRA_STATUS''' ► Instead of the 2 status (Closed, Open), a Warehouse has 3 status: Closed, Open (for all movements), Open (for internal movement only). Internal movement only means you can't use the warehouse to make shipment or receptions.

*'''SUPPLIER_ORDER_STATUS_FOR_VIRTUAL_STOCK''' ► For the calculation of virtual stocks, by default supplier orders with the status 3 (ordered) and 4 (partially received) are used. You can enter the list of statuses to be taken into account separated by commas for this calculation (example: 0,1,2,3)

*'''STOCK_MOVEMENT_LIST_HIDE_UNIT_PRICE''' ► to hide unit price on some pages (V15+)

*'''DISABLE_QTY_OVERWRITE''' ► Disable quantity overwrites on inventories ► (v19.0)

[[#Top|(back to top)]]

=Suppliers Module=

*'''FOURN_PRODUCT_AVAILABILITY''' ► On the Suppliers price page of the products, activate the supplier product availability. ''This is duplicate feature with delivery_delay introduced with 3.8.''

*'''RELOAD_PAGE_ON_SUPPLIER_CHANGE''' ► On creation of a supplier order/invoice, reload form with supplier-specific details when supplier is selected from drop-down list.

*'''SUPPLIER_INVOICE_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier invoice to only those with a buying price defined for that supplier. ► (v6.0+)

*'''SUPPLIER_ORDER_AUTOADD_USER_CONTACT''' ► Add user approving supplier order as a contact automatically.

*'''SUPPLIER_ORDER_DEFAULT_PAYMENT_MODE_ID''' ► Set the default payment method for suppliers (<code>rowid</code> in table <code>llx_c_paiement</code>).

*'''SUPPLIER_ORDER_USE_DISPATCH_STATUS''' ► Add a status on each dispatch order line when receiving products from suppliers ► (v4.0+)

*'''SUPPLIER_ORDER_NO_DIRECT_APPROVE''' ► No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

*'''SUPPLIER_ORDER_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier order to only those with a buying price defined for that supplier. ► (v6.0+)

*'''SUPPLIER_ORDER_EDIT_BUYINGPRICE_DURING_RECEIPT''' ► Can modify the buying price used for PMP calculation when making a stock reception on a supplier order. ► (v6.0+)

*'''SUPPLIER_PROPOSAL_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier proposal to only those with a buying price defined for that supplier. ► (v6.0+)

*'''DISPLAY_DISCOUNTED_SUPPLIER_PRICE''' ► Allow to display discounted supplier price when searching product in supplier documents ► (v10.0)

*'''MAIN_CAN_EDIT_SUPPLIER_ON_SUPPLIER_ORDER''' ► Allow to change the supplier on a draft supplier order ► (v10.0)

*'''SUPPLIER_PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD'''

*'''SUPPLIER_ORDER_CAN_UPDATE_BUYINGPRICE_DURING_RECEIPT''' ► Allow to change price on receipt ► (v19.0)

*'''SUPPLIER_HIDE_SUPPLIER_OBJECTLINES''' ► Hide the supplier information on objectlines (invoices, etc..) ► (v19.0)

[[#Top|(back to top)]]

=Third Parties Module=

*'''COMPANY_AQUARIUM_CLEAN_REGEX''' ► Add a REGEX rule on the third parties names. It applies a regex replacement pattern on generated code if COMPANY_AQUARIUM_CLEAN_REGEX is set. Value must be a regex with parenthesis. The part into parenthesis is kept, the rest removed. For example if COMPANY_AQUARIUM_CLEAN_REGEX = '<code>^..(..)..(.*)</code>' the first char and second char are removed and the char 5 and 6 too ► (>= 8.0.1)

*'''MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES''' ► See in Global options section.

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► See in Global options section.

*'''SOCIETE_EMAIL_MANDATORY''' ► E-mail is a mandatory field when creating a thirdparty

*'''SOCIETE_DISABLE_CUSTOMERS''' ► Remove all menu and features related to customers

*'''SOCIETE_DISABLE_PROSPECTS''' ► Remove all menu and features related to prospects
*'''SOCIETE_DISABLE_PROSPECTSCUSTOMERS ►''' Remove the status "Customer/Prospect" when thirdparties creation or modification

*'''SOCIETE_DISABLE_STATE''' ► Do not use field "state/province"

*'''SOCIETE_SORT_ON_TYPEENT''' ► The combo list of "type of third party" is sorted on alphabetical order instead of the field "position" that appears into dictionary instead.

*'''SOCIETE_ASK_FOR_SHIPPING_METHOD''' ► Shipping method can be predefined on customer card and will be used as default on order creation
*'''SOCIETE_ADD_REF_IN_LIST''' ► Displays the code before the name in the lists ► Value 1 -> Code + name + alias ou Code + name if colone alias 2 -> Code + alias 3 -> Alias

*'''THIRDPARTY_CAN_HAVE_CATEGORY_EVEN_IF_NOT_CUSTOMER_PROSPECT_SUPPLIER''' ► Possible to add Categories to third parties that are not customer, prospect or supplier.

*'''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.

*'''THIRDPARTY_NOTCUSTOMERPROSPECT_BY_DEFAULT''' ► Do not set status "Customer/Prospect" to "on" when creating a new third party from menu "New third party".

*'''THIRDPARTY_INCLUDE_PARENT_IN_LINKTO''' ► Search also for elements on parent third party when using the "link to" object feature.

*'''THIRDPARTY_INCLUDE_PROJECT_THIRDPARY_IN_LINKTO''' ► Search also for elements on third party that own the project of the current element when using the "link to" object feature (if project is owned by a different thirdparty than current one).

*'''THIRDPARTY_LOGO_ALLOW_EXTERNAL_DOWNLOAD''' ► When a logo is uploaded, a share key is automatically set so the file can be downloaded using the share key.

*'''THIRDPARTY_SUGGEST_ALSO_ADDRESS_CREATION''' ► Enabled contact creation on third-party create card
*'''THIRDPARTY_QUICKSEARCH_ON_FIELDS''' ► Personalized search criteria ► Example: $conf->global->THIRDPARTY_QUICKSEARCH_ON_FIELDS = 's.nom=ThirdPartyName;s.name_alias=AliasNameShort;s.code_client=CustomerCode'
*'''MEMBER_CAN_CONVERT_CUSTOMERS_TO_MEMBERS''' ► Enabled member creation on third-party create card
*'''SOCIETE_DISABLE_PARENTCOMPANY''' ► Disables attachment to a parent company.
*'''THIRDPARTY_CUSTOMERPROSPECT_BY_DEFAULT''' ► Set the third party to customer by default
*'''THIRDPARTY_SUPPLIER_BY_DEFAULT''' ► Set the third party to supplier by default
*'''THIRDPARTY_CUSTOMERTYPE_BY_DEFAULT''' ► Set the third party type by default (3 = customer & prospect / 2 = prospect / 1 = customer )
*'''CONTACT_DISABLE_PERSONALINFO''' ► Disable Personal data on contact page
*'''SOCIETE_DISABLE_WORKFORCE''' ► Disable work force selector on society page
*'''SOCIETE_SHOW_VAT_IN_LIST''' ► display VAT number in combo list of thirdparties ► (V15+)
*'''THIRDPARTY_DEFAULT_CREATE_CONTACT''' ► When set, a contact is created at the creation of an individual third party ► (v14.0)

*'''MAIN_SUPPORT_SHARED_CONTACT_BETWEEN_THIRDPARTIES''' ► Able to share contact between several third parties

[[#Top|(back to top)]]

=Ticket Module=

*'''TICKET_SHOW_MESSAGES_ON_CARD''' ►Display all ticket related messages on the main ticket card. ► (>= 10.0)
*'''TICKET_AUTO_ASSIGN_CONTRACT_CREATE''' ►Automatically create a contract linked to the ticket ► (>= 10.0)
*'''TICKET_AUTO_CREATE_FICHINTER_CREATE''' ►Automatically create an intervention linked to the ticket ► (>= 10.0)
*'''WORKFLOW_TICKET_CLOSE_INTERVENTION''' ►On ticket close, automatically close an intervention linked to the ticket
*'''TICKET_CHECK_NOTIFY_THIRDPARTY_AT_CREATION''' ►Automatically check "notify thirdparty at creation" ( >=16)
*'''TICKETS_MESSAGE_FORCE_MAIL''' ► Pre check email sending on ticket message (>=15)
*'''TICKET_SEND_PRIVATE_EMAIL ►''' Allow a private message to be sent by mail (>=17)
*'''TICKET_LIMIT_VIEW_ASSIGNED_ONLY''' '''►''' Only display tickets assigned to the user
*'''TICKET_ADD_AUTHOR_AS_CONTACT''' '''►''' If set to 1: Automatically adds the author as internal contact. If set to 2: Automatically adds the author as external contact if external user. (>=20)
*'''TICKET_ASSIGN_CONTACT_TO_MESSAGE''' '''►''' If known, the external contact is assigned to the message. (>=19)
*'''TICKET_ALLOW_CLASSIFICATION_MODIFICATION_EVEN_IF_CLOSED''' '''►'''Allow modify ticket classification even if closed. (>=19)

 

=VAT Report=

*'''MAIN_INCLUDE_ZERO_VAT_IN_REPORTS''' ► Include lines with VAT to 0% (for "auto-liquidation" in EEC) ► (v8.0.3+)

[[#Top|(back to top)]]

=Website Module=

*'''WEBSITE_USE_WEBSITE_ACCOUNTS''' ► Add a table and a tab to manage some accounts for websites to a third party
*'''WEBSITE_ALLOW_OVERWRITE_GIT_SOURCE''' ► Add a button to export a website over the GIT sources
*'''WEBSITE_ADD_CSS_TO_BODY''' ► Add a CSS class to the body tag of websites

[[#Top|(back to top)]]

 

=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 guaranteed with this. Also if the image is removed or renamed by the image hosting service, your proposal, order or invoice will be broken.
*'''FCKEDITOR_ALLOW_ANY_CONTENT''' ► Allow to enter any content. However, this will totally disable content filtering which is one of the most important CKEditor features. You can use this to keep all your tags and attributes in the html content.
*'''FCKEDITOR_ENABLE_SCAYT_AUTOSTARTUP ►''' Allow to activate the SpellCheckAsYouType (SCAYT) plugins of CKEditor i.e an automatic spell checking. The value to activate this option is 1.

[[#Top|(back to top)]]

=STRIPE Module=

*'''STRIPE_FORCE_VERSION''' ► Force the STRIPE version. For Example: "2019-09-09" (v11+)
*'''STRIPE_REUSE_EXISTING_INTENT_IF_FOUND''' ► With this, you will have idempotency key but the payment intention will be reuse and not Generate again (13+)

[[#Top|(back to top)]]

=ClickToDial Module=

*'''CLICKTODIAL_FORCENEWTARGET''' ► Open in new page.

[[#Top|(back to top)]]

 

=For SaaS / Cloud hosting integrators=

The following options are useless for a common usage of Dolibarr. But they are usefull if you plan to host / provide Dolibarr instances as Software As A Service (SAAS) to your customers.

*'''CRON_DISABLE_KEY_CHANGE''' ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*'''CRON_DISABLE_TUTORIAL_CRON''' ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*'''CRON_WARNING_DELAY_HOURS''' ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

*'''MAILING_NO_USING_PHPMAIL''' ► To avoid bad use of the emailing module, it is recommended to set this option to 1 (This option is described previously). Also you can complete the message visible by customers when they try to setup the SMTP credentials of their Dolibarr by using the constant MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS (This option is described previously). For example, you can point to a FAQ on your website.

*'''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► If you have set a system limit on number of recipients on your system, you can set also this option to match the same value, so users will be informed: So '''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' restricts sending of 1 email message to <code>x</code> recipients for the same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include a ton of recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available. Note that this is not a hard limit; it is just the quantity that will be displayed on warnings on screen. For a real limit, this must be implemented into the system.

*'''MAILING_LIMIT_SENDBYDAY''' ► This is a limit of number of emails, an instance can send. Note that this is not a hard limit; it is just the quantity that will be displayed on warnings on screen. For a real limit, this must be implemented into the system.

*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Set this value to a translation key. Then add translation keys into the instance so user will see a message when into the email setup page. For example, you can set a message to say ''Warning: To avoid abuse, when using default setup, you are restricted to 500 emails per day for all your application (account may be suspended in case of violation of this rule. You can setup application to use your own SMTP server for sending email so you want have no restriction at all (see menu Home-Setup-Emails)''

*'''MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE''' ► If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock and remove the upgrade.unlock so the administration tools like install.php, upgrade.php and repair.php can't be used on your customer instance (until the install.lock file is deleted or the upgrade.unlock file is created).

*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option '''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD'''.

*'''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD''' ► Set here the string to add in the SPF record This string will be shown into a help message when the user in in the setup of email page and has choose a method using an external SMTP server.

*'''MAIN_FIRST_PING_OK_ID''' ► Set this value to "disabled" to remove completely any ping after a complete setup.

*'''MAIN_FILECHECK_LOCAL_SUFFIX''' and '''MAIN_FILECHECK_LOCAL_EXT''' ► If you offer a customized or patched version of Dolibarr, when the user will use the tool to check the integrity of files, the default xml file name used for signature checking will be the official file provided by the Dolibarr team, so it does not includes your own changes. To have the suggested signature file being your own file, you can set the constant MAIN_FILECHECK_LOCAL_SUFFIX to a suffix. For example, set this to "'''-mysaassolution'''". So, when the user will use the file integrity tool, the default file to check for signature will be "'''/install/filelist-10.0.2-mysaassolution.xml'''" instead of "'''/install/filelist-10.0.2.xml'''". All you have to do is generate the signature file '''mysaassolution''' using the tool '''build/generate_filelist_xml.php''' and put this file into the install directory of your customer instance. Doing this, your customer, and yourself, will be able to check if a file was modified without being disturbed by false alerts due to your customized files or patches (they will be included in the signature used for check). Also, if you want to zip the customized signature file into "'''/install/filelist-10.0.2-mysaassolution.xml.zip'''", you can set the constant MAIN_FILECHECK_LOCAL_EXT to '.zip'.

*'''MAIN_HIDE_WARNING_TO_ENCOURAGE_SMTP_SETUP''' ► Set to 1 by default (so warning is hidden). You can set it to 0 to show a warning to encourage admin to set its own SMTP service.

*'''MAIN_MAIL_SENDMODE_password''' ► To force the mode to send the email on the "password forgotten" page. So you can decide to use php mail or SMTP method for this specific use case.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► If set to N, the warning saying modules are not activated will be shown if number of activated module is < N (Having this variable not defined is same than having it set to 1). This may be usefull if you preinstall an application with some modules already loaded by default and you want to keep the warning to be sure the user will enable other modules he need, even if some modules are already enabed.

*'''MAIN_NO_UPGRADE_REDIRECT_ON_LEVEL_3_CHANGE''' ► The page to make the migration is not shown automatically when you deploy files of version X.Y.Z+delta over an installation with a database version X.Y.Z. The upgrade page will be shown automatically only if there is a change on value of X or Y in version.

*'''SYSLOG_DISABLE_LOGHANDLER_SYSLOG''' ► Set this to 1 to disable usage of syslog (having all customer instances logging in the same system file is not a good idea).

*'''WEBSITE_REPLACE_INFO_ABOUT_USAGE_WITH_WEBSERVER''' ► Put here a text or a translation key of a text to show when the user will use the feature "Deploy" when he want to deploy a website done with Dolibarr CMS. So you can, for example, show him a message that this feature is not part of its subscription and putting a website online may need a complementary subscription.

[[#Top|(back to top)]]

Fichier de configuration

2024-06-11T15:51:02Z

Iouston:

[[en:Configuration_file]]
[[es:Fichero_de_configuración]]


[[Category:Admin fr]]
{{TemplateDocDev}}

Le fichier de configuration de Dolibarr est '''conf/conf.php'''. Il est écrit par la procédure d'installation automatisée.

=Contenu=
Le contenu du fichier standard est :
<source lang="php">
$dolibarr_main_document_root="/home/www/dolibarr/htdocs";
$dolibarr_main_url_root="http://mondomaine.com/dolibarr";
$dolibarr_main_db_type="mysql";
$dolibarr_main_db_host="localhost";
$dolibarr_main_db_port="3306";
$dolibarr_main_db_name="dolibarr";
$dolibarr_main_db_user="dolibarr";
$dolibarr_main_db_pass="";
</source>

'''Autres options :'''
<source lang="php">
$dolibarr_main_demo="demologin,demopass"
</source>
-> Désactive certaines fonctions pour rendre l'application figée à certains niveaux. Ceci est requis si Dolibarr est en accès comme site de démo à des utilisateurs qui aiment un peu trop faire n'importe quoi.

<source lang="php">
$dolibarr_main_prod="1"
</source>
-> Quand cette option est définie, les messages d'erreurs internes à Dolibarr ne sont plus remontée à l'écran. Cette option est conçue pour les environnements de production afin de ne pas divulguer d'informations aux hackers.

<source lang="php">
$dolibarr_main_authentication="dolibarr"
</source>
-> Permet de changer la manière dont le mot de passe est controlé:

*La valeur "dolibarr" s'appuie sur le mot de passe en base de donnée.
*"ldap" permet de se baser sur un annuaire LDAP (dans ce cas il faut renseigner les autres parametres LDAP (vor ficiher conf.php.example).
*"http" utilise l'authentification du protocol HTTP Basic (il est nécesssaire de configurer votre serveur web pour avoir Dolibarr dans une session d'authentification HTTP Basic).

<source lang="php">
$dolibarr_main_authentication="dolibarr"
</source>

<source lang="php">
$dolibarr_allow_download_external_modules=1
</source>
-> Permet d'afficher un lien de téléchargement du fichier zip d'un module externe placé dans le dossier custom. Le lien de téléchargement est accessible après avoir cliqué sur l'icone d'aide '?' depuis la liste des modules.

Dolibarr fournit un fichier conf modèle nommé '''conf/conf.php.example''' où chaque paramètre est commenté.

=Lecture/Ecriture du fichier=
Ce fichier ne doit pas jamais être ni lu directement, ni modifié par aucune fonctionnalité de Dolibarr.

Il est créé par la procédure d'installation ou de mise a jour de Dolibarr (install/index.php) qui est la seule habilitée à effectuer des actions sur ce fichier.

=Utilisation dans le code=
Le contenu de ce fichier est accessible au développeur au travers de constantes ou de l'objet '''$conf''' déjà chargés par le code présent dans '''master.inc.php''' ou '''main.inc.php''' (ces fichiers doivent etre inclus au début de tout programme PHP Dolibarr: master.inc.php pour les scripts et main.inc.php pour les pages). Votre code ne doit jamais ouvrir le fichier de configuration directement. Ce n'est pas nécessaire.

Ainsi:

*$dolibarr_main_data_root est connu dans le code grâce à la constante: DOL_DATA_ROOT (indique l'emplacement physique des fichiers uploadés ou temporaires crées dans Dolibarr)
*$dolibarr_main_document_root est connu dans le code grâce à la constante: DOL_DOCUMENT_ROOT (mais aussi dans le tableau $conf->file->dol_document_root[]. Indique l'emplacement physique des fichiers programmes Dolibarr)
*$dolibarr_main_url_root est connu dans le code grâce à la constante: DOL_URL_ROOT (indique le chemin URL racine de Dolibarr)
*$dolibarr_main_db_type est accessible par $conf->db->type
*$dolibarr_main_db_host est accessible par $conf->db->host
*$dolibarr_main_db_port est accessible par $conf->db->port
*$dolibarr_main_db_name est accessible par $conf->db->name
*$dolibarr_main_db_user est accessible par $conf->db->login
*$dolibarr_main_db_pass n'est pas accessible. Il est lu par '''master.inc.php''' (appelé par tout fichier PHP) qui crée un connexion '''$db''' puis efface de sa mémoire le mot de passe.

Voir les tutoriaux sur le [[Developpement_module|Développements de modules]] ou [[Développement de scripts]] pour plus d'information.

Fichier de configuration

2024-06-11T15:49:57Z

Iouston: add $dolibarr_allow_download_external_modules

[[en:Configuration_file]]
[[es:Fichero_de_configuración]]


[[Category:Admin fr]]
{{TemplateDocDev}}

Le fichier de configuration de Dolibarr est '''conf/conf.php'''. Il est écrit par la procédure d'installation automatisée.

=Contenu=
Le contenu du fichier standard est :
<source lang="php">
$dolibarr_main_document_root="/home/www/dolibarr/htdocs";
$dolibarr_main_url_root="http://mondomaine.com/dolibarr";
$dolibarr_main_db_type="mysql";
$dolibarr_main_db_host="localhost";
$dolibarr_main_db_port="3306";
$dolibarr_main_db_name="dolibarr";
$dolibarr_main_db_user="dolibarr";
$dolibarr_main_db_pass="";
</source>

'''Autres options :'''
<source lang="php">
$dolibarr_main_demo="demologin,demopass"
</source>
-> Désactive certaines fonctions pour rendre l'application figée à certains niveaux. Ceci est requis si Dolibarr est en accès comme site de démo à des utilisateurs qui aiment un peu trop faire n'importe quoi.

<source lang="php">
$dolibarr_main_prod="1"
</source>
-> Quand cette option est définie, les messages d'erreurs internes à Dolibarr ne sont plus remontée à l'écran. Cette option est conçue pour les environnements de production afin de ne pas divulguer d'informations aux hackers.

<source lang="php">
$dolibarr_main_authentication="dolibarr"
</source>
-> Permet de changer la manière dont le mot de passe est controlé:

*La valeur "dolibarr" s'appuie sur le mot de passe en base de donnée.
*"ldap" permet de se baser sur un annuaire LDAP (dans ce cas il faut renseigner les autres parametres LDAP (vor ficiher conf.php.example).
*"http" utilise l'authentification du protocol HTTP Basic (il est nécesssaire de configurer votre serveur web pour avoir Dolibarr dans une session d'authentification HTTP Basic).

<source lang="php">
$dolibarr_main_authentication="dolibarr"
</source>

<source lang="php">
$dolibarr_main_authentication="dolibarr"
</source>
-> Permet d'afficher un lien de téléchargement du fichier zip d'un module externe placé dans le dossier custom. Le lien de téléchargement est accessible après avoir cliqué sur l'icone d'aide '?' depuis la liste des modules.

Dolibarr fournit un fichier conf modèle nommé '''conf/conf.php.example''' où chaque paramètre est commenté.

=Lecture/Ecriture du fichier=
Ce fichier ne doit pas jamais être ni lu directement, ni modifié par aucune fonctionnalité de Dolibarr.

Il est créé par la procédure d'installation ou de mise a jour de Dolibarr (install/index.php) qui est la seule habilitée à effectuer des actions sur ce fichier.

=Utilisation dans le code=
Le contenu de ce fichier est accessible au développeur au travers de constantes ou de l'objet '''$conf''' déjà chargés par le code présent dans '''master.inc.php''' ou '''main.inc.php''' (ces fichiers doivent etre inclus au début de tout programme PHP Dolibarr: master.inc.php pour les scripts et main.inc.php pour les pages). Votre code ne doit jamais ouvrir le fichier de configuration directement. Ce n'est pas nécessaire.

Ainsi:

*$dolibarr_main_data_root est connu dans le code grâce à la constante: DOL_DATA_ROOT (indique l'emplacement physique des fichiers uploadés ou temporaires crées dans Dolibarr)
*$dolibarr_main_document_root est connu dans le code grâce à la constante: DOL_DOCUMENT_ROOT (mais aussi dans le tableau $conf->file->dol_document_root[]. Indique l'emplacement physique des fichiers programmes Dolibarr)
*$dolibarr_main_url_root est connu dans le code grâce à la constante: DOL_URL_ROOT (indique le chemin URL racine de Dolibarr)
*$dolibarr_main_db_type est accessible par $conf->db->type
*$dolibarr_main_db_host est accessible par $conf->db->host
*$dolibarr_main_db_port est accessible par $conf->db->port
*$dolibarr_main_db_name est accessible par $conf->db->name
*$dolibarr_main_db_user est accessible par $conf->db->login
*$dolibarr_main_db_pass n'est pas accessible. Il est lu par '''master.inc.php''' (appelé par tout fichier PHP) qui crée un connexion '''$db''' puis efface de sa mémoire le mot de passe.

Voir les tutoriaux sur le [[Developpement_module|Développements de modules]] ou [[Développement de scripts]] pour plus d'information.

Setup Other

2024-05-13T15:22:12Z

Iouston: Add ACCOUNTANCY_USE_PRODUCT_ACCOUNT_ON_THIRDPARTY

[[fr:Paramétrage_Divers]]
[[es:Configuración_Varios]]
[[de:Erweiterte_Einstellungen]]
[[zh:其他设置]]


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

'''Help About Screen''': Other setup

'''Menu Path''': Home ► Setup ► Other

'''Introduction'''

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

{{warning|32px}} This page contains the list of some advanced development parameters. In most cases, it is parameters for internal usage, development, external modules, features in development not stable or that may lead to security risk. For standard usage of Dolibarr, such parameters '''SHOULD NOT''' be used. All experimental options are NOT supported. They may be removed in a future, modified at any version and break stability of your application.

To enable/override a parameter you have to define the constant name and set it to 1 (unless otherwise stated) in <code>Home ► Setup ► Other Setup</code>

The options here may not be documented since they are not stable and unsupported (remember they are experimental or development options). The basic format of how the list is written is broken down in the example below:

UNSTABLE_OR_DEV_OPTION ► ''Description of config and goal'' ► ''(specific version information) or values''
<center>
__TOC__
</center>
=Global Options=

*'''ADD_UNSPLASH_LOGIN_BACKGROUND''' ► The background image will be refreshed on every login page refresh. Background image is pulled from the popular open source image website Unsplash. If an already saved static background image exists, then this code will override it (but not delete the saved image). Warning: Using this may allow this external website to steel your login credentials (the value to be put is the URL of the service, exemple : https://source.unsplash.com/random) ► (v10.0)
*'''MAIN_HIDE_POWERED_BY''' ► Hide the "Powered by Dolibarr"
*'''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 fail by smartphone applications like [[Application Android - DoliDroid]] breaking some features when using Dolibarr from this application.

*'''MAIN_AUTOFILL_DATE''' ► If this constant is defined (to something other than <code>0</code>), the date of invoice, proposal, order or payment are auto-filled with the current date. It is highly recommended to NOT ENABLE this feature. This can create a lot of input errors with data not validated by users. This leads to incorrect values saved in the database causing confusion when you have to do your accountancy reports!

*'''MAIN_AUTO_TIMESTAMP_IN_PUBLIC_NOTES''' ► Add a timestamp and user automatically when editing the ''public'' note.

*'''MAIN_AUTO_TIMESTAMP_IN_PRIVATE_NOTES''' ► Add a timestamp and user automatically when editing the ''private'' note.

*'''MAIN_COUNTRIES_IN_EEC''' ► Country list in European Area (For VAT purpose) ► (v10.0-v13.0). From v14, do not use this any more (remove the constant if you set it and instead set if the country is in Europe or not from the DB for V14 - V15 and from dictionary of countries in V16 and more).

*'''MAIN_DEFAULT_PAYMENT_TERM_ID''' ► With ID of a payment term, will use this as default payment term each time you create a new proposal, order, invoice (customer and supplier). Deprecated. Replaced with the default setup feature instead.
*'''MAIN_DEFAULT_PAYMENT_TYPE_ID''' ► With ID of a payment type, will use this as default payment type each time you create a new proposal, order, invoice (customer and supplier). Deprecated. Replaced with the default setup feature instead.

*'''MAIN_DEFAULT_LANGUAGE_FILTER''' ► Useful if you do not want to show <code>en_US</code> language option in combo boxes (other languages can easily be removed in <code>langs</code> directory but not <code>en_US</code>) ► (v10.0)

*'''MAIN_LANGUAGES_ALLOWED''' ► Is a list of languages without spaces, example : <code>fr_FR,en_US,de_DE,it_IT</code> If defined, only those languages will appear in combos. ► (v11.0)

*'''MAIN_DISABLE_NOTES_TAB''' ► Show or hide notes tab in the card page

*'''MAIN_DISABLE_CONTACTS_TAB''' ► Show or hide contacts tab in the card page

*'''MAIN_DISABLE_FULL_SCANLIST''' ► Disables the complete scan of tables to allow the pagination to show total number of pages. May be useful to activate on systems with a very high quantity of data (tables with more than 2 000 000 records).

*'''MAIN_DISABLE_JQUERY_JNOTIFY''' ► Disable usage of <code>JNotify</code> to show confirm or error messages

*'''MAIN_DISABLE_AJAX_COMBOX''' ► If you have a large number of third parties or products, you can disable the autocomplete feature on the third parties list by setting this constant to <code>1</code> ► (v3.6.0+)
*'''MAIN_DISABLE_MULTIPLE_FILEUPLOAD''' ► Disable users to upload multiple files at once.
*'''MAIN_DISABLE_TRUNC''' ► Disable all truncings in select list. ► (v7.0+)

*'''MAIN_DISABLEDRAFTSTATUS''' ► Disable the status "Draft" for some objects (project, donation, ...) so the object is directly created with status "Validated"

*'''MAIN_DOC_USE_OBJECT_THIRDPARTY_NAME''' ► Add name of thirdparty at begin of generated document.

*'''MAIN_DOC_USE_TIMING''' ► Add a timestamp at end of generated document. Value must be format of timestamp. For example: <code>%Y%m%d%H%M</code> (only for ODT files)

*'''MAIN_DOC_UPLOAD_NOT_RENAME_BY_DEFAULT''' ► Disable the auto renaming on upload file ► (v10.0)

*'''MAIN_DOL_SCRIPTS_ROOT''' ► Define directory who contains 'scripts' directory (e.g. <code>/var/www/dolibarr</code>). Value of this variable may be requested by some external script or tools.

*'''MAIN_ENABLE_LOG_TO_HTML''' ► If this constant is defined, it is possible to have logs inside pages by adding the parameter <code>&logtohtml=1</code> into URL.

*'''MAIN_ENABLE_IMPORT_LINKED_OBJECT_LINES''' ► Allow to import lines into current document from "linked" compatible documents ► (v8.0+)

*'''MAIN_FIRST_TO_UPPER''' ► Dolibarr add uppercase to Third Parties, 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_ALL_TO_UPPER''' ► Dolibarr puts uppercase for Third Parties, 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. ► (v11.0)

*'''MAIN_ALL_TOWN_TO_UPPER''' ► Dolibarr puts uppercase for town names if not done. ► (v13.0)

*'''MAIN_FILESYSTEM_ENCODING''' ► With some PHP versions, PHP is not able to detect the page code for filesystem of the server OS. To solve this, Dolibarr assumes your OS filesystem is <code>UTF-8</code> if on Linux or OSX system, and <code>ISO-8859-1</code> if on Windows. If not, for example on a Windows server with a NTFS <code>UTF-8</code> pagecode, you can set the variable <code>MAIN_FILESYSTEM_ENCODING</code> to "<code>utf-8</code>".

*'''MAIN_FORCELANGDIR''' ► Relative path of the directory holding your custom <code>langs</code> folder.

*'''MAIN_HTML_TITLE''' ► Can be used to control how the html page title is formatted. If value contains key '<code>noapp</code>', application name will not be output. If value contains '<code>thirdpartynameonly</code>', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: '<code>noapp;thirdpartynameonly</code>'

*'''MAIN_HELPCENTER_LINKTOUSE''' ► Define the URL link to use as the target page for link "I need help" onto logon page

*'''MAIN_LOGOUT_GOTO_URL''' ► URL to which the user will be redirected after LOGOUT

*'''MAIN_MAXTABS_IN_CARD''' ► Maximum number of tabs visible. Others are grouped into a combo list.

*'''MAIN_MAXLIST_OVERLOAD''' ► Maximum number of line in space's domain.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► A warning saying setup of modules is not complete is shown if the number of enabled modules is lower or equal than this value (<code>1</code> if not defined)

*'''MAIN_NO_CONCAT_DESCRIPTION''' ► Allow to use only input custom description in lines (proposal, order, invoice) ► (v10.0)

*'''MAIN_OPTIMIZE_SPEED''' ► Use some speed enhancements. See page [[FAQ Increase Performance]] for more information.

*'''MAIN_PROPAGATE_CONTACTS_FROM_ORIGIN''' ► When creating an order, contract, invoice from another object, specific contacts of objects are set as specific contact of the new object when possible. ► (v4.0+)

*'''MAIN_PUBLIC_NOTE_IN_ADDRESS''' ► Show public note in address block ► (v4.0+)

*'''MAIN_REMOVE_INSTALL_WARNING''' ► Remove all security warnings that appear to administrator users if URL <code>/install</code> is public. You should solve the problem if warning occurs, instead of removing the warning! For this, create a file called <code>install.lock</code> into Dolibarr root directory. This will stop the warning but also make the page <code>/install</code> not possible to use, to protect your installation.

*'''MAIN_REPEATCONTACTONEACHTAB''' ► If added and set to <code>1</code>, this adds contacts on all tabs, not only main tab.

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

*'''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND''' ► Change way of rounding total TTC lines, rounding first of after.

*'''MAIN_SERVER_TZ''' ► If you can't set the time zone of your PHP installation, set this constant. Better is to set it to UTC. In future, this constant will be forced to '<code>UTC</code>' so PHP server time zone will not have effect any more. Examples: <code>Europe/Paris</code>, <code>auto</code>.

*'''MAIN_SEARCH_FORM_ON_HOME_AREAS''' ► Show the search form on home page areas for core modules (Removed after v5 due to global search combo) ► (v6.0+)

*'''MAIN_SEARCHFORM_SUPPLIER_INVOICE_DISABLED''' ► Disable the supplier invoice on the search form

*'''MAIN_SEARCH_DIRECT_OPEN_IF_ONLY_ONE''' ► If only one result is found, then setting this value to <code>1</code> will take you direct to the item (default method). Setting the value to <code>0</code> will show the result in the list as a single result ► (v5.0+)

*'''MAIN_SERVICES_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country.

*'''MAIN_SHOW_TUNING_INFO''' ► Add tuning information into JavaScript console. Better when xdebug is enabled.

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show also technical IDs on elements cards or some lists (not supported everywhere).

*'''MAIN_SHOWDATABASENAMEINHELPPAGESLINK''' ► Show database name in upper help menu ► (v8.0+)

*'''MAIN_USE_ALTERNATE_TRANSLATION_FOR''' ► List of fields per object that need an alternate translation. Example: <code>MAIN_USE_ALTERNATE_TRANSLATION_FOR=societe:name,town;contact:firstname,lastname</code>

*'''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_USE_JQUERY_JEDITABLE''' ► Allow to update from screen, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this feature, because it bypasses some business actions (updates on other data that should be done consistently) and ignores business controls on data you saved. Consequently this feature breaks consistency of data and possibly the stability of the 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_USE_OLD_SEARCH_FORM''' ► Display the old search form in left menu.

*'''MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS''' ► Allow to force the VAT rate to a given value (instead of higher VAT rate of country) if the VAT rate of product was not defined.

*'''MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES''' ► If we can't guess if a thirdparty is a company or individual (not VAT ID fill, no Prof ID fill, no type of thirdparty fill), then we suppose it is a company (B2B business) instead of an individual (B2C business).

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► For intra CEE sales, we use by default, on proposal, order or invoice creation, a 0 VAT for customers that are companies (see MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES to change behaviour to know if a thirdparty is a company or an individual). But if the option MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL is set, we will use the 0 VAT only if a VAT ID is defined for the customer.

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_INDIVIDUAL_CUSTOMER_OUT_OF_EEC''' ► For to use the default VAT of product for individual customers that are out E.E.C. (European Economic Community) ► (v7.0+). ''There is no reason to use this.''

*'''MAIN_VIEW_LINE_NUMBER''' ► Shows a line number for each line of products/services at documents like proposal / order / invoice. Only on screen, not on PDF.

*'''MAIN_VIEW_LINE_NUMBER_IN_LIST''' ► Shows a line number in lists ► (v12.0)

*'''MAIN_VOLUME_DEFAULT_ROUND''' ► Accuracy of volume (number of decimals)

*'''MAIN_VOLUME_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''MAIN_WEIGHT_DEFAULT_ROUND''' ► Accuracy of weight (number of decimals)

*'''MAIN_WEIGHT_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''USER_HIDE_INACTIVE_IN_COMBOBOX''' ► Disable display inactive users in combobox.

*'''MAIN_DISABLE_PDF_THUMBS''' ► Disable thumbs PDF in case of imagick bug

*'''MAIN_KEEP_REF_CUSTOMER_ON_CLONING''' ► Keep the Customer Reference on cloned object (Propal/Invoice)

*'''MAIN_DONT_KEEP_NOTE_ON_CLONING''' ► Remove the object notes during cloning ► (v11.0)

*'''MAIN_DOC_SORT_FIELD''' ► Set the default sorting field on document page (name by default) ► (v11.0)

*'''MAIN_DOC_SORT_ORDER''' ► Set the default sorting order (ASC or DESC) on document page (ASC by default) ► (v11.0)

*'''MAIN_USE_ZIPTOWN_DICTIONNARY''' ► Use dictionary ZIP for create card.

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Show search in top menu with theme eldy ► (v11.0)

*'''MAIN_PHONE_SEPAR''' ► Separ phone number other space ► (v12.0)

*'''GRAPH_USE_FISCAL_YEAR''' ► Widgets uses fiscal year

*'''SHOW_SOCINFO_ON_PRINT''' ► Permit to add user company information on each printed document (when click on Dolibarr print button) ► (v12.0)

*'''MAIN_FEATURES_LEVEL''' ► Level of features to show: <code>-1=stable+deprecated</code>, <code>0=stable only (default)</code>, <code>1=stable+experimental</code>, <code>2=stable+experimental+development</code>

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show technical id for object.

*'''MAIN_HTTP_CONTENT_SECURITY_POLICY''' ► Allows you to fill in the content security rules ► (v6.0)

*'''SOCIETE_ON_SEARCH_AND_LIST_GO_ON_CUSTOMER_OR_SUPPLIER_CARD''' ► Allow to change the link of the third party to customer/supplier card instead of contact card on List.

*'''MAIN_MODULE_SETUP_ON_LIST_BY_DEFAULT''' ► If set to "common" the setup module becomes list by defaut

*'''MAIN_PAGESIZE_CHOICES''' ► Configure select field to choose number of lines displayed on listing (<code>10:10,15:15,20:20,30:30,40:40,50:50,100:100,250:250,500:500,1000:1000,5000:5000</code>).

*'''MAIN_USE_TOP_MENU_QUICKADD_DROPDOWN''' ► Add a dropdown menu with shortcuts to create new objects ► (v13.0)

*'''MAIN_EMAILCOLLECTOR_MAIL_WITHOUT_HEADER''' ► Remove the header stored by email collector ► (v13.0)

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID'''

*'''MAIN_OPTIMIZEFORTEXTBROWSER''' ► Optimise interface for a text only browser. This variable is set to 1 automatically if your browser is lynx or links

*'''MAIN_NB_OF_YEAR_IN_WIDGET_GRAPH''' ► Set the number of years visible on some graph of some widgets (2 is default value)

*'''MAIN_CREATEFROM_KEEP_LINE_ORIGIN_INFORMATION'''

*'''API_DISABLE_LOGIN_API''' ►(v14.0)

*'''MAIN_LOGIN_BADCHARUNAUTHORIZED''' ► Add possibility to define bad character unauthorized into login name REGEX expression (Default value is @<>"\') ► (v16.0)
*'''MAIN_SHOW_ALL_FILES_ON_DOCUMENT_TOOLTIP''' ► Add all files visible from the object to be visible from the list of object.
*'''MAIN_LIST_ALLOW_PUBLIC_NOTES''' ► Display public notes on list
*'''MAIN_LIST_ALLOW_PRIVATE_NOTES''' ► Display private notes on list

*'''MAIN_CHECKBOX_LEFT_COLUMN''' ► Display private check boxes on the left ► (v17.0)
*'''MAIN_STATS_GRAPHS_SHOW_N_YEARS''' ► Nb of years to shows in widget and graph ► (v14.0)
*'''MAIN_HOOK_DEBUG''' ► if >=2 the hook in the logs are more verbose ► (v18.0)

*'''MAIN_ENABLE_AJAX_TOOLTIP''' ► if 1 the tooltips are updated with AJAX request ► (v18.0)
*'''MAIN_NO_INPUT_PRICE_WITH_TAX''' ► if 1 the TTC input field is removed from propal/invoices/... ► (v17.0)

*'''MAIN_DISABLE_SELECT2_FOCUS_PROTECTION''' ► if 1 disable the focus protection ► (v17.0)
*'''MAIN_USE_ADVANCED_PERMS ►''' Add advanced user permission

[[#Top|(back to top)]]

=Security Options=

*'''MAIN_SECURITY_ANTI_SSRF_SERVER_IP''' ► Can set a complete list of IPs of server.

*'''MAIN_SECURITY_CSRF_WITH_TOKEN''' ► Activate a second anti-CSRF protection on POST (so 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 more powerful. ► (v5.0+)

*'''MAIN_MODULES_FOR_EXTERNAL''' ► Limit available modules for external users. By default value is '<code>facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda</code>'

*'''MAIN_ALLOW_SVG_FILES_AS_IMAGES''' ► Allow to use SVG file as image files. Warning: This may introduce security vulnerability (javascript can be embedded into SVG file).

*'''MAIN_RESTRICTHTML_ONLY_VALID_HTML''' ► Refused parameter if value is not a valid HTML content.

*'''MAIN_RESTRICTHTML_REMOVE_ALSO_BAD_ATTRIBUTES''' ► Sanitize also non standard attributes on HTML content.
*'''MAIN_SECURITY_SALT''' ► A salt string to base the hashing on. 8 strings length recommended.

*'''MAIN_SECURITY_MAX_IMG_IN_HTML_CONTENT''' ► Maximum number of Images on the HTML content
*'''MAIN_SECURITY_ALLOW_UNSECURED_LABELS_WITH_HTML''' ► Allow HTML tags into products label

[[#Top|(back to top)]]

=Adherent Module=

*'''MEMBER_NEWFORM_FORCEMORPHY''' ► Force nature of member set to "phy" for physical or to "mor" for moral ► (v12.0)
*'''MEMBER_ALLOW_CHANGE_OF_TYPE''' ► Member can edit their type on public subscription page ► (v13.0)
*'''ADHERENT_DEFAULT_CREATE_THIRDPARTY''' ► Thirdparty is created when creating a new member ► (v13.0)
*'''MEMBER_SUBSCRIPTION_SUGGEST_END_OF_MONTH''' ► If set to 1, the member subscription end date will be suggested for the end of the month ► (v18.0)
*'''MEMBER_SUBSCRIPTION_SUGGEST_END_OF_YEAR''' ► If set to 1, the member subscription end date will be suggested for the end of the year ► (v18.0)
*'''MAIN_NB_OF_YEAR_IN_MEMBERSHIP_WIDGET_GRAPH''' ► If set, it limits the number of years visible on graph and widgets of membership (empty is default value to show all) ► (v18.0)

[[#Top|(back to top)]]

=Accountancy Module=

*'''ACCOUNTANCY_COMBO_FOR_AUX''' ► Add graphic option for ACCOUNTANCY_COMBO_FOR_AUX. Having this option on may slow down and even freeze the accounting features if you have a very large number of thirdparties ► (v10.0)
*'''ACCOUNTING_DEFAULT_NOT_NOTIFIED_VALIDATION_DATE''' ► Avoid validating the lines with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*'''ACCOUNTING_DEFAULT_NOT_NOTIFIED_EXPORT_DATE''' ► Avoid flagging the lines as exported with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*'''ACCOUNTANCY_USE_PRODUCT_ACCOUNT_ON_THIRDPARTY ►''' Add 2 fields on thirdparty card which allow you to set an account for all sells products and an other for all buying products for this customer ► (v14.0)

[[#Top|(back to top)]]

=Agenda Module=

*'''AGENDA_ALL_CALENDARS''' ► Change the default view of calendar pages to see all the Agenda's (instead or yours only be default)

*'''AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS''' ► To automatically set end date of event to start date + delta on event creation page.

*'''AGENDA_DISABLE_LOCATION''' ► Disable location field in action card ► (>=v5.0)

*'''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''''').

*'''MAIN_ADD_EVENT_ON_ELEMENT_CARD''' ► Allow to create an event from a document (proposal, order, invoice)

*'''AGENDA_SUPPORT_PRIORITY_IN_EVENTS''' ► Allow to have priorities in events ► (>=v13.0)

*'''AGENDA_ADDACTIONFORPHONE''' ► Allow you to create a event from phone number ► (=<v12.0) - Need to be fix for (=>v12.0) https://github.com/Dolibarr/dolibarr/issues/22720

*'''AGENDA_ADDACTIONFOREMAIL''' ► Allow you to create a event from Email ► (=<v12.0) - Need to be fix for (=>v12.0) https://github.com/Dolibarr/dolibarr/issues/22720

[[#Top|(back to top)]]
=Bank Module=

*'''BANK_CAN_RECONCILIATE_CASHACCOUNT''' ► Can reconciliate cash accounts ► (v3.8)

*'''BANK_DISABLE_CHECK_DEPOSIT''' ► Disable check deposit feature

*'''BANK_ASK_PAYMENT_BANK_DURING_ORDER''' ► Ask bank account during creation of an order

*'''BANK_ASK_PAYMENT_BANK_DURING_PROPOSAL''' ► Ask bank account during creation of a proposal

*'''BANK_USE_OLD_VARIOUS_PAYMENT''' ► To allow to enter miscellaneous payments (not covered by other modules) using old method. '''''Deprecated'''''. Entering various payment is preferred ► (<=v12.0).
*'''MAIN_IBAN_IS_NEVER_MANDATORY''' ► IBAN and BIC informations not mandatory. (V15)

[[#Top|(back to top)]]

 

=BOM and MO Module=

*'''ALLOW_USE_KITS_INTO_BOM_AND_MO'''
*'''BOM_SUB_BOM''' ►Allow to add a BOM in another BOM►(v16.0)

[[#Top|(back to top)]]

 

=Bookmarks Module=

*'''BOOKMARKS_SHOW_IN_MENU''' ► Numbers of bookmark entries to be displayed (10 by default)

[[#Top|(back to top)]]

 

=Inalterable Log Module=

*'''BLOCKEDLOG_ADD_ACTIONS_SUPPORTED''' ► Can complete list of triggered action that are logged

[[#Top|(back to top)]]

 

=Category-Tags Module=

*'''CATEGORY_SHOW_COUNTS''' ► Shows nb of object by tags in tag tree

[[#Top|(back to top)]]

 

=Contracts=

*'''CONTRACT_SUPPORT_PRODUCTS''' ► Products are also suggested into module contract.
*
*'''CONTRACT_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)
*'''CONTRACT_HIDE_PLANNED_DATE_ON_PDF''' ► allows you to not display dates on pdf files.
*'''CONTRACT_HIDE_REAL_DATE_ON_PDF''' ► allows you to not display dates on pdf files.

[[#Top|(back to top)]]

=Cron module=

*'''CRON_DISABLE_KEY_CHANGE''' ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*'''CRON_DISABLE_TUTORIAL_CRON''' ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*'''CRON_WARNING_DELAY_HOURS''' ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

[[#Top|(back to top)]]

 

=Direct Debit Orders=

*'''WITHDRAWAL_ALLOW_ANY_INVOICE_STATUS''' ► If this option is set, all invoices status (even already paid) may appear on the list of invoices qualified for a direct debit payment. This is the list of invoices with a payment request done, and not linked to a direct debit payment. By default, only "unpayed" invoices are used to avoid to pay twice the same invoice.

[[#Top|(back to top)]]

=Donation Module=

*'''DONATION_USE_THIRDPARTIES''' ► If this option is set, a thirdparty field appear on donation forms.

[[#Top|(back to top)]]
=Email=

*'''MAIN_MAILFORM_DISABLE_ENTERKEY''' ► Activate JavaScript code to disable the enter key in the MAIL form. ► (>= 8.0.1)

*'''MAIL_PREFIX_FOR_EMAIL_ID''' ► Prefix for the mails ID. Default value is <code>$_SERVER["SERVER_NAME"]</code> ► (>= 8.0.1)

*'''MAIN_MAIL_DEBUG''' ► Write content with header of last mail into file <code>dolibarr_mail.log</code> into directory <code>dolibarr_main_data_root</code>.

*'''MAIN_MAIL_DEBUG_ERR_WITH_DATE''' ► Use a different filename (by adding a prefix of date) for each email sent with error when MAIN_MAIL_DEBUG.

*'''MAIN_MAIL_DEBUG_LOG_WITH_DATE''' ► Use a different filename (by adding a prefix of date) to log each email sent (whatever is result) when MAIN_MAIL_DEBUG.

*'''MAIN_MAIL_FORCE_FROM''' ► (v19+) Can force the value into the From field of the SMTP header. Note that email sender is always saved into the "Reply-To".

*'''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 <code>-f</code>. This option is here to ask Dolibarr to call the function mail of PHP by adding value for the option <code>-f</code>. 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 setup or version of sendmail that ask the -f option to be mandatory or for sendmail setup that does not use by default the From of the header email to define the sender (with this option, the from can be forced on command line to avoid to have the from lost by sendmail).

*'''MAIN_MAIL_SENDMAIL_FORCE_BA''' ► On Linux 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 asks PHP to provide this parameter when sending a mail. Note that another solution is to edit the mail.force_extra_parameters=-ba into <code>php.ini</code> 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 <code>orange.fr</code> or <code>hotmail.com</code>

*'''MAIN_MAIL_DO_NOT_USE_SIGN''' ► Do not add user signature at end of suggested pre-defined email

*'''MAIN_MAIL_FORCE_NOT_SENDING_TO''' ► If en email is defined into this variable, emails will never be sent to this email.

*'''MAIL_FORCE_DELIVERY_RECEIPT_INVOICE''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Invoice'' module.

*'''MAIL_FORCE_DELIVERY_RECEIPT_ORDER''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Order'' module.

*'''MAIL_FORCE_DELIVERY_RECEIPT_PROPAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Proposal'' module.
*'''MAIL_FORCE_DELIVERY_RECEIPT_SUPPLIER_PROPOSAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Supplier Proposal'' module.

*'''MAIN_EMAIL_SUPPORT_ACK ►''' Restore email acknowledgment checkbox on sending emails. This feature is commonly abandoned by mailers. Active from Dolibarr V17 - see [https://github.com/Dolibarr/dolibarr/blob/33744f74da1a5c20f8aa9950018ab4e549e00205/ChangeLog#L53 changelog]
*'''MAIN_EMAIL_USECCC''' ► 1 = Shows field BCC into email forms, If value is an email = Shows the BCC pre filled with the email value.

*'''MAIN_MAIL_AUTOCOPY_PROPOSAL_TO''', '''MAIN_MAIL_AUTOCOPY_ORDER_TO''', '''MAIN_MAIL_AUTOCOPY_INVOICE_TO''', '''MAIN_MAIL_AUTOCOPY_SHIPMENT_TO''', '''MAIN_MAIL_AUTOCOPY_..._TO''' ► Email to use as a BCC recipient 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 third party 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 third party or object, the email exchange is related to.

*'''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► Restrict sending of 1 email message to <code>x</code> recipients for same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include 1000 recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available.

*'''MAIN_MAIL_FORCE_CONTENT_TYPE_TO_HTML''' ► Force to send all email (event with text only content) as HTML formatted email.

*'''MAIN_MAIL_USE_MULTI_PART''' ► Forge email content using an alternate text part ► (for 5.0.2+). By default with 6.0+
*'''MAIN_INFO_SOCIETE_MAIL_ALIASES''' ► add address aliases for the from field on mail. Set his value with "Firstname Name <firstname.lastname@mydomain.tld, Otherfirstname OtherlastName <othermail@mydomain.tld>,..." ► (v5.0.0+)

*'''MAIN_MAIL_ADD_INLINE_IMAGES_IF_IN_MEDIAS''' ► If images were stored into the medias directory from CKEditor, then images into emails are replaced with "inline content". This may increase seriously risk of being detected as SPAM.

*'''MAIN_COPY_FILE_IN_EVENT_AUTO''' ► Add attachment document on event auto generated by sending email from dolibarr. ► (v6.0+)

*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option '''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD'''.

*'''MAIN_MAIL_ENABLED_USER_DEST_SELECT''' ► Show also internal users into list of recipients of email in email sending form ► (v8.0+)

[[#Top|(back to top)]]

=SMS=

*'''MAIN_SMS_DEBUG''' ► Write content of SMS sent into file <code>dolibarr_sms.log</code> into directory <code>dolibarr_main_data_root</code>.

[[#Top|(back to top)]]

=Emailing Module=

*'''MAILING_PREFIX_FOR_EMAIL_ID''' ► Set the value that will be used to compose the "Email ID" into email headers. If you set this value to '<code>SERVER_NAME</code>', the virtual host of web server will be used. By default, this is not defined, so a hash key, unique to each instance, is used.

*'''MAILING_NO_USING_PHPMAIL''' ► If set, the module emailing can't be used with mail setup of "phpmail". Using a thirdparty SMTP server is required. You can complete warning message by adding an email to contact for setup help with constant <code>'''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS'''</code>.

*'''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS''' ► Contains the email of contact to show into the message visible to a user when he try to use emailing module without SMTP server and if option '''MAILING_NO_USING_PHPMAIL''' is set to on.

*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is on "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.

*'''MAILING_LIMIT_WARNING_NOPHPMAIL''' ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is something else than "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.
*'''EMAILING_USE_ADVANCED_SELECTOR''' ► Enable the advanced selector for recipients.

*'''MAILING_LIMIT_SENDBYWEB''' ► Restrict number of emails you can send in same sending session with emailing module from GUI. The value "<code>dolibarr_mailing_limit_sendbyweb</code>" if defined into config file is used in priority for this limit. A negative value means, sending by web is forbidden.

*'''MAILING_LIMIT_SENDBYCLI''' ► Restrict number of emails you can send in same sending session with emailing module from CLI script. The value "<code>dolibarr_mailing_limit_sendbycli</code>" if defined into config file is used in priority for this limit.

[[#Top|(back to top)]]

 

=Expense Report=

*'''EXPENSEREPORT_ALLOW_OVERLAPPING_PERIODS''' ► Can enter several expense reports on same or overlapping date periods. ► (v7.0+)

*'''EXPENSEREPORT_OVERRIDE_VAT''' ► Setting this constant to 1 will allow expense reports to show VAT even if the global VAT setting is off ► (v10.0)

*'''EXPENSEREPORT_USE_OLD_NUMBERING_RULE''' ► The module Expense Report use numbering rules that you can setup (like other modules do). If you need to keep the hard-coded numbering rule of expenses report used in v6.0 set this constant to 1 ► (>=v7.0+)

*'''MAIN_USE_EXPENSE_IK''' ► This feature allows you to set index kilometres against a mileage index for different types of vehicles. ► (v7.0+)

*'''MAIN_USE_EXPENSE_RULE''' ► This feature allows you to set a variety of rules per user/group/all so they can only create reports within their limits. ► (v7.0+)

[[#Top|(back to top)]]

 

=Export Module=

*'''EXPORT_CSV_SEPARATOR_TO_USE''' ► String value to use as default separator to delimit fields of exported files (by default Dolibarr uses "<code>,</code>"). Example: EXPORT_CSV_SEPARATOR_TO_USE=<code>;</code>

*'''EXPORT_CSV_FORCE_CHARSET''' ► Choose the charset used in the output file built by the CSV exporter. By default it is ISO-8859-1. Example: EXPORT_CSV_FORCE_CHARSET= <code>utf-8</code>

*'''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 (<code>"</code>).
*'''EXPORTS_SHARE_MODELS''' ► Share export models between users.

[[#Top|(back to top)]]

=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 added in front of payment cell, into the page to make online subscription.

[[#Top|(back to top)]]

=Interventions Module=

*'''FICHINTER_CLASSIFY_BILLED'''► Allow to classify an intervention card as "Billed". This add also trigger <code>FICHINTER_CLASSIFY_BILLED</code> into list of possible automatic event into agenda.

*'''FICHINTER_DISABLE_DETAILS'''► Disable entry of details line on intervention. Can validate with no line.

[[#Top|(back to top)]]

=Invoice Module=

*'''MAIN_DEPOSIT_MULTI_TVA''' ► In deposits invoice, creates one line per VAT rate from the origin document ► (6.0)

*'''INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED''' ► If a credit note was partially refunded (a refund was sent to the customer), with common situation, we wait to have the remain refunded too. With this option, it is possible to convert the remain of invoice into a discount to reuse it into another invoice.

*'''SUPPLIER_INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED''' ► See INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED, but for supplier credit notes.

*'''INVOICE_CAN_ALWAYS_BE_EDITED''' changed in version 15 or 16 to '''INVOICE_CAN_BE_EDITED_EVEN_IF_PAYMENT_DONE''' ► Allow to edit invoices even if payment was started. Note: If the module "BlockedLog" is active (required in some countries for legal reasons), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*'''INVOICE_CAN_ALWAYS_BE_REMOVED''' ► Allow to always delete invoices (even if invoice is not last one). Note: If the module "BlockedLog" is active (required by some countries for legal reason), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*'''INVOICE_CAN_NEVER_BE_REMOVED''' ► Never allow to delete invoices (except draft invoices with ref like (PROV%)).

*'''INVOICE_POSITIVE_CREDIT_NOTE''' ► All amounts on PDF credit notes are positive.

*'''FACTURE_DEPOSITS_ARE_JUST_PAYMENTS''' ► An old way to create initial payment. This treats deposit invoices as a special case and not as legal deposit invoice. 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. WARNING: In a lot of european countries, using this option is not allowed.

*'''FACTURE_SENDBYEMAIL_FOR_ALL_STATUS''' ► Can send invoice by email to customer even if invoice has status "draft".

*'''INVOICE_CREDIT_NOTE_STANDALONE''' ► Start implementation to allow a credit note even without invoice (dangerous) ► (v3.9)

*'''INVOICE_USE_SITUATION''' ► Enable the "situation invoice" feature. Warning, this feature is bugged and may not be compatible with the final version of the feature once the bug will be solved. Also, using the double-entry accountancy module is not possible when this option is on (due to the same design problem).

*'''INVOICE_USE_SITUATION_CREDIT_NOTE''' ► Enable the "situation credit note" feature (need <code>INVOICE_USE_SITUATION</code>) ► (v8.0)
*'''INVOICE_USE_RETAINED_WARRANTY''' ► Enable the retained warranty on invoice ► (v14.0)

*'''INVOICE_DISABLE_DEPOSIT''' ► Disable deposit invoices

*'''INVOICE_DISABLE_REPLACEMENT''' ► Disable replacement invoices

*'''INVOICE_DISABLE_CREDIT_NOTE''' ► Disable credit notes

*'''INVOICE_ADD_ZATCA_QR_CODE''' ► Add a QR code with format ZATCA (for Saudi Arabia) on PDF of invoices.
*<bdi>'''INVOICE_ADD_EXTRAFIELD_IN_NOTE''' ► Add extrafields in note for canelle template ► (v17.0+)</bdi>
*'''INVOICE_DEFAULT_NOTE_PUBLIC''' <bdi>► Default text in public note</bdi>

Note: To decode a QR image of a ZATCA code: https://www.onlinebarcodereader.com/. You can also use the mobile application https://play.google.com/store/apps/details?id=com.posbankbh.einvoiceqrreader&gl=FR

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT''' ► See PDF option

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN''' ► See PDF options

*'''WORKFLOW_BILL_ON_SHIPMENT''' ► Change label of button with suitable label when you need to create invoice on shipments

*'''INVOICE_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. Use the tag __DIRECTDOWNLOAD_URL_INVOICE__ in email template to insert it. ► (v7.0+)

*'''INVOICE_POINTOFTAX_DATE''' ► Add Point of Tax Date on invoices for country-specific legality reasons ► (v4.0+)
*'''FACTURE_ENABLE_NEGATIVE''' ► Can validate an invoice when amount is negative

*'''FACTURE_ENABLE_NEGATIVE_LINES''' ► Allows to add negative lines to an invoice ► (v8.0.2+)

*'''INVOICE_USE_DEFAULT_DOCUMENT''' ► Allow user to select a default invoice documents models according to invoice type. On invoice create page, the model is dynamically changed on invoice type selection. ► (v9.0+)

*'''FACTURE_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object (Proposal,...) when creating the bill.
*'''FACTUREFOURN_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object when creating the supplier bill ► (V13.0)
*'''MAIN_SHOW_FACNUMBER_IN_DISCOUNT_LIST''' ► Display the reference of credit notes in discount list when creating the bill.
*'''INVOICE_ALLOW_FREE_REF''' ► Capability to change reference of an invoice. This will be possible as long as the invoice has the status “Draft” and only if your country is not in Europe(V11)

*'''INVOICE_DISALLOW_REOPEN'''

*'''INVOICE_MAX_FUTURE_DELAY''' ► Numbers of seconds allowed for billing in the future ► (V14.0)
*'''INVOICE_AUTO_NEXT_MONTH_ON_LINES''' ► Increase start date and end date by one month, if an invoice line is a clone of a time based service AND if this services started on the first day of month and ended on the last day of month ► (V13.0.1)
*'''INVOICE_KEEP_DISCOUNT_LINES_AS_IN_ORIGIN''' ► Does not change a line with a negative price into an absolute discount when creating an invoice ► (V16 ?)
*'''INVOICEREC_SET_AUTOFILL_DATE_START''' and '''INVOICEREC_SET_AUTOFILL_DATE_END ►''' Set start and end date to yes for lines of template invoice when created from a draft invoice ► (V16)
*'''INVOICE_REC_DATE_TO_YES''' '''►''' Set start and end date to yes by default in add line form for template invoice ► (V16)
*'''INVOICE_SUBTYPE_ENABLED''' ► Extends Dolibarr standard invoice with more invoice types used in some countries. A combo box in the new invoice creation card allows the selection of "subtypes" with values from dictionary "Invoice Subtypes" ► (v19.0+)

[[#Top|(back to top)]]

=Leave=

*'''MAIN_NON_WORKING_DAYS_INCLUDE_SATURDAY''' ► Set this value to 0 if you want to have the Saturday as a working day
*'''MAIN_NON_WORKING_DAYS_INCLUDE_SUNDAY''' ► Set this value to 0 if you want to have the Sunday as a working day

=Look or Theme=

*'''MAIN_FAVICON_URL''' ► favicon url

*'''MAIN_EASTER_EGG_COMMITSTRIP''' ► Show a comic image from the CommitStrip website. Images are refreshed daily. ► (v6.0+)

*'''MAIN_STATUS_USES_CSS''' ► Change status design using new style ► (v10.0+)

*'''MAIN_INCLUDE_GLOBAL_STATS_IN_OPENED_DASHBOARD''' ► This conf will auto remove global stats box item if there are already in the new dashboard of opened elements and keep displayed stats on the opened item box (not only on mouse over) ► (v11.0+)

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Actually only for eldy theme, this conf move search input to top menu and use new design too ► (v11.0+)

*'''THEME_AGRESSIVENESS_RATIO''' ► This conf can be used to increase/decrease aggressiveness of colors. Value 0 is medium, value is between -100 (light grey colors) to +100 (very flashy colors) ► (v11.0+)

*'''THEME_SHOW_BORDER_ON_INPUT'''
*'''MAIN_DISABLE_GLOBAL_WORKBOARD''' ► Hide the work board of the main page ► (v13.0+)
*'''MAIN_DISABLE_GLOBAL_BOXSTATS''' ► Hide the Statistic Box of the main page
*'''ALLOW_THEME_JS ►''' Allow JS file in theme folder (same name as theme folder)

 

=Manifest (Progressive Web App)=

*'''MAIN_MANIFEST_APPLI_THEME_COLOR ►''' Theme color for manifest
*'''MAIN_MANIFEST_APPLI_BG_COLOR ►''' Background color for manifest
*'''MAIN_MANIFEST_APPLI_LOGO_URL ►''' Logo for manifest
*'''MAIN_MANIFEST_APPLI_LOGO_URL_SIZE ►''' Logo url size for app (150, 192, 512px) missing 3 configurations

[[#Top|(back to top)]]

=Order Module=

*'''MAIN_MASSACTION_CREATEBILLS_REDIRECT_IF_ONE''' ► If set 1, redirects to the one bill created from massaction create bills from order list ► (v20.0)

*'''MAIN_MASSACTION_CREATEBILLS_REDIRECT_IF_MANY''' ► If set to 1, redirects to the invoice list after plural invoices where generated from tho massaction create bills from order list ► (v20.0)

*'''MAIN_ORDERLIST_CREATEBILLS_ONEBYTHIRD''' ► Allow defining value for option "one by thirdparty" in massaction create bills from orders list page (no by default, yes if set to 'yes' or 1) ► (v20.0)

*'''MAIN_USE_PROPAL_REFCLIENT_FOR_ORDER''' => Copy customer reference from proposal to order. ► (v7.0+)

*'''ORDER_REQUIRE_SOURCE''' => Make the input field "Source of order" mandatory.

*'''ORDER_VALID_AFTER_CLOSE_PROPAL''' => When an order is created on a proposal close, the order is directly defined with status "Validated".

*'''ORDER_ALLOW_EXTERNAL_DOWNLOAD''' => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*'''ORDER_ENABLE_NEGATIVE''' => Can validate an order when amount is negative

*'''THIRDPARTY_PROPAGATE_EXTRAFIELDS_TO_ORDER''' => Copy also extrafields from thirdparty to order (if name match). ► (v11.0+)

[[#Top|(back to top)]]

 

=PDF Options=

*'''MAIN_ADD_PDF_BACKGROUND''' ► Define this constant with short name of a PDF file (example "<code>mypdf.pdf</code>") that must be saved into directory "<code>documents/mycompany</code>". 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_DISABLE_FORCE_SAVEAS''' ► If your browser always asks to save downloaded files on disk (like PDF), try this this option. File may be displayed directly in your browser. Values : 0= Default (file is auto downloaded), 1= For to output the file into the browser tab, 2= For to output the file into a browser tab open with target_blank

*'''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 servers with low CPU.

*'''MAIN_DISABLE_PDF_COMPRESSION''' ► Disable PDF compression.

*'''MAIN_DOCUMENTS_WITH_PICTURE_WIDTH''' ► Can change size of picture when hidden option <code>MAIN_GENERATE_PROPOSALS_WITH_PICTURE</code> is used. By default value is <code>20</code>.

*'''MAIN_GENERATE_DOCUMENTS_SHOW_FOOT_DETAILS''' ► Adding the company address at the bottom of the page. Disabled by default

*'''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer proposals.
*'''MAIN_GENERATE_ORDERS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer orders.

*'''MAIN_GENERATE_INVOICES_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer invoices.

*'''MAIN_GENERATE_SUPPLIER_PROPOSAL_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier proposals ► (v5.0.3+)
*'''MAIN_GENERATE_SUPPLIER_ORDER_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier orders

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT''' ► Disable VAT on generated documents. like for an association. (Works with crabe template)

*'''MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN''' ► Hide column with VAT information but only column not total.

*'''MAIN_INVERT_SENDER_RECIPIENT''' ► Invert sender and recipient in some PDF. Note: This option is set automatically if country if Germany.

*'''MAIN_ODT_AS_PDF''' ► Activate ODT to PDF conversion. Value can be "libreoffice" or "unoconv". Do not use value '''<nowiki/>'jodconverter'<nowiki/>''' any more, as it is declared deprecated and partly not functional, use value '''<nowiki/>'libreoffice'''' instead, it requires only '''soffice''' (OpenOffice or LibreOffice) installed on server (use '''apt install soffice libreoffice-common libreoffice-writer''').

If you got this error: javaldx failed! Warning: failed to read path from javaldx with no return to prompt when running soffice --headless -env:UserInstallation=file:"/tmp" --convert-to pdf --outdir xxx ./yyy.odt, check that directory defined into env:UserInstallation parameters exists and is writeable.

You may also have a look at this page if your server is on Windows: [[Générer automatiquement des documents PDF à partir de fichier ODT avec Doliwamp]]

*'''MAIN_ODT_AS_PDF_DEL_SOURCE''' ► For ODT generation. If set, then initial behaviour is conserved but ODT file is removed when option to convert it as PDF (see previous) is on. Disabled by default

*'''MAIN_PDF_FORCE_FONT''' ► To ignore font defined into language file and force usage of a particular font. For example "<code>DejaVuSans</code>".

*'''MAIN_PDF_FORCE_FONT_SIZE''' ► To force size of font (by default 10). For example "<code>12</code>" ► (v11.0)

*'''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: <code>220,220,200</code>

*'''MAIN_PDF_USE_LARGE_LOGO''' ► Use the original logo with its higher resolution into the PDF instead of the small thumb. This may lead to very very large PDF !

*'''MAIN_USE_BACKGROUND_ON_PDF''' ► Define this constant with short name of an image (example "<code>myimage.jpg</code>") that must be saved into directory "<code>documents/mycompany/logos</code>". This will add this background image into your generated PDF files.

*'''MAIN_USE_COMPANY_NAME_OF_CONTACT''' ► Use contact name and information rather than company

*'''MAIN_PDF_ADDALSOTARGETDETAILS''' ► If 1, add details of recipient on generated PDFs (email, fax, url and phone). Can be useful in cases where a printed order/invoice etc is given to a delivery driver/courier etc.

*'''MAIN_TVAINTRA_IN_SOURCE_ADDRESS''' ► Show VAT N° in source address of PDF to comply with legalities in certain countries. Note that VAT number should be already visible in footer of page ► (v8.0.1+)

*'''MAIN_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► Add optional esign field in pdf propal ► (v8.0+)

*'''MAIN_PROFID1_IN_SOURCE_ADDRESS''' ► Show Professional ID 1 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID2_IN_SOURCE_ADDRESS''' ► Show Professional ID 2 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID3_IN_SOURCE_ADDRESS''' ► Show Professional ID 3 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID4_IN_SOURCE_ADDRESS''' ► Show Professional ID 4 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID5_IN_SOURCE_ADDRESS''' ► Show Professional ID 5 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*'''MAIN_PROFID6_IN_SOURCE_ADDRESS''' ► Show Professional ID 6 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

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

*'''PDF_BOLD_PRODUCT_REF_AND_PERIOD''' ► Add more visibility (bold) on product ref and period of service in desc. ► (v12.0)

*'''PDF_HIDE_PRODUCT_REF_IN_SUPPLIER_LINES''' ► Modify the use/position of Supplier Ref/Internal Ref with the item Label (name) on PDF documents.

Default (constant not set or Value <code>0</code>): Internal ref followed by supplier ref in brackets."COMPANY-REF-001 (Vendor SKU SUPPLIER-REF-001) - LABEL...".

Value <code>1</code>: Supplier ref only eg."SUPPLIER-REF-001 - LABEL...".

Value <code>2</code>: Supplier ref followed by internal ref in brackets. eg."SUPPLIER-REF-001 (InternalRef COMPANY-REF-001) - LABEL...".

*'''PDF_INCLUDE_ALIAS_IN_THIRDPARTY_NAME''' ► Include alternative/alias name into name on PDF.

*'''PDF_SECURITY_ENCRYPTION''' ► Encrypt PDF produced by dolibarr ► (v?) . See additional parameters :PDF_SECURITY_ENCRYPTION_RIGHTS (block 'modify' or 'copy') - '''PDF_SECURITY_ENCRYPTION_USERPASS''' - '''PDF_SECURITY_ENCRYPTION_OWNERPASS''' (random if not specified) - '''PDF_SECURITY_ENCRYPTION_STRENGTH''' (0 = RC4 40 bit; 1 = RC4 128 bit; 2 = AES 128 bit; 3 = AES 256 bit) - '''PDF_SECURITY_ENCRYPTION_PUBKEYS''' Array of recipients containing public-key certificates ('c') and permissions ('p') - For example: array(array('c' => 'file://../examples/data/cert/tcpdf.crt', 'p' => array('print')))

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

*'''PDF_USE_1A''' ► PDF files produced by dolibarr respect PDF/A standard ► (v?)

*'''PDF_USE_ALSO_LANGUAGE_CODE''' ► The value of this constant must be a language code ('fr_FR', 'en_US', 'sa_SA', ...). If set, the PDF document will contains both language (default and the one defined by the constant).
*'''DOC_SHOW_FIRST_SALES_REP''' ► Show the sales representant on header (at least on propal azur and rubis template)
*'''MAIN_PDF_DASH_BETWEEN_LINES'''
*
*'''SHOW_SUBPRODUCT_REF_IN_PDF'''
*'''PDF_HIDE_PRODUCT_LABEL_IN_SUPPLIER_LINES''' ► hide product label in supplier order lines (V15+)
*'''SHIPPING_PDF_DISPLAY_AMOUNT_HT''' ► Show HT unit price and HT total price for lines of PDF shipment

*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_FACTURE''' ► To Hide product description in Customer Invoice
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_COMMANDE''' ► To Hide product description in Sales Order
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_ORDER_SUPPLIER''' ► To Hide product description in Purchase Order
*'''MAIN_DOCUMENTS_HIDE_DESCRIPTION_FOR_INVOICE_SUPPLIER''' ► To Hide product description in Vendor Invoice

*'''PDF_PROPAL_SHOW_PRICE_INCL_TAX''' ► Display price with tax on Proposal(cyan template), Order(eratosthene template), Bill(sponge template) (V17+)

[[#Top|(back to top)]]

=Point of Sale (POS)=

*'''CASHDESK_SHOW_KEYPAD''' ► Show a mouse key pad into the 'Simple Point of Sale' module.

*'''POS_ADDON''' ► Set this value to an existing numbering module rule (for example '<code>mod_facture_terre</code>', '<code>mod_facture_mars</code>', ...) to force the numbering module to use for invoice ref definition when invoice is created by the POS. For example setting value <code>POS_ADDON</code> to '<code>mod_facture_terre</code>' will use the numbering module '<code>terre</code>' for invoice generated from POS, whatever is the numbering rule defined into invoice module setup (you can also use POS_NUMBERING_TERRE_FORCE_PREFIX and POS_NUMBERING_MARS_FORCE_PREFIX variable to change the prefix used).

*'''TAKEPOS_ENABLE_SUMUP''' ► Enable the compatibility of TakePOS with the card reader terminal [https://SumUp.fr SumUp]
*'''TAKEPOS_CAN_FORCE_BANK_ACCOUNT_DURING_PAYMENT''' ► Possibility to force the bank account during the payment in TakePOS ► (v13.0)
*'''TAKEPOS_CONTROL_CASH_OPENING''' ► Control the cash opening
*'''TAKEPOS_NUMPAD_FORCE_PAYMENT_ICONS_LABELS'''

[[#Top|(back to top)]]

=Products Module=

*'''CATEGORY_GRAPHSTATS_ON_PRODUCTS''' ► Show graph of products with categories and totals in Products Area screen

*'''MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE''' ► Avoid customs 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.

*'''MAIN_DIRECT_STATUS_UPDATE''' ► Allows you to change the status of the product (''for sale/not for sale for purchase/not for purchase'') directly on the product page via a ''on/off'' switch button. This can be convenient for those who need to quickly disable certain statuses of products without having to go through the editing product page individually. Also can be very useful if used as a filter on the product and product search list. This option doesn't generate a MODIFY trigger, so be careful with external modules. ► (v4.0+)

*'''MAIN_SEARCH_PRODUCT_BY_FOURN_REF''' ► Allow to search a product by supplier ref in document's add line form. ► (>= 8.0)

*'''MAIN_DISABLE_FREE_LINES''' ► Disallow using free lines to add line in documents ► (>= 8.0)

*'''MAIN_SHOW_PRODUCT_ACTIVITY_TRIM''' ► Show Product and Services turnover before for all four quarters tax over recent years recent years on the product area ► (v5.0+)

*'''PRODUIT_DESC_IN_LIST''' ► Show long description of product/service into lists.

*'''PRODUCT_DISABLE_PROPAGATE_CUSTOMER_PRICES_ON_CHILD_COMPANIES''' ► Disable propagation of prices per customer from a customer to its child company.

*'''PRODUCT_DISABLE_PUBLIC_URL''' ► Disable public url in product card ► (v14.0+)
*'''PRODUCT_DISABLE_STOCK_LEVELS''' ► Disable properties of stock limits and desired optimal value on product ► (v14.0+)
*'''PRODUCT_DISABLE_NATURE''' ► Disable nature in product card ► (v14.0+)
*'''PRODUCT_DISABLE_WEIGHT''' ► Disable weight in product card ► (v14.0+)
*'''PRODUCT_DISABLE_PRICES''' ► Disable prices in product card ► (v14.0+)
*'''PRODUCT_DISABLE_ACCOUNTING''' ► Disable accounting in product card ► (v14.0+)
*'''PRODUCT_DISABLE_SIZE''' ► Disable size in product card.

*'''PRODUCT_DISABLE_LENGTH''' ► Disable length in product card ► (v4.0+)

*'''PRODUCT_DISABLE_SURFACE''' ► Disable surface in product card. ► (v4.0+)

*'''PRODUCT_DISABLE_VOLUME''' ► Disable volume in product card.

*'''PRODUCT_DISABLE_CUSTOM_INFO''' ► Disable custom info (custom code and country origin) in product/service card.

*'''PRODUIT_MULTIPRICES_USE_VAT_PER_LEVEL''' ► When option to use price per level/segment is on, this allows to also set a dedicated vat for each price level.

*'''PRODUIT_CUSTOMER_PRICES_BY_QTY''' ► If price per quantity ► ''Experimental''
*'''PRODUIT_CUSTOMER_PRICES_BY_QTY_MULTIPRICES''' ► If price per quantity and customer ► ''Experimental''

*'''PRODUCT_LOT_ENABLE_QUALITY_CONTROL''' ► Enable feature (Display fields for life time and quality control duration) for quality control on product and lot

*'''PRODUCT_MAX_LENGTH_COMBO''' ► Limit the length of the label displayed when adding lines in proposals/invoices/orders

*'''PRODUCT_MAX_VISIBLE_PHOTO''' ► Show a maximum number of product photos (as thumbnails) on the product main card. Example, setting this constant to '<code>5</code>' will show the first five product photos found on the product card.

*'''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''' ► Add other units on products (Use same dictionary as default unit feature) and propagate this unit on line of documents.
*'''MAIN_EDIT_LINE_ALLOW_ALL_UNIT_TYPE ►''' Allow the selection of other unit types when editing the document line

*'''RESOURCE_ON_PRODUCTS''' ► Allow to affect resources on products/services ► (v10.0+)
*'''RESOURCE_ON_SERVICES''' ► Allow to affect resources on products/services ► (v10.0+)
*'''PRODUCT_SHOW_ORIGIN_IN_COMBO''' ► Show origin of products when adding lines in proposals/invoices/orders ► (v12.0+)
*'''PRODUIT_ATTRIBUTES_HIDECHILD''' ► Add option hide child if variantes

*'''PRODUCT_ADD_FORM_ADD_TO''' ► Add a product to a draft proposal/order/invoice, from the product card.
*'''PRODUCT_DISABLE_SELLBY''' ► Hide the Sell by date ► (v13.0+)
*'''PRODUCT_DISABLE_EATBY''' ► Hide the Eat by date ► (v13.0+)

*'''PRODUCT_DENY_CHANGE_PRODUCT_TYPE''' ► Forbid to change the product type

*'''PRODUCT_SORT_BY_CATEGORY''' ► Sort the product by categories instead of by ID
*'''PRODUCT_ADD_NET_MEASURE''' ► Support Net Measure in product's card.php (For real weight, volume or piece; needed for some business ie fruits, vegetables....). Note brut value is already available natively, use this option only if you need 2 weights, 2 volumes, ...for each product) ► (v11.0.1+)
*'''PRODUCT_PRICE_BASE_TYPE''' ► value 'TTC' / 'HT' specify the default value of the price (with or without taxes) ► (v16.0.0+)

*'''PRODUCT_LOAD_EXTRAFIELD_INTO_OBJECTLINES''' ► Load product extrafiled on object lines

*'''PRODUCT_USE_SUB_COST_PRICES_IF_COST_PRICE_EMPTY''' : Calculate the parent product production price by child prices.

[[#Top|(back to top)]]

 

=Projects Module=

*'''PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY''' ► Option related to the combo list Project on elements. It is a list of thirdparty IDs. If set, you can link an object to a project owned by one of this thirdparty in the list.

*'''PROJECT_ALLOW_COMMENT_ON_PROJECT''' ► Add comment feature on a project

*'''PROJECT_ALLOW_COMMENT_ON_TASK''' ► Add comment feature on project task
*'''PROJECT_ALWAYS_DISCARD_CLOSED_PROJECTS_IN_SELECT''' ► Discards closed projects in every select field. A closed project can't be associated to an object ► (v20.0+)

*'''PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS''' ► Option related to the combo list Project on elements. Can link an element (purhcase invoice, purchase order, reception, ...) to any project even if object has a different supplier than the one of the project to link to. See also PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY that is different because it allows to define some given thirdparty ID to allow.

*'''PROJECT_CREATE_ON_OVERVIEW_DISABLED''' ► Hide the "create ..." button on the overview page ► (v4.0)

*'''PROJECT_DISABLE_UNLINK_FROM_OVERVIEW''' ► Enable removing the button from a link in the project overview. ► (>= v8.0.1)

*'''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''' ► Hide the "link to" form on the overview page ► (v4.0)

*'''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_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_OPEN_ALWAYS_ON_TAB''' ► Set to value 'task', or 'preview' to always open the project on the given tab instead of main tab.
*
*
*'''PROJECT_ELEMENTS_FOR_MINUS_MARGIN'''

[[#Top|(back to top)]]

=Proposals Module=

*'''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Add a picture of the product (the first one found if there are several) into the generated PDF of proposals. Note that using this will reduce the available width for the product description.

*'''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_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► add optional esign field in pdf propal ► (v8.0+)

*'''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.

*'''PROPAL_DISABLE_SIGNATURE''' ► Do no show the box for signature.

*'''PRODUIT_PDF_MERGE_PROPAL''' ► When generating the proposal PDF, all PDFs linked to products linked to proposal are also included into final PDF

*'''PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*'''PROPOSAL_AUTO_ADD_AUTHOR_AS_CONTACT''' ► Add Proposal Author as user contact follow proposal

*'''PROPOSAL_PDF_HIDE_PAYMENTTERM''' ► Do not show the payment term on proposal ► (v11.0+)

*'''PROPOSAL_PDF_HIDE_PAYMENTMODE''' ► Do not show the payment mode on proposal ► (v11.0+)

*'''WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES''' ► Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.
*'''PROPAL_REOPEN_UNSIGNED_ONLY''' ► Do not allow reopening of signed (or billed) proposals. (V15)
*'''PROPOSAL_ARE_NOT_BILLABLE''' ► Disable billing button on proposals (V15)
*'''PROPAL_DEFAULT_NOTE_PUBLIC''' ► Default text in public note

[[#Top|(back to top)]]

 

=Services Module=

*'''SERVICE_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country. For french speaking people, see also the page [[Loi_européenne_TVA_Vente_à_Distance_VAD_et_e-commerce_BtoC]].

*'''MAIN_FILL_SERVICE_DATES_FROM_LAST_SERVICE_LINE''' ► (v13.0) On add line form add a button to fill service dates from the last service line

[[#Top|(back to top)]]

=Shipments=

*'''STOCK_WAREHOUSE_NOT_REQUIRED_FOR_SHIPMENTS''' ► If set, you can add a shipment line, with no stock source defined. ► (>= 8.0.1)

*'''SHIPMENT_GETS_ALL_ORDER_PRODUCTS''' ► Add all order lines in shipment, including the one with 0 in quantity
*'''SHIPPING_PDF_HIDE_ORDERED''' ►Hide column quantity ordered on shipment pdf (>=15.0)
*'''STOCK_SUPPORTS_SERVICES''' ►Allow to manage services into warehouse and allow to ship services
*'''SHIPMENT_SUPPORTS_SERVICES''' ►Allow to ship services without stock (>=19.0)

[[#Top|(back to top)]]

=Stocks=

*'''SUPPLIER_ORDER_DISABLE_STOCK_DISPATCH_WHEN_TOTAL_REACHED''' ► Disable stock dispatch when total expected was already received

*'''STOCK_EXCLUDE_VIRTUAL_PRODUCTS''' ► If product is a virtual product, we do not manage stock for it.

*'''ENTREPOT_EXTRA_STATUS''' ► Instead of the 2 status (Closed, Open), a Warehouse has 3 status: Closed, Open (for all movements), Open (for internal movement only). Internal movement only means you can't use the warehouse to make shipment or receptions.
*'''SUPPLIER_ORDER_STATUS_FOR_VIRTUAL_STOCK''' ► For the calculation of virtual stocks, by default supplier orders with the status 3 (ordered) and 4 (partially received) are used. You can enter the list of statuses to be taken into account separated by commas for this calculation (example: 0,1,2,3)
*'''STOCK_MOVEMENT_LIST_HIDE_UNIT_PRICE''' ► to hide unit price on some pages (V15+)

[[#Top|(back to top)]]

=Suppliers Module=

*'''FOURN_PRODUCT_AVAILABILITY''' ► On the Suppliers price page of the products, activate the supplier product availability. ''This is duplicate feature with delivery_delay introduced with 3.8.''

*'''RELOAD_PAGE_ON_SUPPLIER_CHANGE''' ► On creation of a supplier order/invoice, reload form with supplier-specific details when supplier is selected from drop-down list.

*'''SUPPLIER_INVOICE_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier invoice to only those with a buying price defined for that supplier. ► (v6.0+)

*'''SUPPLIER_ORDER_AUTOADD_USER_CONTACT''' ► Add user approving supplier order as a contact automatically.

*'''SUPPLIER_ORDER_DEFAULT_PAYMENT_MODE_ID''' ► Set the default payment method for suppliers (<code>rowid</code> in table <code>llx_c_paiement</code>).

*'''SUPPLIER_ORDER_USE_DISPATCH_STATUS''' ► Add a status on each dispatch order line when receiving products from suppliers ► (v4.0+)

*'''SUPPLIER_ORDER_NO_DIRECT_APPROVE''' ► No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

*'''SUPPLIER_ORDER_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier order to only those with a buying price defined for that supplier. ► (v6.0+)

*'''SUPPLIER_ORDER_EDIT_BUYINGPRICE_DURING_RECEIPT''' ► Can modify the buying price used for PMP calculation when making a stock reception on a supplier order. ► (v6.0+)

*'''SUPPLIER_PROPOSAL_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier proposal to only those with a buying price defined for that supplier. ► (v6.0+)

*'''DISPLAY_DISCOUNTED_SUPPLIER_PRICE''' ► Allow to display discounted supplier price when searching product in supplier documents ► (v10.0)

*'''MAIN_CAN_EDIT_SUPPLIER_ON_SUPPLIER_ORDER''' ► Allow to change the supplier on a draft supplier order ► (v10.0)
*
*'''SUPPLIER_PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD'''

[[#Top|(back to top)]]

=Third Parties Module=

*'''COMPANY_AQUARIUM_CLEAN_REGEX''' ► Add a REGEX rule on the third parties names. It applies a regex replacement pattern on generated code if COMPANY_AQUARIUM_CLEAN_REGEX is set. Value must be a regex with parenthesis. The part into parenthesis is kept, the rest removed. For example if COMPANY_AQUARIUM_CLEAN_REGEX = '<code>^..(..)..(.*)</code>' the first char and second char are removed and the char 5 and 6 too ► (>= 8.0.1)

*'''MAIN_UNKNOWN_CUSTOMERS_ARE_COMPANIES''' ► See in Global options section.

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► See in Global options section.

*'''SOCIETE_EMAIL_MANDATORY''' ► E-mail is a mandatory field when creating a thirdparty

*'''SOCIETE_DISABLE_CUSTOMERS''' ► Remove all menu and features related to customers

*'''SOCIETE_DISABLE_PROSPECTS''' ► Remove all menu and features related to prospects
*'''SOCIETE_DISABLE_PROSPECTSCUSTOMERS ►''' Remove the status "Customer/Prospect" when thirdparties creation or modification

*'''SOCIETE_DISABLE_STATE''' ► Do not use field "state/province"

*'''SOCIETE_SORT_ON_TYPEENT''' ► The combo list of "type of third party" is sorted on alphabetical order instead of the field "position" that appears into dictionary instead.

*'''SOCIETE_ASK_FOR_SHIPPING_METHOD''' ► Shipping method can be predefined on customer card and will be used as default on order creation
*'''SOCIETE_ADD_REF_IN_LIST''' ► Displays the code before the name in the lists ► Value 1 -> Code + name + alias ou Code + name if colone alias 2 -> Code + alias 3 -> Alias

*'''THIRDPARTY_CAN_HAVE_CATEGORY_EVEN_IF_NOT_CUSTOMER_PROSPECT_SUPPLIER''' ► Possible to add Categories to third parties that are not customer, prospect or supplier.

*'''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.

*'''THIRDPARTY_NOTCUSTOMERPROSPECT_BY_DEFAULT''' ► Do not set status "Customer/Prospect" to "on" when creating a new third party from menu "New third party".

*'''THIRDPARTY_INCLUDE_PARENT_IN_LINKTO''' ► Search also for elements on parent third party when using the "link to" object feature.

*'''THIRDPARTY_INCLUDE_PROJECT_THIRDPARY_IN_LINKTO''' ► Search also for elements on third party that own the project of the current element when using the "link to" object feature (if project is owned by a different thirdparty than current one).

*'''THIRDPARTY_LOGO_ALLOW_EXTERNAL_DOWNLOAD''' ► When a logo is uploaded, a share key is automatically set so the file can be downloaded using the share key.

*'''THIRDPARTY_SUGGEST_ALSO_ADDRESS_CREATION''' ► Enabled contact creation on third-party create card
*'''THIRDPARTY_QUICKSEARCH_ON_FIELDS''' ► Personalized search criteria ► Example: $conf->global->THIRDPARTY_QUICKSEARCH_ON_FIELDS = 's.nom=ThirdPartyName;s.name_alias=AliasNameShort;s.code_client=CustomerCode'
*'''MEMBER_CAN_CONVERT_CUSTOMERS_TO_MEMBERS''' ► Enabled member creation on third-party create card
*'''SOCIETE_DISABLE_PARENTCOMPANY''' ► Disables attachment to a parent company.
*'''THIRDPARTY_CUSTOMERPROSPECT_BY_DEFAULT''' ► Set the third party to customer by default
*'''THIRDPARTY_SUPPLIER_BY_DEFAULT''' ► Set the third party to supplier by default
*'''THIRDPARTY_CUSTOMERTYPE_BY_DEFAULT''' ► Set the third party type by default (3 = customer & prospect / 2 = prospect / 1 = customer )
*'''CONTACT_DISABLE_PERSONALINFO''' ► Disable Personal data on contact page
*'''SOCIETE_DISABLE_WORKFORCE''' ► Disable work force selector on society page
*'''SOCIETE_SHOW_VAT_IN_LIST''' ► display VAT number in combo list of thirdparties ► (V15+)
*'''THIRDPARTY_DEFAULT_CREATE_CONTACT''' ► When set, a contact is created at the creation of an individual third party ► (v14.0)

*'''MAIN_SUPPORT_SHARED_CONTACT_BETWEEN_THIRDPARTIES''' ► Able to share contact between several third parties

[[#Top|(back to top)]]

=Ticket Module=

*'''TICKET_SHOW_MESSAGES_ON_CARD''' ►Display all ticket related messages on the main ticket card. ► (>= 10.0)
*'''TICKET_AUTO_ASSIGN_CONTRACT_CREATE''' ►Automatically create a contract linked to the ticket ► (>= 10.0)
*'''TICKET_AUTO_CREATE_FICHINTER_CREATE''' ►Automatically create an intervention linked to the ticket ► (>= 10.0)
*'''WORKFLOW_TICKET_CLOSE_INTERVENTION''' ►On ticket close, automatically close an intervention linked to the ticket
*'''TICKET_CHECK_NOTIFY_THIRDPARTY_AT_CREATION''' ►Automatically check "notify thirdparty at creation" ( >=16)
*'''TICKETS_MESSAGE_FORCE_MAIL''' ► Pre check email sending on ticket message (>=15)
*'''TICKET_SEND_PRIVATE_EMAIL ►''' Allow a private message to be sent by mail (>=17)
*'''TICKET_LIMIT_VIEW_ASSIGNED_ONLY''' '''►''' Only display tickets assigned to the user
*'''TICKET_ADD_AUTHOR_AS_CONTACT''' '''►''' If set to 1: Automatically adds the author as internal contact. If set to 2: Automatically adds the author as external contact if external user. (>=20)

 

=VAT Report=

*'''MAIN_INCLUDE_ZERO_VAT_IN_REPORTS''' ► Include lines with VAT to 0% (for "auto-liquidation" in EEC) ► (v8.0.3+)

[[#Top|(back to top)]]

=Website Module=

*'''WEBSITE_USE_WEBSITE_ACCOUNTS''' ► Add a table and a tab to manage some accounts for websites to a third party
*'''WEBSITE_ALLOW_OVERWRITE_GIT_SOURCE''' ► Add a button to export a website over the GIT sources
*'''WEBSITE_ADD_CSS_TO_BODY''' ► Add a CSS class to the body tag of websites

[[#Top|(back to top)]]

 

=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 guaranteed with this. Also if the image is removed or renamed by the image hosting service, your proposal, order or invoice will be broken.
*'''FCKEDITOR_ALLOW_ANY_CONTENT''' ► Allow to enter any content. However, this will totally disable content filtering which is one of the most important CKEditor features. You can use this to keep all your tags and attributes in the html content.
*'''FCKEDITOR_ENABLE_SCAYT_AUTOSTARTUP ►''' Allow to activate the SpellCheckAsYouType (SCAYT) plugins of CKEditor i.e an automatic spell checking. The value to activate this option is 1.

[[#Top|(back to top)]]

=STRIPE Module=

*'''STRIPE_FORCE_VERSION''' ► Force the STRIPE version. For Example: "2019-09-09" (v11+)
*'''STRIPE_REUSE_EXISTING_INTENT_IF_FOUND''' ► With this, you will have idempotency key but the payment intention will be reuse and not Generate again (13+)

[[#Top|(back to top)]]

=ClickToDial Module=

*'''CLICKTODIAL_FORCENEWTARGET''' ► Open in new page.

[[#Top|(back to top)]]

 

=For SaaS / Cloud hosting integrators=

The following options are useless for a common usage of Dolibarr. But they are usefull if you plan to host / provide Dolibarr instances as Software As A Service (SAAS) to your customers.

*'''CRON_DISABLE_KEY_CHANGE''' ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*'''CRON_DISABLE_TUTORIAL_CRON''' ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*'''CRON_WARNING_DELAY_HOURS''' ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

*'''MAILING_NO_USING_PHPMAIL''' ► To avoid bad use of the emailing module, it is recommended to set this option to 1 (This option is described previously). Also you can complete the message visible by customers when they try to setup the SMTP credentials of their Dolibarr by using the constant MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS (This option is described previously). For example, you can point to a FAQ on your website.

*'''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► If you have set a system limit on number of recipients on your system, you can set also this option to match the same value, so users will be informed: So '''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' restricts sending of 1 email message to <code>x</code> recipients for the same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include a ton of recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available. Note that this is not a hard limit; it is just the quantity that will be displayed on warnings on screen. For a real limit, this must be implemented into the system.

*'''MAILING_LIMIT_SENDBYDAY''' ► This is a limit of number of emails, an instance can send. Note that this is not a hard limit; it is just the quantity that will be displayed on warnings on screen. For a real limit, this must be implemented into the system.

*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Set this value to a translation key. Then add translation keys into the instance so user will see a message when into the email setup page. For example, you can set a message to say ''Warning: To avoid abuse, when using default setup, you are restricted to 500 emails per day for all your application (account may be suspended in case of violation of this rule. You can setup application to use your own SMTP server for sending email so you want have no restriction at all (see menu Home-Setup-Emails)''

*'''MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE''' ► If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock and remove the upgrade.unlock so the administration tools like install.php, upgrade.php and repair.php can't be used on your customer instance (until the install.lock file is deleted or the upgrade.unlock file is created).

*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option '''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD'''.

*'''MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD''' ► Set here the string to add in the SPF record This string will be shown into a help message when the user in in the setup of email page and has choose a method using an external SMTP server.

*'''MAIN_FIRST_PING_OK_ID''' ► Set this value to "disabled" to remove completely any ping after a complete setup.

*'''MAIN_FILECHECK_LOCAL_SUFFIX''' and '''MAIN_FILECHECK_LOCAL_EXT''' ► If you offer a customized or patched version of Dolibarr, when the user will use the tool to check the integrity of files, the default xml file name used for signature checking will be the official file provided by the Dolibarr team, so it does not includes your own changes. To have the suggested signature file being your own file, you can set the constant MAIN_FILECHECK_LOCAL_SUFFIX to a suffix. For example, set this to "'''-mysaassolution'''". So, when the user will use the file integrity tool, the default file to check for signature will be "'''/install/filelist-10.0.2-mysaassolution.xml'''" instead of "'''/install/filelist-10.0.2.xml'''". All you have to do is generate the signature file '''mysaassolution''' using the tool '''build/generate_filelist_xml.php''' and put this file into the install directory of your customer instance. Doing this, your customer, and yourself, will be able to check if a file was modified without being disturbed by false alerts due to your customized files or patches (they will be included in the signature used for check). Also, if you want to zip the customized signature file into "'''/install/filelist-10.0.2-mysaassolution.xml.zip'''", you can set the constant MAIN_FILECHECK_LOCAL_EXT to '.zip'.

*'''MAIN_HIDE_WARNING_TO_ENCOURAGE_SMTP_SETUP''' ► Set to 1 by default (so warning is hidden). You can set it to 0 to show a warning to encourage admin to set its own SMTP service.

*'''MAIN_MAIL_SENDMODE_password''' ► To force the mode to send the email on the "password forgotten" page. So you can decide to use php mail or SMTP method for this specific use case.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► If set to N, the warning saying modules are not activated will be shown if number of activated module is < N (Having this variable not defined is same than having it set to 1). This may be usefull if you preinstall an application with some modules already loaded by default and you want to keep the warning to be sure the user will enable other modules he need, even if some modules are already enabed.

*'''MAIN_NO_UPGRADE_REDIRECT_ON_LEVEL_3_CHANGE''' ► The page to make the migration is not shown automatically when you deploy files of version X.Y.Z+delta over an installation with a database version X.Y.Z. The upgrade page will be shown automatically only if there is a change on value of X or Y in version.

*'''SYSLOG_DISABLE_LOGHANDLER_SYSLOG''' ► Set this to 1 to disable usage of syslog (having all customer instances logging in the same system file is not a good idea).

*'''WEBSITE_REPLACE_INFO_ABOUT_USAGE_WITH_WEBSERVER''' ► Put here a text or a translation key of a text to show when the user will use the feature "Deploy" when he want to deploy a website done with Dolibarr CMS. So you can, for example, show him a message that this feature is not part of its subscription and putting a website online may need a complementary subscription.

[[#Top|(back to top)]]

Module Factures Clients

2023-09-04T11:43:38Z

Iouston: /* Escompte */ Complétion de ce paragraphe

[[en:Module_Customers_Invoices]]
[[es:Módulo_Facturas_a_clientes]]
[[pt:Módulo_Faturas_de_Clientes]]
[[zh:客户发票模块]]


{{TemplateDocUtil}}
{{TemplateModFR}}
[[Category:Facture]]
{{BasculeDevUser|
nom=Factures|
num=30|
devdoc=[[Module Factures Clients (développeur)]]|
userdoc=Cette page|}}

=Introduction=
Le module Factures Clients permet de saisir, modifier ou créer une facture composée de lignes de factures.
C'est également ce module qui permet de saisir les paiements réalisés sur une facture.
Il inclut également les fonctions de génération d'une facture dans un format de document comme un PDF.

Les factures fournisseurs sont gérées par le [[Module Fournisseurs Factures]].

=Installation=
{{NoInstallModuleFr}}

=Configuration=
{{ActivationModuleFr}}

La page [[Configuration module facture]] vous explique comment configurer le module Facturation et donne quelques exemples de modèles de factures.

=Création de facture=

Dolibarr vous permet d'établir des factures aux clients que vous avez préalablement saisis (voir [[Module Tiers]]).

Vous pouvez créer une facture directement à partir d'une fiche client, depuis une proposition commerciale classée acceptée, ou à partir d'une commande clôturée à l'état "accepté", ou encore depuis un contrat de service.

'''Types de factures'''

Si vous créez une facture depuis une fiche client, vous pouvez choisir 4 types de factures:

*Les factures de "doit"

Il s'agit d'une facture standard.
Il n'y a aucun prérequis.

*Les factures de "doit" de remplacement

Une facture de remplacement permet de refaire une facture sur laquelle il y aurait des erreurs et sur laquelle rien n'aurait été fait (aucun paiement saisi).

On ne peut créer qu'une seule facture de remplacement pour une facture de "doit" donnée. Quand on créé une facture de remplacement R, on choisit la facture de doit F qui doit être remplacée. Il n'est alors plus possible de faire d'actions sur la facture F, bien que cette dernière ne change pas de statut après que la facture de remplacement R ait été créée au statut '''brouillon'''.

Si la facture de remplacement R est supprimée, la facture F reprends son état initial et le cycle de vie de la facture F peut reprendre.

Si la facture de remplacement R est '''validée''', la facture F passe alors au statut '''abandonnée''' automatiquement. Le cycle de vie continue sur la facture R.

*Les factures d'avoir

On crée une facture d'avoir sur une facture de "doit".
On peut créer plusieurs factures d'avoir sur une facture donnée. La facture d'avoir est transformée en réduction qui sert à réduire le paiement de n'importe quelle autre facture en attente de paiement.

*Les factures d'acomptes

Vous pouvez créer autant de facture d'acompte que désiré. Une facture d'acompte sera ensuite convertie en réduction (déjà payé) pour une autre facture (la facture définitive) sur laquelle porte l'acompte.

'''Procédure'''

Une fois une facture créée (en mode ''brouillon''), vous devez intégrer, dans la facture, des Produits ou Services déjà définis dans Dolibarr ou bien dont vous saisissez directement l'intitulé, le taux de TVA, le prix unitaire.
Pour chaque ligne de la facture vous définissez aussi une quantité et éventuellement une remise (pourcentage).

Une fois la facture prête vous devez la valider. Quand vous validez la facture un numéro lui est attribué selon le modèle de numérotation que vous avez choisi dans la configuration du module Facture.
Si une erreur est détectée après avoir validé la facture, vous pouvez modifier la facture en cliquant sur le bouton '''modifier''' en bas de la fiche facture ( si la facture n'a pas atteint le status Payé), ou ré-ouvrir le facture pour la modification avec le bouton '''réouvrir''' en bas de la fiche facture( si la facture a atteint le statut Payé).

'''Règles de calcul de la TVA'''

*Les règles de calculs de la TVA sont expliquées sur la page: [[Règles de calcul et arrondi de TVA]].

'''Timbre fiscal'''

*Certains pays (comme la tunisie) sont soumis à un timbre fiscal (montant d'une taxe fixe pour chaque facture produite). La liste des pays et montants concernés se paramètre dans la [[Table_llx_c_revenuestamp]]. Si le pays de la société fait partie de cette configuration, alors un champ "Timbre fiscal" apparait sur les écrans et documents de facture.

=Réduire le montant total et/ou le solde à payer=
Il est possible de réduire le montant total et/ou le solde à payer d'une facture, mais il convient de faire une distinction entre une remise et une réduction, bien que ces deux termes soient un peu amalgamés par endroits.
==Réduction==
Une '''réduction''' est une réduction relative (pourcentage) du prix de vente d'un ou de plusieurs produits ou services détaillés dans la facture. Cette réduction doit être définie ligne par ligne lors de l'édition de la facture et être comprise entre 0% et 100% (NB : le pourcentage de remise est remplacé dans le cas 100% de réduction par la mention ''offert'').

==Remise==
Une '''remise''' est une réduction du prix total de la facture. Elle peut être définie de deux manières selon qu'elle est ou non associée à une autre facture, c'est-à-dire à un versement déjà perçus ou non.
===Remise associée à un trop perçu===
Les factures d'avoir et factures d'acompte, qui sont saisies pour tracer des versements perçus (en trop pour la facture avoir ou en avance pour l'acompte), peuvent être ''converties en réduction future''. Après conversion en réduction, elles apparaissent dans la section ''Remises fixes'' du tiers. Il sera alors possible de l'attribuer à une autre facture pour en réduire le montant.

Le trop-perçu, lié au règlement d'une facture supérieur au montant de la facture, apparaît également dans les remises.

Lorsque le montant de la remise est supérieur à celui de la facture à régler, depuis la liste des remises, on sépare la remise en deux (bouton à droite de la ligne) avec un premier montant correspondant à la facture, puis le solde. On peut alors utiliser une partie de cette remise pour l'appliquer au règlement de la facture qui peut alors être classer "Réglée".

Dans le cas de l'utilisation d'une remise dans une nouvelle facture, elle sera mentionnée soit sous forme de paiement réduisant le reste à payer, soit sous forme d'une ligne de détail de la facture.
Par défaut, il s'agit d'une ligne de détail ajouté à la facture et donc réduisant le montant total de cette nouvelle facture.

Rem: L'option cachée FACTURE_DEPOSITS_ARE_JUST_PAYMENTS permet d'avoir cette déduction qui apparaît comme montant déjà payé et non comme diminution du montant total de la facture finale. Dans ce cas, les factures acomptes ne sont pas incluses dans les calculs de chiffre d'affaires (puisqu'inclut dans le montant total de la facture finale). Le bon choix de cette option dépendra des règles comptable de votre pays, mais les 2 sont en général acceptés.

===Remise non associée à un versement déjà perçu===
Il est aussi possible de définir une remise qui n'est pas relative à un versement déjà perçu. Dans ce cas, il faut aller sur la fiche du client, onglet ''client'', et définir la ou les remises fixes (montant) ou relatives (pourcentage) qu'on attribue à ce client, et pourquoi (geste commercial, compensation suite à retard de livraison, etc). Une fois ces remises attribuées au client, elles seront disponibles lors de l'édition de n'importe quelle facture de ce client, dans la rubrique '''Remises''' en haut de page. A l'inverse des remises consécutives à des versements déjà perçus, celles-ci seront mentionnées comme des lignes négatives dans le détail de la facture, et réduiront donc le montant total de celle-ci, avant déduction des versements éventuellement déjà perçus. Mais ces remises ne sont PAS associées à une facture avoir ou d'acompte.

==Rabais==
A compléter

==Escompte==
Un escompte est une remise accordée, sur une facture donnée, à un client car ce dernier a réalisé son règlement avant l'échéance. Ce choix est possible si votre facture indique une mention adéquate, par exemple : escompte pour règlement anticipé : 2%. A l'inverse vous pouvez indiquer : Escompte pour règlement anticipé : 0%.

Pour enregistrer un escompte dans dolibarr :

* Saisissez un paiement sur une facture (par exemple 980€ pour une facture de 1000€).
* Une fois le règlement enregistré, cliquez sur le bouton "classez payée partiellement".
* Une fenêtre modale s'ouvre et vous propose plusieurs motifs permettant de justifier le paiement partiel.
* Sélectionnez le choix "Escompte pour règlement anticipé" et valider.
* La facture est désormais passée au statut 'payée partiellement'.
* Après avoir généré le pdf, l'escompte apparait sur le pdf de la facture.

==Résumé==
Il y a donc 3 possibilités pour réduire le prix d'une facture :

*attribuer une '''réduction''' en pourcentage sur certains produits/service détaillés dans la facture, ce qui aura pour effet de définir un '''montant total''' plus bas que normalement prévu;
*attribuer au client une '''remise globale''', non associée à une facture avoir ou d'acompte, et qui sera alors ajoutée comme une ligne de montant négatif qui réduira le '''montant total''' de la facture;
*mentionner, via des '''factures avoir ou d'acompte''' transformées en réduction future, que des versements anticipés ont déjà été perçus, ce qui réduira le '''solde à payer''' mais pas le montant total de la facture;

=Génération PDF, Impression, Envoi=
Lorsqu'un document est généré, il est fabriqué suivant un modèle choisi parmi une liste activée dans les écrans Accueil - Configuration - Modules - Facture

Pour que le document intègre le numéro de compte bancaire de votre société ou l'adresse de paiement par chèque (ou les 2), il convient de :

#activer le module Banques/Caisses
#Créer le compte de votre société
#Paramétrer le module Factures et Avoirs en allant dans '''Configuration - Modules - Factures et Avoirs''' puis cliquer sur l’icône configuration, choisir dans la rubrique "Mode de règlement" le compte créé à l'étape 2 ci-dessus, où l'adresse à utiliser pour le paiement par chèque, et valider le changement en cliquant sur le bouton "Modifier" de la rubrique.

Vous pouvez maintenant régénérer votre facture, et vous verrez, pour le modèle crabe, le RIB ou les coordonnées s'afficher sous les conditions de paiement.

Si vous avez activé l'envoi par e-mail, un bouton spécifique "Envoyer par email" est disponible. Il fait apparaître en bas de la fenêtre un formulaire d'envoi, avec la facture en pièce jointe. Vous pouvez également définir un modèle de rappel pour les factures impayées.

Dans le cas d'une ligne provenant d'un produit ou d'un service enregistré, la référence, le libellé et la description sont affichés par défaut. Si vous souhaitez masquer la référence ou la description, vous pouvez le faire en passant par '''Accueil - Configuration - PDF'''.

Vous avez deux options que vous pouvez modifier :

*Cacher la description des produits sur les PDF générés
*Cacher la référence des produits sur les PDF générés

Ce paramétrage s'applique aussi aux propositions commerciales et aux commandes
==Impression en nombre==
Si vous souhaitez imprimer plusieurs factures en une seule fois, vous pouvez générer un document PDF rassemblant les documents à imprimer, puis ouvrir et imprimer ce document.

Pour cela, à partir de '''Facturation|Paiement - Factures clients - Liste''',

*appliquer un filtre qui vous convient pour faire apparaître toutes les factures à imprimer ensemble,
*cocher globalement (case à cocher en haut de colonne à droite) ou individuellement les documents souhaités,
*'''-- Sélectionner l'action-- - Fusion PDF''' dans la liste déroulante qui apparaît à partir de la coche d'au moins une case, et
*appuyer sur '''Confirmer'''.

Un lien vers un document PDF est ajouté dans une liste qui se trouve sous le tableau (appuyer sur '''Afficher la liste des fichiers générés en masse''' si nécessaire).

=Saisir les paiements=
Les paiements ne peuvent s'effectuer que sur des factures validées.

Si un avoir est disponible, il pourra être imputé sur une facture d'un montant total inférieur à celui de l'avoir.

Après la saisie du paiement, il est possible de régénérer le PDF de la facture pour y faire apparaître le règlement effectué et le solde à payer.

=Clore une facture=

Une facture validée peut être définitivement classée à l'état:

*Payé (Si la somme des paiements est supérieure ou égale au montant réclamé).
*Payé partiellement (Si la somme des paiements est supérieure à 0 mais strictement inférieure au montant réclamé).
*Abandonné (Si aucun paiement n'a eu lieu).

=Exporter les factures=

Dolibarr fournit un outil générique vous permettant d'exporter les données de vos factures.
Pour cela, il faut utiliser l'assistant Export qui se trouve dans le menu '''Outils - Nouvel export''' (Si le [[Module Exports]] a été activé).

Voir la page [[Module Exports]] pour plus d'informations.

=Factures pré-définies=
Dans Dolibarr, une facture désignée comme pré-définie est simplement une facture dont on réutilise la plupart des données pour émettre d'autres factures sur base de ces informations, ce qui permet un gain de temps non-négligeable à la saisie

Dans le cas de la mise en oeuvre des contrats, une facture prédéfinies peut être définie et correspondant aux éléments récurrents du contrat. Ceci est très intéressant.
Le seul bémol, la période indiquée pour chaque élément de la facture résultante couvre toute la période du contrat. Elle ne devrait porter que sur le mois de facturation.

=Videos sur le sujet=

<youtube width="280">MFaXoooysEo</youtube>

Les factures:

<youtube width="280">7BVKHt91jrI</youtube>

Les paiements:

<youtube width="280">ii8kdfa9BxA</youtube>

=Exemples de cas d'utilisations=
==Acomptes==
{{ExamplesCaseFr
|nom=UCIN01: Réception d'un acompte de 10 pour une commande de 100 puis facture finale
|situation=Réception acompte à commande puis facture finale
|actions=Je reçois un règlement d'acompte de mon client.
Je crée '''de zéro''' pour ce client une '''facture d'acompte''' du montant effectivement '''reçu''' de 10 avec, par exemple, le libellé "''Acompte sur prestation/produit/facture/commande/... n° XXXX''".

Je '''convertis''' ensuite cette facture en '''réduction future'''.

La facture de doit, complète, éventuellement créée à partir de la proposition ou de la commande précédente, peut avoir été générée avant ou après, cela est indépendant.

Dans cette facture de doit, j'inclus la réduction de l'acompte, ce qui réduit le reste à payer. La facture de doit se retrouve à un total de 90.

Rem: si l'option cachée FACTURE_DEPOSITS_ARE_JUST_PAYMENTS est définie, elle vaudra 100 mais dans ce cas, les factures acomptes ne seront pas incluses dans le calcul des chiffres d'affaire.

J'envoie ou réenvoie la facture de doit générée qui indique qu'un (ou plusieurs) acompte a déjà été reçu.
}} 

==Facturation et paiements==
{{ExamplesCaseFr
|nom=UCIN02: Facturation et paiement intégral'''
|situation=Je crée une facture.
Je reçois l'intégralité des paiements.
|actions=Je saisis tous les paiement sur la facture. Le solde devient à 0.
Je peux classer la facture à '''Payée'''.
}}

{{ExamplesCaseFr
|nom=UCIN03: Facturation et paiement supérieur reçu
|situation=Je crée une facture.
Je reçois un paiement supérieur au montant réclamé.
|actions=Je saisis le montant reçu.
Je clos la facture à l'état '''Payé'''.
Je crée un avoir du trop perçu.
Rem: L'action reste à étudier car ne semble pas ok: Voir http://www.dolibarr.fr/forum/12-howto--aide/35761-trop-percu/post?do=reply avec proposition de solution.
}}

{{ExamplesCaseFr
|nom=UCIN04: Facturation et paiement intégral puis produit retourné
|situation=Je crée une facture.
Je reçois l'intégralité des paiements. Je les saisis et le solde devient 0.
Je clos la facture à l'état '''Payé'''.
Plus tard, je reçois un retour de produit suite à rétractation légale.
|actions=Je saisis un avoir sur cette facture.
Cet avoir peut etre converti en réduction pour la prochaine facture ou remboursé en monétaire.
}}

{{ExamplesCaseFr
|nom=UCIN05: Facturation et paiement intégral puis erreur détecté sur la ligne produit'''
|situation=Je crée une facture.
Je reçois l'intégralité des paiements. Je les saisis et le solde devient 0.
Je clos la facture à l'état '''Payé'''.
Plus tard, je découvre une erreur de produit.
|actions=Je saisis un avoir sur cette facture qui contient le produit en erreur.
Je convertis cet avoir en réduction.
Je crée une nouvelle facture avec le bon produit. J'intègre l'avoir dans cette nouvelle facture.
Eventuellement si j'utilise le module stock, je corrige le stock en manuel.
}}

{{ExamplesCaseFr
|nom=UCIN06: Facturation et paiement partiel car anticipé (escompte)
|situation=Je crée une facture.
Je reçois un paiement du montant de la facture moins un escompte accordé pour paiement anticipé.
|actions=Je saisis le paiment reçu de la valeur reçue.
Je classe la facture à '''Payé partiellement''' et renseigne le motif "Le manque est un '''Escompte'''".
}}

{{ExamplesCaseFr
|nom=UCIN07: Facturation et paiement partiel ou nul puis retour produit et attente correction anomalie ou erreur infine tolerable'''
|situation=Je crée une facture.
Si je reçois un paiement partiel, je le saisis.
Je reçois un retour d'une partie des produits (retractation du client) ou ne reçois plus les quelques centimes manquant.
Eventuellement, le client attend un avoir pour payer la fin de la facture.
|actions=Je saisis un avoir sur la facture.
J'envoie l'avoir.
Ensuite, je convertis cet avoir en reduction pour le client.
Je saisis eventuellement la suite des paiements reçus.
Eventuellement j'inclus l'avoir dans la liste des paiements de la facture (sinon il pourra être inclu dans une autre facture).
Je classe la facture à l'état '''Payé'''.

'''TODO''' Contrôle a inclure en plus : Quand l'avoir est fait sur une facture au statut 'Réglement commencé', il faut mettre un message disant "Attention, ne créer un avoir sur une facture en cours de paiement que si le client a cessé le paiement et attend cet avoir pour poursuivre la suite ou parce que vous fermez la facture".
Ensuite il faut vérifier que le montant de l'avoir est inférieur au montant de la facture auquel il s'applique - montant déja reçu. Sinon, refuser création avoir.
}}

{{ExamplesCaseFr
|nom=UCIN08: Facturation et paiement partiel car mauvais payeur
|situation=Je crée une facture.
Je reçois un paiement partiel, je le saisis.
Après une longue attente, la suite des paiements n'est pas reçue et j'abandonne tout espoir.
|actions=Je classe la facture à l'état '''Payé partiellement''' et renseigne le motif '''Mauvais payeur'''.
}}

{{ExamplesCaseFr
|nom=UCIN09: Facturation et aucun paiement reçu car mauvais payeur'''
|situation=Je crée une facture.
Après une longue attente, la suite des paiements n'est pas reçu et j'abandonne tout espoir.
|actions=Je classe la facture à l'état '''Abandonnée''' et renseigne le motif '''Mauvais payeur'''.
}} 

==Correction des erreurs de facturation==
{{ExamplesCaseFr
|nom=UCIN00: Erreur sur le contenu de la facture corrigée par facture remplacement
|situation=Je crée une facture.
Je valide.
Je me rend compte de l'erreur sur le contenu (montant, descriptif) après validation (voir use case UCIN10 en cas d'erreur sur client).
|actions=Je classe la facture abandonnée pour motif 'Autre' (opération non obligatoire car automatique avec étape suivante).
Je crée une nouvelle facture en choisissant '''Facture de remplacement''' et en selectionnant la facture remplacée comme facture.
}}

{{ExamplesCaseFr
|nom=UCIN10: Erreur sur le client détecté après validation mais avant paiement
|situation=Je crée une facture.
Je valide.
Je me rend compte que la facture a été crée sur le mauvais client.
|actions=Je classe la facture abandonnée pour motif 'Autre' et je renseigne le motif "Erreur saisie sur mauvais client".
Je crée une nouvelle facture sur le bon client.

'''TODO''': Faire confirmer par expert que possible si c'est fait avant envoi.
Si pas possible, interdire la possibilité et utiliser le cas suivant.
}}

{{ExamplesCaseFr
|nom=UCIN10: Erreur sur le client (ou facture saisie 2 fois) détecté après envoi facture mais avant paiement
|situation=Je crée une facture.
Je valide et l'envoie au client.
Je me rend compte que la facture a été crée sur le mauvais client ou facture en doublon avec une autre deja envoyée.
|actions=Je crée un avoir sur la facture qui n'a pas encore de paiement, du montant inverse exacte.
Je convertit l'avoir en réduction. L'avoir se retrouve ainsi "traité", je peux l'envoyer au client si je le désire.
Je retourne sur la fiche facture en erreur et j'applique la réduction issue de l'avoir.
Le du devient alors zéro et je la classe à '''Payée complètement''' (paiement de 0).
Que le client ait reçu ou non la facture initiale, cette dernière a été annulée et fermé par l'avoir.
Je resaisi la facture sur le bon client.
}}

{{ExamplesCaseFr
|nom=UCIN10: Erreur sur le libellé client détecté après saisie de paiement'''
|situation=Je crée une facture sur le client de libellé X.
Je valide.
Je saisi les paiements.
Je classe la facture payée.
Je me rend compte que la facture a été crée sur le mauvais client et le client me demande une contrefacture sur l'ancien nom X et une nouvelle sur le nouveau nom Y.
|actions=Je crée un avoir sur la facture en erreur avec toutes les lignes en inverse.
Je transforme l'avoir en réduction. L'avoir se retrouve ainsi "traité".
J'édite la fiche client pour corriger le libellé client X par Y.
Je crée la nouvelle facture sur le nouveau client Y en incluant toutes les lignes.
Je la valide.
J'inclut le paiement issue de l'avoir.
Le solde passe alors à 0 (aucun du).
Je peux classer la facture à '''Payée''' sans saisir d'autres réglements (le client a déjà payé).
}} 

==Factures pré-définies==

{{ExamplesCaseFr
|nom=UCRIN01: Création d'une facture pré-définie
|situation=Création d'une facture pré-définie
|actions=Il n'est pas possible de créer une facture récurrente en partant de rien. Il s'agit d'une facture standard de doit que l'on convertie et réutilise par la suite. Voir cas d'utilisation suivant donc.
}}

{{ExamplesCaseFr
|nom=UCRIN02: Transformation d'une facture standard en facture prédéfinie
|situation=Transformation d'une facture standard en facture prédéfinie
|actions=Je crée ou ouvre une facture brouillon. Je clique sur le bouton "Convertir en récurrente". J'entre un titre (par exemple, "Mise-à-jour trimestrielle") et éventuellement une note, qui pourrait être une explication de la raison de la répétition de cette facture. Ma facture est à présent une facture récurrente. Cela ne sera visible que si je demande l'affichage des factures récurrentes ou que je crée une nouvelle facture.
}}

{{ExamplesCaseFr
|nom=UCRIN03: Utilisation d'une facture prédéfinie pour la création d'une nouvelle facture
|situation=Utilisation d'une facture prédéfinie pour la création d'une nouvelle facture
|actions=Je crée une nouvelle facture ("Créer facture"), et j'utilise la boîte de sélection en bas de page pour sélectionner la facture récurrente que je veux utiliser comme gabarit (template). Ma nouvelle facture est pré-remplie, les modifications à apporter sont mineures.
}}

Template:ListOfContexts

2023-04-19T12:23:09Z

Iouston: add userlist

adherents\card.php(111): membercard 
adherents\type.php(73): membertypecard 
categories\categorie.php(96): categorycard 
comm\card.php(72): commcard 
comm\propal.php(99): propalcard 
comm\action\card.php(85): actioncard 
comm\action\index.php(112): agenda 
comm\mailing\card.php(55): mailingcard 
commande\card.php(93): ordercard 
compta\facture.php(105): invoicecard 
compta\paiement.php(70): paiementcard 
compta\deplacement\card.php(50): tripsandexpensescard 
compta\dons\card.php(53): doncard 
compta\localtax\clients.php(172): externalbalance 
compta\salaries\card.php(47): salarycard 
compta\tva\card.php(45): taxvatcard 
contact\card.php(77): contactcard 
contrat\card.php(70): contractcard 
expedition\card.php(85): expeditioncard 
fichinter\card.php(80): interventioncard 
fourn\card.php(54): suppliercard 
fourn\commande\card.php(80): ordersuppliercard 
fourn\commande\orderstoinvoice.php(88): orderstoinvoicesupplier 
fourn\facture\card.php(72): invoicesuppliercard 
fourn\facture\paiement.php(71): paymentsupplier 
livraison\card.php(68): deliverycard 
product\card.php(91): productcard 
product\fournisseurs.php(62): pricesuppliercard 
product\stats\commande.php(45): productstatsorder 
product\stats\commande_fournisseur.php(45): productstatssupplyorder 
product\stats\contrat.php(45): productstatscontract 
product\stats\facture.php(48): productstatsinvoice 
product\stats\facture_fournisseur.php(47): productstatssupplyinvoice 
product\stats\propal.php(45): productstatspropal 
product\stock\card.php(54): warehousecard 
projet\card.php(48): projectcard 
projet\tasks.php(67): projecttaskcard 
resource\card.php(60): resource_card 
resource\element_resource.php(58): element_resource 
societe\agenda.php(41): agendathirdparty 
societe\commerciaux.php(40): salesrepresentativescard 
societe\consumption.php(80): consumptionthirdparty 
societe\info.php(41): infothirdparty 
societe\soc.php(80): thirdpartycard 
user\card.php(93): usercard 
user\list.php(72): userlist 
user\passwordforgotten.php(56): passwordforgottenpage

Système de substitution de variables

2023-03-20T09:24:29Z

Iouston: add __CONTACT_NAME_CUSTOMER__

[[en:Variable_substitution_system]]


{{TemplateDocUtil}}
{{TemplateDocDev}}

Les variables de substitutions sont des mots clés qui peuvent être utilisés à de nombreux endroits dans Dolibarr pour être remplacés ultérieurement.
On s'en sert par exemple dans les modèles d'emails ou de texte de configuration pour qu'un texte soit personnalisé au moment de son affichage ou de son envoi pour les emails.

=Variables de substitution disponibles=

*

{| class="wikitable sortable"
|+
!Variable
!Valeur Affichée
!Note
!Dolibarr Mini
|-
|__USER_SIGNATURE__
|Ma super signature
|Signature de l'utilisateur
|
|-
|__USER_ID__
|1
|ID de l'utilisateur
|
|-
|__USER_LOGIN__
|doli9
|Login de l'utilisateur
|
|-
|__USER_LASTNAME__
|Admin
|Nom de l'utilisateur
|
|-
|__USER_FIRSTNAME__
|Super
|Prénom de l'utilisateur
|
|-
|__USER_FULLNAME__
|SuperAdmin
|Nom complet de l'utilisateur
|
|-
|__USER_SUPERVISOR_ID__
|1
|ID du superviseur
|
|-
|__USER_REMOTE_IP__
|xxx.xxx.xxx.xxx
|IP de l'utilisateur
|
|-
|__MYCOMPANY_NAME__
|Ma petite entreprise
|Nom de l'entreprise
|
|-
|__MYCOMPANY_EMAIL__
|contact@monentreprise.fr
|Adresse email de contact de mon entreprise
|
|-
|__MYCOMPANY_PROFID1__
|12345678
|Id. prof. 1 (TIN)
|
|-
|__MYCOMPANY_PROFID2__
|12345678
|Id. prof. 2 (PAN)
|
|-
|__MYCOMPANY_PROFID3__
|12345678
|Id. prof. 3 (SRVC TAX)
|
|-
|__MYCOMPANY_PROFID4__
|12345678
|Id. prof. 4
|
|-
|__MYCOMPANY_PROFID5__
|12345678
|Id. prof. 5
|
|-
|__MYCOMPANY_PROFID6__
|FR12345678
|Numéro de TVA
|
|-
|__MYCOMPANY_CAPITAL__
|10000
|Capital de mon entreprise
|
|-
|__MYCOMPANY_FULLADDRESS__
|12 rue laurent 75001 Paris France
|Adresse complète de mon entreprise
|
|-
|__MYCOMPANY_ADDRESS__
|12 rue laurent
|Rue et numéro de rue de mon entreprise
|
|-
|__MYCOMPANY_ZIP__
|75001
|Code postale de mon entreprise
|
|-
|__MYCOMPANY_TOWN__
|Paris
|Ville de mon entreprise
|
|-
|__MYCOMPANY_COUNTRY__
|France
|Pays de mon entreprise
|
|-
|__MYCOMPANY_COUNTRY_ID__
|1
|Identifiant du pays de mon entreprise
|
|-
|__MYCOMPANY_CURRENCY_CODE__
|EUR
|Devise principale de mon entreprise
|
|-
|__ID__
|1
|ID de l'object
|
|-
|__REF__
|1234
|Référence de l'objet
|
|-
|__REF_CLIENT__
|1234
|Référence client de l'objet
|
|-
|__REF_SUPPLIER__
|1234
|Référence fournisseur de l'objet
|
|-
|__EXTRAFIELD_XXX__
|?????
|Attribut supplémentaire de l'object (XXX doit être remplacé par le code de l'attribut)
|
|-
|__THIRDPARTY_ID__
|1
|ID du tiers
|
|-
|__THIRDPARTY_NAME__
|MonClient
|Nom du tiers
|
|-
|__THIRDPARTY_NAME_ALIAS__
|MonC
|Alias du tiers
|
|-
|__THIRDPARTY_EMAIL__
|contact@monclient.com
|Adresse email du tiers
|
|-
|__CONTACT_NAME_CUSTOMER__
|civilité prénom nom
|Genre prénom et nom du contact de type 'contact suivi proposition' d'une proposition commerciale
|
|-
|__PROJECT_ID__
|1
|ID du projet de l'objet
|
|-
|__PROJECT_REF__
|1234
|Référence du projet de l'objet
|
|-
|__PROJECT_NAME__
|MonProjet
|Nom du projet de l'objet
|
|-
|__CONTRACT_HIGHEST_PLANNED_START_DATE__
|01/01/2020
|Date la plus tardive prévue pour le démarrage du contrat
|
|-
|__CONTRACT_HIGHEST_PLANNED_START_DATETIME__
|1/1/2020 13h
|Date et heure la plus tardive prévue pour le démarrage du contrat
|
|-
|__CONTRACT_LOWEST_EXPIRATION_DATE__
|01/01/2020
|Date la plus proche pour l'expiration du contrat
|
|-
|__CONTRACT_LOWEST_EXPIRATION_DATETIME__
|1/1/2020 13h
|Date et heure la plus proche pour l'expiration du contrat
|
|-
|__ONLINE_PAYMENT_URL__
|<nowiki>https://mondoli.com/payment</nowiki>
|Adresse du paiement en ligne (si applicable)
|
|-
|__ONLINE_PAYMENT_TEXT_AND_URL__
|Cliquez pour payer
|Texte et adresse du paiement en ligne (si applicable)
|
|-
|__SECUREKEYPAYMENT__
|
|Clé de sécurité pour le paiement (si la clé n'est pas unique par enregistrement)
|
|-
|__SECUREKEYPAYMENT_MEMBER__
|
|Clé de sécurité pour le paiement de l'abonnement d'un membre (une clé par membre)
|
|-
|__SECUREKEYPAYMENT_ORDER__
|
|Clé de sécurité pour le paiement d'une commande
|
|-
|__SECUREKEYPAYMENT_INVOICE__
|
|Clé de sécurité pour le paiement d'une facture
|
|-
|__SECUREKEYPAYMENT_CONTRACTLINE__
|
|Clé de sécurité pour le paiement d'un contrat
|
|-
|__DIRECTDOWNLOAD_URL_PROPOSAL__
|<nowiki>https://mondoli.com/devis.pdf</nowiki>
|URL de téléchargement direct d'un devis
|
|-
|__DIRECTDOWNLOAD_URL_ORDER__
|<nowiki>http://mondoli.com/commande.pdf</nowiki>
|URL de téléchargement direct d'une commande
|
|-
|__DIRECTDOWNLOAD_URL_INVOICE__
|<nowiki>http://mondoli.com/facture.pdf</nowiki>
|URL de téléchargement direct d'une facture. Pour cela, il faut que le paramètre INVOICE_ALLOW_EXTERNAL_DOWNLOAD soit configuré pour permettre de générer le lien.
|
|-
|__SHIPPINGTRACKNUM__
|XXXXX
|Numéro de suivi du colis
|
|-
|__SHIPPINGTRACKNUMURL__
|<nowiki>http://trackingcompagny.com/XXXXX</nowiki>
|URL de suivi du colis
|
|-
|__DATE_YMD__
|01/01/2020
|Date d'aujourd'hui
|
|-
|__DATE_DUE_YMD__
|01/01/2020
|Date d'échéance
|
|-
|__AMOUNT__ ->
|1243,34
|Montant total
|
|-
|__AMOUNT_EXCL_TAX__ -> __AMOUNT_EXCL_TAX__
|1234,45
|Montant total hors taxe
|
|-
|__AMOUNT_VAT__ -> __AMOUNT_VAT__
|123,4
|Montant TVA
|
|-
|__AMOUNT_FORMATED__
|1243,34 €
|Montant total formaté
|
|-
|__AMOUNT_EXCL_TAX_FORMATED__
|1234,45 €
|Montant total hors taxe formaté
|
|-
|__AMOUNT_VAT_FORMATED__ -> __AMOUNT_VAT_FORMATED__
|123,4 €
|Montant TVA formaté
|
|-
|__DAY__
|12
|Jours actuel (chiffre)
|
|-
|__DAY_TEXT__
|Mardi
|Jours actuel (texte)
|
|-
|__DAY_TEXT_SHORT__
|Ma
|Jours actuel en texte abrégé
|
|-
|__DAY_TEXT_MIN__
|M
|Jours actuel en texte en une lettre
|
|-
|__MONTH__
|3
|Mois actuel (chiffre)
|
|-
|__MONTH_TEXT__
|Mars
|Mois actuel (texte)
|
|-
|__MONTH_TEXT_SHORT__
|Ma.
|Mois actuel en texte abrégé
|
|-
|__MONTH_TEXT_MIN__
|M
|Mois actuel en texte en une lettre
|
|-
|__YEAR__
|2020
|Année actuelle
|
|-
|__PREVIOUS_DAY__
|11
|Hier (chiffre)
|
|-
|__PREVIOUS_MONTH__
|2
|Mois précédent (chiffre)
|
|-
|__PREVIOUS_YEAR__
|2019
|Année précédente
|
|-
|__NEXT_DAY__
|13
|Demain (chiffre)
|
|-
|__NEXT_MONTH__
|4
|Mois prochain
|
|-
|__NEXT_YEAR__
|2021
|Année prochaine
|
|-
|__DOL_MAIN_URL_ROOT__
|<nowiki>http://mondolibarr.fr/htdocs</nowiki>
|Adresse de mon dolibarr
|
|-
|__(Clédetraduction)__
|Clé traduite
|N'importe qu'elle clé de traduction
|
|-
|__[constante]__
|Valeure de la constante
|N'importe qu'elle constante
|
|-
|__DATE_DELIVERY__
|21/09/1974
|Date de livraison de la Propal
|V14
|-
|__CONTACT_NAME_XXX__
|Mr T
|XXX est le type de contact défini dans Accueil>configuration>dictionnaires>Types de contacts/adresses (par exemple : __CONTACT_NAME_BILLING__ pour le contact client désigné comme responsable de la facturation sur une facture). Contient Titre+Nom+Prénom
|
|-
|__UNSUBSCRIBE__
|
|Lien de désinscription
|
|}

=Variables de substitution Personnalisées=
Un module peut ajouter ses propres variables de substitutions.
Pour cela, le module doit embarquer un fichier avec le nom '''monmodule/core/substitutions/functions_monmodule.lib.php'''

Setup EMails

2022-10-11T08:29:18Z

Iouston: /* Several smtp logins or servers */ remove link to dolistore multi smtp plugin which don't exist

[[fr:Paramétrage_EMails]]
[[es:Configuración_EMails]]


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

'''Help about screen:''' EMail setup

'''Menu path:''' Home ► Setup ► EMails

The EMails setup screen allows you to setup Dolibarr to send EMails and to test your setup.

=E-Mails setup parameters=
[[File:Emails Setup EN.png|alt=Emails Setup|thumb|Emails Setup]]
This is explanation of all setup parameters:

==Disable globally all emails sendings (test mode or demo)==
Set this to No. If you set to yes (for a demo system for example), no more mail will be sent.

==Send all emails to (instead of real recipients, for test purposes)==
Enter an email address. All the outgoing emails will be sent to that address. For test purpose.

==Suggest emails of employees==
Suggest emails of employees (if defined) into the list of predefined recipient when writing a new email

==Method to send emails==

*The default method is '''PHP mail function'''. This means that Dolibarr use your PHP to send emails. This suppose your PHP setup is complete. If you don't know how to setup PHP for email sending, prefer next method.
*If your email sending server needs authentication, or if you don't have permission or knowledge to setup your PHP, choose the second method: '''SMTP/SMTPS socket library''' (or '''Swift Mailer socket library''' if you fails to make the previous one working with your email provider).

[[File:Warning.png]] WARNING

Some email provider (like Yahoo) does not allow you to send an email from another server than the Yahoo server if the email address used as a sender is a Yahoo email (for example myemail@yahoo.com, myemail@yahoo.fr, ...). If you use the PHPmail method, it means you will use the server of your application to send emails, so some recipients (the one compatible with DMARC protocol), will ask Yahoo if they can accept your email and Yahoo will respond "no" because the server is not a Yahoo server, and some of your Emails may not be received. 
If like Yahoo, your Email provider has this restriction, you must set this setup to choose the other method "SMTP/SMTPS socket library" and enter here the SMTP server and credentials provided
by your Email provider.

==Hostname or ip address of SMTP/SMTPS sending server==
Name or IP address of the server that send mail. It is usually an name like smtp.xxx.zzz provided by your Internet Service Provider.

For example:

*smtp.aol.com
*smtp.free.fr
*smtp.myprovider.com
*smtp.gmail.com (with login/pass of gmail or gmail for works account)
*smtp-relay.gmail.com (with mode relay of gmail for works)

==Port of SMTP/SMTPS sending server==
If the email sending server use the standard port (25), you can let the field empty.

Other examples:

*25 (SMTP standard)
*465 (SMTPS gmail of free Gmail or Gmail Suite)
*25, 465 or 587 (SMTP gmail with the mode relay available with Gmail Suite, depending on setup)

==SMTP Authentification ID==
Visible if you have choose '''SMTP/SMTPS socket library''' as sending method. Put here your login.

==SMTP Authentification Password==
Visible if you have choose '''SMTP/SMTPS socket library''' as sending method. Put here your password.

==Usage of TLS (SSL)==
Some emails servers require encrypted communication (For example the SMTP server of Google smtp.gmail.com. It's SMTPS).

The only method that support this protocol is '''SMTP/SMTPS socket library'''. You must enable cryptography by setting this method if you need such encryption.

Note: SSL functions must be available in your PHP. If not, you probably forget to install the '''openssl''' module of PHP.

Note: There is 2 different types of SMTP secured encoding:

*Sending SMTP protocol inside a crypted stream ('''SSL''' or '''non standard TLS'''). Server is often running on port '''465'''.
*Sending crypted data inside SMTP ('''TLS using STARTTLS'''). Server is often running on port '''587'''.

More information on difference between TLS and STARTTLS here: https://www.fastmail.com/help/technical/ssltlsstarttls.html

==EMail used as sender for automatic emails==
Set here the eMail that will be used by default by Dolibarr as eMail sender, if sender is not explicitly defined.

==Default sender email for manual sending==
You can use User email or Company email

==Email used for error returns emails==
Set an error returns email address (fields 'Errors-To' in emails sent). All the emails that has not been properly received, will be sent back to this address

==Copy (Bcc) all sent emails to==
If you want to have all the Dolibarr outgoing email sent in copy to a general mail address

==Examples for common Mail server setup==

This is some examples of values (for common email providers) to use to setup your emails with the SMTPs method and use the SMTP server of your email provider. Contact your email provider if it is not in this list or if you are not sure of which value to use to ask him the credentials (SMTP server, port, Use of TLS or not).

===Gmail (with login/pass or login/pass of application)===

*SMTP server: smtp.gmail.com
*Port: 465
*SMTP Username: Your Gmail login (xxx@gmail.com or xxx@yourdomain.com)
*SMTP Password: A generated application password (not your GMail password, see later)
*Use TLS (SSL) encrypt: yes
*Use TLS (STARTTLS) encrypt: no

[[File:warning.png]] Because using this SMTPS access need to store a login/pass into the application, this access is classified by Google as a "less secured access". So check that such access is enabled for your Google account: Take a look at your dashboard for parameter: "Access for less secured application" on https://www.google.com/settings/security/lesssecureapps.

You must enable the 2-steps authentication on your Google account. Once done, you must create a dedicated alternative password for your account. This can be done on: https://myaccount.google.com/security, menu "Application password". Create the alternative password. You must then use it instead of your standard Gmail password into setup (the login that is the main email does not change).

[[File:warning.png]] If you have email aliases on your account, be sure to set as login, the main username/email and not the alias.

[[File:warning.png]] Note also that when sending email with google smtps, if the email of sender is not the google email, neither a declared alias, google will replace the "From" visible by the recipient with your default email alias (but the reply to will still be the sender email even if not declared)

Note: With this mode, all sent emails are automatically added into "Sent" folder of the '''main account'''. If your are a Gsuite user with several users/mailboxes, prefer to use the next method.

===Gmail (with mode relay of Gmail with Google Workspace - GSuite)===

*SMTP server: smtp-relay.gmail.com
*Port: 25, 465 or 587
*Use TLS: Depend on relay setup
*Login/Pass: Keep login/pass empty (Choice A). In such case, on your Google console for email, you must set "Allow some IP addresses only" and enter the public IP of your Dolibarr server (see later). Or (choice B) enter your GSuite email account and an "application" password that is not the password of your account but a second password generated from https://myaccount.google.com/security).

Note 1: You must first setup your Google account to relay outgoing email and to set the list of ip of your SMTP clients (https://admin.google.com, Application - GSuite - GMail - Advanced setup - Routing). Then choose "Accept all emails from my domain" or "Accept all", Choose "Enable TLS" and choose "SMTP authentication required" to no (Choice A) or yes (Choice B).

*If you made Choice A, you must also enter the public ip address of the server of your Dolibarr in "Allow some IP addresses only".
*If you made Choice B, you must create an "application password" from https://myaccount.google.com/security and use this one. (2FA needs to be enabled in order to be able to create "application passwords")

Whatever is the choice (A or B), you will never have to enter the password of your Google account when using the GMail relay solution.

Note 2: With this mode, emails sent can also be saved into the "Sent" folder if option "Stock a copy of all emails sent..." is on.

If your are a Gsuite user with several users/mailboxes, this mode is required if you want to have each user having its sent mails automatically stored into its own "Sent" directory of Gmail.

===iCloud===

iCloud does not support SSL/TLS, only TLS with STARTTLS.

Setup would be:

*Server: smtp.mail.me.com
*User name: Your iCloud Mail email address (Do include the domain name—what follows "@" in your iCloud Mail address; if your iCloud Mail email address is "me@icloud.com", for instance, do use "me@icloud.com" as the user name.)
*Password: iCloud Mail SMTP password: Your iCloud Mail password or an app-specific password (with two-step authentication enabled)
*Port: 587
*Use TLS (SSL) encrypt: no
*Use TLS (STARTTLS) encrypt: yes

===Gandi===

Setup would be:

*Server: mail.gandi.net
*User name: Your email address of your Gandi account
*Password: Your password of your Gandi account
*Port: 587
*Use TLS (SSL) encrypt: no
*Use TLS (STARTTLS) encrypt: yes

===Orange===

Setup would be:

*Server: smtp.orange.fr
*User name: Your email address of your Orange account (ex: myname@wanadoo.fr)
*Password: Your password of your Orange account
*Port: 25
*Use TLS (SSL) encrypt: no
*Use TLS (STARTTLS) encrypt: no

===Outlook / Office365 / Exchange server (with login/pass)===

This mode is not compatible with the two factor authentication. It is also called the SMTP AUTH method or Option 1 in this [https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365#option-3-configure-a-connector-to-send-mail-using-microsoft-365-or-office-365-smtp-relay Microsoft Tutorial]. Warning, according to Microsoft doc, this method is limited: It supports only 1 possible sender. Any other accounts will appear as the same sender.

Setup may be:

*Server: smtp.office365.com (Microsoft Office 365, Exchange Server) and smtp-mail.outlook.com
*User name: Your email account
*Password: Your password account (If you enabled the Double Authentication Method, you must create an "Application password" from menu https://account.microsoft.com/security/ -> "More security options" and use it as the password instead of your common password)
*Port: 587
*Use TLS (SSL) encrypt: no
*Use TLS (STARTTLS) encrypt: yes

Note: Outlook and Office365 are the worst platforms we know to manage emails. It is not compliant with most web and emails standard so the setup is often difficult with this platform. Documentation about SMTP credential is also poor. It depends on a lot of parameters saved into your Outlook platform. Ask the parameters to use the SMTP server of your Outlook/Office365 platform to your Outlook/Office365 provider. Only your Outlook/Office365 provider is able to give you those parameters. If you can't contact him, I'm afraid, trying any combination of parameters is the only solution to find the good one with this email platform but the one suggested in this wiki should works in 90% of the cases (note that some other parameters specific to Office365 may also be expected by the platform, ask your Microsoft integrator).

Note: Some users has reported that you may solve trouble in the user/password validation by adding a rule in Office365 to accept SMTP e-mail without authentication keeping a restriction on the IP address of the server hosting your Dolibarr application.

===Outlook / Office365 / Exchange server (with mode relay)===

This method needs a complex Microsoft Office365 setup (creation of a "Microsoft SMTP Connector"). Also, with this method, Office365 is not able to keep the email sent into the directory "Sent" of the user that send the email. This is a serious limitation for companies with several mailboxes. We recommend using another email provider if you need this (for example gmail that has not this limit).
This mode is compatible with the two factor authentication. More information available on Option 3 variante 2 of this [https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365#option-3-configure-a-connector-to-send-mail-using-microsoft-365-or-office-365-smtp-relay Microsoft Tutorial]

Setup may be (see however note after):

*Server: yourdomainname.mail.protection.outlook.com
*User name: Keep empty
*Password: Keep empty
*Port: 25
*Use TLS (SSL) encrypt: no
*Use TLS (STARTTLS) encrypt: no or yes

Note: You must add a rule in office365 to accept SMTP e-mail without authentication but with a restriction on the IP address of the server hosting your Dolibarr application.

===OVH===
Setup would be:

*Server: exX.mail.ovh.net (ask OVH to know value of X)
*User name: Your email
*Password: Your email password (not your OVH account password)
*Port: 587
*Use TLS (SSL) encrypt: no
*Use TLS (STARTTLS) encrypt: yes

Some uses also succeed with:

*Server: sslX.ovh.net (ask OVH to know value of X)
*User name: Your email
*Password: Your email password (not your OVH account password)
*Port: 465
*Use TLS (SSL) encrypt: yes
*Use TLS (STARTTLS) encrypt: no

===SendGrid===

Setup would be:

*Server: smtp.sendgrid.net
*User name: Your SendGrid api key
*Password: Your SendGrid api pass
*Port: 2525
*Use TLS (SSL) encrypt: no
*Use TLS (STARTTLS) encrypt: yes

===Yahoo (with login/pass)===

*SMTP server: smtp.mail.yahoo.com
*Port: 465
*SMTP Username: Your Yahoo login (xxx@yahoo.com)
*SMTP Password: The alternative application password, see later
*Use TLS (SSL) encrypt: yes
*Use TLS (STARTTLS) encrypt: no

[[File:warning.png]] Because using this smtps access need to store your login/pass into application, this access is classified by Yahoo as a "less secured access".

You need to create a dedicated password for the application : on Yahoo go on "Personal Information"->"Account Security"->"Manage application passwords".

In the list, select an application of your choice for Dolibarr, for exempel "Android Mail" then click on "generate"
In the new window that opens copy the password and paste it on the Dolibarr Email setup

===Several smtp logins or servers===
At this time there is nos solution for that.

Note that in most cases, even if each user has its own email address and its own mailbox and "Sent" directory, using several SMTP login/servers is not required (see for example the comment for Gmail setup using the "relay" mode).

=Actions=
==Test server availability==
This button is to test if you can communicate with the server. This allow you validate the parameter:

*Hostname or ip address of SMTP/SMTPS sending server
*Port of SMTP/SMTPS sending server
*Usage of TLS (SSL)

==Test send email==
This button is to test what happens when you send an email with simple text content.

==Test send email HTML==
This button is to test what happens when you send an email with HTML content.

==SPAM troubles==
If your email is set as SPAM by your EMail reader, you can test to send en email to this service to get more information why your email is set as SPAM: https://www.mail-tester.com/

=Outgoing email setup (for module EMailing)=
This tab allows you to change the email setting of the Mass EMailing module. By default, it uses the same settings defined in the previous tab.

=Email templates=
[[File:Email Template Setup EN.png|alt=Email Template Setup |thumb|Email Template Setup ]]
This tab allows you to create email template that will be proposed on specific modules or globally.
You can either create new template or modify existing templates.

==Create an email template==
To create an email template, you have several fields to fill :

*Code of the template : Code is free to define
*Language : Language of the template
*Type of template : Email template can be dedicated to modules or visible globally
*Owner of the template
*Private : If set to private, only the owner will see the template
*Position : Position of the template on the list (1 being the top position)
*Subject of the email : [[Variable substitution system]] can be used
*Attach file : If the email is sent from a screen where a document is available, the document will be immediately added to mail if you enter "1".
*Content of the email : [[Variable substitution system]] can be used

==Modify an existing email template==
On the email template list, you can :

*See the resume of the template
*Activate or deactivate the template by clicking on the Status column
*Modify the template by clicking on the pencil icon
*Delete the template by clicking on the garbage icon

=Emails sender profiles=
You can keep this section empty. If you enter some emails here, they will be added to the list of possible senders into the combobox when your write a new email.

=Emails Tracking=
Like most modern ERP and email clients, all emails sent by Dolibarr contains a header line "Reference" with a tracking information to know from which source element the email were sent. This tracking informations will also be present into the emails answer, but only if the reader has sent the answer using the "Reply / Answer" feature of its email reader and not by creating a new email from scratch of course.
This tracking id can be used by the [[Module EMail Collector]] that scan your mailbox and can automatically store the answer or email sent as en event, lead, ticket or candidature in your Dolibarr, at the good place (so it is automatically linked to the related customer and/or quotation for example).

Setup Other

2022-07-25T11:34:09Z

Iouston: MAIN_COUNTRIES_IN_EEC - ad a precision

[[fr:Paramétrage_Divers]]
[[es:Configuración_Varios]]
[[de:Erweiterte_Einstellungen]]
[[zh:其他设置]]


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

'''Help About Screen''': Other setup

'''Menu Path''': Home ► Setup ► Other

'''Introduction'''

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

{{warning|32px}} This page contains the list of some advanced development parameters. In most cases, it is parameters for internal usage, development, external modules, features in development not stable or that may lead to security risk. For standard usage of Dolibarr, such parameters '''SHOULD NOT''' be used. All experimental options are NOT supported. They may be removed in a future, modified at any version and break stability of your application.

To enable/override a parameter you have to define the constant name and set it to 1 (unless otherwise stated) in <code>Home ► Setup ► Other Setup</code>

The options here may not be documented since they are not stable and unsupported (remember they are experimental or development options). The basic format of how the list is written is broken down in the example below:

HIDDEN_CONFIG ► ''Description of config and goal'' ► ''(specific version information) or values''
<center>
__TOC__
</center>
=Global Options=

*'''ADD_UNSPLASH_LOGIN_BACKGROUND''' ► The background image will be refreshed on every login page refresh. Background image is pulled from the popular open source image website Unsplash. If an already saved static background image exists, then this code will override it (but not delete the saved image). Warning: Using this may allow this external website to steel your login credentials ► (v10.0)

*'''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 fail by smartphone applications like [[Application Android - DoliDroid]] breaking some features when using Dolibarr from this application.

*'''MAIN_AUTOFILL_DATE''' ► If this constant is defined (to something other than <code>0</code>), the date of invoice, proposal, order or payment are auto-filled with the current date. It is highly recommended to NOT ENABLE this feature. This can create a lot of input errors with data not validated by users. This leads to incorrect values saved in the database causing confusion when you have to do your accountancy reports!

*'''MAIN_AUTO_TIMESTAMP_IN_PUBLIC_NOTES''' ► Add a timestamp and user automatically when editing the ''public'' note.

*'''MAIN_AUTO_TIMESTAMP_IN_PRIVATE_NOTES''' ► Add a timestamp and user automatically when editing the ''private'' note.

*'''MAIN_COUNTRIES_IN_EEC''' ► Country list in European Area (For VAT purpose) ► (v10.0-v13.0). From v14, do not use this anymore (remove the constant if you set it and instead set if the country is in Europe or not from the DB for V14 - V15 and from dictionary of countries in V16 and more).

*'''MAIN_DEFAULT_PAYMENT_TERM_ID''' ► With ID of a payment term, will use this as default payment term each time you create a new proposal, order, invoice (customer and supplier)
*'''MAIN_DEFAULT_PAYMENT_TYPE_ID''' ► With ID of a payment type, will use this as default payment type each time you create a new proposal, order, invoice (customer and supplier) ► (v12.0)

*'''MAIN_DEFAULT_LANGUAGE_FILTER''' ► Useful if you do not want to show <code>en_US</code> language option in combo boxes (other languages can easily be removed in <code>langs</code> directory but not <code>en_US</code>) ► (v10.0)

*'''MAIN_LANGUAGES_ALLOWED''' ► Is a list of languages without spaces, example : <code>fr_FR,en_US,de_DE,it_IT</code> If defined, only those languages will appear in combos. ► (v11.0)

*'''MAIN_DISABLE_NOTES_TAB''' ► Show or hide notes tab in the card page

*'''MAIN_DISABLE_CONTACTS_TAB''' ► Show or hide contacts tab in the card page

*'''MAIN_DISABLE_FULL_SCANLIST''' ► Disables the complete scan of tables to allow the pagination to show total number of pages. May be useful to activate on systems with a very high quantity of data (tables with more than 2 000 000 records).

*'''MAIN_DISABLE_JQUERY_JNOTIFY''' ► Disable usage of <code>JNotify</code> to show confirm or error messages

*'''MAIN_DISABLE_AJAX_COMBOX''' ► If you have a large number of third parties or products, you can disable the autocomplete feature on the third parties list by setting this constant to <code>1</code> ► (v3.6.0+)
*'''MAIN_DISABLE_MULTIPLE_FILEUPLOAD''' ► Disable users to upload multiple files at once.
*'''MAIN_DISABLE_TRUNC''' ► Disable all truncings in select list. ► (v7.0+)

*'''MAIN_DISABLEDRAFTSTATUS''' ► Disable the status "Draft" for some objects (project, donation, ...) so the object is directly created with status "Validated"

*'''MAIN_DOC_USE_OBJECT_THIRDPARTY_NAME''' ► Add name of thirdparty at begin of generated document.

*'''MAIN_DOC_USE_TIMING''' ► Add a timestamp at end of generated document. Value must be format of timestamp. For example: <code>%Y%m%d%H%M</code> (only for ODT files)

*'''MAIN_DOC_UPLOAD_NOT_RENAME_BY_DEFAULT''' ► Disable the auto renaming on upload file ► (v10.0)

*'''MAIN_DOL_SCRIPTS_ROOT''' ► Define directory who contains 'scripts' directory (e.g. <code>/var/www/dolibarr</code>). Value of this variable may be requested by some external script or tools.

*'''MAIN_ENABLE_LOG_TO_HTML''' ► If this constant is defined, it is possible to have logs inside pages by adding the parameter <code>&logtohtml=1</code> into URL.

*'''MAIN_ENABLE_IMPORT_LINKED_OBJECT_LINES''' ► Allow to import lines into current document from "linked" compatible documents ► (v8.0+)

*'''MAIN_FIRST_TO_UPPER''' ► Dolibarr add uppercase to Third Parties, 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_ALL_TO_UPPER''' ► Dolibarr puts uppercase for Third Parties, 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. ► (v11.0)

*'''MAIN_ALL_TOWN_TO_UPPER''' ► Dolibarr puts uppercase for town names if not done. ► (v13.0)

*'''MAIN_FILESYSTEM_ENCODING''' ► With some PHP versions, PHP is not able to detect the page code for filesystem of the server OS. To solve this, Dolibarr assumes your OS filesystem is <code>UTF-8</code> if on Linux or OSX system, and <code>ISO-8859-1</code> if on Windows. If not, for example on a Windows server with a NTFS <code>UTF-8</code> pagecode, you can set the variable <code>MAIN_FILESYSTEM_ENCODING</code> to "<code>utf-8</code>".

*'''MAIN_FORCELANGDIR''' ► Relative path of the directory holding your custom <code>langs</code> folder.

*'''MAIN_HTML_TITLE''' ► Can be used to control how the html page title is formatted. If value contains key '<code>noapp</code>', application name will not be output. If value contains '<code>thirdpartynameonly</code>', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: '<code>noapp;thirdpartynameonly</code>'

*'''MAIN_HELPCENTER_LINKTOUSE''' ► Define the URL link to use as the target page for link "I need help" onto logon page

*'''MAIN_LANDING_PAGE''' ► Can choose the first page to show after login (the landing page). This option works as a global option (<code>llx_const</code>) and per user option (<code>llx_user_param</code>). ► (v3.9+)

*'''MAIN_LOGOUT_GOTO_URL''' ► URL to which the user will be redirected after LOGOUT

*'''MAIN_MAXTABS_IN_CARD''' ► Maximum number of tabs visible. Others are grouped into a combo list.

*'''MAIN_MAXLIST_OVERLOAD''' ► Maximum number of line in space's domain.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► A warning saying setup of modules is not complete is shown if the number of enabled modules is lower or equal than this value (<code>1</code> if not defined)

*'''MAIN_NO_CONCAT_DESCRIPTION''' ► Allow to use only input custom description in lines (propale, order, invoice) ► (v10.0)

*'''MAIN_ONLY_LOGIN_ALLOWED''' ► Only the specified login is allowed to log in Dolibarr (maintenance mode).

*'''MAIN_OPTIMIZE_SPEED''' ► Use some speed enhancements. See page [[FAQ Increase Performance]] for more information.

*'''MAIN_PROPAGATE_CONTACTS_FROM_ORIGIN''' ► When creating an order, contract, invoice from another object, specific contacts of objects are set as specific contact of the new object when possible. ► (v4.0+)

*'''MAIN_PUBLIC_NOTE_IN_ADDRESS''' ► Show public note in address block ► (v4.0+)

*'''MAIN_REMOVE_INSTALL_WARNING''' ► Remove all security warnings that appear to administrator users if URL <code>/install</code> is public. You should solve the problem if warning occurs, instead of removing the warning! For this, create a file called <code>install.lock</code> into Dolibarr root directory. This will stop the warning but also make the page <code>/install</code> not possible to use, to protect your installation.

*'''MAIN_REPEATCONTACTONEACHTAB''' ► If added and set to <code>1</code>, this adds contacts on all tabs, not only main tab.

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

*'''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND''' ► Change way of rounding total TTC lines, rounding first of after.

*'''MAIN_SERVER_TZ''' ► If you can't set the timezone of your PHP installation, set this constant. Better is to set it to UTC. In future, this constant will be forced to '<code>UTC</code>' so PHP server timezone will not have effect anymore. Examples: <code>Europe/Paris</code>, <code>auto</code>.

*'''MAIN_SEARCH_FORM_ON_HOME_AREAS''' ► Show the search form on home page areas for core modules (Removed after v5 due to global search combo) ► (v6.0+)

*'''MAIN_SEARCHFORM_SUPPLIER_INVOICE_DISABLED''' ► Disable the supplier invoice on the search form

*'''MAIN_SEARCH_DIRECT_OPEN_IF_ONLY_ONE''' ► If only one result is found, then setting this value to <code>1</code> will take you direct to the item (default method). Setting the value to <code>0</code> will show the result in the list as a single result ► (v5.0+)

*'''MAIN_SERVICES_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country.

*'''MAIN_SHOW_TUNING_INFO''' ► Add tuning information into javascript console. Better when xdebug is enabled.

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show also technical IDs on elements cards or some lists (not supported everywhere).

*'''MAIN_SHOWDATABASENAMEINHELPPAGESLINK''' ► Show database name in upper help menu ► (v8.0+)

*'''MAIN_USE_ALTERNATE_TRANSLATION_FOR''' ► List of fields per object that need an alternate translation. Example: <code>MAIN_USE_ALTERNATE_TRANSLATION_FOR=societe:name,town;contact:firstname,lastname</code>

*'''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_USE_JQUERY_JEDITABLE''' ► Allow to update from screen, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this feature, because it bypasses some business actions (updates on other data that should be done consistently) and ignores business controls on data you saved. Consequently this feature breaks consistency of data and possibly the stability of the 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_USE_OLD_SEARCH_FORM''' ► Display the old search form in left menu.

*'''MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS''' ► Allow to force the VAT rate to a given value (instead of higher VAT rate of country) if the VAT rate of product was not defined.

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► If the buyer is a company that is in Europe but has no valid intracommunautary VAT ID, it is processed like if it is an individual, not a company. TODO: Must be implemented into accountancy module too instead of being set to <code>1</code> systematically into accountancy module.

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_INDIVIDUAL_CUSTOMER_OUT_OF_EEC''' ► For to use the default VAT of product for individual customers that are out E.E.C. (European Economic Community) ► (v7.0+). ''There is no reason to use this.''

*'''MAIN_VIEW_LINE_NUMBER''' ► Shows a line number for each line of products/services at documents like proposal / order / invoice. Only on screen, not on PDF.

*'''MAIN_VIEW_LINE_NUMBER_IN_LIST''' ► Shows a line number in lists ► (v12.0)

*'''MAIN_VOLUME_DEFAULT_ROUND''' ► Accuracy of volume (number of decimals)

*'''MAIN_VOLUME_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''MAIN_WEIGHT_DEFAULT_ROUND''' ► Accuracy of weight (number of decimals)

*'''MAIN_WEIGHT_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''USER_HIDE_INACTIVE_IN_COMBOBOX''' ► Disable display inactive users in combobox.

*'''MAIN_DISABLE_PDF_THUMBS''' ► Disable thumbs PDF in case of imagick bug

*'''MAIN_KEEP_REF_CUSTOMER_ON_CLONING''' ► Keep the Customer Reference on cloned object (Propal/Invoice)

*'''MAIN_DONT_KEEP_NOTE_ON_CLONING''' ► Remove the object notes during cloning ► (v11.0)

*'''MAIN_DOC_SORT_FIELD''' ► Set the default sorting field on document page (name by default) ► (v11.0)

*'''MAIN_DOC_SORT_ORDER''' ► Set the default sorting order (ASC or DESC) on document page (ASC by default) ► (v11.0)

*'''MAIN_USE_ZIPTOWN_DICTIONNARY''' ► Use dictionary ZIP for create card.

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Show search in top menu with theme eldy ► (v11.0)

*'''MAIN_PHONE_SEPAR''' ► Separ phone number other space ► (v12.0)

*'''GRAPH_USE_FISCAL_YEAR''' ► Widgets uses fiscal year

*'''SHOW_SOCINFO_ON_PRINT''' ► Permit to add user company information on each printed document (when click on Dolibarr print button) ► (v12.0)

*'''MAIN_FEATURES_LEVEL''' ► Level of features to show: <code>-1=stable+deprecated</code>, <code>0=stable only (default)</code>, <code>1=stable+experimental</code>, <code>2=stable+experimental+development</code>

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show technical id for object.

*'''MAIN_HTTP_CONTENT_SECURITY_POLICY''' ► Allows you to fill in the content security rules ► (v6.0)

*'''SOCIETE_ON_SEARCH_AND_LIST_GO_ON_CUSTOMER_OR_SUPPLIER_CARD''' ► Allow to change the link of the third party to customer/supplier card instead of contact card on List.

*'''MAIN_MODULE_SETUP_ON_LIST_BY_DEFAULT''' ► If set to "common" the setup module becomes list by defaut

*'''MAIN_PAGESIZE_CHOICES''' ► Configure select field to choose number of lines displayed on listing (<code>10:10,15:15,20:20,30:30,40:40,50:50,100:100,250:250,500:500,1000:1000,5000:5000</code>).

*'''MAIN_USE_TOP_MENU_QUICKADD_DROPDOWN''' ► Add a dropdown menu with shortcuts to create new objects ► (v13.0)

*'''MAIN_EMAILCOLLECTOR_MAIL_WITHOUT_HEADER''' ► Remove the header stored by email collector ► (v13.0)

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID'''

*'''MAIN_OPTIMIZEFORTEXTBROWSER''' ► Optimise interface for a text only browser. This variable is set to 1 automatically if your browser is lynx or links

*'''MAIN_NB_OF_YEAR_IN_WIDGET_GRAPH''' ► Set the number of years visible on some graph of some widgets (2 is default value)

*'''MAIN_CREATEFROM_KEEP_LINE_ORIGIN_INFORMATION'''

*'''API_DISABLE_LOGIN_API''' ►(v14.0)

*'''MAIN_LOGIN_BADCHARUNAUTHORIZED''' ► Add possibility to define bad character unauthorized into login name REGEX expression (Default value is @<>"\') ► (v16.0)
*'''MAIN_SHOW_ALL_FILES_ON_DOCUMENT_TOOLTIP ►''' Add all files visible from the object to be visible from the list of object.

=Security Options=

*MAIN_SECURITY_ANTI_SSRF_SERVER_IP ► Can set a complete list of IPs of server.

*MAIN_SECURITY_CSRF_WITH_TOKEN ► Activate a second anti-CSRF protection on POST (so 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 more powerful. ► (v5.0+)

*MAIN_MODULES_FOR_EXTERNAL ► Limit available modules for external users. By default value is '<code>facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda</code>'

*MAIN_ALLOW_SVG_FILES_AS_IMAGES ► Allow to use SVG file as image files. Warning: This may introduce security vulnerability (javascript can be embedded into SVG file).

*MAIN_RESTRICTHTML_ONLY_VALID_HTML ► Refused parameter if value is not a valid HTML content.

*MAIN_RESTRICTHTML_REMOVE_ALSO_BAD_ATTRIBUTES ► Sanitize also non standard attributes on HTML content.

[[#Top|(back to top)]]

=Accountancy Module=

*ACCOUNTANCY_COMBO_FOR_AUX ► Add graphic option for ACCOUNTANCY_COMBO_FOR_AUX. Having this option on may slow down and even freeze the accounting features if you have a very large number of thirdparties ► (v10.0)
*ACCOUNTING_DEFAULT_NOT_NOTIFIED_VALIDATION_DATE ► Avoid validating the lines with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v14.0)
*ACCOUNTING_DEFAULT_NOTIFIED_EXPORT_DATE ► Avoid flaging the lines as exported with the accountancy export.(1= box unchecked by default / 0 = box checked by default) ► (v15.0)

[[#Top|(back to top)]]

=Agenda Module=

*AGENDA_ALL_CALENDARS ► Change the default view of calendar pages to see all the Agenda's (instead or yours only be default)

*AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS ► To automatically set end date of event to start date + delta on event creation page.

*AGENDA_DISABLE_LOCATION ► Disable location field in action card ► (>=v5.0)

*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''''').

*MAIN_ADD_EVENT_ON_ELEMENT_CARD ► Allow to create an event from a document (proposal, order, invoice)

*AGENDA_SUPPORT_PRIORITY_IN_EVENTS ► Allow to have priorities in events ► (>=v13.0)

[[#Top|(back to top)]]

=Bank Module=

*BANK_CAN_RECONCILIATE_CASHACCOUNT ► Can reconciliate cash accounts ► (v3.8)

*BANK_DISABLE_CHECK_DEPOSIT ► Disable check deposit feature

*BANK_ASK_PAYMENT_BANK_DURING_ORDER ► Ask bank account during creation of an order

*BANK_ASK_PAYMENT_BANK_DURING_PROPOSAL ► Ask bank account during creation of a proposal

*BANK_USE_OLD_VARIOUS_PAYMENT ► To allow to enter miscellaneous payments (not covered by other modules) using old method. '''''Deprecated'''''. Entering various payment is preferred ► (<=v12.0).
*MAIN_IBAN_IS_NEVER_MANDATORY ► IBAN and BIC informations not mandatory. (V15)

[[#Top|(back to top)]]

 

=BOM and MO Module=

*ALLOW_USE_KITS_INTO_BOM_AND_MO
*BOM_SUB_BOM ►Allow to add a BOM in another BOM►(v16.0)

[[#Top|(back to top)]]

 

=Inalterable Log Module=

*BLOCKEDLOG_ADD_ACTIONS_SUPPORTED ► Can complete list of triggered action that are logged

[[#Top|(back to top)]]

 

=Contracts=

*CONTRACT_SUPPORT_PRODUCTS ► Products are also suggested into module contract.
*
*CONTRACT_ALLOW_EXTERNAL_DOWNLOAD

[[#Top|(back to top)]]

=Cron module=

*CRON_DISABLE_KEY_CHANGE ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*CRON_DISABLE_TUTORIAL_CRON ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*CRON_WARNING_DELAY_HOURS ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

[[#Top|(back to top)]]

 

=Direct Debit Orders=

*WITHDRAWAL_ALLOW_ANY_INVOICE_STATUS ► If this option is set, all invoices status (even already paid) may appear on the list of invoices qualified for a direct debit payment. This is the list of invoices with a payment request done, and not linked to a direct debit payment. By default, only "unpayed" invoices are used to avoid to pay twice the same invoice.

[[#Top|(back to top)]]

=Donation Module=

*DONATION_USE_THIRDPARTIES ► If this option is set, a thirdparty field appear on donation forms.

[[#Top|(back to top)]]
=Email and SMS=

*MAIN_MAILFORM_DISABLE_ENTERKEY ► Activate javascript code to disable the enter key in the MAIL form. ► (>= 8.0.1)

*MAIL_PREFIX_FOR_EMAIL_ID ► Prefix for the mails ID. Default value is <code>$_SERVER["SERVER_NAME"]</code> ► (>= 8.0.1)

*MAIN_MAIL_DEBUG ► Write content with header of last mail into file <code>dolibarr_mail.log</code> into directory <code>dolibarr_main_data_root</code>.

*MAIN_SMS_DEBUG ► Write content of SMS sent into file <code>dolibarr_sms.log</code> into directory <code>dolibarr_main_data_root</code>.

*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 <code>-f</code>. This option is here to ask Dolibarr to call the function mail of PHP by adding value for the option <code>-f</code>. 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 Linux 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 asks PHP to provide this parameter when sending a mail. Note that another solution is to edit the mail.force_extra_parameters=-ba into <code>php.ini</code> 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 <code>orange.fr</code> or <code>hotmail.com</code>

*MAIN_MAIL_DO_NOT_USE_SIGN ► Do not add user signature at end of suggested pre-defined email

*MAIL_FORCE_DELIVERY_RECEIPT_INVOICE ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Invoice'' module.

*MAIL_FORCE_DELIVERY_RECEIPT_ORDER ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Order'' module.

*MAIL_FORCE_DELIVERY_RECEIPT_PROPAL ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Proposal'' module.
*MAIL_FORCE_DELIVERY_RECEIPT_SUPPLIER_PROPOSAL ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Supplier Proposal'' module.

*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 recipient 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 third party 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 third party or object, the email exchange is related to.

*MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL ► Restrict sending of 1 email message to <code>x</code> recipients for same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include 1000 recipients in 1 message. Note that MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL, MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL and MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL are also available.

*MAIN_MAIL_FORCE_CONTENT_TYPE_TO_HTML ► Force to send all email (event with text only content) as HTML formatted email.

*MAIN_MAIL_USE_MULTI_PART ► Forge email content using an alternate text part ► (for 5.0.2+). By default with 6.0+
*MAIN_INFO_SOCIETE_MAIL_ALIASES ► add address aliases for the from field on mail. Set his value with "Firstname Name <firstname.lastname@mydomain.tld, Otherfirstname OtherlastName <othermail@mydomain.tld>,..." ► (v5.0.0+)

*MAIN_MAIL_ADD_INLINE_IMAGES_IF_IN_MEDIAS ► If images were stored into the medias directory from CKEditor, then images into emails are replaced with "inline content". This may increase seriously risk of being detected as SPAM.

*MAIN_COPY_FILE_IN_EVENT_AUTO ► Add attachement document on event auto generated by sending email from dolibarr. ► (v6.0+)

*MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD.

*MAIN_MAIL_ENABLED_USER_DEST_SELECT ► Show also internal users into list of recipients of email in email sending form ► (v8.0+)
*

[[#Top|(back to top)]]

 

=Emailing Module=

*MAILING_PREFIX_FOR_EMAIL_ID ► Set the value that will be used to compose the "Email ID" into email headers. If you set this value to '<code>SERVER_NAME</code>', the virtual host of web server will be used. By default, this is not defined, so a hash key, unique to each instance, is used.

*MAILING_NO_USING_PHPMAIL ► If set, the module emailing can't be used with mail setup of "phpmail". Using a thirdparty SMTP server is required. You can complete warning message by adding an email to contact for setup help with constant <code>MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS</code>.

*MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS ► Contains the email of contact to show into the message visible to a user when he try to use emailing module without SMTP server and if option MAILING_NO_USING_PHPMAIL is set to on.

*MAILING_LIMIT_WARNING_PHPMAIL ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is on "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.

*MAILING_LIMIT_WARNING_NOPHPMAIL ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is something else than "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.
*EMAILING_USE_ADVANCED_SELECTOR ► Enable the advanced selector for recipients.

*MAILING_LIMIT_SENDBYWEB ► Restrict number of emails you can send in same sending session with emailing module from GUI. The value "<code>dolibarr_mailing_limit_sendbyweb</code>" if defined into config file is used in priority for this limit. A negative value means, sending by web is forbidden.

*MAILING_LIMIT_SENDBYCLI ► Restrict number of emails you can send in same sending session with emailing module from CLI script. The value "<code>dolibarr_mailing_limit_sendbycli</code>" if defined into config file is used in priority for this limit.

[[#Top|(back to top)]]

 

=Expense Report=

*EXPENSEREPORT_ALLOW_OVERLAPPING_PERIODS ► Can enter several expense reports on same or overlapping date periods. ► (v7.0+)

*EXPENSEREPORT_OVERRIDE_VAT ► Setting this constant to 1 will allow expense reports to show VAT even if the global VAT setting is off ► (v10.0)

*EXPENSEREPORT_USE_OLD_NUMBERING_RULE ► The module Expense Report use numbering rules that you can setup (like other modules do). If you need to keep the hard-coded numbering rule of expenses report used in v6.0 set this constant to 1 ► (>=v7.0+)

*MAIN_USE_EXPENSE_IK ► This feature allows you to set index kilometers against a mileage index for different types of vehicles. ► (v7.0+)

*MAIN_USE_EXPENSE_RULE ► This feature allows you to set a variety of rules per user/group/all so they can only create reports within their limits. ► (v7.0+)

[[#Top|(back to top)]]

 

=Export Module=

*EXPORT_CSV_SEPARATOR_TO_USE ► String value to use as default separator to delimit fields of exported files (by default Dolibarr uses "<code>,</code>"). Example: EXPORT_CSV_SEPARATOR_TO_USE=<code>;</code>

*EXPORT_CSV_FORCE_CHARSET ► Choose the charset used in the output file built by the CSV exporter. By default it is ISO-8859-1. Example: EXPORT_CSV_FORCE_CHARSET= <code>utf-8</code>

*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 (<code>"</code>).
*EXPORTS_SHARE_MODELS ► Share export models between users.

[[#Top|(back to top)]]

=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 added in front of payment cell, into the page to make online subscription.

[[#Top|(back to top)]]

=Interventions Module=

*FICHINTER_CLASSIFY_BILLED► Allow to classify an intervention card as "Billed". This add also trigger <code>FICHINTER_CLASSIFY_BILLED</code> into list of possible automatic event into agenda.

*FICHINTER_DISABLE_DETAILS► Disable entry of details line on intervention. Can validate with no line.

[[#Top|(back to top)]]

=Invoice Module=

*MAIN_DEPOSIT_MULTI_TVA ► In deposits invoice, creates one line per VAT rate from the origin document ► (6.0)

*INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED* ► If a credit note was partially refunded (a refund was sent to the customer), with common situation, we wait to have the remain refunded too. With this option, it is possible to convert the remain of invoice into a discount to reuse it into another invoice.

*SUUPLIER_INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED* ► See INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED, but for supplier credit notes.

*INVOICE_CAN_ALWAYS_BE_EDITED ► Allow to edit invoices even if payment was started. Note: If the module "BlockedLog" is active (required in some countries for legal reasons), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*INVOICE_CAN_ALWAYS_BE_REMOVED ► Allow to always delete invoices (even if invoice is not last one). Note: If the module "BlockedLog" is active (required by some countries for legal reason), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*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_DEPOSITS_ARE_JUST_PAYMENTS ► An old way to create initial payment. This treats deposit invoices as a special case and not as legal deposit invoice. 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. WARNING: In a lot of european countries, using this option is not allowed.

*FACTURE_SENDBYEMAIL_FOR_ALL_STATUS ► Can send invoice by email to customer even if invoice has status "draft".

*INVOICE_CREDIT_NOTE_STANDALONE ► Start implementation to allow a credit note even without invoice (dangerous) ► (v3.9)

*INVOICE_USE_SITUATION ► Enable the "situation invoice" feature. Warning, this feature is bugged and may not be compatible with the final version of the feature once the bug will be solved. Also, using the double-entry accountancy module is not possible when this option is on (due to the same design problem).

*INVOICE_USE_SITUATION_CREDIT_NOTE ► Enable the "situation credit note" feature (need <code>INVOICE_USE_SITUATION</code>) ► (v8.0)
*INVOICE_USE_RETAINED_WARRANTY ► Enable the retained warranty on invoice ► (v14.0)

*INVOICE_DISABLE_DEPOSIT ► Disable deposit invoices

*INVOICE_DISABLE_REPLACEMENT ► Disable replacement invoices

*INVOICE_DISABLE_CREDIT_NOTE ► Disable credit notes

*INVOICE_ADD_ZATCA_QR_CODE ► Add a QR code with format ZATCA (for Saudi Arabia) on PDF of invoices.

Note: To decode a QR image of a ZATCA code: https://www.onlinebarcodereader.com/. You can also use the mobile application https://play.google.com/store/apps/details?id=com.posbankbh.einvoiceqrreader&gl=FR

*MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT ► See PDF option

*MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN ► See PDF options

*WORKFLOW_BILL_ON_SHIPMENT ► Change label of button with suitable label when you need to create invoice on shipments

*INVOICE_ALLOW_EXTERNAL_DOWNLOAD ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. Use the tag __DIRECTDOWNLOAD_URL_INVOICE__ in email template to insert it. ► (v7.0+)

*INVOICE_POINTOFTAX_DATE ► Add Point of Tax Date on invoices for country-specific legality reasons ► (v4.0+)
*FACTURE_ENABLE_NEGATIVE ► Can validate an invoice when amount is negative

*FACTURE_ENABLE_NEGATIVE_LINES ► Allows to add negative lines to an invoice ► (v8.0.2+)

*INVOICE_USE_DEFAULT_DOCUMENT ► Allow user to select a default invoice documents models according to invoice type. On invoice create page, the model is dynamically changed on invoice type selection. ► (v9.0+)

*FACTURE_REUSE_NOTES_ON_CREATE_FROM ► Reuse the Public Note and Private note of the previous object (Proposal,...) when creating the bill.
*FACTUREFOURN_REUSE_NOTES_ON_CREATE_FROM ► Reuse the Public Note and Private note of the previous object when creating the supplier bill ► (V13.0)
*MAIN_SHOW_FACNUMBER_IN_DISCOUNT_LIST ► Display the reference of credit notes in discount list when creating the bill.
*INVOICE_ALLOW_FREE_REF ► Capability to change reference of an invoice. This will be possible as long as the invoice has the status “Draft” and only if your country is not in Europe(V11)

*INVOICE_DISALLOW_REOPEN

*INVOICE_MAX_FUTURE_DELAY ► Numbers of seconds allowed for billing in the future ► (V14.0)
*INVOICE_AUTO_NEXT_MONTH_ON_LINES ► Increase start date and end date by one month, if an invoice line is a clone of a time based service AND if this services started on the first day of month and ended on the last day of month ► (V13.0.1)

[[#Top|(back to top)]]

=Leave=

*MAIN_NON_WORKING_DAYS_INCLUDE_SATURDAY ► Set this value to 0 if you want to have the saturday as a working day
*MAIN_NON_WORKING_DAYS_INCLUDE_SUNDAY ► Set this value to 0 if you want to have the sunday as a working day

=Look or Theme=

*MAIN_FAVICON_URL ► favicon url

*MAIN_EASTER_EGG_COMMITSTRIP ► Show a comic image from the CommitStrip website. Images are refreshed daily. ► (v6.0+)

*MAIN_STATUS_USES_CSS ► Change status design using new style ► (v10.0+)

*MAIN_INCLUDE_GLOBAL_STATS_IN_OPENED_DASHBOARD ► This conf will auto remove global stats box item if there are already in the new dashboard of opened elements and keep displayed stats on the opened item box (not only on mouse over) ► (v11.0+)

*MAIN_USE_TOP_MENU_SEARCH_DROPDOWN ► Actually only for eldy theme, this conf move search input to top menu and use new design too ► (v11.0+)

*THEME_AGRESSIVENESS_RATIO ► This conf can be used to increase/decrease agressiveness of colors. Value 0 is medium, value is between -100 (light grey colors) to +100 (very flashy colors) ► (v11.0+)

*THEME_SHOW_BORDER_ON_INPUT
*MAIN_DISABLE_GLOBAL_WORKBOARD ► Hide the workboard of the main page ► (v13.0+)
*MAIN_DISABLE_GLOBAL_BOXSTATS ► Hide the Statistic Box of the main page

[[#Top|(back to top)]]

=MultiCurrency=

*MAIN_MULTICURRENCY_ALLOW_SYNCHRONIZATION ► Enable CurrencyLayer API synchronization

[[#Top|(back to top)]]

=Order Module=

*MAIN_USE_PROPAL_REFCLIENT_FOR_ORDER => Copy customer reference from proposal to order. ► (v7.0+)

*ORDER_REQUIRE_SOURCE => Make the input field "Source of order" mandatory.

*ORDER_VALID_AFTER_CLOSE_PROPAL => When an order is created on a proposal close, the order is directly defined with status "Validated".

*ORDER_ALLOW_EXTERNAL_DOWNLOAD => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*ORDER_ENABLE_NEGATIVE => Can validate an order when amount is negative

*THIRDPARTY_PROPAGATE_EXTRAFIELDS_TO_ORDER => Copy also extrafields from thirdparty to order (if name match). ► (v11.0+)

[[#Top|(back to top)]]

 

=PDF Options=

*MAIN_ADD_PDF_BACKGROUND ► Define this constant with short name of a PDF file (example "<code>mypdf.pdf</code>") that must be saved into directory "<code>documents/mycompany</code>". 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_DISABLE_FORCE_SAVEAS ► If your browser always asks to save downloaded files on disk (like PDF), try this this option. File may be displayed directly in your browser.

*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 servers with low CPU.

*MAIN_DISABLE_PDF_COMPRESSION ► Disable PDF compression.

*MAIN_DOCUMENTS_WITH_PICTURE_WIDTH ► Can change size of picture when hidden option <code>MAIN_GENERATE_PROPOSALS_WITH_PICTURE</code> is used. By default value is <code>20</code>.

*MAIN_GENERATE_DOCUMENTS_SHOW_FOOT_DETAILS ► Adding the company address at the bottom of the page. Disabled by default

*MAIN_GENERATE_PROPOSALS_WITH_PICTURE ► Include the first image of the product into the line of the generated PDF for customer proposals.

*MAIN_GENERATE_INVOICES_WITH_PICTURE ► Include the first image of the product into the line of the generated PDF for customer invoices.

*MAIN_GENERATE_SUPPLIER_PROPOSAL_WITH_PICTURE ► Include the first image of the product into the line of the generated PDF for supplier proposals ► (v5.0.3+)
*MAIN_GENERATE_SUPPLIER_ORDER_WITH_PICTURE ► Include the first image of the product into the line of the generated PDF for supplier orders

*MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT ► Disable VAT on generated documents. like for an association. (Works with crabe template)

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

*MAIN_INVERT_SENDER_RECIPIENT ► Invert sender and recipient in some PDF. Note: This option is set automatically if country if Germany.

*MAIN_ODT_AS_PDF ► Activate ODT to PDF conversion. Value can be "libreoffice" or "unoconv". Do not use value '''<nowiki/>'jodconverter'<nowiki/>''' any more, as it is declared deprecated and partly not functional, use value '''<nowiki/>'libreoffice'''' instead, it requires only '''soffice''' (OpenOffice or LibreOffice) installed on server (use '''apt install soffice libreoffice-common libreoffice-writer''').

If you got this error: javaldx failed! Warning: failed to read path from javaldx with no return to prompt when running soffice --headless -env:UserInstallation=file:"/tmp" --convert-to pdf --outdir xxx ./yyy.odt, check that directory defined into env:UserInstallation parameters exists and is writeable.

You may also have a look at this page if your server is on Windows: [[Générer automatiquement des documents PDF à partir de fichier ODT avec Doliwamp]]

*MAIN_ODT_AS_PDF_DEL_SOURCE ► For ODT generation. If set, then initial behaviour is conserved but ODT file is removed when option to convert it as PDF (see previous) is on. Disabled by default

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

*MAIN_PDF_FORCE_FONT_SIZE ► To force size of font (by default 10). For example "<code>12</code>" ► (v11.0)

*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: <code>220,220,200</code>

*MAIN_PDF_USE_LARGE_LOGO ► Use the original logo with its higher resolution into the PDF instead of the small thumb. This may lead to very very large PDF !

*MAIN_USE_BACKGROUND_ON_PDF ► Define this constant with short name of an image (example "<code>myimage.jpg</code>") that must be saved into directory "<code>documents/mycompany/logos</code>". This will add this background image into your generated PDF files.

*MAIN_USE_COMPANY_NAME_OF_CONTACT ► Use contact name and information rather than company

*MAIN_PDF_ADDALSOTARGETDETAILS ► If 1, add details of reipient on generated PDFs (email, fax, url and phone). Can be useful in cases where a printed order/invoice etc is given to a delivery driver/courier etc.

*MAIN_TVAINTRA_IN_SOURCE_ADDRESS ► Show VAT N° in source address of PDF to comply with legalities in certain countries. Note that VAT number should be already visible in footer of page ► (v8.0.1+)

*MAIN_PDF_PROPAL_USE_ELECTRONIC_SIGNING ► Add optional esign field in pdf propal ► (v8.0+)

*MAIN_PROFID1_IN_SOURCE_ADDRESS ► Show Professional ID 1 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*MAIN_PROFID2_IN_SOURCE_ADDRESS ► Show Professional ID 2 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*MAIN_PROFID3_IN_SOURCE_ADDRESS ► Show Professional ID 3 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*MAIN_PROFID4_IN_SOURCE_ADDRESS ► Show Professional ID 4 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*MAIN_PROFID5_IN_SOURCE_ADDRESS ► Show Professional ID 5 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*MAIN_PROFID6_IN_SOURCE_ADDRESS ► Show Professional ID 6 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

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

*PDF_BOLD_PRODUCT_REF_AND_PERIOD ► Add more visibility (bold) on product ref and period of service in desc. ► (v12.0)

*PDF_HIDE_PRODUCT_REF_IN_SUPPLIER_LINES ► Modify the use/position of Supplier Ref/Internal Ref with the item Label (name) on PDF documents.

Default (constant not set or Value <code>0</code>): Internal ref followed by supplier ref in brackets."COMPANY-REF-001 (Vendor SKU SUPPLIER-REF-001) - LABEL...".

Value <code>1</code>: Supplier ref only eg."SUPPLIER-REF-001 - LABEL...".

Value <code>2</code>: Supplier ref followed by internal ref in brackets. eg."SUPPLIER-REF-001 (InternalRef COMPANY-REF-001) - LABEL...".

*PDF_INCLUDE_ALIAS_IN_THIRDPARTY_NAME ► Include alternative/alias name into name on PDF.

*PDF_SECURITY_ENCRYPTION ► Encrypt PDF produced by dolibarr ► (v?) . See additional parameters :PDF_SECURITY_ENCRYPTION_RIGHTS (block 'modify' or 'copy') - PDF_SECURITY_ENCRYPTION_USERPASS - PDF_SECURITY_ENCRYPTION_OWNERPASS (random if not specified) - PDF_SECURITY_ENCRYPTION_STRENGTH (0 = RC4 40 bit; 1 = RC4 128 bit; 2 = AES 128 bit; 3 = AES 256 bit) - PDF_SECURITY_ENCRYPTION_PUBKEYS Array of recipients containing public-key certificates ('c') and permissions ('p') - For example: array(array('c' => 'file://../examples/data/cert/tcpdf.crt', 'p' => array('print')))

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

*PDF_USE_1A ► PDF files produced by dolibarr respect PDF/A standard ► (v?)

*PDF_USE_ALSO_LANGUAGE_CODE ► The value of this constant must be a language code ('fr_FR', 'en_US', 'sa_SA', ...). If set, the PDF document will contains both language (default and the one defined by the constant).
*DOC_SHOW_FIRST_SALES_REP ► Show the sales representant on header (at least on propal azur and rubis template)
*MAIN_PDF_DASH_BETWEEN_LINES
*
*SHOW_SUBPRODUCT_REF_IN_PDF
*PDF_HIDE_PRODUCT_LABEL_IN_SUPPLIER_LINES ► hide product label in supplier order lines (V15+)
*SHIPPING_PDF_DISPLAY_AMOUNT_HT ► Show HT unit price and HT total price for lines of PDF shipment

[[#Top|(back to top)]]

=Point of Sale (POS)=

*CASHDESK_SHOW_KEYPAD ► Show a mouse key pad into the 'Simple Point of Sale' module.

*POS_ADDON ► Set this value to an existing numbering module rule (for example '<code>mod_facture_terre</code>', '<code>mod_facture_mars</code>', ...) to force the numbering module to use for invoice ref definition when invoice is created by the POS. For example setting value <code>POS_ADDON</code> to '<code>mod_facture_terre</code>' will use the numbering module '<code>terre</code>' for invoice generated from POS, whatever is the numbering rule defined into invoice module setup (you can also use POS_NUMBERING_TERRE_FORCE_PREFIX and POS_NUMBERING_MARS_FORCE_PREFIX variable to change the prefix used).

*TAKEPOS_ENABLE_SUMUP ► Enable the compatibility of TakePOS with the card reader terminal [https://SumUp.fr SumUp]
*TAKEPOS_CAN_FORCE_BANK_ACCOUNT_DURING_PAYMENT ► Possibility to force the bank account during the payment in TakePOS ► (v13.0)
*TAKEPOS_CONTROL_CASH_OPENING ► Control the cash openning
*TAKEPOS_NUMPAD_FORCE_PAYMENT_ICONS_LABELS

[[#Top|(back to top)]]

=Products Module=

*CATEGORY_GRAPHSTATS_ON_PRODUCTS ► Show graph of products with categories and totals in Products Area screen

*MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE ► Avoid customs 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.

*MAIN_DIRECT_STATUS_UPDATE ► Allows you to change the status of the product (''for sale/not for sale for purchase/not for purchase'') directly on the product page via a ''on/off'' switch button. This can be convenient for those who need to quickly disable certain statuses of products without having to go through the editing product page individually. Also can be very useful if used as a filter on the product and product search list. This option doesn't generate a MODIFY trigger, so be careful with external modules. ► (v4.0+)

*MAIN_SEARCH_PRODUCT_BY_FOURN_REF ► Allow to search a product by supplier ref in document's add line form. ► (>= 8.0)

*MAIN_DISABLE_FREE_LINES ► Disallow using free lines to add line in documents ► (>= 8.0)

*MAIN_SHOW_PRODUCT_ACTIVITY_TRIM ► Show Product and Services turnover before for all four quarters tax over recent years recent years on the product area ► (v5.0+)

*PRODUIT_DESC_IN_LIST ► Show long description of product/service into lists.

*PRODUCT_DISABLE_PROPAGATE_CUSTOMER_PRICES_ON_CHILD_COMPANIES ► Disable propagation of prices per customer from a customer to its child company.

*PRODUCT_DISABLE_PUBLIC_URL ► Disable public url in product card ► (v14.0+)
*PRODUCT_DISABLE_STOCK_LEVELS ► Disable properties of stock limits and desired optimal value on product ► (v14.0+)
*PRODUCT_DISABLE_NATURE ► Disable nature in product card ► (v14.0+)
*PRODUCT_DISABLE_WEIGHT ► Disable weight in product card ► (v14.0+)
*PRODUCT_DISABLE_PRICES ► Disable prices in product card ► (v14.0+)
*PRODUCT_DISABLE_ACCOUNTING ► Disable accounting in product card ► (v14.0+)
*PRODUCT_DISABLE_SIZE ► Disable size in product card.

*PRODUCT_DISABLE_LENGTH ► Disable length in product card ► (v4.0+)

*PRODUCT_DISABLE_SURFACE ► Disable surface in product card. ► (v4.0+)

*PRODUCT_DISABLE_VOLUME ► Disable volume in product card.

*PRODUCT_DISABLE_CUSTOM_INFO ► Disable custom info (custom code and country origin) in product/service card.

*PRODUIT_MULTIPRICES_USE_VAT_PER_LEVEL ► When option to use price per level/segment is on, this allows to also set a dedicated vat for each price level.

*PRODUIT_CUSTOMER_PRICES_BY_QTY ► If price per quantity ► ''Experimental''
*PRODUIT_CUSTOMER_PRICES_BY_QTY_MULTIPRICES ► If price per quantity and customer ► ''Experimental''

*PRODUCT_LOT_ENABLE_QUALITY_CONTROL ► Enable feature for control quality on Lot

*PRODUCT_MAX_LENGTH_COMBO ► Limit the length of the label displayed when adding lines in proposals/invoices/orders

*PRODUCT_MAX_VISIBLE_PHOTO ► Show a maximum number of product photos (as thumbnails) on the product main card. Example, setting this constant to '<code>5</code>' will show the first five product photos found on the product card.

*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 ► Add another units on products (Use same dictionnary as default unit feature) and propagate this unit on line of documents.

*RESOURCE_ON_PRODUCTS_RESOURCE_ON_SERVICES ► Allow to affect ressources on products/services ► (v10.0+)
*PRODUCT_SHOW_ORIGIN_IN_COMBO ► Show origin of products when adding lines in proposals/invoices/orders ► (v12.0+)
*PRODUIT_ATTRIBUTES_HIDECHILD ► Add option hide child if variantes

*PRODUCT_ADD_FORM_ADD_TO ► Add a product to a draft proposal/order/invoice, from the product card.
*PRODUCT_DISABLE_SELLBY ► Hide the Sell by date ► (v13.0+)
*PRODUCT_DISABLE_EATBY ► Hide the Eat by date ► (v13.0+)

*PRODUCT_DENY_CHANGE_PRODUCT_TYPE ► Forbid to change the product type

*PRODUCT_SORT_BY_CATEGORY ► Sort the product by categories instead of by ID
*PRODUCT_ADD_NET_MEASURE ► Support Net Measure in product's card.php (For real weight, volume or piece; needed for some business ie fruits, vegetables....). Note brut value is already available natively, use this option only if you need 2 weights, 2 volumes, ...for each product) ► (v11.0.1+)

[[#Top|(back to top)]]

 

=Projects Module=

*PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY ► Can link an object to a project of another thirdparty
*PROJECT_ALLOW_COMMENT_ON_PROJECT ► Add comment feature on a project

*PROJECT_ALLOW_COMMENT_ON_TASK ► Add comment feature on project task

*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_CREATE_ON_OVERVIEW_DISABLED ► Hide the "create ..." button on the overview page ► (v4.0)

*PROJECT_DISABLE_UNLINK_FROM_OVERVIEW ► Enable removing the button from a link in the project overview. ► (>= v8.0.1)

*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 ► Hide the "link to" form on the overview page ► (v4.0)

*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_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_OPEN_ALWAYS_ON_TAB ► Set to value 'task', or 'preview' to always open the project on the given tab instead of main tab.
*
*
*PROJECT_ELEMENTS_FOR_MINUS_MARGIN

[[#Top|(back to top)]]

=Proposals Module=

*MAIN_GENERATE_PROPOSALS_WITH_PICTURE ► Add a picture of the product (the first one found if there are several) into the generated PDF of proposals. Note that using this will reduce the available width for the product description.

*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_PDF_PROPAL_USE_ELECTRONIC_SIGNING ► add optional esign field in pdf propal ► (v8.0+)

*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.

*PROPAL_DISABLE_SIGNATURE ► Do no show the box for signature.

*PRODUIT_PDF_MERGE_PROPAL ► When generating the proposal PDF, all PDFs linked to products linked to proposal are also included into final PDF

*PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*PROPOSAL_AUTO_ADD_AUTHOR_AS_CONTACT ► Add Proposal Author as user contact follow proposal

*PROPOSAL_PDF_HIDE_PAYMENTTERM ► Do not show the payment term on proposal ► (v11.0+)

*PROPOSAL_PDF_HIDE_PAYMENTMODE ► Do not show the payment mode on proposal ► (v11.0+)

*WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES ► Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.
*PROPAL_REOPEN_UNSIGNED_ONLY ► Do not allow reopening of signed (or billed) proposals. (V15)
*PROPOSAL_ARE_NOT_BILLABLE ► Disable billing button on proposals (V15)

[[#Top|(back to top)]]

 

=Services Module=

*SERVICE_ARE_ECOMMERCE_200238EC ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country. For french speaking people, see also the page [[Loi_européenne_TVA_Vente_à_Distance_VAD_et_e-commerce_BtoC]].

*MAIN_FILL_SERVICE_DATES_FROM_LAST_SERVICE_LINE ► (v13.0) On add line form add a button to fill service dates from the last service line

[[#Top|(back to top)]]

=Shipments=

*STOCK_WAREHOUSE_NOT_REQUIRED_FOR_SHIPMENTS ► If set, you can add a shipment line, with no stock source defined. ► (>= 8.0.1)

*SHIPMENT_GETS_ALL_ORDER_PRODUCTS ► Add all order lines in shipment, including the one with 0 in quantity

[[#Top|(back to top)]]

=Stocks=

*SUPPLIER_ORDER_DISABLE_STOCK_DISPATCH_WHEN_TOTAL_REACHED ► Disable stock dispatch when total expected was already received

*STOCK_EXCLUDE_VIRTUAL_PRODUCTS ► If product is a virtual product, we do not manage stock for it.

*ENTREPOT_EXTRA_STATUS ► Instead of the 2 status (Closed, Open), a Warehouse has 3 status: Closed, Open (for all movements), Open (for internal movement only). Internal movement only means you can't use the warehouse to make shipment or receptions.
*SUPPLIER_ORDER_STATUS_FOR_VIRTUAL_STOCK ► For the calculation of virtual stocks, by default supplier orders with the status 3 (ordered) and 4 (partially received) are used. You can enter the list of statuses to be taken into account separated by commas for this calculation (example: 0,1,2,3)
*STOCK_MOVEMENT_LIST_HIDE_UNIT_PRICE ► to hide unit price on some pages (V15+)

[[#Top|(back to top)]]

=Suppliers Module=

*FOURN_PRODUCT_AVAILABILITY ► On the Suppliers price page of the products, activate the supplier product availability. ''This is duplicate feature with delivery_delay introduced with 3.8.''

*RELOAD_PAGE_ON_SUPPLIER_CHANGE ► On creation of a supplier order/invoice, reload form with supplier-specific details when supplier is selected from drop-down list.

*SUPPLIER_INVOICE_WITH_PREDEFINED_PRICES_ONLY ► Restrict selection of products in supplier invoice to only those with a buying price defined for that supplier. ► (v6.0+)

*SUPPLIER_ORDER_AUTOADD_USER_CONTACT ► Add user approving supplier order as a contact automatically.

*SUPPLIER_ORDER_DEFAULT_PAYMENT_MODE_ID ► Set the default payment method for suppliers (<code>rowid</code> in table <code>llx_c_paiement</code>).

*SUPPLIER_ORDER_USE_DISPATCH_STATUS ► Add a status on each dispatch order line when receiving products from suppliers ► (v4.0+)

*SUPPLIER_ORDER_NO_DIRECT_APPROVE ► No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

*SUPPLIER_ORDER_WITH_PREDEFINED_PRICES_ONLY ► Restrict selection of products in supplier order to only those with a buying price defined for that supplier. ► (v6.0+)

*SUPPLIER_ORDER_EDIT_BUYINGPRICE_DURING_RECEIPT ► Can modify the buying price used for PMP calculation when making a stock reception on a supplier order. ► (v6.0+)

*SUPPLIER_PROPOSAL_WITH_PREDEFINED_PRICES_ONLY ► Restrict selection of products in supplier proposal to only those with a buying price defined for that supplier. ► (v6.0+)

*DISPLAY_DISCOUNTED_SUPPLIER_PRICE ► Allow to display discounted supplier price when searching product in supplier documents ► (v10.0)

*MAIN_CAN_EDIT_SUPPLIER_ON_SUPPLIER_ORDER ► Allow to change the supplier on a draft supplier order ► (v10.0)
*
*SUPPLIER_PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD

[[#Top|(back to top)]]

=Third Parties Module=

*COMPANY_AQUARIUM_CLEAN_REGEX ► Add a REGEX rule on the third parties names. It applies a regex replacement pattern on generated code if COMPANY_AQUARIUM_CLEAN_REGEX is set. Value must be a regex with parenthesis. The part into parenthesis is kept, the rest removed. For example if COMPANY_AQUARIUM_CLEAN_REGEX = '<code>^..(..)..(.*)</code>' the first char and second char are removed and the char 5 and 6 too ► (>= 8.0.1)
*SOCIETE_EMAIL_MANDATORY ► E-mail is a mandatory field when creating a thirdparty

*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"

*SOCIETE_SORT_ON_TYPEENT ► The combo list of "type of third party" is sorted on alphabetical order instead of the field "position" that appears into dictionary instead.

*SOCIETE_ASK_FOR_SHIPPING_METHOD ► Shipping method can be predefined on customer card and will be used as default on order creation
*SOCIETE_ADD_REF_IN_LIST ► Displays the code before the name in the lists ► Value 1 -> Code + name + alias ou Code + name if colone alias 2 -> Code + alias 3 -> Alias

*THIRDPARTY_CAN_HAVE_CATEGORY_EVEN_IF_NOT_CUSTOMER_PROSPECT_SUPPLIER ► Possible to add Categories to third parties that are not customer, prospect or supplier.

*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.

*THIRDPARTY_NOTCUSTOMERPROSPECT_BY_DEFAULT ► Do not set status "Customer/Prospect" to "on" when creating a new third party from menu "New third party".

*THIRDPARTY_INCLUDE_PARENT_IN_LINKTO ► Search also for elements on parent third party when using the "link to" object feature.

*THIRDPARTY_INCLUDE_PROJECT_THIRDPARY_IN_LINKTO ► Search also for elements on third party that own the project of the current element when using the "link to" object feature (if project is owned by a different thirdparty than current one).

*THIRDPARTY_LOGO_ALLOW_EXTERNAL_DOWNLOAD ► When a logo is uploaded, a share key is automatically set so the file can be downloaded using the share key.

*THIRDPARTY_SUGGEST_ALSO_ADDRESS_CREATION ► Enabled contact creation on third-party create card
*THIRDPARTY_QUICKSEARCH_ON_FIELDS ► Personalized search criterias ► Example: $conf->global->THIRDPARTY_QUICKSEARCH_ON_FIELDS = 's.nom=ThirdPartyName;s.name_alias=AliasNameShort;s.code_client=CustomerCode'
*MEMBER_CAN_CONVERT_CUSTOMERS_TO_MEMBERS ► Enabled member creation on third-party create card
*SOCIETE_DISABLE_PARENTCOMPANY ► Disables attachment to a parent company.
*THIRDPARTY_CUSTOMERPROSPECT_BY_DEFAULT ► Set the third party to customer by default
*THIRDPARTY_SUPPLIER_BY_DEFAULT ► Set the third party to supplier by default
*THIRDPARTY_CUSTOMERTYPE_BY_DEFAULT ► Set the third party type by default (3 = customer & prospect / 2 = prospect / 1 = customer )
*CONTACT_DISABLE_PERSONALINFO ► Disable Personal data on contact page
*SOCIETE_DISABLE_WORKFORCE ► Disable work force selector on society page
*SOCIETE_SHOW_VAT_IN_LIST ► display VAT number in combo list of thirdparties (V15+)

[[#Top|(back to top)]]

=Ticket Module=

*TICKET_SHOW_MESSAGES_ON_CARD ►Display all ticket related messages on the main ticket card. ► (>= 10.0)
*TICKET_AUTO_ASSIGN_CONTRACT_CREATE ►Automatically create a contract linked to the ticket ► (>= 10.0)
*TICKET_AUTO_CREATE_FICHINTER_CREATE ►Automatically create an intervention linked to the ticket ► (>= 10.0)
*WORKFLOW_TICKET_CLOSE_INTERVENTION ►On ticlet close, automatically close an intervention linked to the ticket
*TICKET_CHECK_NOTIFY_THIRDPARTY_AT_CREATION ►Automatically check "notify thirdparty at creation" ( >=16)
*TICKETS_MESSAGE_FORCE_MAIL ► Precheck email sending on ticket message (>=15)

 

=VAT Report=

*MAIN_INCLUDE_ZERO_VAT_IN_REPORTS ► Include lines with VAT to 0% (for "auto-liquidation" in EEC) ► (v8.0.3+)

[[#Top|(back to top)]]

=Website Module=

*WEBSITE_USE_WEBSITE_ACCOUNTS ► Add a table and a tab to manage some accounts for websites to a third party
*
*
*WEBSITE_ADD_CSS_TO_BODY

[[#Top|(back to top)]]

 

=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 guaranteed with this. Also if the image is removed or renamed by the image hosting service, your proposal, order or invoice will be broken.
*FCKEDITOR_ALLOW_ANY_CONTENT ► Allow to enter any content. However, this will totally disable content filtering which is one of the most important CKEditor features. You can use this to keep all your tags and attributes in the html content.

[[#Top|(back to top)]]

=STRIPE Module=

*STRIPE_FORCE_VERSION ► Force the STRIPE version. For Example: "2019-09-09" (v11+)

[[#Top|(back to top)]]

=ClickToDial Module=

*CLICKTODIAL_FORCENEWTARGET ► Open in new page.

[[#Top|(back to top)]]

 

=For SaaS / Cloud hosting integrators=

The following options are useless for a common usage of Dolibarr. But they are usefull if you plan to host / provide Dolibarr instances as Software As A Service (SAAS) to your customers.

*CRON_DISABLE_KEY_CHANGE ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*CRON_DISABLE_TUTORIAL_CRON ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*CRON_WARNING_DELAY_HOURS ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

*To avoid bad use of the emailing module, it is recommended to set the option MAILING_NO_USING_PHPMAIL to 1 (This option is described previously). Also you can complete the message visible by customers when they try to setup the SMTP credentials of their Dolibarr by using the constant MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS (This option is described previously). For example, you can point to a FAQ on your website.

*If you set a system limit on number of recipient, you can set some option to match the same values so users will be informed: MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL ► Restrict sending of 1 email message to <code>x</code> recipients for same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include 1000 recipients in 1 message. Note that MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL, MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL and MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL are also available.

*MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE ► If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock so the administration tools like install.php and repair.php can't be used on your customer instance (until the lock file is deleted).

*MAIN_HIDE_WARNING_TO_ENCOURAGE_SMTP_SETUP ► Set to 1 by default. You can set it to 0 to show a warning to encourage admin to set its own SMTP service.

*MAILING_LIMIT_WARNING_PHPMAIL ► Set this value to a translation key. Then add translation keys into the instance so user will see a message when into the email setup page. For example, you can set a message to say ''Warning: To avoid abuse, when using default setup, you are restricted to 500 emails per day for all your application (account may be suspended in case of violation of this rule. You can setup application to use your own SMTP server for sending email so you want have no restriction at all (see menu Home-Setup-Emails)''

*MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD.

*MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD ► Set here the string to add in the SPF record This string will be shown into a help message when the user in in the setup of email page and has choose a method using an external SMTP server.

*MAIN_FIRST_PING_OK_ID ► Set this value to "disabled" to remove completely any ping after a complete setup.

*MAIN_FILECHECK_LOCAL_SUFFIX and MAIN_FILECHECK_LOCAL_EXT ► If you offer a customized or patched version of Dolibarr, when the user will use the tool to check the integrity of files, the default xml file name used for signature checking will be the official file provided by the Dolibarr team, so it does not includes your own changes. To have the suggested signature file being your own file, you can set the constant MAIN_FILECHECK_LOCAL_SUFFIX to a suffix. For example, set this to "'''-mysaassolution'''". So, when the user will use the file integrity tool, the default file to check for signature will be "'''/install/filelist-10.0.2-mysaassolution.xml'''" instead of "'''/install/filelist-10.0.2.xml'''". All you have to do is generate the signature file '''mysaassolution''' using the tool '''build/generate_filelist_xml.php''' and put this file into the install directory of your customer instance. Doing this, your customer, and yourself, will be able to check if a file was modified without being disturbed by false alerts due to your customized files or patches (they will be included in the signature used for check). Also, if you want to zip the customized signature file into "'''/install/filelist-10.0.2-mysaassolution.xml.zip'''", you can set the constant MAIN_FILECHECK_LOCAL_EXT to '.zip'.

*MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING ► If set to N, the warning saying modules are not activated will be shown if number of activated module is < N (Having this variable not defined is same than having it set to 1). This may be usefull if you preinstall an application with some modules already loaded by default and you want to keep the warning to be sure the user will enable other modules he need, even if some modules are already enabed.

*SYSLOG_DISABLE_LOGHANDLER_SYSLOG ► Set this to 1 to disable usage of syslog (having all customer instances logging in the same system file is not a good idea).

*WEBSITE_REPLACE_INFO_ABOUT_USAGE_WITH_WEBSERVER ► Put here a text or a translation key of a text to show when the user will use the feature "Deploy" when he want to deploy a website done with Dolibarr CMS. So you can, for example, show him a message that this feature is not part of its subscription and putting a website online may need a complementary subscription.

[[#Top|(back to top)]]

Langages et normes

2022-06-27T07:24:16Z

Iouston: suppression correction car il duplique plusieurs fois...

[[en:Language_and_development_rules]]
[[de:Sprachen_und_Programmierregeln]]
[[es:Lenguaje_y_Normas_de_Desarrollo]]
[[zh:语言和开发规则]]


{{TemplateDocDev}}

Voici les quelques règles sur le langage, la syntaxe et normes de développement en vigueur pour le projet Dolibarr :

=Versions=

*Dolibarr doit fonctionner sur:

#Tous OS (Windows, Linux, MACOS...)
#PHP {{PHPMinVersion}} (Doit fonctionner sans aucun module PHP complémentaire hors les modules d'accès base de donnée).
#Mysql {{MySqlMinVersion}}

=Normes Copyright=

*Tout fichier PHP doit avoir un en-tête selon le masque suivant

<syntaxhighlight lang="PHP">
<?php
/* Copyright (C) YYYY John Doe <email@email.com>
*
* Licence information
*/
...
</syntaxhighlight>
Quand vous éditez un fichier existant du projet, ajouter une ligne Copyright sous celles existantes.

=Normes PHP=

==PHP==

*Dolibarr est écrit en PHP et supporte toutes versions PHP supérieures à la {{PHPMinVersion}}. Les fichiers doivent tous comporter l'extension .php

*L'appel aux variables superglobales PHP doit passer par les opérateurs dédiés $_COOKIES, $_SERVER, $_ENV. Mais pour récupérer les contenus de $_GET ou $_POST, il faut passer par la fonction dolibarr [[Fonctions utiles Dolibarr|GETPOST()]] .

Les autres opérateurs ($HTTP_SERVER_GET, ...) ayant été passés en deprecated au sein de PHP, ne doivent plus être utilisés. Ainsi le code doit fonctionner y compris quand l'option '''register_long_arrays''' est à off.
De plus, le code doit fonctionner aussi bien quand l'option PHP '''register_globals''' est à off (recommandé par PHP) que quand l'option '''register_globals''' est à on (par défaut sur de nombreuses installations).

*Pas d'utilisation de la variable '''PHP_SELF'''. Utiliser à la place $_SERVER["PHP_SELF"]. Notez aussi que le framework Dolibarr passe une routine pour rendre plus sûr le contenu du $_SERVER["PHP_SELF"] (dans le fichier main.inc.php, donc avant tout traitement métier)

*Quand plusieurs variables doivent être initialisées avec la même valeur, il faut utiliser plusieurs instructions:

<syntaxhighlight lang="PHP">
$var1 = 1; $var2 = 1; $var3 = 1;
</syntaxhighlight>
plutôt que
<syntaxhighlight lang="PHP">
$var1 = $var2 = $var3 = 1;
</syntaxhighlight>
qui est moins performant.

*Les chaines doivent avoir les variables sorties de la chaine.

<syntaxhighlight lang="PHP">
print "Mon texte affiche ma ".$variable." !\n";
</syntaxhighlight>

*Les commentaires doivent suivre la syntaxe C, ie un double antislash pour un commentaire d'une ligne et utilisation slash-étoile pour ouvrir un bloc de plusieurs lignes

<syntaxhighlight lang="PHP">
/* Bloc de commentaire
*
* Fin du bloc
*/

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

for ($i = 1 , $i < 2 ; $i++)
{
// commentaire sur une ligne
print $i;
}

</syntaxhighlight>

*Les fonctions doivent retourner une valeur strictement > à 0 en cas de succès, et un nombre < à 0 en cas d'erreur.

*Pas de code mort (non utilisé) dans le code principal de Dolibarr (le code utilisé uniquement par un module externe doit être inclus dans le module externe).

*Utiliser "include_once" pour l'inclusion de tout fichier contenant des définitions de fonction ou de classes (donc fichiers *.class.php et *.lib.php), utiliser "include" pour tout inclusion de fichier de type template ou contenant un mixte de HTML et PHP (donc fichiers *.inc.php et *.tpl.php).

*Le style de code a utiliser est le PSR-12 (https://www.php-fig.org/psr/psr-12/). Seules les règles "MUST" sont imposées. Notez aussi les points/exceptions suivants:
**La longueur des lignes: PSR-12 indique que la longueur des lignes a une limite "soft" à 120. Il est en effet préférable d'avoir de longues lignes de données de déclaration plutôt que de longues pages car ce code ne contient aucune logique intéressante ou utile, toutefois une limite "hard" a été instauré à '''1000''' caractères. Du code qui ira au delà provoquera des erreurs dans la plateforme d'Intégration Continue.
**Les tabulations sont acceptées : L'autre exception est qu'on ne remplace pas les tabulations systématiquement par des espaces. L'utilisation des tabulations simplifie la vie de certains développeurs. De plus, l'utilisation d'espaces rend certaines fonctions d'autoformatage défectueuses (comme sur certaines versions d'Eclipse, lors de copier-coller).
**Note 1: Les règles suivantes sont particulièrement importantes :
***Les fichiers doivent être sauvés en format Unix (LF) et non Windows (CR/LF). Le format Unix étant compatible sur les OS Unix like, Windows, Mac, alors que le format fichier texte Windows pose problème sous certains PHP sous Unix.
***Les smart tags PHP ne sont pas utilisés. Les sections de code doivent commencer par '''<?php'''
**Note 2: Vous pouvez utiliser le fichier '''dev/setup/codesniffer/ruleset.xml''' comme fichier de contrôle pour vérifier votre style de code avec PHPCodeSniffer.
**Note 3: Vous pouvez utiliser le fichier '''dev/setup/eclipse/PSR-12 [built-in].xml''' comme fichier de règles de syntax pour configurer Eclipse.
**Note 4: Vous remarquerez que le code actuel ne suit pas forcément tout cela. La raison est historique. La règle fut instaurée en cours de route, aussi, si vous trouvez du code non respectueux de ce standard, n'hésitez pas à le corriger.

==Structures des classes et champs==

Certaines propriétés de classes se retrouvent dans de nombreuses classes. Pour homogénéité, on utilisera les noms suivants:
{{TemplatePHPFields}}

=Normes SQL=

==Structure des tables et champs==

*Toutes les tables sont préfixées pour éviter les conflits de nommage. Aujourd'hui, le préfixe est modifiable au moment de l'installation. Sa valeur par défaut est <tt>llx_</tt>.

*Structure des tables.

Lorsque vous créez une table, il est recommandé de prendre les même conventions de nommages de tables que les autres tables Dolibarr. Avec, à minima les champs suivant:
- rowid INTEGER AUTO_INCREMENT PRIMARY KEY qui est l'id technique
- entity INTEGER default 1 that is id for the multicompany feature
- date_creation datetime that is the creation date
- tms timestamp qui sera un champ contenant la date de chaque mise à jour (la base de donnée le gère tout seul, pas besoin de le gérer par le code)
- import_key varchar(32) qui contiendra le code d'import YYYYMMDDHHMMSS si vous faites des imports en masse dans la table.
- status smallint pour stocker le status d'un object

Eventuellement
- fk_user_creat integer qui est l'id du user de création (fk_user_author also found)
- fk_user_modif integer qui est l'id du user de modification
- fk_user_valid integer qui est l'id du user de validation
- fk_soc integer qui est l'id du tiers (si applicable)

*Type des champs

Dans la pratique, afin d'être compatible avec toutes les précisions des pays, syntaxes des bases, on utilisera uniquement les types suivants:
- integer pour tout nombre entier, id ou clé étrangère (bigint éventuellement accepté pour les id des très grosses tables)
- smallint pour tout numérique entier de petite taille (comme pour stocker un code de status)
- double(24,8) pour tout montant
- double(6,3) pour les taux de tva
- real pour une quantité
- varchar pour une chaîne (y compris de longueur 1, le type char est de plus en plus déprécié)
- timestamp pour un champ date+heure devant être mis a jour automatiquement
- datetime pour un champ date+heure
- date pour un champ date

==Clé primaire==
La clé primaire d'une table s'appelle <tt>rowid</tt>.

Il y a quelques tables qui échappent à cette règle actuellement (ex [[Table llx_c_actioncomm]]), pour des raisons historiques. Une évolution pourra être étudiée pour une prochaine version.

==Clés étrangères==
Le nom d'une clé étrangère commence par le préfixe <tt>fk_</tt> suivi du nom de la table liée (requis pour éviter doublons globales à la base, problématiques sous certains SGBD comme postgresql) puis du champ lié (pour permettre plusieurs clés étrangères différentes sur une même table).

Exemple:
fk_facture_fourn_fk_soc

Note: Si vous développez votre propre module externe, il ne doit pas y avoir de clé étrangère depuis vos tables qui pointent sur les tables standards de Dolibarr. Ceci casserait les fonctionnalités de mise à jour, de réparation, de sauvegardes et de restauration.

==Clés alternatives==
Parfois, il n'y a pas que la clé primaire qui doit être unique. On peut donc ajouter aussi un index clé alternative unique. Un tel index est nommé par un nom qui commence par le préfixe <tt>uk_</tt> suivi du nom de la table (requis pour éviter doublons d'index globals à la base, problématiques sous certains SGBD comme postgresql) puis d'un suffixe qui caractérise la clé (pour permettre plusieurs index uniques sur une même table).

Exemple:
uk_societe_code_client

==Index performance==
Certains champs sont souvent utilisés comme critère de recherche, de tri ou de jointure. Il convient dans ce cas, d'y mettre un index de performance. De tels indexes seront nommés avec un préfix <tt>idx_</tt> puis le nom de la table et le nom du champ sur lequel porte l'index.

Exemple:
idx_societe_user_creat

==Format de fichier DDL==
Les fichiers qui contiennent la définition de la structure de la base (DDL) doivent être au nombre de 2 par tables:
Chaque table est définie dans son propre fichier dont le nom est <tt>llx_''matable''.sql</tt>.
On mettra un commentaire à côté de chaque champ pour en expliquer la signification.
Les clés étrangères et index de performance ou autres contraintes d'unicité sont définies dans un fichier séparé dont le nom est <tt>llx_''matable''.key.sql</tt>

Ces fichiers sont placés dans le répertoire '''install/mysql/tables''' pour les fichiers standards ou '''monmodule/tables''' pour les tables amenées par un module.

Exemple '''fichier table llx_matable.sql''':

<syntaxhighlight lang="sql">
-- ===========================================================================
-- Copyright (C) 2008 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 2 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_matable
(
rowid integer AUTO_INCREMENT PRIMARY KEY,
field_one integer,
field_two integer NOT NULL,
fk_field integer,
field_date datetime,
tms timestamp
)ENGINE=innodb;
</syntaxhighlight>

Exemple '''fichier clés/index llx_matable.key.sql''':

<syntaxhighlight lang="sql">
-- ===========================================================================
-- Copyright (C) 2008 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 2 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);
</syntaxhighlight>

==Règles de codage SQL==

*Utilisation des alias/nommage de champs

Dans le cas des select on pourra utiliser les alias pour simplifier l'écriture des requêtes:
<syntaxhighlight lang="sql">
select chp1, chpxxx2 as chp2 from table2 as t1, table2 as t2 where t1.chpx = t2.chpy
</syntaxhighlight>
Toutefois, il ne faut pas utiliser ces alias sur des requêtes update car non compatible avec mysql 3.1.

*Les SELECT * sont interdits ! Chaque SELECT doit spécifier la liste complète des champs à récupérer. Cela permet d'éviter les confusions. Exemple:

<syntaxhighlight lang="sql">
SELECT field_a, field_b, field_c FROM table_1 WHERE field_d = '$id'
</syntaxhighlight>

*Dans les requêtes SQL, on quote les champs mais pas les numériques qui contiennent des montants destinés à être stockés dans des champs de type double ou real. Les quotes sur les numériques de type float provoquent parfois un stockage d'une valeur différente. Par exemple 412.62 dans le insert sera en fait stocké avec la valeur 412.61999512 en base (suite à des conversions chaines-numériques implicites) si le champ est de type double(24,8). Et seul le PHP voit 412.61999512. Les autres outils verront 412.62 donnant l'impression qu'il n'y a pas de problème. Et c'est le PHP qui a raison, il y a problème en base. En supprimant les quotes sur les numériques, cela va mieux.

Exemple:
<syntaxhighlight lang="sql">
Bon: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', 412.62)
Mauvais: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', '412.62')
</syntaxhighlight>

Remarque, le problème des float est général et pas seulement sur les accès base, il est présent dans tous les languages quand on travaille sur des nombres réels, aussi ils doivent être, dès que affectés, nettoyés par la fonction price2num avec le 2eme paramètre renseigné à:
'MU' (si il s'agit d'un prix unitaire), 'MT' (s'il s'agit d'un prix total) ou 'MS' (autres cas) selon le besoin.
Voir aussi le chapitre "Les nombres réels, montants et calculs" plus bas.

*Les fonctions NOW, SYSDATE ou DATEDIFF sont interdites au sein des ordres SQL. S'il faut saisir la date du moment dans un champ, la valeur doit venir du PHP, par exemple par la fonction dol_now(), et non du moteur de base de données. Ceci afin d'avoir une meilleure portabilité du code mais surtout d'avoir une gestion correcte des TimeZone et ne pas dépendre du TimeZone de la base de donnée.

Par exemple, on ne fera pas:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield = NOW()";
</syntaxhighlight>
mais:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield = '".$this->db->idate(dol_now())."'";
</syntaxhighlight>

Par exemple, on ne fera pas:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where DATEDIFF(table.datefield, NOW()) > 7";
</syntaxhighlight>
mais:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield < '".$this->db->idate(dol_now() - (7 * 24 * 3600))."'";
</syntaxhighlight>

Un autre avantage de cette règle est que la requête peut bénéficier de l'utilisation de l'index puisqu'on compare datefield à une valeur fixe. Dans le cas du datediff, on applique un traitement sur le champ avant comparaison, rendant impossible l'utilisation de l'index de ce champ. Les conséquences sont des performances très dégradées par rapport à la version sans datediff.

==Règles de migration de base==

*Les scripts de migration de structure sont les fichiers de type '''install/mysql/migration/a.b.c-x.y.z.sql'''. Dans un fichier de migration de n vers n+1, on ne détruit une table (DROP TABLE) qui n'est plus utilisée en n+1 que lors de la migration de la version n+1 vers n+2. Ceci afin de toujours conserver les tables deprecated le temps d'une version pour réparer une situation en cas d'erreur de migration.

==Spécificités MySQL==

*Les tables doivent être au format InnoDB.

En effet, ce format gère les clés étrangères, les éventuelles restrictions qui y sont attachées et la notion d'intégrité de transactions requise pour avoir des données en base cohérente entre tables.

*Dolibarr DOIT fonctionner même avec les options '''strict''' de Mysql active.

Pour l'activer (fortement recommandé en développement), ajouter la ligne suivante dans le fichier config du serveur Mysql (my.cnf ou my.ini)
{{MySqlStrictMode}}

==Spécificités PostgreSQL==
Seuls les fichiers pour Mysql doivent être maintenus.
Les fichiers pour les autres bases sont convertis "à la volée" par le driver Dolibarr de la base.

Il existe une exception.
Les requêtes "UPDATE FROM" :
Syntax MySQL :
<syntaxhighlight lang="sql">
UPDATE table_taget as target, table_source as source SET fieldtarget=source.fieldsource
WHERE source.rowid=target.rowid;
</syntaxhighlight>

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

Il n'en existe pas dans Dolibarr, mais pour vos modules Vous devriez faire tel que :
<syntaxhighlight 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";
}
</syntaxhighlight>

=Normes HTML=

*Tous les attributs dans les balises HTML doivent être *en minuscule* et quotés avec des *doubles quote*.

*Les liens href doivent être absolus en se basant sur la fonction dol_buildpath() pour obtenir un chemin absolu depuis un chemin relatif au répertoire htdocs. Pour les tags img, il faut faire appel à la fonction img_picto().

Par example:
<syntaxhighlight lang="PHP">
print '<a href="'.dol_buildpath('/monrep/mapage.php').'">'.img_picto('Texte alt','nompictopng','').'</a>';
</syntaxhighlight>

*Les tables HTML doivent avoir des colonnes sans valeurs forcées, excepté pour les colonnes qui contiennent une information dont la longueur est non variable. Par exemple, une colonne avec un picto peut être forcée à with="20px". Dans les autres cas, il faut éviter de forcer la largeur des colonnes. La raison est que, dans la plupart des cas, le navigateur fait un meilleur travail pour définir automatiquement la bonne largeur des colonnes qu'en forçant manuellement les largeurs. Et ceci marche quelle que soit la résolution de l'écran.

*Le javascript/ajax et l'appel aux scripts java dans les pages php est à proscrire. Si toutefois du code javascript est inclus, il doit être conditionné par le test sur "$conf->use_javascript_ajax"

<syntaxhighlight lang="PHP">
if ($conf->use_javascript_ajax) {
... // Le code php qui génère du javascript est ici
}
</syntaxhighlight>

*Les popups windows ne doivent pas être utilisées, sauf pour des tooltips (et restent conditionnées par le point ci-dessus).

*Les scripts externes sont écrits en Perl s'ils ne peuvent l'être en php, l'utilisation d'un autre langage n'est pas interdit mais doit être discuté au préalable dans la mailing list des développeurs.

=Normes Dolibarr et squelettes de code=

==Squelettes de code==
Afin d'uniformiser le code et d'accélérer le développement de nouveaux composants dans Dolibarr, se trouvent dans le répertoire '''htdocs/modulebuilder/templates'''.

Par exemple:

*1 fichier qui sert d'exemple de descripteur de module: '''myModule.class.php'''
*1 fichier qui sert d'exemple de code pour faire une nouvelle classe: '''skeleton_class.class.php'''
*1 fichier qui sert d'exemple de code pour faire une nouvelle page: '''skeleton_page.php'''
*1 fichier qui sert d'exemple de code pour faire un script à exécuter en ligne de commande: '''skeleton_script.php'''

...

Servez-vous en comme exemple.
Notons que ces squelettes sont aussi utilisés par le générateur de code PHP ([[Module ModuleBuilder]]) qui est décrit dans la chapitre de développement de module Dolibarr pour accélérer vos développements.

==Les dates et TimeZone==
Dolibarr se veut une application multi-utilisateur et multi-localisation. Il convient donc de stocker les dates dans le bon format. Pour éviter les problèmes de conversion, les règles suivantes doivent être appliquées:

*Une date en mémoire doit être au format Timestamp GMT.
*Une date stockée en base de données contient le Timestamp issue de la date soumise dans la requête en heure locale du serveur PHP. Cela ne concerne pas les dates mises à jour automatiquement par la base (champ '''tms''' en base).

Ainsi le 1er janvier 1970, 3 heures à Paris (TZ=+1) = 1er janvier 1970, 2 heures à Greenwich (TZ=0) sera stocké en mémoire par 7200 et sera soumis à la base de données avec la chaine '19700101030000' (PHP convertit en heure de son TZ et la base déconvertit avec son TZ qui est le même que celui de PHP).

Les méthodes select doivent donc traduire les champs dates lus qui sont au format chaine TZ de la base ('19700101030000') par appel de la méthode db->jdate afin de récupérer une information en mémoire au format Timestamp GMT. Et les méthodes insert doivent lors de la génération de la requête convertir la date mémoire connue en variable, par la méthode db->idate (Voir exemples générés par le squelette).

*Les dates mises à jour automatiquement par la base (champ '''tms''' en base) contiennent le Timestamp où la modification est faite selon le timezone de la base de donnée. Les méthodes select récupèrent cette donnée en mémoire au format Timestamp GMT en appliquant également le db->jdate. Si le timezone de la base de donnée diffère de celui du PHP (un des 2 est mal réglé), il peut donc y avoir des écarts entre date de création et modification.

*La manipulation de dates en PHP doit être faite en utilisant les fonctions dates de Dolibarr: '''dol_now(), dol_mktime(), dol_stringtotime(), dol_getdate(), dol_time_plus_duree()'''. Vous trouverez également d'autres fonctions prêtes à l'emploi dans le fichier '''date.lib.php'''.

==L'encodage UTF8/ISO==
Dolibarr stocke les informations de manière suivante:

*En base de donnée, les données sont en UTF8 ou ISO. Cela dépend du pagecode de la base, donc des options à la création de cette base. Dans tous les cas le driver d'accès base Dolibarr (dans /lib/database) s'arrange à la lecture et insertion pour convertir vers et depuis de l'UTF8.
*Les données en mémoires sont donc stockées en UTF8 (instances d'objets PHP).
*Les pages web affichées à l'écran sont au format UTF8

==Les nombres réels, montants et calculs==
En PHP comme dans d'autres langages (Java par exemple), les données non entières (float, real, double) ne sont pas fiables.
Essayer de faire par exemple
<syntaxhighlight lang="PHP">
print 239.2 - 229.3 - 9.9;
</syntaxhighlight>
Vous n'obtiendrez pas zéro mais un nombre très petit en puissance de 10 négative. Si vous obtenez zéro, vous pourrez trouvez d'autres exemples qui ne fonctionnent pas.
Le problème des float est général, une variable résultante de calcul de nombre réels doit SYSTEMATIQUEMENT être nettoyée par la fonction '''price2num()''' avec le 2eme paramètre renseigné à: 'MU', 'MT' ou 'MS' selon le besoin (voir doc fonction).
<syntaxhighlight lang="PHP">
print price2num(239.2 - 229.3 - 9.9, 'MT');
</syntaxhighlight>
S'il ne s'agit pas d'un prix sur lequel s'adapte les paramètres MU, MT ou MS, il faut utiliser la fonction '''round()'''.

==Création de tables==
Ne pas créer de table à l'utilisation, c'est-à-dire à la '''première utilisation''' du module.
Si vous créez un module qui utilise des tables qui ne sont pas intégrées en standard dans le code de Dolibarr, veillez à suivre le didacticiel [[Développement module]] qui explique comment joindre des tables qui se créent à l'activation du module et non à son utilisation (voir plus haut).

==Comparer la version==

Si votre code a besoin de faire des choses différentes selon la version de Dolibarr, vous pouvez utiliser le truc suivant pour comparer les versions

<syntaxhighlight lang="PHP">
$version=preg_split('/[\.-]/',DOL_VERSION);
if (versioncompare($version,array(5,0,-4)) >= 0) { //mycode for 5.0 only; } // For dolibarr 5.0.* (the -4 means we include also alpha, beta, rc and rcX)
</syntaxhighlight>

Mais cette solution requiert de faire un include avoir la fonction versioncompare. Une alternative est d'utiliser le test suivant :
<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

 

==Logs==
Ajouter des traces dans votre code avec la fonction
<syntaxhighlight lang="PHP">
dol_syslog($yourmessage, LOG_INFO|LOG_DEBUG|LOG_WARNING|LOG_ERR);
</syntaxhighlight>

==Répertoires de travail==
Si vous avez besoin de créer un répertoire de travail, dans votre code, faites référence à ce répertoire par
'''DOL_DATA_ROOT.'/monmodule''''

Le répertoire peut être créé dans votre code à l'exécution par le code suivant:
<syntaxhighlight lang="PHP">
$mymoduledir=DOL_DATA_ROOT.'/monmodule';
dol_mkdir($mymoduledir);
</syntaxhighlight>

Si vous avez besoin d'un répertoire qui contiendra des données temporaires, ce répertoire doit être''' DOL_DATA_ROOT.'/monmodule/temp''''

=Design patterns et programmation objet=

==Design patterns de Création (GoF)==
Design patterns définis par le Gang Of Four (voir la wikipédia sur les [[wikipedia:Patron de conception|Design patterns]]).
Dans Dolibarr, pas de mise en oeuvre de design patterns de comportement particulier.
On trouve des objets proches des Singletons et Fabriques conformes à 100% dans l'esprit mais pas dans la syntaxe, ceci afin d’être compatible avec la plus large plage possible de versions de PHP.

==Design patterns d'entreprises (Martin Fowler)==

===Mode d'organisation du code===
[[wikipedia:Martin_Fowler|Martin Fowler]] a identifié 3 méthodes d'organisation du code appelées '''patterns''' ('''motifs'''):

*Le '''Transaction Script''' (Le code est linéaire en fonction d'une action utilisateur).

C'est le motif à l'ancienne utilisé dans les langages procéduraux.
Inconvénient: Redondance du code. Nécessité de connaitre le modèle physique pour développer les parties métiers.

*Le '''Domain Model'''

C'est un concept possible depuis les langages objets. Ce sont les procédures métiers (qui doivent être identifiés avant) qui servent de bases pour les classes objets.
Inconvénient : Motif complexe à maintenir.

*Le '''Table Module'''

Un intermédiaire entre les 2 précédents où l'on a une instance unique de classe par table de la base de données.

-> Comme le montre les squelettes de code (voir point précédent), Dolibarr se base sur le principe du '''Table Module'''.

===Communication Logique métier - Données (ORM)===
Il existe 3 modes de liaisons:

*Le '''Table And Row Data Gateway'''

C'est le plus simple. On crée une classe par table et chaque classe est un pont avec la table correspondante et propose les méthodes CRUD sur cette table (Create, Read, Update, Delete). Une instance de classe étant alors un enregistrement de la table. La classe ne contient que du code d'accès aux lignes ou colonnes de tables. Le code métier doit alors être ajouté dans d'autres classes. Les liens entre ces classes tables et les classes métiers devant être connues ou déduites de la connaissance du développeur.

Exemple: C'est le mode mis en oeuvre quand on utilise certains Frameworks d'ORM comme '''iBatis''' (http://ibatis.apache.org/).

*Le '''Active Record'''

Identique au précédent, mais on se permet d'ajouter quelques fonctions métiers sur la classe, à condition que ces fonctions soient bien propres à la table ou à la notion métier portée par l'enregistrement. C'est le pattern qui offre le meilleur rapport fonctionnalité/complexité.

Exemple: C'est le mode choisi pour les développements Dolibarr et de nombreuses autres applications PHP qui ont leur propre framework et pratiques de développement.

*Le '''Data Mapper'''

Les classes représentent les entités du problème et non les données. Il faut donc doubler, tripler... ces classes avec des classes Mapper pour accéder aux données.
Plus "puriste" sur le papier car plus proche du métier, ce mode a aussi l'inconvénient d'être très complexe et difficile à maintenir dans la réalité (l'expérience pratique constatée ne rejoignant pas les promesses de la théorie).

Exemple: C'est le choix si on utilise le Framework d'ORM '''Propel''' (http://propel.phpdb.org/trac/). On le trouve donc sur des applications plus lourdes basées sur cet ORM entre autres.

-> Pour les développements Dolibarr, il est recommandé d'utiliser le mode de liaison '''Active Record''' qui offre les avantages d'un modèle proche du métier sans en avoir la complexité et sans trop masquer non plus la technique. C'est dans ce mode que le développement, la compréhension du code et la maintenance technique et/ou fonctionnelle semble la plus productive (ceci est toutefois un éternel débat entre les puristes et les pragmatiques, débat dans lequel personne ne peut vraiment avoir raison, car tout dépend des objectifs à atteindre).

==Design Pattern d'Interface Graphique (MVC)==
Il existe plusieurs design pattern pour les interfaces utilisateurs (MVC, MVP, MVVM).
Beaucoup confonde ce design pattern avec celui consistant à utiliser un framework de templates. C'est sans rapport. Un framework de template (voir point précédent) n'est en lien qu'avec la partie "V" de ces modèles.

-> Dolibarr utilise le Design Pattern '''MVC'''. La partie M est matérialisée par une classe DAO contenant les méthode CRUD (Create-Read-Update-Delete) d'accès à la table.
Beaucoup de frameworks ont fait le choix de mettre la partie de code C (Controller) et la partie de code du V (vue) dans des fichiers, voir même répertoires séparés. La maintenance semble plus aisé sur la papier, en pratique, il faut sans arrêt jonglé entre n fichiers, le C étant fortement lié au V. Aussi dans Dolibarr, la séparation est faite par une simple section de commentaire. La partie de code C (Controller) est donc le code qui se trouve sont la balise
<pre>
/*
* Actions
*/
</pre>
Elle est suivi par la partie de code V (Vue), bien séparé du C par la balise
<pre>
/*
* View
*/
</pre>

Ce mode de séparation a eu un effet neutre sur les nouveaux développement mais a permis de réduire de manière si importante le temps requis pour la maintenance et correction de bugs qu'il n'est pas envisagé de basculer vers un autre type de séparation (oui les constats fait dans la vraie vie ne sont pas toujours ceux attendus par la théorie scolaire). L'important reste qu'il y ait toujours séparation entre le C et le V, peut importe comment est matérialisé cette séparation, du moment qu'elle l'est (Rappel: Ne pas confondre la notion de séparation du C et du V avec la notion de séparation du code pour alimenter la données d'une Vue et du code pour formater la Vue, ceci un principe de séparation relevant du Design Pattern de Vue, voir point suivant).

==Design Pattern de Vue - Présentation==
Il existe des frameworks spécialisés dans le Design Pattern de Vue, la partie qui consiste à formater l'écran vue par l'utilisateur.
Les vieilles versions de Dolibarr utilisaient Smarty. Ce framework est une surcouche à un Framework, déjà très puissant, de formatage d'écran nommé... PHP. Les bénéfices étant très inférieurs aux inconvénients, il a été abandonné au profit de templates PHP (fichier .tpl.php) qui restent le plus simple, le plus universel, le plus évolutif et le plus performant, des frameworks de présentation.

Son seul défaut est qu'il ne peut garantir à 100% les écarts d'un développeur qui irait intégrer dans la Vue, une logique sans rapport avec la présentation (donc autre que du code à vocation de génération, de formatage, de sortie HTML, de logique de test ou de boucle). Ce point est toutefois contrôlé par le mécanisme de validation du code des chefs de projets.

La encore, c'est l'expérience et le constat "sur le terrain" d'un meilleur rendement de productivité qui a motivé l'abandon des frameworks de Présentation externes au profit du framework PHP.

Langages et normes

2022-06-27T07:23:43Z

Iouston:

[[en:Language_and_development_rules]]
[[de:Sprachen_und_Programmierregeln]]
[[es:Lenguaje_y_Normas_de_Desarrollo]]
[[zh:语言和开发规则]]


{{TemplateDocDev}}

Voici les quelques règles sur le langage, la syntaxe et normes de développement en vigueur pour le projet Dolibarr :

=Versions=

*Dolibarr doit fonctionner sur:

#Tous OS (Windows, Linux, MACOS...)
#PHP {{PHPMinVersion}} (Doit fonctionner sans aucun module PHP complémentaire hors les modules d'accès base de donnée).
#Mysql {{MySqlMinVersion}}

=Normes Copyright=

*Tout fichier PHP doit avoir un en-tête selon le masque suivant

<syntaxhighlight lang="PHP">
<?php
/* Copyright (C) YYYY John Doe <email@email.com>
*
* Licence information
*/
...
</syntaxhighlight>
Quand vous éditez un fichier existant du projet, ajouter une ligne Copyright sous celles existantes.

=Normes PHP=

==PHP==

*Dolibarr est écrit en PHP et supporte toutes versions PHP supérieures à la {{PHPMinVersion}}. Les fichiers doivent tous comporter l'extension .php

*L'appel aux variables superglobales PHP doit passer par les opérateurs dédiés $_COOKIES, $_SERVER, $_ENV. Mais pour récupérer les contenus de $_GET ou $_POST, il faut passer par la fonction dolibarr [[Fonctions utiles Dolibarr|GETPOST()]] .

Les autres opérateurs ($HTTP_SERVER_GET, ...) ayant été passés en deprecated au sein de PHP, ne doivent plus être utilisés. Ainsi le code doit fonctionner y compris quand l'option '''register_long_arrays''' est à off.
De plus, le code doit fonctionner aussi bien quand l'option PHP '''register_globals''' est à off (recommandé par PHP) que quand l'option '''register_globals''' est à on (par défaut sur de nombreuses installations).

*Pas d'utilisation de la variable '''PHP_SELF'''. Utiliser à la place $_SERVER["PHP_SELF"]. Notez aussi que le framework Dolibarr passe une routine pour rendre plus sûr le contenu du $_SERVER["PHP_SELF"] (dans le fichier main.inc.php, donc avant tout traitement métier)

*Quand plusieurs variables doivent être initialisées avec la même valeur, il faut utiliser plusieurs instructions:

<syntaxhighlight lang="PHP">
$var1 = 1; $var2 = 1; $var3 = 1;
</syntaxhighlight>
plutôt que
<syntaxhighlight lang="PHP">
$var1 = $var2 = $var3 = 1;
</syntaxhighlight>
qui est moins performant.

*Les chaines doivent avoir les variables sorties de la chaine.

<syntaxhighlight lang="PHP">
print "Mon texte affiche ma ".$variable." !\n";
</syntaxhighlight>

*Les commentaires doivent suivre la syntaxe C, ie un double antislash pour un commentaire d'une ligne et utilisation slash-étoile pour ouvrir un bloc de plusieurs lignes

<syntaxhighlight lang="PHP">
/* Bloc de commentaire
*
* Fin du bloc
*/

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

for ($i = 1 , $i < 2 ; $i++)
{
// commentaire sur une ligne
print $i;
}

</syntaxhighlight>

*Les fonctions doivent retourner une valeur strictement > à 0 en cas de succès, et un nombre < à 0 en cas d'erreur.

*Pas de code mort (non utilisé) dans le code principal de Dolibarr (le code utilisé uniquement par un module externe doit être inclus dans le module externe).

*Utiliser "include_once" pour l'inclusion de tout fichier contenant des définitions de fonction ou de classes (donc fichiers *.class.php et *.lib.php), utiliser "include" pour tout inclusion de fichier de type template ou contenant un mixte de HTML et PHP (donc fichiers *.inc.php et *.tpl.php).

*Le style de code a utiliser est le PSR-12 (https://www.php-fig.org/psr/psr-12/). Seules les règles "MUST" sont imposées. Notez aussi les points/exceptions suivants:
**La longueur des lignes: PSR-12 indique que la longueur des lignes a une limite "soft" à 120. Il est en effet préférable d'avoir de longues lignes de données de déclaration plutôt que de longues pages car ce code ne contient aucune logique intéressante ou utile, toutefois une limite "hard" a été instauré à '''1000''' caractères. Du code qui ira au delà provoquera des erreurs dans la plateforme d'Intégration Continue.
**Les tabulations sont acceptées : L'autre exception est qu'on ne remplace pas les tabulations systématiquement par des espaces. L'utilisation des tabulations simplifie la vie de certains développeurs. De plus, l'utilisation d'espaces rend certaines fonctions d'autoformatage défectueuses (comme sur certaines versions d'Eclipse, lors de copier-coller).
**Note 1: Les règles suivantes sont particulièrement importantes :
***Les fichiers doivent être sauvés en format Unix (LF) et non Windows (CR/LF). Le format Unix étant compatible sur les OS Unix like, Windows, Mac, alors que le format fichier texte Windows pose problème sous certains PHP sous Unix.
***Les smart tags PHP ne sont pas utilisés. Les sections de code doivent commencer par '''<?php'''
**Note 2: Vous pouvez utiliser le fichier '''dev/setup/codesniffer/ruleset.xml''' comme fichier de contrôle pour vérifier votre style de code avec PHPCodeSniffer.
**Note 3: Vous pouvez utiliser le fichier '''dev/setup/eclipse/PSR-12 [built-in].xml''' comme fichier de règles de syntax pour configurer Eclipse.
**Note 4: Vous remarquerez que le code actuel ne suit pas forcément tout cela. La raison est historique. La règle fut instaurée en cours de route, aussi, si vous trouvez du code non respectueux de ce standard, n'hésitez pas à le corriger.

==Structures des classes et champs==

Certaines propriétés de classes se retrouvent dans de nombreuses classes. Pour homogénéité, on utilisera les noms suivants:
{{TemplatePHPFields}}

=Normes SQL=

==Structure des tables et champs==

*Toutes les tables sont préfixées pour éviter les conflits de nommage. Aujourd'hui, le préfixe est modifiable au moment de l'installation. Sa valeur par défaut est <tt>llx_</tt>.

*Structure des tables.

Lorsque vous créez une table, il est recommandé de prendre les même conventions de nommages de tables que les autres tables Dolibarr. Avec, à minima les champs suivant:
- rowid INTEGER AUTO_INCREMENT PRIMARY KEY qui est l'id technique
- entity INTEGER default 1 that is id for the multicompany feature
- date_creation datetime that is the creation date
- tms timestamp qui sera un champ contenant la date de chaque mise à jour (la base de donnée le gère tout seul, pas besoin de le gérer par le code)
- import_key varchar(32) qui contiendra le code d'import YYYYMMDDHHMMSS si vous faites des imports en masse dans la table.
- status smallint pour stocker le status d'un object

Eventuellement
- fk_user_creat integer qui est l'id du user de création (fk_user_author also found)
- fk_user_modif integer qui est l'id du user de modification
- fk_user_valid integer qui est l'id du user de validation
- fk_soc integer qui est l'id du tiers (si applicable)

*Type des champs

Dans la pratique, afin d'être compatible avec toutes les précisions des pays, syntaxes des bases, on utilisera uniquement les types suivants:
- integer pour tout nombre entier, id ou clé étrangère (bigint éventuellement accepté pour les id des très grosses tables)
- smallint pour tout numérique entier de petite taille (comme pour stocker un code de status)
- double(24,8) pour tout montant
- double(6,3) pour les taux de tva
- real pour une quantité
- varchar pour une chaîne (y compris de longueur 1, le type char est de plus en plus déprécié)
- timestamp pour un champ date+heure devant être mis a jour automatiquement
- datetime pour un champ date+heure
- date pour un champ date

==Clé primaire==
La clé primaire d'une table s'appelle <tt>rowid</tt>.

Il y a quelques tables qui échappent à cette règle actuellement (ex [[Table llx_c_actioncomm]]), pour des raisons historiques. Une évolution pourra être étudiée pour une prochaine version.

==Clés étrangères==
Le nom d'une clé étrangère commence par le préfixe <tt>fk_</tt> suivi du nom de la table liée (requis pour éviter doublons globales à la base, problématiques sous certains SGBD comme postgresql) puis du champ lié (pour permettre plusieurs clés étrangères différentes sur une même table).

Exemple:
fk_facture_fourn_fk_soc

Note: Si vous développez votre propre module externe, il ne doit pas y avoir de clé étrangère depuis vos tables qui pointent sur les tables standards de Dolibarr. Ceci casserait les fonctionnalités de mise à jour, de réparation, de sauvegardes et de restauration.

==Clés alternatives==
Parfois, il n'y a pas que la clé primaire qui doit être unique. On peut donc ajouter aussi un index clé alternative unique. Un tel index est nommé par un nom qui commence par le préfixe <tt>uk_</tt> suivi du nom de la table (requis pour éviter doublons d'index globals à la base, problématiques sous certains SGBD comme postgresql) puis d'un suffixe qui caractérise la clé (pour permettre plusieurs index uniques sur une même table).

Exemple:
uk_societe_code_client

==Index performance==
Certains champs sont souvent utilisés comme critère de recherche, de tri ou de jointure. Il convient dans ce cas, d'y mettre un index de performance. De tels indexes seront nommés avec un préfix <tt>idx_</tt> puis le nom de la table et le nom du champ sur lequel porte l'index.

Exemple:
idx_societe_user_creat

==Format de fichier DDL==
Les fichiers qui contiennent la définition de la structure de la base (DDL) doivent être au nombre de 2 par tables:
Chaque table est définie dans son propre fichier dont le nom est <tt>llx_''matable''.sql</tt>.
On mettra un commentaire à côté de chaque champ pour en expliquer la signification.
Les clés étrangères et index de performance ou autres contraintes d'unicité sont définies dans un fichier séparé dont le nom est <tt>llx_''matable''.key.sql</tt>

Ces fichiers sont placés dans le répertoire '''install/mysql/tables''' pour les fichiers standards ou '''monmodule/tables''' pour les tables amenées par un module.

Exemple '''fichier table llx_matable.sql''':

<syntaxhighlight lang="sql">
-- ===========================================================================
-- Copyright (C) 2008 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 2 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_matable
(
rowid integer AUTO_INCREMENT PRIMARY KEY,
field_one integer,
field_two integer NOT NULL,
fk_field integer,
field_date datetime,
tms timestamp
)ENGINE=innodb;
</syntaxhighlight>

Exemple '''fichier clés/index llx_matable.key.sql''':

<syntaxhighlight lang="sql">
-- ===========================================================================
-- Copyright (C) 2008 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 2 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);
</syntaxhighlight>

==Règles de codage SQL==

*Utilisation des alias/nommage de champs

Dans le cas des select on pourra utiliser les alias pour simplifier l'écriture des requêtes:
<syntaxhighlight lang="sql">
select chp1, chpxxx2 as chp2 from table2 as t1, table2 as t2 where t1.chpx = t2.chpy
</syntaxhighlight>
Toutefois, il ne faut pas utiliser ces alias sur des requêtes update car non compatible avec mysql 3.1.

*Les SELECT * sont interdits ! Chaque SELECT doit spécifier la liste complète des champs à récupérer. Cela permet d'éviter les confusions. Exemple:

<syntaxhighlight lang="sql">
SELECT field_a, field_b, field_c FROM table_1 WHERE field_d = '$id'
</syntaxhighlight>

*Dans les requêtes SQL, on quote les champs mais pas les numériques qui contiennent des montants destinés à être stockés dans des champs de type double ou real. Les quotes sur les numériques de type float provoquent parfois un stockage d'une valeur différente. Par exemple 412.62 dans le insert sera en fait stocké avec la valeur 412.61999512 en base (suite à des conversions chaines-numériques implicites) si le champ est de type double(24,8). Et seul le PHP voit 412.61999512. Les autres outils verront 412.62 donnant l'impression qu'il n'y a pas de problème. Et c'est le PHP qui a raison, il y a problème en base. En supprimant les quotes sur les numériques, cela va mieux.

Exemple:
<syntaxhighlight lang="sql">
Bon: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', 412.62)
Mauvais: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', '412.62')
</syntaxhighlight>

Remarque, le problème des float est général et pas seulement sur les accès base, il est présent dans tous les languages quand on travaille sur des nombres réels, aussi ils doivent être, dès que affectés, nettoyés par la fonction price2num avec le 2eme paramètre renseigné à:
'MU' (si il s'agit d'un prix unitaire), 'MT' (s'il s'agit d'un prix total) ou 'MS' (autres cas) selon le besoin.
Voir aussi le chapitre "Les nombres réels, montants et calculs" plus bas.

*Les fonctions NOW, SYSDATE ou DATEDIFF sont interdites au sein des ordres SQL. S'il faut saisir la date du moment dans un champ, la valeur doit venir du PHP, par exemple par la fonction dol_now(), et non du moteur de base de données. Ceci afin d'avoir une meilleure portabilité du code mais surtout d'avoir une gestion correcte des TimeZone et ne pas dépendre du TimeZone de la base de donnée.

Par exemple, on ne fera pas:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield = NOW()";
</syntaxhighlight>
mais:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield = '".$this->db->idate(dol_now())."'";
</syntaxhighlight>

Par exemple, on ne fera pas:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where DATEDIFF(table.datefield, NOW()) > 7";
</syntaxhighlight>
mais:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield < '".$this->db->idate(dol_now() - (7 * 24 * 3600))."'";
</syntaxhighlight>

Un autre avantage de cette règle est que la requête peut bénéficier de l'utilisation de l'index puisqu'on compare datefield à une valeur fixe. Dans le cas du datediff, on applique un traitement sur le champ avant comparaison, rendant impossible l'utilisation de l'index de ce champ. Les conséquences sont des performances très dégradées par rapport à la version sans datediff.

==Règles de migration de base==

*Les scripts de migration de structure sont les fichiers de type '''install/mysql/migration/a.b.c-x.y.z.sql'''. Dans un fichier de migration de n vers n+1, on ne détruit une table (DROP TABLE) qui n'est plus utilisée en n+1 que lors de la migration de la version n+1 vers n+2. Ceci afin de toujours conserver les tables deprecated le temps d'une version pour réparer une situation en cas d'erreur de migration.

==Spécificités MySQL==

*Les tables doivent être au format InnoDB.

En effet, ce format gère les clés étrangères, les éventuelles restrictions qui y sont attachées et la notion d'intégrité de transactions requise pour avoir des données en base cohérente entre tables.

*Dolibarr DOIT fonctionner même avec les options '''strict''' de Mysql active.

Pour l'activer (fortement recommandé en développement), ajouter la ligne suivante dans le fichier config du serveur Mysql (my.cnf ou my.ini)
{{MySqlStrictMode}}

==Spécificités PostgreSQL==
Seuls les fichiers pour Mysql doivent être maintenus.
Les fichiers pour les autres bases sont convertis "à la volée" par le driver Dolibarr de la base.

Il existe une exception.
Les requêtes "UPDATE FROM" :
Syntax MySQL :
<syntaxhighlight lang="sql">
UPDATE table_taget as target, table_source as source SET fieldtarget=source.fieldsource
WHERE source.rowid=target.rowid;
</syntaxhighlight>

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

Il n'en existe pas dans Dolibarr, mais pour vos modules Vous devriez faire tel que :
<syntaxhighlight 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";
}
</syntaxhighlight>

=Normes HTML=

*Tous les attributs dans les balises HTML doivent être *en minuscule* et quotés avec des *doubles quote*.

*Les liens href doivent être absolus en se basant sur la fonction dol_buildpath() pour obtenir un chemin absolu depuis un chemin relatif au répertoire htdocs. Pour les tags img, il faut faire appel à la fonction img_picto().

Par example:
<syntaxhighlight lang="PHP">
print '<a href="'.dol_buildpath('/monrep/mapage.php').'">'.img_picto('Texte alt','nompictopng','').'</a>';
</syntaxhighlight>

*Les tables HTML doivent avoir des colonnes sans valeurs forcées, excepté pour les colonnes qui contiennent une information dont la longueur est non variable. Par exemple, une colonne avec un picto peut être forcée à with="20px". Dans les autres cas, il faut éviter de forcer la largeur des colonnes. La raison est que, dans la plupart des cas, le navigateur fait un meilleur travail pour définir automatiquement la bonne largeur des colonnes qu'en forçant manuellement les largeurs. Et ceci marche quelle que soit la résolution de l'écran.

*Le javascript/ajax et l'appel aux scripts java dans les pages php est à proscrire. Si toutefois du code javascript est inclus, il doit être conditionné par le test sur "$conf->use_javascript_ajax"

<syntaxhighlight lang="PHP">
if ($conf->use_javascript_ajax) {
... // Le code php qui génère du javascript est ici
}
</syntaxhighlight>

*Les popups windows ne doivent pas être utilisées, sauf pour des tooltips (et restent conditionnées par le point ci-dessus).

*Les scripts externes sont écrits en Perl s'ils ne peuvent l'être en php, l'utilisation d'un autre langage n'est pas interdit mais doit être discuté au préalable dans la mailing list des développeurs.

=Normes Dolibarr et squelettes de code=

==Squelettes de code==
Afin d'uniformiser le code et d'accélérer le développement de nouveaux composants dans Dolibarr, se trouvent dans le répertoire '''htdocs/modulebuilder/templates'''.

Par exemple:

*1 fichier qui sert d'exemple de descripteur de module: '''myModule.class.php'''
*1 fichier qui sert d'exemple de code pour faire une nouvelle classe: '''skeleton_class.class.php'''
*1 fichier qui sert d'exemple de code pour faire une nouvelle page: '''skeleton_page.php'''
*1 fichier qui sert d'exemple de code pour faire un script à exécuter en ligne de commande: '''skeleton_script.php'''

...

Servez-vous en comme exemple.
Notons que ces squelettes sont aussi utilisés par le générateur de code PHP ([[Module ModuleBuilder]]) qui est décrit dans la chapitre de développement de module Dolibarr pour accélérer vos développements.

==Les dates et TimeZone==
Dolibarr se veut une application multi-utilisateur et multi-localisation. Il convient donc de stocker les dates dans le bon format. Pour éviter les problèmes de conversion, les règles suivantes doivent être appliquées:

*Une date en mémoire doit être au format Timestamp GMT.
*Une date stockée en base de données contient le Timestamp issue de la date soumise dans la requête en heure locale du serveur PHP. Cela ne concerne pas les dates mises à jour automatiquement par la base (champ '''tms''' en base).

Ainsi le 1er janvier 1970, 3 heures à Paris (TZ=+1) = 1er janvier 1970, 2 heures à Greenwich (TZ=0) sera stocké en mémoire par 7200 et sera soumis à la base de données avec la chaine '19700101030000' (PHP convertit en heure de son TZ et la base déconvertit avec son TZ qui est le même que celui de PHP).

Les méthodes select doivent donc traduire les champs dates lus qui sont au format chaine TZ de la base ('19700101030000') par appel de la méthode db->jdate afin de récupérer une information en mémoire au format Timestamp GMT. Et les méthodes insert doivent lors de la génération de la requête convertir la date mémoire connue en variable, par la méthode db->idate (Voir exemples générés par le squelette).

*Les dates mises à jour automatiquement par la base (champ '''tms''' en base) contiennent le Timestamp où la modification est faite selon le timezone de la base de donnée. Les méthodes select récupèrent cette donnée en mémoire au format Timestamp GMT en appliquant également le db->jdate. Si le timezone de la base de donnée diffère de celui du PHP (un des 2 est mal réglé), il peut donc y avoir des écarts entre date de création et modification.

*La manipulation de dates en PHP doit être faite en utilisant les fonctions dates de Dolibarr: '''dol_now(), dol_mktime(), dol_stringtotime(), dol_getdate(), dol_time_plus_duree()'''. Vous trouverez également d'autres fonctions prêtes à l'emploi dans le fichier '''date.lib.php'''.

==L'encodage UTF8/ISO==
Dolibarr stocke les informations de manière suivante:

*En base de donnée, les données sont en UTF8 ou ISO. Cela dépend du pagecode de la base, donc des options à la création de cette base. Dans tous les cas le driver d'accès base Dolibarr (dans /lib/database) s'arrange à la lecture et insertion pour convertir vers et depuis de l'UTF8.
*Les données en mémoires sont donc stockées en UTF8 (instances d'objets PHP).
*Les pages web affichées à l'écran sont au format UTF8

==Les nombres réels, montants et calculs==
En PHP comme dans d'autres langages (Java par exemple), les données non entières (float, real, double) ne sont pas fiables.
Essayer de faire par exemple
<syntaxhighlight lang="PHP">
print 239.2 - 229.3 - 9.9;
</syntaxhighlight>
Vous n'obtiendrez pas zéro mais un nombre très petit en puissance de 10 négative. Si vous obtenez zéro, vous pourrez trouvez d'autres exemples qui ne fonctionnent pas.
Le problème des float est général, une variable résultante de calcul de nombre réels doit SYSTEMATIQUEMENT être nettoyée par la fonction '''price2num()''' avec le 2eme paramètre renseigné à: 'MU', 'MT' ou 'MS' selon le besoin (voir doc fonction).
<syntaxhighlight lang="PHP">
print price2num(239.2 - 229.3 - 9.9, 'MT');
</syntaxhighlight>
S'il ne s'agit pas d'un prix sur lequel s'adapte les paramètres MU, MT ou MS, il faut utiliser la fonction '''round()'''.

==Création de tables==
Ne pas créer de table à l'utilisation, c'est-à-dire à la '''première utilisation''' du module.
Si vous créez un module qui utilise des tables qui ne sont pas intégrées en standard dans le code de Dolibarr, veillez à suivre le didacticiel [[Développement module]] qui explique comment joindre des tables qui se créent à l'activation du module et non à son utilisation (voir plus haut).

==Comparer la version==

Si votre code a besoin de faire des choses différentes selon la version de Dolibarr, vous pouvez utiliser le truc suivant pour comparer les versions

<syntaxhighlight lang="PHP">
$version=preg_split('/[\.-]/',DOL_VERSION);
if (versioncompare($version,array(5,0,-4)) >= 0) { //mycode for 5.0 only; } // For dolibarr 5.0.* (the -4 means we include also alpha, beta, rc and rcX)
</syntaxhighlight>

Mais cette solution requiert de faire un include avoir la fonction versioncompare. Une alternative est d'utiliser le test suivant :
<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

Il également possible de faire appel à la fonction version_compare de php, ce qui donne ici :

<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

 

==Logs==
Ajouter des traces dans votre code avec la fonction
<syntaxhighlight lang="PHP">
dol_syslog($yourmessage, LOG_INFO|LOG_DEBUG|LOG_WARNING|LOG_ERR);
</syntaxhighlight>

==Répertoires de travail==
Si vous avez besoin de créer un répertoire de travail, dans votre code, faites référence à ce répertoire par
'''DOL_DATA_ROOT.'/monmodule''''

Le répertoire peut être créé dans votre code à l'exécution par le code suivant:
<syntaxhighlight lang="PHP">
$mymoduledir=DOL_DATA_ROOT.'/monmodule';
dol_mkdir($mymoduledir);
</syntaxhighlight>

Si vous avez besoin d'un répertoire qui contiendra des données temporaires, ce répertoire doit être''' DOL_DATA_ROOT.'/monmodule/temp''''

=Design patterns et programmation objet=

==Design patterns de Création (GoF)==
Design patterns définis par le Gang Of Four (voir la wikipédia sur les [[wikipedia:Patron de conception|Design patterns]]).
Dans Dolibarr, pas de mise en oeuvre de design patterns de comportement particulier.
On trouve des objets proches des Singletons et Fabriques conformes à 100% dans l'esprit mais pas dans la syntaxe, ceci afin d’être compatible avec la plus large plage possible de versions de PHP.

==Design patterns d'entreprises (Martin Fowler)==

===Mode d'organisation du code===
[[wikipedia:Martin_Fowler|Martin Fowler]] a identifié 3 méthodes d'organisation du code appelées '''patterns''' ('''motifs'''):

*Le '''Transaction Script''' (Le code est linéaire en fonction d'une action utilisateur).

C'est le motif à l'ancienne utilisé dans les langages procéduraux.
Inconvénient: Redondance du code. Nécessité de connaitre le modèle physique pour développer les parties métiers.

*Le '''Domain Model'''

C'est un concept possible depuis les langages objets. Ce sont les procédures métiers (qui doivent être identifiés avant) qui servent de bases pour les classes objets.
Inconvénient : Motif complexe à maintenir.

*Le '''Table Module'''

Un intermédiaire entre les 2 précédents où l'on a une instance unique de classe par table de la base de données.

-> Comme le montre les squelettes de code (voir point précédent), Dolibarr se base sur le principe du '''Table Module'''.

===Communication Logique métier - Données (ORM)===
Il existe 3 modes de liaisons:

*Le '''Table And Row Data Gateway'''

C'est le plus simple. On crée une classe par table et chaque classe est un pont avec la table correspondante et propose les méthodes CRUD sur cette table (Create, Read, Update, Delete). Une instance de classe étant alors un enregistrement de la table. La classe ne contient que du code d'accès aux lignes ou colonnes de tables. Le code métier doit alors être ajouté dans d'autres classes. Les liens entre ces classes tables et les classes métiers devant être connues ou déduites de la connaissance du développeur.

Exemple: C'est le mode mis en oeuvre quand on utilise certains Frameworks d'ORM comme '''iBatis''' (http://ibatis.apache.org/).

*Le '''Active Record'''

Identique au précédent, mais on se permet d'ajouter quelques fonctions métiers sur la classe, à condition que ces fonctions soient bien propres à la table ou à la notion métier portée par l'enregistrement. C'est le pattern qui offre le meilleur rapport fonctionnalité/complexité.

Exemple: C'est le mode choisi pour les développements Dolibarr et de nombreuses autres applications PHP qui ont leur propre framework et pratiques de développement.

*Le '''Data Mapper'''

Les classes représentent les entités du problème et non les données. Il faut donc doubler, tripler... ces classes avec des classes Mapper pour accéder aux données.
Plus "puriste" sur le papier car plus proche du métier, ce mode a aussi l'inconvénient d'être très complexe et difficile à maintenir dans la réalité (l'expérience pratique constatée ne rejoignant pas les promesses de la théorie).

Exemple: C'est le choix si on utilise le Framework d'ORM '''Propel''' (http://propel.phpdb.org/trac/). On le trouve donc sur des applications plus lourdes basées sur cet ORM entre autres.

-> Pour les développements Dolibarr, il est recommandé d'utiliser le mode de liaison '''Active Record''' qui offre les avantages d'un modèle proche du métier sans en avoir la complexité et sans trop masquer non plus la technique. C'est dans ce mode que le développement, la compréhension du code et la maintenance technique et/ou fonctionnelle semble la plus productive (ceci est toutefois un éternel débat entre les puristes et les pragmatiques, débat dans lequel personne ne peut vraiment avoir raison, car tout dépend des objectifs à atteindre).

==Design Pattern d'Interface Graphique (MVC)==
Il existe plusieurs design pattern pour les interfaces utilisateurs (MVC, MVP, MVVM).
Beaucoup confonde ce design pattern avec celui consistant à utiliser un framework de templates. C'est sans rapport. Un framework de template (voir point précédent) n'est en lien qu'avec la partie "V" de ces modèles.

-> Dolibarr utilise le Design Pattern '''MVC'''. La partie M est matérialisée par une classe DAO contenant les méthode CRUD (Create-Read-Update-Delete) d'accès à la table.
Beaucoup de frameworks ont fait le choix de mettre la partie de code C (Controller) et la partie de code du V (vue) dans des fichiers, voir même répertoires séparés. La maintenance semble plus aisé sur la papier, en pratique, il faut sans arrêt jonglé entre n fichiers, le C étant fortement lié au V. Aussi dans Dolibarr, la séparation est faite par une simple section de commentaire. La partie de code C (Controller) est donc le code qui se trouve sont la balise
<pre>
/*
* Actions
*/
</pre>
Elle est suivi par la partie de code V (Vue), bien séparé du C par la balise
<pre>
/*
* View
*/
</pre>

Ce mode de séparation a eu un effet neutre sur les nouveaux développement mais a permis de réduire de manière si importante le temps requis pour la maintenance et correction de bugs qu'il n'est pas envisagé de basculer vers un autre type de séparation (oui les constats fait dans la vraie vie ne sont pas toujours ceux attendus par la théorie scolaire). L'important reste qu'il y ait toujours séparation entre le C et le V, peut importe comment est matérialisé cette séparation, du moment qu'elle l'est (Rappel: Ne pas confondre la notion de séparation du C et du V avec la notion de séparation du code pour alimenter la données d'une Vue et du code pour formater la Vue, ceci un principe de séparation relevant du Design Pattern de Vue, voir point suivant).

==Design Pattern de Vue - Présentation==
Il existe des frameworks spécialisés dans le Design Pattern de Vue, la partie qui consiste à formater l'écran vue par l'utilisateur.
Les vieilles versions de Dolibarr utilisaient Smarty. Ce framework est une surcouche à un Framework, déjà très puissant, de formatage d'écran nommé... PHP. Les bénéfices étant très inférieurs aux inconvénients, il a été abandonné au profit de templates PHP (fichier .tpl.php) qui restent le plus simple, le plus universel, le plus évolutif et le plus performant, des frameworks de présentation.

Son seul défaut est qu'il ne peut garantir à 100% les écarts d'un développeur qui irait intégrer dans la Vue, une logique sans rapport avec la présentation (donc autre que du code à vocation de génération, de formatage, de sortie HTML, de logique de test ou de boucle). Ce point est toutefois contrôlé par le mécanisme de validation du code des chefs de projets.

La encore, c'est l'expérience et le constat "sur le terrain" d'un meilleur rendement de productivité qui a motivé l'abandon des frameworks de Présentation externes au profit du framework PHP.

Langages et normes

2022-06-27T07:22:33Z

Iouston:

[[en:Language_and_development_rules]]
[[de:Sprachen_und_Programmierregeln]]
[[es:Lenguaje_y_Normas_de_Desarrollo]]
[[zh:语言和开发规则]]


{{TemplateDocDev}}

Voici les quelques règles sur le langage, la syntaxe et normes de développement en vigueur pour le projet Dolibarr :

=Versions=

*Dolibarr doit fonctionner sur:

#Tous OS (Windows, Linux, MACOS...)
#PHP {{PHPMinVersion}} (Doit fonctionner sans aucun module PHP complémentaire hors les modules d'accès base de donnée).
#Mysql {{MySqlMinVersion}}

=Normes Copyright=

*Tout fichier PHP doit avoir un en-tête selon le masque suivant

<syntaxhighlight lang="PHP">
<?php
/* Copyright (C) YYYY John Doe <email@email.com>
*
* Licence information
*/
...
</syntaxhighlight>
Quand vous éditez un fichier existant du projet, ajouter une ligne Copyright sous celles existantes.

=Normes PHP=

==PHP==

*Dolibarr est écrit en PHP et supporte toutes versions PHP supérieures à la {{PHPMinVersion}}. Les fichiers doivent tous comporter l'extension .php

*L'appel aux variables superglobales PHP doit passer par les opérateurs dédiés $_COOKIES, $_SERVER, $_ENV. Mais pour récupérer les contenus de $_GET ou $_POST, il faut passer par la fonction dolibarr [[Fonctions utiles Dolibarr|GETPOST()]] .

Les autres opérateurs ($HTTP_SERVER_GET, ...) ayant été passés en deprecated au sein de PHP, ne doivent plus être utilisés. Ainsi le code doit fonctionner y compris quand l'option '''register_long_arrays''' est à off.
De plus, le code doit fonctionner aussi bien quand l'option PHP '''register_globals''' est à off (recommandé par PHP) que quand l'option '''register_globals''' est à on (par défaut sur de nombreuses installations).

*Pas d'utilisation de la variable '''PHP_SELF'''. Utiliser à la place $_SERVER["PHP_SELF"]. Notez aussi que le framework Dolibarr passe une routine pour rendre plus sûr le contenu du $_SERVER["PHP_SELF"] (dans le fichier main.inc.php, donc avant tout traitement métier)

*Quand plusieurs variables doivent être initialisées avec la même valeur, il faut utiliser plusieurs instructions:

<syntaxhighlight lang="PHP">
$var1 = 1; $var2 = 1; $var3 = 1;
</syntaxhighlight>
plutôt que
<syntaxhighlight lang="PHP">
$var1 = $var2 = $var3 = 1;
</syntaxhighlight>
qui est moins performant.

*Les chaines doivent avoir les variables sorties de la chaine.

<syntaxhighlight lang="PHP">
print "Mon texte affiche ma ".$variable." !\n";
</syntaxhighlight>

*Les commentaires doivent suivre la syntaxe C, ie un double antislash pour un commentaire d'une ligne et utilisation slash-étoile pour ouvrir un bloc de plusieurs lignes

<syntaxhighlight lang="PHP">
/* Bloc de commentaire
*
* Fin du bloc
*/

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

for ($i = 1 , $i < 2 ; $i++)
{
// commentaire sur une ligne
print $i;
}

</syntaxhighlight>

*Les fonctions doivent retourner une valeur strictement > à 0 en cas de succès, et un nombre < à 0 en cas d'erreur.

*Pas de code mort (non utilisé) dans le code principal de Dolibarr (le code utilisé uniquement par un module externe doit être inclus dans le module externe).

*Utiliser "include_once" pour l'inclusion de tout fichier contenant des définitions de fonction ou de classes (donc fichiers *.class.php et *.lib.php), utiliser "include" pour tout inclusion de fichier de type template ou contenant un mixte de HTML et PHP (donc fichiers *.inc.php et *.tpl.php).

*Le style de code a utiliser est le PSR-12 (https://www.php-fig.org/psr/psr-12/). Seules les règles "MUST" sont imposées. Notez aussi les points/exceptions suivants:
**La longueur des lignes: PSR-12 indique que la longueur des lignes a une limite "soft" à 120. Il est en effet préférable d'avoir de longues lignes de données de déclaration plutôt que de longues pages car ce code ne contient aucune logique intéressante ou utile, toutefois une limite "hard" a été instauré à '''1000''' caractères. Du code qui ira au delà provoquera des erreurs dans la plateforme d'Intégration Continue.
**Les tabulations sont acceptées : L'autre exception est qu'on ne remplace pas les tabulations systématiquement par des espaces. L'utilisation des tabulations simplifie la vie de certains développeurs. De plus, l'utilisation d'espaces rend certaines fonctions d'autoformatage défectueuses (comme sur certaines versions d'Eclipse, lors de copier-coller).
**Note 1: Les règles suivantes sont particulièrement importantes :
***Les fichiers doivent être sauvés en format Unix (LF) et non Windows (CR/LF). Le format Unix étant compatible sur les OS Unix like, Windows, Mac, alors que le format fichier texte Windows pose problème sous certains PHP sous Unix.
***Les smart tags PHP ne sont pas utilisés. Les sections de code doivent commencer par '''<?php'''
**Note 2: Vous pouvez utiliser le fichier '''dev/setup/codesniffer/ruleset.xml''' comme fichier de contrôle pour vérifier votre style de code avec PHPCodeSniffer.
**Note 3: Vous pouvez utiliser le fichier '''dev/setup/eclipse/PSR-12 [built-in].xml''' comme fichier de règles de syntax pour configurer Eclipse.
**Note 4: Vous remarquerez que le code actuel ne suit pas forcément tout cela. La raison est historique. La règle fut instaurée en cours de route, aussi, si vous trouvez du code non respectueux de ce standard, n'hésitez pas à le corriger.

==Structures des classes et champs==

Certaines propriétés de classes se retrouvent dans de nombreuses classes. Pour homogénéité, on utilisera les noms suivants:
{{TemplatePHPFields}}

=Normes SQL=

==Structure des tables et champs==

*Toutes les tables sont préfixées pour éviter les conflits de nommage. Aujourd'hui, le préfixe est modifiable au moment de l'installation. Sa valeur par défaut est <tt>llx_</tt>.

*Structure des tables.

Lorsque vous créez une table, il est recommandé de prendre les même conventions de nommages de tables que les autres tables Dolibarr. Avec, à minima les champs suivant:
- rowid INTEGER AUTO_INCREMENT PRIMARY KEY qui est l'id technique
- entity INTEGER default 1 that is id for the multicompany feature
- date_creation datetime that is the creation date
- tms timestamp qui sera un champ contenant la date de chaque mise à jour (la base de donnée le gère tout seul, pas besoin de le gérer par le code)
- import_key varchar(32) qui contiendra le code d'import YYYYMMDDHHMMSS si vous faites des imports en masse dans la table.
- status smallint pour stocker le status d'un object

Eventuellement
- fk_user_creat integer qui est l'id du user de création (fk_user_author also found)
- fk_user_modif integer qui est l'id du user de modification
- fk_user_valid integer qui est l'id du user de validation
- fk_soc integer qui est l'id du tiers (si applicable)

*Type des champs

Dans la pratique, afin d'être compatible avec toutes les précisions des pays, syntaxes des bases, on utilisera uniquement les types suivants:
- integer pour tout nombre entier, id ou clé étrangère (bigint éventuellement accepté pour les id des très grosses tables)
- smallint pour tout numérique entier de petite taille (comme pour stocker un code de status)
- double(24,8) pour tout montant
- double(6,3) pour les taux de tva
- real pour une quantité
- varchar pour une chaîne (y compris de longueur 1, le type char est de plus en plus déprécié)
- timestamp pour un champ date+heure devant être mis a jour automatiquement
- datetime pour un champ date+heure
- date pour un champ date

==Clé primaire==
La clé primaire d'une table s'appelle <tt>rowid</tt>.

Il y a quelques tables qui échappent à cette règle actuellement (ex [[Table llx_c_actioncomm]]), pour des raisons historiques. Une évolution pourra être étudiée pour une prochaine version.

==Clés étrangères==
Le nom d'une clé étrangère commence par le préfixe <tt>fk_</tt> suivi du nom de la table liée (requis pour éviter doublons globales à la base, problématiques sous certains SGBD comme postgresql) puis du champ lié (pour permettre plusieurs clés étrangères différentes sur une même table).

Exemple:
fk_facture_fourn_fk_soc

Note: Si vous développez votre propre module externe, il ne doit pas y avoir de clé étrangère depuis vos tables qui pointent sur les tables standards de Dolibarr. Ceci casserait les fonctionnalités de mise à jour, de réparation, de sauvegardes et de restauration.

==Clés alternatives==
Parfois, il n'y a pas que la clé primaire qui doit être unique. On peut donc ajouter aussi un index clé alternative unique. Un tel index est nommé par un nom qui commence par le préfixe <tt>uk_</tt> suivi du nom de la table (requis pour éviter doublons d'index globals à la base, problématiques sous certains SGBD comme postgresql) puis d'un suffixe qui caractérise la clé (pour permettre plusieurs index uniques sur une même table).

Exemple:
uk_societe_code_client

==Index performance==
Certains champs sont souvent utilisés comme critère de recherche, de tri ou de jointure. Il convient dans ce cas, d'y mettre un index de performance. De tels indexes seront nommés avec un préfix <tt>idx_</tt> puis le nom de la table et le nom du champ sur lequel porte l'index.

Exemple:
idx_societe_user_creat

==Format de fichier DDL==
Les fichiers qui contiennent la définition de la structure de la base (DDL) doivent être au nombre de 2 par tables:
Chaque table est définie dans son propre fichier dont le nom est <tt>llx_''matable''.sql</tt>.
On mettra un commentaire à côté de chaque champ pour en expliquer la signification.
Les clés étrangères et index de performance ou autres contraintes d'unicité sont définies dans un fichier séparé dont le nom est <tt>llx_''matable''.key.sql</tt>

Ces fichiers sont placés dans le répertoire '''install/mysql/tables''' pour les fichiers standards ou '''monmodule/tables''' pour les tables amenées par un module.

Exemple '''fichier table llx_matable.sql''':

<syntaxhighlight lang="sql">
-- ===========================================================================
-- Copyright (C) 2008 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 2 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_matable
(
rowid integer AUTO_INCREMENT PRIMARY KEY,
field_one integer,
field_two integer NOT NULL,
fk_field integer,
field_date datetime,
tms timestamp
)ENGINE=innodb;
</syntaxhighlight>

Exemple '''fichier clés/index llx_matable.key.sql''':

<syntaxhighlight lang="sql">
-- ===========================================================================
-- Copyright (C) 2008 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 2 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);
</syntaxhighlight>

==Règles de codage SQL==

*Utilisation des alias/nommage de champs

Dans le cas des select on pourra utiliser les alias pour simplifier l'écriture des requêtes:
<syntaxhighlight lang="sql">
select chp1, chpxxx2 as chp2 from table2 as t1, table2 as t2 where t1.chpx = t2.chpy
</syntaxhighlight>
Toutefois, il ne faut pas utiliser ces alias sur des requêtes update car non compatible avec mysql 3.1.

*Les SELECT * sont interdits ! Chaque SELECT doit spécifier la liste complète des champs à récupérer. Cela permet d'éviter les confusions. Exemple:

<syntaxhighlight lang="sql">
SELECT field_a, field_b, field_c FROM table_1 WHERE field_d = '$id'
</syntaxhighlight>

*Dans les requêtes SQL, on quote les champs mais pas les numériques qui contiennent des montants destinés à être stockés dans des champs de type double ou real. Les quotes sur les numériques de type float provoquent parfois un stockage d'une valeur différente. Par exemple 412.62 dans le insert sera en fait stocké avec la valeur 412.61999512 en base (suite à des conversions chaines-numériques implicites) si le champ est de type double(24,8). Et seul le PHP voit 412.61999512. Les autres outils verront 412.62 donnant l'impression qu'il n'y a pas de problème. Et c'est le PHP qui a raison, il y a problème en base. En supprimant les quotes sur les numériques, cela va mieux.

Exemple:
<syntaxhighlight lang="sql">
Bon: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', 412.62)
Mauvais: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', '412.62')
</syntaxhighlight>

Remarque, le problème des float est général et pas seulement sur les accès base, il est présent dans tous les languages quand on travaille sur des nombres réels, aussi ils doivent être, dès que affectés, nettoyés par la fonction price2num avec le 2eme paramètre renseigné à:
'MU' (si il s'agit d'un prix unitaire), 'MT' (s'il s'agit d'un prix total) ou 'MS' (autres cas) selon le besoin.
Voir aussi le chapitre "Les nombres réels, montants et calculs" plus bas.

*Les fonctions NOW, SYSDATE ou DATEDIFF sont interdites au sein des ordres SQL. S'il faut saisir la date du moment dans un champ, la valeur doit venir du PHP, par exemple par la fonction dol_now(), et non du moteur de base de données. Ceci afin d'avoir une meilleure portabilité du code mais surtout d'avoir une gestion correcte des TimeZone et ne pas dépendre du TimeZone de la base de donnée.

Par exemple, on ne fera pas:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield = NOW()";
</syntaxhighlight>
mais:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield = '".$this->db->idate(dol_now())."'";
</syntaxhighlight>

Par exemple, on ne fera pas:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where DATEDIFF(table.datefield, NOW()) > 7";
</syntaxhighlight>
mais:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield < '".$this->db->idate(dol_now() - (7 * 24 * 3600))."'";
</syntaxhighlight>

Un autre avantage de cette règle est que la requête peut bénéficier de l'utilisation de l'index puisqu'on compare datefield à une valeur fixe. Dans le cas du datediff, on applique un traitement sur le champ avant comparaison, rendant impossible l'utilisation de l'index de ce champ. Les conséquences sont des performances très dégradées par rapport à la version sans datediff.

==Règles de migration de base==

*Les scripts de migration de structure sont les fichiers de type '''install/mysql/migration/a.b.c-x.y.z.sql'''. Dans un fichier de migration de n vers n+1, on ne détruit une table (DROP TABLE) qui n'est plus utilisée en n+1 que lors de la migration de la version n+1 vers n+2. Ceci afin de toujours conserver les tables deprecated le temps d'une version pour réparer une situation en cas d'erreur de migration.

==Spécificités MySQL==

*Les tables doivent être au format InnoDB.

En effet, ce format gère les clés étrangères, les éventuelles restrictions qui y sont attachées et la notion d'intégrité de transactions requise pour avoir des données en base cohérente entre tables.

*Dolibarr DOIT fonctionner même avec les options '''strict''' de Mysql active.

Pour l'activer (fortement recommandé en développement), ajouter la ligne suivante dans le fichier config du serveur Mysql (my.cnf ou my.ini)
{{MySqlStrictMode}}

==Spécificités PostgreSQL==
Seuls les fichiers pour Mysql doivent être maintenus.
Les fichiers pour les autres bases sont convertis "à la volée" par le driver Dolibarr de la base.

Il existe une exception.
Les requêtes "UPDATE FROM" :
Syntax MySQL :
<syntaxhighlight lang="sql">
UPDATE table_taget as target, table_source as source SET fieldtarget=source.fieldsource
WHERE source.rowid=target.rowid;
</syntaxhighlight>

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

Il n'en existe pas dans Dolibarr, mais pour vos modules Vous devriez faire tel que :
<syntaxhighlight 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";
}
</syntaxhighlight>

=Normes HTML=

*Tous les attributs dans les balises HTML doivent être *en minuscule* et quotés avec des *doubles quote*.

*Les liens href doivent être absolus en se basant sur la fonction dol_buildpath() pour obtenir un chemin absolu depuis un chemin relatif au répertoire htdocs. Pour les tags img, il faut faire appel à la fonction img_picto().

Par example:
<syntaxhighlight lang="PHP">
print '<a href="'.dol_buildpath('/monrep/mapage.php').'">'.img_picto('Texte alt','nompictopng','').'</a>';
</syntaxhighlight>

*Les tables HTML doivent avoir des colonnes sans valeurs forcées, excepté pour les colonnes qui contiennent une information dont la longueur est non variable. Par exemple, une colonne avec un picto peut être forcée à with="20px". Dans les autres cas, il faut éviter de forcer la largeur des colonnes. La raison est que, dans la plupart des cas, le navigateur fait un meilleur travail pour définir automatiquement la bonne largeur des colonnes qu'en forçant manuellement les largeurs. Et ceci marche quelle que soit la résolution de l'écran.

*Le javascript/ajax et l'appel aux scripts java dans les pages php est à proscrire. Si toutefois du code javascript est inclus, il doit être conditionné par le test sur "$conf->use_javascript_ajax"

<syntaxhighlight lang="PHP">
if ($conf->use_javascript_ajax) {
... // Le code php qui génère du javascript est ici
}
</syntaxhighlight>

*Les popups windows ne doivent pas être utilisées, sauf pour des tooltips (et restent conditionnées par le point ci-dessus).

*Les scripts externes sont écrits en Perl s'ils ne peuvent l'être en php, l'utilisation d'un autre langage n'est pas interdit mais doit être discuté au préalable dans la mailing list des développeurs.

=Normes Dolibarr et squelettes de code=

==Squelettes de code==
Afin d'uniformiser le code et d'accélérer le développement de nouveaux composants dans Dolibarr, se trouvent dans le répertoire '''htdocs/modulebuilder/templates'''.

Par exemple:

*1 fichier qui sert d'exemple de descripteur de module: '''myModule.class.php'''
*1 fichier qui sert d'exemple de code pour faire une nouvelle classe: '''skeleton_class.class.php'''
*1 fichier qui sert d'exemple de code pour faire une nouvelle page: '''skeleton_page.php'''
*1 fichier qui sert d'exemple de code pour faire un script à exécuter en ligne de commande: '''skeleton_script.php'''

...

Servez-vous en comme exemple.
Notons que ces squelettes sont aussi utilisés par le générateur de code PHP ([[Module ModuleBuilder]]) qui est décrit dans la chapitre de développement de module Dolibarr pour accélérer vos développements.

==Les dates et TimeZone==
Dolibarr se veut une application multi-utilisateur et multi-localisation. Il convient donc de stocker les dates dans le bon format. Pour éviter les problèmes de conversion, les règles suivantes doivent être appliquées:

*Une date en mémoire doit être au format Timestamp GMT.
*Une date stockée en base de données contient le Timestamp issue de la date soumise dans la requête en heure locale du serveur PHP. Cela ne concerne pas les dates mises à jour automatiquement par la base (champ '''tms''' en base).

Ainsi le 1er janvier 1970, 3 heures à Paris (TZ=+1) = 1er janvier 1970, 2 heures à Greenwich (TZ=0) sera stocké en mémoire par 7200 et sera soumis à la base de données avec la chaine '19700101030000' (PHP convertit en heure de son TZ et la base déconvertit avec son TZ qui est le même que celui de PHP).

Les méthodes select doivent donc traduire les champs dates lus qui sont au format chaine TZ de la base ('19700101030000') par appel de la méthode db->jdate afin de récupérer une information en mémoire au format Timestamp GMT. Et les méthodes insert doivent lors de la génération de la requête convertir la date mémoire connue en variable, par la méthode db->idate (Voir exemples générés par le squelette).

*Les dates mises à jour automatiquement par la base (champ '''tms''' en base) contiennent le Timestamp où la modification est faite selon le timezone de la base de donnée. Les méthodes select récupèrent cette donnée en mémoire au format Timestamp GMT en appliquant également le db->jdate. Si le timezone de la base de donnée diffère de celui du PHP (un des 2 est mal réglé), il peut donc y avoir des écarts entre date de création et modification.

*La manipulation de dates en PHP doit être faite en utilisant les fonctions dates de Dolibarr: '''dol_now(), dol_mktime(), dol_stringtotime(), dol_getdate(), dol_time_plus_duree()'''. Vous trouverez également d'autres fonctions prêtes à l'emploi dans le fichier '''date.lib.php'''.

==L'encodage UTF8/ISO==
Dolibarr stocke les informations de manière suivante:

*En base de donnée, les données sont en UTF8 ou ISO. Cela dépend du pagecode de la base, donc des options à la création de cette base. Dans tous les cas le driver d'accès base Dolibarr (dans /lib/database) s'arrange à la lecture et insertion pour convertir vers et depuis de l'UTF8.
*Les données en mémoires sont donc stockées en UTF8 (instances d'objets PHP).
*Les pages web affichées à l'écran sont au format UTF8

==Les nombres réels, montants et calculs==
En PHP comme dans d'autres langages (Java par exemple), les données non entières (float, real, double) ne sont pas fiables.
Essayer de faire par exemple
<syntaxhighlight lang="PHP">
print 239.2 - 229.3 - 9.9;
</syntaxhighlight>
Vous n'obtiendrez pas zéro mais un nombre très petit en puissance de 10 négative. Si vous obtenez zéro, vous pourrez trouvez d'autres exemples qui ne fonctionnent pas.
Le problème des float est général, une variable résultante de calcul de nombre réels doit SYSTEMATIQUEMENT être nettoyée par la fonction '''price2num()''' avec le 2eme paramètre renseigné à: 'MU', 'MT' ou 'MS' selon le besoin (voir doc fonction).
<syntaxhighlight lang="PHP">
print price2num(239.2 - 229.3 - 9.9, 'MT');
</syntaxhighlight>
S'il ne s'agit pas d'un prix sur lequel s'adapte les paramètres MU, MT ou MS, il faut utiliser la fonction '''round()'''.

==Création de tables==
Ne pas créer de table à l'utilisation, c'est-à-dire à la '''première utilisation''' du module.
Si vous créez un module qui utilise des tables qui ne sont pas intégrées en standard dans le code de Dolibarr, veillez à suivre le didacticiel [[Développement module]] qui explique comment joindre des tables qui se créent à l'activation du module et non à son utilisation (voir plus haut).

==Comparer la version==

Si votre code a besoin de faire des choses différentes selon la version de Dolibarr, vous pouvez utiliser le truc suivant pour comparer les versions

<syntaxhighlight lang="PHP">
$version=preg_split('/[\.-]/',DOL_VERSION);
if (versioncompare($version,array(5,0,-4)) >= 0) { //mycode for 5.0 only; } // For dolibarr 5.0.* (the -4 means we include also alpha, beta, rc and rcX)
</syntaxhighlight>

Mais cette solution requiert de faire un include avoir la fonction versioncompare. Une alternative est d'utiliser le test suivant :
<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

Il également possible de faire appel à la fonction version_compare de php, ce qui donne ici :

<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

 

==Logs==
Ajouter des traces dans votre code avec la fonction
<syntaxhighlight lang="PHP">
dol_syslog($yourmessage, LOG_INFO|LOG_DEBUG|LOG_WARNING|LOG_ERR);
</syntaxhighlight>

==Répertoires de travail==
Si vous avez besoin de créer un répertoire de travail, dans votre code, faites référence à ce répertoire par
'''DOL_DATA_ROOT.'/monmodule''''

Le répertoire peut être créé dans votre code à l'exécution par le code suivant:
<syntaxhighlight lang="PHP">
$mymoduledir=DOL_DATA_ROOT.'/monmodule';
dol_mkdir($mymoduledir);
</syntaxhighlight>

Si vous avez besoin d'un répertoire qui contiendra des données temporaires, ce répertoire doit être''' DOL_DATA_ROOT.'/monmodule/temp''''

=Design patterns et programmation objet=

==Design patterns de Création (GoF)==
Design patterns définis par le Gang Of Four (voir la wikipédia sur les [[wikipedia:Patron de conception|Design patterns]]).
Dans Dolibarr, pas de mise en oeuvre de design patterns de comportement particulier.
On trouve des objets proches des Singletons et Fabriques conformes à 100% dans l'esprit mais pas dans la syntaxe, ceci afin d’être compatible avec la plus large plage possible de versions de PHP.

==Design patterns d'entreprises (Martin Fowler)==

===Mode d'organisation du code===
[[wikipedia:Martin_Fowler|Martin Fowler]] a identifié 3 méthodes d'organisation du code appelées '''patterns''' ('''motifs'''):

*Le '''Transaction Script''' (Le code est linéaire en fonction d'une action utilisateur).

C'est le motif à l'ancienne utilisé dans les langages procéduraux.
Inconvénient: Redondance du code. Nécessité de connaitre le modèle physique pour développer les parties métiers.

*Le '''Domain Model'''

C'est un concept possible depuis les langages objets. Ce sont les procédures métiers (qui doivent être identifiés avant) qui servent de bases pour les classes objets.
Inconvénient : Motif complexe à maintenir.

*Le '''Table Module'''

Un intermédiaire entre les 2 précédents où l'on a une instance unique de classe par table de la base de données.

-> Comme le montre les squelettes de code (voir point précédent), Dolibarr se base sur le principe du '''Table Module'''.

===Communication Logique métier - Données (ORM)===
Il existe 3 modes de liaisons:

*Le '''Table And Row Data Gateway'''

C'est le plus simple. On crée une classe par table et chaque classe est un pont avec la table correspondante et propose les méthodes CRUD sur cette table (Create, Read, Update, Delete). Une instance de classe étant alors un enregistrement de la table. La classe ne contient que du code d'accès aux lignes ou colonnes de tables. Le code métier doit alors être ajouté dans d'autres classes. Les liens entre ces classes tables et les classes métiers devant être connues ou déduites de la connaissance du développeur.

Exemple: C'est le mode mis en oeuvre quand on utilise certains Frameworks d'ORM comme '''iBatis''' (http://ibatis.apache.org/).

*Le '''Active Record'''

Identique au précédent, mais on se permet d'ajouter quelques fonctions métiers sur la classe, à condition que ces fonctions soient bien propres à la table ou à la notion métier portée par l'enregistrement. C'est le pattern qui offre le meilleur rapport fonctionnalité/complexité.

Exemple: C'est le mode choisi pour les développements Dolibarr et de nombreuses autres applications PHP qui ont leur propre framework et pratiques de développement.

*Le '''Data Mapper'''

Les classes représentent les entités du problème et non les données. Il faut donc doubler, tripler... ces classes avec des classes Mapper pour accéder aux données.
Plus "puriste" sur le papier car plus proche du métier, ce mode a aussi l'inconvénient d'être très complexe et difficile à maintenir dans la réalité (l'expérience pratique constatée ne rejoignant pas les promesses de la théorie).

Exemple: C'est le choix si on utilise le Framework d'ORM '''Propel''' (http://propel.phpdb.org/trac/). On le trouve donc sur des applications plus lourdes basées sur cet ORM entre autres.

-> Pour les développements Dolibarr, il est recommandé d'utiliser le mode de liaison '''Active Record''' qui offre les avantages d'un modèle proche du métier sans en avoir la complexité et sans trop masquer non plus la technique. C'est dans ce mode que le développement, la compréhension du code et la maintenance technique et/ou fonctionnelle semble la plus productive (ceci est toutefois un éternel débat entre les puristes et les pragmatiques, débat dans lequel personne ne peut vraiment avoir raison, car tout dépend des objectifs à atteindre).

==Design Pattern d'Interface Graphique (MVC)==
Il existe plusieurs design pattern pour les interfaces utilisateurs (MVC, MVP, MVVM).
Beaucoup confonde ce design pattern avec celui consistant à utiliser un framework de templates. C'est sans rapport. Un framework de template (voir point précédent) n'est en lien qu'avec la partie "V" de ces modèles.

-> Dolibarr utilise le Design Pattern '''MVC'''. La partie M est matérialisée par une classe DAO contenant les méthode CRUD (Create-Read-Update-Delete) d'accès à la table.
Beaucoup de frameworks ont fait le choix de mettre la partie de code C (Controller) et la partie de code du V (vue) dans des fichiers, voir même répertoires séparés. La maintenance semble plus aisé sur la papier, en pratique, il faut sans arrêt jonglé entre n fichiers, le C étant fortement lié au V. Aussi dans Dolibarr, la séparation est faite par une simple section de commentaire. La partie de code C (Controller) est donc le code qui se trouve sont la balise
<pre>
/*
* Actions
*/
</pre>
Elle est suivi par la partie de code V (Vue), bien séparé du C par la balise
<pre>
/*
* View
*/
</pre>

Ce mode de séparation a eu un effet neutre sur les nouveaux développement mais a permis de réduire de manière si importante le temps requis pour la maintenance et correction de bugs qu'il n'est pas envisagé de basculer vers un autre type de séparation (oui les constats fait dans la vraie vie ne sont pas toujours ceux attendus par la théorie scolaire). L'important reste qu'il y ait toujours séparation entre le C et le V, peut importe comment est matérialisé cette séparation, du moment qu'elle l'est (Rappel: Ne pas confondre la notion de séparation du C et du V avec la notion de séparation du code pour alimenter la données d'une Vue et du code pour formater la Vue, ceci un principe de séparation relevant du Design Pattern de Vue, voir point suivant).

==Design Pattern de Vue - Présentation==
Il existe des frameworks spécialisés dans le Design Pattern de Vue, la partie qui consiste à formater l'écran vue par l'utilisateur.
Les vieilles versions de Dolibarr utilisaient Smarty. Ce framework est une surcouche à un Framework, déjà très puissant, de formatage d'écran nommé... PHP. Les bénéfices étant très inférieurs aux inconvénients, il a été abandonné au profit de templates PHP (fichier .tpl.php) qui restent le plus simple, le plus universel, le plus évolutif et le plus performant, des frameworks de présentation.

Son seul défaut est qu'il ne peut garantir à 100% les écarts d'un développeur qui irait intégrer dans la Vue, une logique sans rapport avec la présentation (donc autre que du code à vocation de génération, de formatage, de sortie HTML, de logique de test ou de boucle). Ce point est toutefois contrôlé par le mécanisme de validation du code des chefs de projets.

La encore, c'est l'expérience et le constat "sur le terrain" d'un meilleur rendement de productivité qui a motivé l'abandon des frameworks de Présentation externes au profit du framework PHP.

Langages et normes

2022-06-27T07:21:39Z

Iouston: ajout comparaison version avec version_compare

[[en:Language_and_development_rules]]
[[de:Sprachen_und_Programmierregeln]]
[[es:Lenguaje_y_Normas_de_Desarrollo]]
[[zh:语言和开发规则]]


{{TemplateDocDev}}

Voici les quelques règles sur le langage, la syntaxe et normes de développement en vigueur pour le projet Dolibarr :

=Versions=

*Dolibarr doit fonctionner sur:

#Tous OS (Windows, Linux, MACOS...)
#PHP {{PHPMinVersion}} (Doit fonctionner sans aucun module PHP complémentaire hors les modules d'accès base de donnée).
#Mysql {{MySqlMinVersion}}

=Normes Copyright=

*Tout fichier PHP doit avoir un en-tête selon le masque suivant

<syntaxhighlight lang="PHP">
<?php
/* Copyright (C) YYYY John Doe <email@email.com>
*
* Licence information
*/
...
</syntaxhighlight>
Quand vous éditez un fichier existant du projet, ajouter une ligne Copyright sous celles existantes.

=Normes PHP=

==PHP==

*Dolibarr est écrit en PHP et supporte toutes versions PHP supérieures à la {{PHPMinVersion}}. Les fichiers doivent tous comporter l'extension .php

*L'appel aux variables superglobales PHP doit passer par les opérateurs dédiés $_COOKIES, $_SERVER, $_ENV. Mais pour récupérer les contenus de $_GET ou $_POST, il faut passer par la fonction dolibarr [[Fonctions utiles Dolibarr|GETPOST()]] .

Les autres opérateurs ($HTTP_SERVER_GET, ...) ayant été passés en deprecated au sein de PHP, ne doivent plus être utilisés. Ainsi le code doit fonctionner y compris quand l'option '''register_long_arrays''' est à off.
De plus, le code doit fonctionner aussi bien quand l'option PHP '''register_globals''' est à off (recommandé par PHP) que quand l'option '''register_globals''' est à on (par défaut sur de nombreuses installations).

*Pas d'utilisation de la variable '''PHP_SELF'''. Utiliser à la place $_SERVER["PHP_SELF"]. Notez aussi que le framework Dolibarr passe une routine pour rendre plus sûr le contenu du $_SERVER["PHP_SELF"] (dans le fichier main.inc.php, donc avant tout traitement métier)

*Quand plusieurs variables doivent être initialisées avec la même valeur, il faut utiliser plusieurs instructions:

<syntaxhighlight lang="PHP">
$var1 = 1; $var2 = 1; $var3 = 1;
</syntaxhighlight>
plutôt que
<syntaxhighlight lang="PHP">
$var1 = $var2 = $var3 = 1;
</syntaxhighlight>
qui est moins performant.

*Les chaines doivent avoir les variables sorties de la chaine.

<syntaxhighlight lang="PHP">
print "Mon texte affiche ma ".$variable." !\n";
</syntaxhighlight>

*Les commentaires doivent suivre la syntaxe C, ie un double antislash pour un commentaire d'une ligne et utilisation slash-étoile pour ouvrir un bloc de plusieurs lignes

<syntaxhighlight lang="PHP">
/* Bloc de commentaire
*
* Fin du bloc
*/

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

for ($i = 1 , $i < 2 ; $i++)
{
// commentaire sur une ligne
print $i;
}

</syntaxhighlight>

*Les fonctions doivent retourner une valeur strictement > à 0 en cas de succès, et un nombre < à 0 en cas d'erreur.

*Pas de code mort (non utilisé) dans le code principal de Dolibarr (le code utilisé uniquement par un module externe doit être inclus dans le module externe).

*Utiliser "include_once" pour l'inclusion de tout fichier contenant des définitions de fonction ou de classes (donc fichiers *.class.php et *.lib.php), utiliser "include" pour tout inclusion de fichier de type template ou contenant un mixte de HTML et PHP (donc fichiers *.inc.php et *.tpl.php).

*Le style de code a utiliser est le PSR-12 (https://www.php-fig.org/psr/psr-12/). Seules les règles "MUST" sont imposées. Notez aussi les points/exceptions suivants:
**La longueur des lignes: PSR-12 indique que la longueur des lignes a une limite "soft" à 120. Il est en effet préférable d'avoir de longues lignes de données de déclaration plutôt que de longues pages car ce code ne contient aucune logique intéressante ou utile, toutefois une limite "hard" a été instauré à '''1000''' caractères. Du code qui ira au delà provoquera des erreurs dans la plateforme d'Intégration Continue.
**Les tabulations sont acceptées : L'autre exception est qu'on ne remplace pas les tabulations systématiquement par des espaces. L'utilisation des tabulations simplifie la vie de certains développeurs. De plus, l'utilisation d'espaces rend certaines fonctions d'autoformatage défectueuses (comme sur certaines versions d'Eclipse, lors de copier-coller).
**Note 1: Les règles suivantes sont particulièrement importantes :
***Les fichiers doivent être sauvés en format Unix (LF) et non Windows (CR/LF). Le format Unix étant compatible sur les OS Unix like, Windows, Mac, alors que le format fichier texte Windows pose problème sous certains PHP sous Unix.
***Les smart tags PHP ne sont pas utilisés. Les sections de code doivent commencer par '''<?php'''
**Note 2: Vous pouvez utiliser le fichier '''dev/setup/codesniffer/ruleset.xml''' comme fichier de contrôle pour vérifier votre style de code avec PHPCodeSniffer.
**Note 3: Vous pouvez utiliser le fichier '''dev/setup/eclipse/PSR-12 [built-in].xml''' comme fichier de règles de syntax pour configurer Eclipse.
**Note 4: Vous remarquerez que le code actuel ne suit pas forcément tout cela. La raison est historique. La règle fut instaurée en cours de route, aussi, si vous trouvez du code non respectueux de ce standard, n'hésitez pas à le corriger.

==Structures des classes et champs==

Certaines propriétés de classes se retrouvent dans de nombreuses classes. Pour homogénéité, on utilisera les noms suivants:
{{TemplatePHPFields}}

=Normes SQL=

==Structure des tables et champs==

*Toutes les tables sont préfixées pour éviter les conflits de nommage. Aujourd'hui, le préfixe est modifiable au moment de l'installation. Sa valeur par défaut est <tt>llx_</tt>.

*Structure des tables.

Lorsque vous créez une table, il est recommandé de prendre les même conventions de nommages de tables que les autres tables Dolibarr. Avec, à minima les champs suivant:
- rowid INTEGER AUTO_INCREMENT PRIMARY KEY qui est l'id technique
- entity INTEGER default 1 that is id for the multicompany feature
- date_creation datetime that is the creation date
- tms timestamp qui sera un champ contenant la date de chaque mise à jour (la base de donnée le gère tout seul, pas besoin de le gérer par le code)
- import_key varchar(32) qui contiendra le code d'import YYYYMMDDHHMMSS si vous faites des imports en masse dans la table.
- status smallint pour stocker le status d'un object

Eventuellement
- fk_user_creat integer qui est l'id du user de création (fk_user_author also found)
- fk_user_modif integer qui est l'id du user de modification
- fk_user_valid integer qui est l'id du user de validation
- fk_soc integer qui est l'id du tiers (si applicable)

*Type des champs

Dans la pratique, afin d'être compatible avec toutes les précisions des pays, syntaxes des bases, on utilisera uniquement les types suivants:
- integer pour tout nombre entier, id ou clé étrangère (bigint éventuellement accepté pour les id des très grosses tables)
- smallint pour tout numérique entier de petite taille (comme pour stocker un code de status)
- double(24,8) pour tout montant
- double(6,3) pour les taux de tva
- real pour une quantité
- varchar pour une chaîne (y compris de longueur 1, le type char est de plus en plus déprécié)
- timestamp pour un champ date+heure devant être mis a jour automatiquement
- datetime pour un champ date+heure
- date pour un champ date

==Clé primaire==
La clé primaire d'une table s'appelle <tt>rowid</tt>.

Il y a quelques tables qui échappent à cette règle actuellement (ex [[Table llx_c_actioncomm]]), pour des raisons historiques. Une évolution pourra être étudiée pour une prochaine version.

==Clés étrangères==
Le nom d'une clé étrangère commence par le préfixe <tt>fk_</tt> suivi du nom de la table liée (requis pour éviter doublons globales à la base, problématiques sous certains SGBD comme postgresql) puis du champ lié (pour permettre plusieurs clés étrangères différentes sur une même table).

Exemple:
fk_facture_fourn_fk_soc

Note: Si vous développez votre propre module externe, il ne doit pas y avoir de clé étrangère depuis vos tables qui pointent sur les tables standards de Dolibarr. Ceci casserait les fonctionnalités de mise à jour, de réparation, de sauvegardes et de restauration.

==Clés alternatives==
Parfois, il n'y a pas que la clé primaire qui doit être unique. On peut donc ajouter aussi un index clé alternative unique. Un tel index est nommé par un nom qui commence par le préfixe <tt>uk_</tt> suivi du nom de la table (requis pour éviter doublons d'index globals à la base, problématiques sous certains SGBD comme postgresql) puis d'un suffixe qui caractérise la clé (pour permettre plusieurs index uniques sur une même table).

Exemple:
uk_societe_code_client

==Index performance==
Certains champs sont souvent utilisés comme critère de recherche, de tri ou de jointure. Il convient dans ce cas, d'y mettre un index de performance. De tels indexes seront nommés avec un préfix <tt>idx_</tt> puis le nom de la table et le nom du champ sur lequel porte l'index.

Exemple:
idx_societe_user_creat

==Format de fichier DDL==
Les fichiers qui contiennent la définition de la structure de la base (DDL) doivent être au nombre de 2 par tables:
Chaque table est définie dans son propre fichier dont le nom est <tt>llx_''matable''.sql</tt>.
On mettra un commentaire à côté de chaque champ pour en expliquer la signification.
Les clés étrangères et index de performance ou autres contraintes d'unicité sont définies dans un fichier séparé dont le nom est <tt>llx_''matable''.key.sql</tt>

Ces fichiers sont placés dans le répertoire '''install/mysql/tables''' pour les fichiers standards ou '''monmodule/tables''' pour les tables amenées par un module.

Exemple '''fichier table llx_matable.sql''':

<syntaxhighlight lang="sql">
-- ===========================================================================
-- Copyright (C) 2008 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 2 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_matable
(
rowid integer AUTO_INCREMENT PRIMARY KEY,
field_one integer,
field_two integer NOT NULL,
fk_field integer,
field_date datetime,
tms timestamp
)ENGINE=innodb;
</syntaxhighlight>

Exemple '''fichier clés/index llx_matable.key.sql''':

<syntaxhighlight lang="sql">
-- ===========================================================================
-- Copyright (C) 2008 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 2 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);
</syntaxhighlight>

==Règles de codage SQL==

*Utilisation des alias/nommage de champs

Dans le cas des select on pourra utiliser les alias pour simplifier l'écriture des requêtes:
<syntaxhighlight lang="sql">
select chp1, chpxxx2 as chp2 from table2 as t1, table2 as t2 where t1.chpx = t2.chpy
</syntaxhighlight>
Toutefois, il ne faut pas utiliser ces alias sur des requêtes update car non compatible avec mysql 3.1.

*Les SELECT * sont interdits ! Chaque SELECT doit spécifier la liste complète des champs à récupérer. Cela permet d'éviter les confusions. Exemple:

<syntaxhighlight lang="sql">
SELECT field_a, field_b, field_c FROM table_1 WHERE field_d = '$id'
</syntaxhighlight>

*Dans les requêtes SQL, on quote les champs mais pas les numériques qui contiennent des montants destinés à être stockés dans des champs de type double ou real. Les quotes sur les numériques de type float provoquent parfois un stockage d'une valeur différente. Par exemple 412.62 dans le insert sera en fait stocké avec la valeur 412.61999512 en base (suite à des conversions chaines-numériques implicites) si le champ est de type double(24,8). Et seul le PHP voit 412.61999512. Les autres outils verront 412.62 donnant l'impression qu'il n'y a pas de problème. Et c'est le PHP qui a raison, il y a problème en base. En supprimant les quotes sur les numériques, cela va mieux.

Exemple:
<syntaxhighlight lang="sql">
Bon: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', 412.62)
Mauvais: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', '412.62')
</syntaxhighlight>

Remarque, le problème des float est général et pas seulement sur les accès base, il est présent dans tous les languages quand on travaille sur des nombres réels, aussi ils doivent être, dès que affectés, nettoyés par la fonction price2num avec le 2eme paramètre renseigné à:
'MU' (si il s'agit d'un prix unitaire), 'MT' (s'il s'agit d'un prix total) ou 'MS' (autres cas) selon le besoin.
Voir aussi le chapitre "Les nombres réels, montants et calculs" plus bas.

*Les fonctions NOW, SYSDATE ou DATEDIFF sont interdites au sein des ordres SQL. S'il faut saisir la date du moment dans un champ, la valeur doit venir du PHP, par exemple par la fonction dol_now(), et non du moteur de base de données. Ceci afin d'avoir une meilleure portabilité du code mais surtout d'avoir une gestion correcte des TimeZone et ne pas dépendre du TimeZone de la base de donnée.

Par exemple, on ne fera pas:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield = NOW()";
</syntaxhighlight>
mais:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield = '".$this->db->idate(dol_now())."'";
</syntaxhighlight>

Par exemple, on ne fera pas:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where DATEDIFF(table.datefield, NOW()) > 7";
</syntaxhighlight>
mais:
<syntaxhighlight lang="PHP">
$sql="SELECT rowid FROM table where datefield < '".$this->db->idate(dol_now() - (7 * 24 * 3600))."'";
</syntaxhighlight>

Un autre avantage de cette règle est que la requête peut bénéficier de l'utilisation de l'index puisqu'on compare datefield à une valeur fixe. Dans le cas du datediff, on applique un traitement sur le champ avant comparaison, rendant impossible l'utilisation de l'index de ce champ. Les conséquences sont des performances très dégradées par rapport à la version sans datediff.

==Règles de migration de base==

*Les scripts de migration de structure sont les fichiers de type '''install/mysql/migration/a.b.c-x.y.z.sql'''. Dans un fichier de migration de n vers n+1, on ne détruit une table (DROP TABLE) qui n'est plus utilisée en n+1 que lors de la migration de la version n+1 vers n+2. Ceci afin de toujours conserver les tables deprecated le temps d'une version pour réparer une situation en cas d'erreur de migration.

==Spécificités MySQL==

*Les tables doivent être au format InnoDB.

En effet, ce format gère les clés étrangères, les éventuelles restrictions qui y sont attachées et la notion d'intégrité de transactions requise pour avoir des données en base cohérente entre tables.

*Dolibarr DOIT fonctionner même avec les options '''strict''' de Mysql active.

Pour l'activer (fortement recommandé en développement), ajouter la ligne suivante dans le fichier config du serveur Mysql (my.cnf ou my.ini)
{{MySqlStrictMode}}

==Spécificités PostgreSQL==
Seuls les fichiers pour Mysql doivent être maintenus.
Les fichiers pour les autres bases sont convertis "à la volée" par le driver Dolibarr de la base.

Il existe une exception.
Les requêtes "UPDATE FROM" :
Syntax MySQL :
<syntaxhighlight lang="sql">
UPDATE table_taget as target, table_source as source SET fieldtarget=source.fieldsource
WHERE source.rowid=target.rowid;
</syntaxhighlight>

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

Il n'en existe pas dans Dolibarr, mais pour vos modules Vous devriez faire tel que :
<syntaxhighlight 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";
}
</syntaxhighlight>

=Normes HTML=

*Tous les attributs dans les balises HTML doivent être *en minuscule* et quotés avec des *doubles quote*.

*Les liens href doivent être absolus en se basant sur la fonction dol_buildpath() pour obtenir un chemin absolu depuis un chemin relatif au répertoire htdocs. Pour les tags img, il faut faire appel à la fonction img_picto().

Par example:
<syntaxhighlight lang="PHP">
print '<a href="'.dol_buildpath('/monrep/mapage.php').'">'.img_picto('Texte alt','nompictopng','').'</a>';
</syntaxhighlight>

*Les tables HTML doivent avoir des colonnes sans valeurs forcées, excepté pour les colonnes qui contiennent une information dont la longueur est non variable. Par exemple, une colonne avec un picto peut être forcée à with="20px". Dans les autres cas, il faut éviter de forcer la largeur des colonnes. La raison est que, dans la plupart des cas, le navigateur fait un meilleur travail pour définir automatiquement la bonne largeur des colonnes qu'en forçant manuellement les largeurs. Et ceci marche quelle que soit la résolution de l'écran.

*Le javascript/ajax et l'appel aux scripts java dans les pages php est à proscrire. Si toutefois du code javascript est inclus, il doit être conditionné par le test sur "$conf->use_javascript_ajax"

<syntaxhighlight lang="PHP">
if ($conf->use_javascript_ajax) {
... // Le code php qui génère du javascript est ici
}
</syntaxhighlight>

*Les popups windows ne doivent pas être utilisées, sauf pour des tooltips (et restent conditionnées par le point ci-dessus).

*Les scripts externes sont écrits en Perl s'ils ne peuvent l'être en php, l'utilisation d'un autre langage n'est pas interdit mais doit être discuté au préalable dans la mailing list des développeurs.

=Normes Dolibarr et squelettes de code=

==Squelettes de code==
Afin d'uniformiser le code et d'accélérer le développement de nouveaux composants dans Dolibarr, se trouvent dans le répertoire '''htdocs/modulebuilder/templates'''.

Par exemple:

*1 fichier qui sert d'exemple de descripteur de module: '''myModule.class.php'''
*1 fichier qui sert d'exemple de code pour faire une nouvelle classe: '''skeleton_class.class.php'''
*1 fichier qui sert d'exemple de code pour faire une nouvelle page: '''skeleton_page.php'''
*1 fichier qui sert d'exemple de code pour faire un script à exécuter en ligne de commande: '''skeleton_script.php'''

...

Servez-vous en comme exemple.
Notons que ces squelettes sont aussi utilisés par le générateur de code PHP ([[Module ModuleBuilder]]) qui est décrit dans la chapitre de développement de module Dolibarr pour accélérer vos développements.

==Les dates et TimeZone==
Dolibarr se veut une application multi-utilisateur et multi-localisation. Il convient donc de stocker les dates dans le bon format. Pour éviter les problèmes de conversion, les règles suivantes doivent être appliquées:

*Une date en mémoire doit être au format Timestamp GMT.
*Une date stockée en base de données contient le Timestamp issue de la date soumise dans la requête en heure locale du serveur PHP. Cela ne concerne pas les dates mises à jour automatiquement par la base (champ '''tms''' en base).

Ainsi le 1er janvier 1970, 3 heures à Paris (TZ=+1) = 1er janvier 1970, 2 heures à Greenwich (TZ=0) sera stocké en mémoire par 7200 et sera soumis à la base de données avec la chaine '19700101030000' (PHP convertit en heure de son TZ et la base déconvertit avec son TZ qui est le même que celui de PHP).

Les méthodes select doivent donc traduire les champs dates lus qui sont au format chaine TZ de la base ('19700101030000') par appel de la méthode db->jdate afin de récupérer une information en mémoire au format Timestamp GMT. Et les méthodes insert doivent lors de la génération de la requête convertir la date mémoire connue en variable, par la méthode db->idate (Voir exemples générés par le squelette).

*Les dates mises à jour automatiquement par la base (champ '''tms''' en base) contiennent le Timestamp où la modification est faite selon le timezone de la base de donnée. Les méthodes select récupèrent cette donnée en mémoire au format Timestamp GMT en appliquant également le db->jdate. Si le timezone de la base de donnée diffère de celui du PHP (un des 2 est mal réglé), il peut donc y avoir des écarts entre date de création et modification.

*La manipulation de dates en PHP doit être faite en utilisant les fonctions dates de Dolibarr: '''dol_now(), dol_mktime(), dol_stringtotime(), dol_getdate(), dol_time_plus_duree()'''. Vous trouverez également d'autres fonctions prêtes à l'emploi dans le fichier '''date.lib.php'''.

==L'encodage UTF8/ISO==
Dolibarr stocke les informations de manière suivante:

*En base de donnée, les données sont en UTF8 ou ISO. Cela dépend du pagecode de la base, donc des options à la création de cette base. Dans tous les cas le driver d'accès base Dolibarr (dans /lib/database) s'arrange à la lecture et insertion pour convertir vers et depuis de l'UTF8.
*Les données en mémoires sont donc stockées en UTF8 (instances d'objets PHP).
*Les pages web affichées à l'écran sont au format UTF8

==Les nombres réels, montants et calculs==
En PHP comme dans d'autres langages (Java par exemple), les données non entières (float, real, double) ne sont pas fiables.
Essayer de faire par exemple
<syntaxhighlight lang="PHP">
print 239.2 - 229.3 - 9.9;
</syntaxhighlight>
Vous n'obtiendrez pas zéro mais un nombre très petit en puissance de 10 négative. Si vous obtenez zéro, vous pourrez trouvez d'autres exemples qui ne fonctionnent pas.
Le problème des float est général, une variable résultante de calcul de nombre réels doit SYSTEMATIQUEMENT être nettoyée par la fonction '''price2num()''' avec le 2eme paramètre renseigné à: 'MU', 'MT' ou 'MS' selon le besoin (voir doc fonction).
<syntaxhighlight lang="PHP">
print price2num(239.2 - 229.3 - 9.9, 'MT');
</syntaxhighlight>
S'il ne s'agit pas d'un prix sur lequel s'adapte les paramètres MU, MT ou MS, il faut utiliser la fonction '''round()'''.

==Création de tables==
Ne pas créer de table à l'utilisation, c'est-à-dire à la '''première utilisation''' du module.
Si vous créez un module qui utilise des tables qui ne sont pas intégrées en standard dans le code de Dolibarr, veillez à suivre le didacticiel [[Développement module]] qui explique comment joindre des tables qui se créent à l'activation du module et non à son utilisation (voir plus haut).

==Comparer la version==

Si votre code a besoin de faire des choses différentes selon la version de Dolibarr, vous pouvez utiliser le truc suivant pour comparer les versions

<syntaxhighlight lang="PHP">
$version=preg_split('/[\.-]/',DOL_VERSION);
if (versioncompare($version,array(5,0,-4)) >= 0) { //mycode for 5.0 only; } // For dolibarr 5.0.* (the -4 means we include also alpha, beta, rc and rcX)
</syntaxhighlight>

Mais cette solution requiert de faire un include avoir la fonction versioncompare. Une alternative est d'utiliser le test suivant :
<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

Il également possible de faire appel à la fonction version_compare de php, ce qui donne ici :
<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

<syntaxhighlight lang="PHP">
if ((float) DOL_VERSION >= 5.0) { //mycode for 5.0 only; } // For dolibarr 5.0.*
</syntaxhighlight>

 

==Logs==
Ajouter des traces dans votre code avec la fonction
<syntaxhighlight lang="PHP">
dol_syslog($yourmessage, LOG_INFO|LOG_DEBUG|LOG_WARNING|LOG_ERR);
</syntaxhighlight>

==Répertoires de travail==
Si vous avez besoin de créer un répertoire de travail, dans votre code, faites référence à ce répertoire par
'''DOL_DATA_ROOT.'/monmodule''''

Le répertoire peut être créé dans votre code à l'exécution par le code suivant:
<syntaxhighlight lang="PHP">
$mymoduledir=DOL_DATA_ROOT.'/monmodule';
dol_mkdir($mymoduledir);
</syntaxhighlight>

Si vous avez besoin d'un répertoire qui contiendra des données temporaires, ce répertoire doit être''' DOL_DATA_ROOT.'/monmodule/temp''''

=Design patterns et programmation objet=

==Design patterns de Création (GoF)==
Design patterns définis par le Gang Of Four (voir la wikipédia sur les [[wikipedia:Patron de conception|Design patterns]]).
Dans Dolibarr, pas de mise en oeuvre de design patterns de comportement particulier.
On trouve des objets proches des Singletons et Fabriques conformes à 100% dans l'esprit mais pas dans la syntaxe, ceci afin d’être compatible avec la plus large plage possible de versions de PHP.

==Design patterns d'entreprises (Martin Fowler)==

===Mode d'organisation du code===
[[wikipedia:Martin_Fowler|Martin Fowler]] a identifié 3 méthodes d'organisation du code appelées '''patterns''' ('''motifs'''):

*Le '''Transaction Script''' (Le code est linéaire en fonction d'une action utilisateur).

C'est le motif à l'ancienne utilisé dans les langages procéduraux.
Inconvénient: Redondance du code. Nécessité de connaitre le modèle physique pour développer les parties métiers.

*Le '''Domain Model'''

C'est un concept possible depuis les langages objets. Ce sont les procédures métiers (qui doivent être identifiés avant) qui servent de bases pour les classes objets.
Inconvénient : Motif complexe à maintenir.

*Le '''Table Module'''

Un intermédiaire entre les 2 précédents où l'on a une instance unique de classe par table de la base de données.

-> Comme le montre les squelettes de code (voir point précédent), Dolibarr se base sur le principe du '''Table Module'''.

===Communication Logique métier - Données (ORM)===
Il existe 3 modes de liaisons:

*Le '''Table And Row Data Gateway'''

C'est le plus simple. On crée une classe par table et chaque classe est un pont avec la table correspondante et propose les méthodes CRUD sur cette table (Create, Read, Update, Delete). Une instance de classe étant alors un enregistrement de la table. La classe ne contient que du code d'accès aux lignes ou colonnes de tables. Le code métier doit alors être ajouté dans d'autres classes. Les liens entre ces classes tables et les classes métiers devant être connues ou déduites de la connaissance du développeur.

Exemple: C'est le mode mis en oeuvre quand on utilise certains Frameworks d'ORM comme '''iBatis''' (http://ibatis.apache.org/).

*Le '''Active Record'''

Identique au précédent, mais on se permet d'ajouter quelques fonctions métiers sur la classe, à condition que ces fonctions soient bien propres à la table ou à la notion métier portée par l'enregistrement. C'est le pattern qui offre le meilleur rapport fonctionnalité/complexité.

Exemple: C'est le mode choisi pour les développements Dolibarr et de nombreuses autres applications PHP qui ont leur propre framework et pratiques de développement.

*Le '''Data Mapper'''

Les classes représentent les entités du problème et non les données. Il faut donc doubler, tripler... ces classes avec des classes Mapper pour accéder aux données.
Plus "puriste" sur le papier car plus proche du métier, ce mode a aussi l'inconvénient d'être très complexe et difficile à maintenir dans la réalité (l'expérience pratique constatée ne rejoignant pas les promesses de la théorie).

Exemple: C'est le choix si on utilise le Framework d'ORM '''Propel''' (http://propel.phpdb.org/trac/). On le trouve donc sur des applications plus lourdes basées sur cet ORM entre autres.

-> Pour les développements Dolibarr, il est recommandé d'utiliser le mode de liaison '''Active Record''' qui offre les avantages d'un modèle proche du métier sans en avoir la complexité et sans trop masquer non plus la technique. C'est dans ce mode que le développement, la compréhension du code et la maintenance technique et/ou fonctionnelle semble la plus productive (ceci est toutefois un éternel débat entre les puristes et les pragmatiques, débat dans lequel personne ne peut vraiment avoir raison, car tout dépend des objectifs à atteindre).

==Design Pattern d'Interface Graphique (MVC)==
Il existe plusieurs design pattern pour les interfaces utilisateurs (MVC, MVP, MVVM).
Beaucoup confonde ce design pattern avec celui consistant à utiliser un framework de templates. C'est sans rapport. Un framework de template (voir point précédent) n'est en lien qu'avec la partie "V" de ces modèles.

-> Dolibarr utilise le Design Pattern '''MVC'''. La partie M est matérialisée par une classe DAO contenant les méthode CRUD (Create-Read-Update-Delete) d'accès à la table.
Beaucoup de frameworks ont fait le choix de mettre la partie de code C (Controller) et la partie de code du V (vue) dans des fichiers, voir même répertoires séparés. La maintenance semble plus aisé sur la papier, en pratique, il faut sans arrêt jonglé entre n fichiers, le C étant fortement lié au V. Aussi dans Dolibarr, la séparation est faite par une simple section de commentaire. La partie de code C (Controller) est donc le code qui se trouve sont la balise
<pre>
/*
* Actions
*/
</pre>
Elle est suivi par la partie de code V (Vue), bien séparé du C par la balise
<pre>
/*
* View
*/
</pre>

Ce mode de séparation a eu un effet neutre sur les nouveaux développement mais a permis de réduire de manière si importante le temps requis pour la maintenance et correction de bugs qu'il n'est pas envisagé de basculer vers un autre type de séparation (oui les constats fait dans la vraie vie ne sont pas toujours ceux attendus par la théorie scolaire). L'important reste qu'il y ait toujours séparation entre le C et le V, peut importe comment est matérialisé cette séparation, du moment qu'elle l'est (Rappel: Ne pas confondre la notion de séparation du C et du V avec la notion de séparation du code pour alimenter la données d'une Vue et du code pour formater la Vue, ceci un principe de séparation relevant du Design Pattern de Vue, voir point suivant).

==Design Pattern de Vue - Présentation==
Il existe des frameworks spécialisés dans le Design Pattern de Vue, la partie qui consiste à formater l'écran vue par l'utilisateur.
Les vieilles versions de Dolibarr utilisaient Smarty. Ce framework est une surcouche à un Framework, déjà très puissant, de formatage d'écran nommé... PHP. Les bénéfices étant très inférieurs aux inconvénients, il a été abandonné au profit de templates PHP (fichier .tpl.php) qui restent le plus simple, le plus universel, le plus évolutif et le plus performant, des frameworks de présentation.

Son seul défaut est qu'il ne peut garantir à 100% les écarts d'un développeur qui irait intégrer dans la Vue, une logique sans rapport avec la présentation (donc autre que du code à vocation de génération, de formatage, de sortie HTML, de logique de test ou de boucle). Ce point est toutefois contrôlé par le mécanisme de validation du code des chefs de projets.

La encore, c'est l'expérience et le constat "sur le terrain" d'un meilleur rendement de productivité qui a motivé l'abandon des frameworks de Présentation externes au profit du framework PHP.

Dolibarr suppliers France

2022-06-03T21:23:03Z

Iouston: minor change add iouston as preferred partner

{{Dolibarr_suppliers}}

{{TemplateCompany|
name=1fonet Services|
profid=|
desc=Integrations and open source development
Specialist software open source.Dolibarr, Joomla! Prestashop, Cahiers des charges ERP/CRM, Ecommerce, site web, gratuits. Complementary development of the module, component or application needs. Based in the PACA region work throughout France.|
web=http://www.1fonet.fr|
email=mailto:contact@1fonet.fr|
zip=13530|
town=Trets|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=2A2C Conseil|
profid=|
desc=CRM et Solutions e-commerce opensource pour TPM et PME, VoIP et Hosting en marque blanche, maintenance informatique, WordPress, Dolibarr, Prestashop, Formation utilisateur|
web=|
email=mailto:info@2a2c-conseil.fr|
zip=75012|
town=PARIS|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=A3SYS : MON-DOLIBARR|
partner=no|
profid=52456658500021 (SIRET)|
desc=Intégration, assistance et développement.
Notre société forte de plus de 25 ans d'expérience dans l'intégration de divers ERP propose ses services aux entreprises souhaitant mettre en place l'ERP Dolibarr. Une plateforme dédiée est mise en place pour proposer des services de qualité à moindre coût.|
web=http://www.mon-dolibarr.fr|
email=http://www.mon-dolibarr.fr/contact/|
zip=59310|
town=Orchies (Nord - France)|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=logo_mon-dolibarr.jpg
}}

{{TemplateCompany|
name=A6TM - SOLUTIONS|
profid=|
desc=A6TM SOLUTIONS, est une entreprise maîtrisant les technologies de l'informatique, et spécialisée dans les solutions informatiques et notamment les services tels que l'infogérance, installations et déploiements, dépannages, maintenance et réseaux informatique. Installation et maintenance CMS(Joomla, Wordpress...), Progiciel ERP/CRM (Dolibarr...)|
web=http://www.a6tm-solutions.fr|
email=mailto:contact@a6tm-solutions.fr|
zip=44|
town=Nantes et son département|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ACN - Atelier de Création Numérique|
profid=808 725 212 00019|
desc=ACN (Atelier de Création Numérique), Maîtres d’œuvres en Informatique, Nous sommes spécialisés dans le conseil, la création et l’intégration de solutions professionnelles pour les bureaux d'études. Nos solutions vont de l’intégration d’outils Open Source et de logiciels libres à la mise en place des meilleurs produits de grands éditeurs du marché.|
web=http://ateliercreationnumerique.com/|
email=mailto:contact@atlcreanum.com|
zip=44|
town=Nantes et Grand Ouest|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=acn.png|
}}

{{TemplateCompany|
name=Apio systems|
profid=529 919 540 00029|
desc=Apio systems vous accompagne dans tous vos projets Open Source. Apio systems prend en charge l'hébergement, l'installation et l'infogérance de vos applications Open Source desservant votre entreprise, tel qu'un environnement web/e-commerce avec WP/PS ou autre au besoin, la partie ERP avec Dolibarr, la partie messagerie collaborative avec Kopano, la partie partage de gros fichier avec NextCloud, etc.|
web=https://apio.systems/|
email=mailto:ping@apio.systems|
zip=13105|
town=Mimet|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
logo=Logo-apio-systems.png|
}}

{{TemplateCompany|
name=Aplose|
partner=yes|
profid=534906698|
desc=
Aplose c'est l'Agence pour la Promotion du Libre et de l'Open Source en Entreprise, société de service et organisme de formation spécialisé dans les logiciels libres de création de site internet et boutique en ligne (wordpress, prestashop), les erp, logiciels de gestion et logiciels de caisse et point de vente (Odoo, Dolibarr), les langages de programmation (java, html5, Javascript, php), les bases de données (mysql, postgresql), les systèmes d'exploitation (linux), les méthodes des gestion de projet agiles (Scrum). Bordeaux - Montpellier|
web=http://www.aplose.fr|
email=[mailto:contact@aplose.fr?subject=Contact%20from%20Dolibarr%20Suppliers%20France20page contact@aplose.fr]|
zip=34990|
town=Juvignac|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_Aplose.png
}}

{{TemplateCompany|
name=Artaban Communication|
partner=no|
profid=400 396 388 00037|
desc=Artaban Communication est une SSLL. Spécialistes du CMS SPIP, nous concevons et réalisons des sites web à forte composante éditoriale. Nous prenons également en charge le webmastering et la création de contenu. Notre expertise s'étend à un certain nombre de logiciels, choisis pour leur qualité et leur intérêt, et avec lesquels nous aimons travailler et notamment Dolibarr. Artaban Communication est membre de l'April.|
web=http://www.artaban.fr|
email=mailto:contact@artaban.fr|
zip=94340|
town=Joinville-le-Pont|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Artaban_logo.png‎|
}}

{{TemplateCompany|
name=ATM Consulting|
partner=yes|
profid=753 447 481 00015|
desc=Consulting company dedicated to small and medium enterprises information system optimization, we provide to our customers open-source based solutions to improve their information system efficiency. We offer hosting and support solutions and we are Dolibarr contributor, developer and integrator. "Open-source. Custom. Freedom"|
web=http://www.atm-consulting.fr|
email=mailto:contact@atm-consulting.fr|
zip=26000|
town=Valence|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=
}}

{{TemplateCompany|
name=AB2L|
profid=|
desc=Un Alsacien à votre service. Installation et configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur notre serveur. Nous vous accompagnons pour un démarrage rapide et serein. Nous sommes une société de service en logiciel libre fournissant un équivalent open source au logiciel propriétaire de tout type. |
web=http://www.ab2l.eu|
email=mailto:contact@ab2l.eu|
zip=67000|
town=Strasbourg|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Axopen IT Services|
profid=|
desc=L'entreprise Axopen propose toute une gamme de produits et services informatiques allant du conseil en système d'informations, développement de solutions sur mesure et intégration de solutions Open Source ou propriétaires. Nous sommes spécialisé en particulier dans l'intégration de solutions de gestion de la relation client Open Source telles que Dolibarr, SugarCRM ou VTiger... |
web=http://www.axopen.com|
email=mailto:contact@axopen.com|
zip=69001|
town=Lyon|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=AKILIS|
profid=|
desc=AKILIS est une société éditrice de logiciels de gestion qui a fait le pari d’utiliser les nouvelles méthodes de travail pour développer des solutions clairs et efficaces. Notre mission est de vous proposer des solutions simples d'utilisation, ne demandant aucun entretien de votre part, ni aucune connaissance technique particulière. Notre outil est celui que VOUS utilisez quotidiennement : le Web.
AKILIS, c’est une équipe toujours disponible pour vous guider et vous écouter. Nous développons et améliorons sans cesse nos logiciels afin que ceux-ci répondent au mieux à votre activité et vos besoins.
AKILIS peut également, dans le cadre de besoin partculier, étudier avec vous un développement sur mesure. |
web=http://www.akilis.fr|
email=mailto:contact@akilis.fr|
zip=69200|
town=Vénissieux|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Altairis|
profid=488020108|
partner=yes|
desc=Développements spécifiques, Installation, Formation, Accompagnement à la mise en oeuvre, Support, Intégration. Spéclialiste solution de gestion des locations de produits avec Dolibarr.|
web=http://www.altairis.fr|
email=contact@altairis.fr|
zip=18270|
town=Culan|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Atoo.Net|
partner=yes|
profid=|
desc=Installation et configuration de l'ERP/CRM Dolibarr soit sur nos serveurs, soit en local dans votre entreprise. Aide à la prise en main et formation.|
web=http://www.atoo-net.com/|
email=contact@atoo-net.com|
zip=45160|
town=Olivet|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Bee-Smart.online|
profid=|
desc=15 ans d'expérience aux services des PME & grands groupes, Bee-Smart vous propose un accompagnement sur mesure , adapté à vos besoins métiers et votre budget.N'hésitez pas, Bee-Smart.online, le partenaire de vos projets réussis.|
web=https://bee-smart.online|
email=contact@bee-smart.online|
zip=25|
town=Montbéliard|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Blue-Click Informatique|
profid=|
desc=Nous proposons l'installation et la configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur votre hébergement Internet. De plus nous assurons la formation pour la prise en main de cet outil adapté aux TPE et PME.|
web=http://www.blue-click.fr|
email=|
zip=92,78|
town=Nanterre,Plaisir|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=CAP-REL|
partner=yes|
profid=|
desc=Après avoir contribué au code de dolibarr dans les années 2004-2005 et l'avoir utilisé en interne pour de nombreux projets depuis cette époque je propose maintenant un service autour de Dolibarr (adaptation, accompagnement, utilisation etc.).|
web=https://www.cap-rel.fr|
email=eric.doli@cap-rel.fr|
zip=30|
town=Département du Gard|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_cap-rel.png‎|
}}

{{TemplateCompany|
name=Caribbean Consult CCC|
partner=yes|
profid=|
desc=Installation, configuration de l'ERP/CRM Dolibarr en ligne, ou en local pour votre entreprise ou association. Migration de données vers Dolibarr. Prise en main, support et formation.|
web=https://dolibarr.ccc.gp|
email=support@caribbeanconsult.com|
zip=97180|
town=Sainte Anne (Guadeloupe et Martinique) Antilles Guyane|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_CCC.png‎|
}}

{{TemplateCompany|
name=Cergy Internet|
profid=|
desc=Cergy Internet est spécialisé dans l’informatique et plus spécifiquement dans l’internet pour les PMI/PME. Nous maitrisons les technologies digitales du simple site web jusqu’au portail complète de pilotage d’entreprise. Grâce à Dolibarr nous pouvons vous donner une vision unique sur vos clients, vos produits et même votre trésorerie. Nous lions Dolibarr avec Wordpress et sur Smartphones pour créer des portails pour vos clients. Notre directeur, Thomas Carter, a fait son MBA à MIT aux USA et a géré des entreprises de plus de 100 personnes. Il met cette expérience à votre disposition. Chez Cergy Internet nous maitrisons la technologie de boute en boute. Nous avons notre propre équipe de jeunes codeurs qui baignent dans tous qui est réseaux sociaux, applications iPhone etc. ainsi qu’une plateforme de 30 serveurs pour héberger vos sites. |
web=www.cergy-internet.fr|
email=mailto:thomas.carter@cergy-internet.fr|
zip=95300|
town=Cergy-Pontoise|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Code 42|
partner=yes|
profid=793 600 735 00021|
desc=Nous vous accompagnons dans l’installation  et le développement de votre outil informatique. Code 42, c’est avant tout une démarche qualité et de conseil pour une relation durable. Vous avez la vision de votre entreprise, nous avons les moyens.|
web=www.code42.fr|
email=mailto:lareponse@code42.fr|
zip=44100|
town=NANTES|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=
}}

{{TemplateCompany|
name=D-BOG|
profid=|
desc=IT services company located in Beaune (21), moved around Dolibarr:
Installation, setup, configuration on the internal server or hosted;
Training agreement;
Outsourcing, on-site maintenance and remote.|
web=http://www.d-bog.com/|
email=|
zip=|
town=Beaune|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=DiVA-Cloud|
profid=|
desc=DiVA-Cloud propose des applications OpenSource de gestion de la communication et de l'information pour les entreprises. Notre logithèque contient des applications de WebConference, ERP, CRM, CMS, GED, et bien d'autres... Toutes ces applications pré-configurés sont mises à disposition sur un environnement privé. |
web=www.diva-cloud.com |
email=mailto:contact@diva-cloud.com |
zip=81100|
town=Castres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=DoliCloud|
partner=yes|
desc=DoliCloud is one of the most important contributor on Dolibarr and can host for you a Dolibarr instance in a SaaS (Software As A Service) mode.|
profid=493 861 496 00021|
web=https://www.dolicloud.com|
email=|
zip=33600|
town=Pessac (Bordeaux)|
country=fr|
service_hosting=yes (https://www.dolicloud.com)|
service_onlinesupport=only for DoliCloud.com customers|
service_emailsupport=only for DoliCloud.com customers|
service_dev=no|
service_local=no|
service_formation=no|
logo=logo_dolicloud.png}}

{{TemplateCompany|
name=Elonet|
partner=yes|
profid=SIRET:52511620800022|
desc=Elonet est intégrateur et développeur de solutions pour Dolibarr.|
web=https://elonet.fr/dolibarr.php|
email=mailto:contact@elonet.fr|
zip=59000|
town=LILLE|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=ElonetNew.png
}}

{{TemplateCompany|
name=FUTUR TECH|
profid=|
desc=Prestataire de services pour artisans, TPE, PME :
Solutions open source, Internet, Sécurité, Sauvegarde, Antivirus, Gestion d'entreprise, Conseil, Formation, Installation et Paramétrage
Intervention sur site client. Situé entre Bordeaux et Libourne|
web=http://www.futur-tech.com|
email=mailto:info@futur-tech.com|
zip=33450|
town=IZON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Groupe KM|
profid=790 885 388 00013|
desc=Intégrateur,développeur et hébergeur de solutions Open Source: Progiciel ERP/CRM (Dolibarr),CMS(Joomla)et e-commerce(Prestashop). Nous déployons aussi des solutions Téléphonie (VOIP, PABX...) et Accés Internet (ADSL/VDSL, SDSL...). 
Secteur Cannes, Antibes, Sophia-Antipolis, Carros, Nice et plus généralement toutes les Alpes-Maritimes. 
Notre objectif : Vous satisfaire!|
web=https://www.groupe-km.com|
email=mailto:contact@groupe-km.com|
zip=06220|
town=Vallauris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=GWARED|
profid=804 659 027 00036|
desc=La société GWARED, est une équipe diplômée dans le domaine de l’informatique, de plus de 10 ans d’expériences dans diverses structures telles que de grandes administrations, sociétés privées mais aussi au service des particuliers. Nous sommes à l’écoute pour vous accompagner dans vos projets.

Professionnel ou particulier, nous vous proposons de nombreux services informatiques et domotiques adaptés à votre configuration et vos besoins. Nos prestations concernent la réparation et la maintenance de votre ordinateur ou de votre parc informatique, l'installation réseau (Local informatique, Internet, intranet, Wifi, CPL, etc.), l'installation d’alarmes et vidéo-surveillance, sur site, à distance ou à domicile.

Notre société se distingue en trois branches :

- L’informatique (GWARED)
- La sécurité (alarme, vidéosurveillance et protection numérique) (GWARDSECURITY)
- Les jeux vidéo (concepteur de console de jeux) (GWARDBOX)

Nous pourrons répondre à tous vos besoins dans le domaine de l’informatique.|
web=http://www.gwared.fr|
email=[mailto:support@gwared.fr?subject=Contact%20de%20Dolibarr%20Suppliers%20France support@gwared.fr]|
zip=77500|
town=Chelles et Île de France|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
logo=Logo_Gwared.png|
}}

{{TemplateCompany|
name=HELIUM TECHNOLOGIES|
profid=494 895 360 00027|
partner=yes|
desc=
Mise en place de solutions ERP Dolibarr sur nos serveurs ou dans votre entreprise avec assistance téléphonique, support technique, développement de modules spécifiques et formation.
 '''SSII basée en Guadeloupe, Martinique et Guyane''', nous proposons également des solutions libres comme GLPI, Prestashop, Joomla, Odoo, Zimbra, BlueMind, Centreon, ...|
web=http://|
email=[mailto:contact@helium-technologies.com?subject=Contact%20from%20Dolibarr%20Suppliers%20France20page contact@helium-technologies.com]|
zip=97122|
town=BAIE-MAHAULT (GUADELOUPE)|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_HeliumTechnologies.jpg
}}

{{TemplateCompany|
name=Infonel.net|
profid=|
desc=administrateur système open source indépendant:
Installation, paramétrage, configuration et sécurisation de dolibarr sur site client|
web=http://www.infonel.net|
email=|
zip=11100|
town=Narbonne|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=iNodbox|
partner=yes|
profid=|
desc=Développeur indépendant d'application web, paramétrage et installation de Dolibarr, développement de modules spécifique. Basé dans l'Ain à Bourg en Bresse (30min de Mâcon, 1h de Chalon sur Saône, 1h de Lyon), je contribue depuis de nombreuses années au développement de Dolibarr.|
web=https://www.inodbox.com/|
email=regis.houssin@inodbox.com|
zip=01000|
town=Bourg en Bresse|
country=fr|
service_hosting=(https://www.inodbox.com)|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Inovea Conseil|
partner=yes|
profid=797 613 072 00017|
desc=Développeur, Intégrateur, Hébergeur et Formateur de Dolibarr pour TPE - PME |
web=https://www.inovea-conseil.com/ |
email=https://www.inovea-conseil.com/contact/ |
zip=88,54,75|
town=Nancy|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Inoveaconseil.png
}}

{{TemplateCompany|
name=i.d & l|
profid=521 749 994 00013|
desc=Conseil et intégration de solutions logicielles libres, dont Dolibarr, pour artisans, TPE, indépendants, commerçants, PME, associations...|
web=https://idl-mp.com|
email=https://idl-mp.com/contact/|
zip=31,32,09,82,81|
town=Région toulousaine|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=iouston informatique|
partner=yes|
profid=792 353 005 00046|
desc=iouston informatique, situé à proximité de Nancy, Metz, Lunéville, est spécialisée auprès des associations, des TPE et des artisans commerçants. Nous installons et configurons dolibarr pour vous et nous formons vos équipes à son utilisation quotidienne. Nous proposons de nombreux autres services, associés ou non à dolibarr. Nous travaillons avec dolibarr depuis plus de 6 ans et éditons des modules supplémentaires pour dolibarr, [https://www.dolistore.com/fr/recherche?controller=search&orderby=position&orderway=desc&search_query=iouston&submit_search= disponibles sur dolistore]|
web=https://www.iouston.com|
email=allo@iouston.com|
zip=54370|
town=Einville au Jard|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ISYNUX|
profid=|
desc=Société de services en réseaux et sytèmes. ISYNUX vous propose un suivi complet pour DOLIBARR : installation, hébergement, personnalisation de vos modèles de document, formation à la carte. |
web=http://www.isynux.fr|
email=mailto:formation@isynux.fr|
zip=626100|
town=Ardres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Jeffinfo (ZenDSI)|
profid=429 625 973|
partner=yes|
desc=Jeffinfo est une société de services en informatique qui vous sert depuis plus de 15 ans dont 10 ans dans le domaine de Dolibarr. Implanté dans le nord à Ennetières en Weppes. Nous sommes à vos services pour vous proposer tous les services autour de votre ERP préféré.
web=https://shop.zendsi.com|
email=mailto:contact@zendsi.com|
zip=59320|
town=Ennetières en Weppes|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no
}}

{{TemplateCompany|
name=KJR online|
profid=818 889 644 00014|
desc=Conseils et Services Informatiques. Installation, formation et personnalisation de Dolibarr. Région Toulousaine.|
web=http://www.kjr-online.fr|
email=mailto:eric.picabia@kjr-online.fr|
zip=31210|
town=Clarac|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=
}}

{{TemplateCompany|
name=Kreiz IT|
partner=yes|
profid= 752 505 131 00017|
desc={{Flag_fr}}Conseils en organisation et sécurité informatique pour les TPE / PME. Dolibarr fait partie des outils informatiques structurants pour les TPE/PME proposé par Kreiz IT.

{{Flag_en}}IT management and security consultant for small to medium business. Dolibarr is part of IT's structuring tools for business used by Kreiz IT. |
web=http://www.kreiz-it.fr |
email=mailto:contact@kreiz-it.fr |
zip=56600|
town=Lanester|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=LogoKIT.jpg
}}

{{TemplateCompany|
name=LIBRE EXPERT|
partner=no|
profid=48879200300045|
desc={{Flag_fr}}Intégrateur et développeur Dolibarr, auteur de plusieurs modules complémentaires, spécialiste également de l'administration Linux.

{{Flag_en}}
Integrator and Dolibarr developer, author of several complementary modules, also specialist in Linux administration. |
web=http://www.libre-expert.com|
email=mailto:contact@libre-expert.com |
zip=63100|
town=Clermont-Ferrand|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Libre Master|
partner=no|
profid=|
desc={{Flag_fr}}Expert système d'hébergement Linux Debian depuis plus de 20 ans, je vous évite de passer du temps à obtenir un Dolibarr fonctionnel, rapide, sécurisé et sauvegardé.
Je connecte également votre Dolibarr à des relais de messagerie pour que vos factures n'arrivent dans les SPAMs.|
web=https://libremaster.ovh/c/dolibarr/|
email=https://libremaster.ovh/contact/ |
zip=38350|
town=La Mure|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=no|
service_formation=no|
}}



{{TemplateCompany|
name=LVS Informatique|
profid=|
desc=Development Specialist php, mysql. Creation, enhancement, customization of modules and components ...
Nos modifs/nos modules :
-cashdesk : prix en ttc, possibilité de modification du prix, du libellé...
-interfaçage avec GoogleAgenda (toutes les actions apparaissent dans GoogleAgenda)
-Mails/Télécopies reçus : apparaissent dans un onglet spécifique sur le tiers en question
-qualification Tiers
-Adresse Tiers vu dans GoogleMap
-creation de nbreux template excel/pdf
|
web=http://www.lvsinformatique.com|
email=|
zip=83860|
town=NANS LES PINS|
country=fr|
service_dev=yes|
service_local=yes|
}}

{{TemplateCompany|
name=MEDIALTA|
profid=|
desc=Installation, configuration de Dolibarr sur nos serveurs, ou dans l'entreprise (Nancy, Metz, Lorraine, Grand Est). Formation, prise en main. Développement de modules sur mesure.|
web=www.medialta.com|
email=|
zip=54340|
town=Pompey|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Mephivio|
profid=|
desc=Services company with a computer located in Montpellier agglo, specializing in computer graphics, secretariat, Joomla web sites, client, opensource (Dolibarr, glpi, voip Elastix / Trixbox / PIAF etc ...)|
web=http://www.mephivio.fr/|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=MEZIANT|
profid=|
desc=MEZIANT propose aux PME, TPE, artisans, commerçants et associations de l'Ouest son expertise en informatique issue d'une expérience de plus de 15 ans en Audit de Système d'Informations, Site internet, Formation et Choix de logiciel de gestion (ERP) comme '''DOLIBARR''' dont elle peut assurer l’installation, la formation ou encore le développement de modules spécifiques sur site client.
web=http://www.meziant.fr |
email=mailto:contact@meziant.fr |
zip=22940|
town=PLAINTEL (Bretagne - France)|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Modulaweb : Technologies modulables orientées web.|
profid=|
desc=Développement d'applicatifs web, hébergement d'applications web, serveurs de fichiers et de sauvegarde, sites internet/intranet et intégration web, espaces clients, communication via internet (VoIP, messagerie instantanée), travail collaboratif. Spécialiste solutions libres pour l'entreprise (Zimbra, Dolibarr, Thaïs...) Région Languedoc-Rouissillon et voisines |
web=http://www.modulaweb.fr|
email=http://www.modulaweb.fr/portail/contact/|
zip=34000|
town=Montpellier|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Net Logic|
partner=yes|
profid=SIRET: 477 583 264 00023|
desc=Installation et configuration de l'ERP/CRM Dolibarr sur nos serveurs, ou en local dans votre entreprise. Paramétrage, personnalisation, reporting spécifique, assistance.|
web=http://www.netlogic.fr/|
email=info@netlogic.fr|
zip=93160|
town=Noisy-le-Grand|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=NORD ERP CRM|
partner=no|
profid=83184221600010 (SIRET)|
desc=Intégration, assistance, formation, développements spécifiques et hébergement de solutions Dolibarr. NORD ERP CRM est certifié QUALIOPI ce qui permet la prise en charge des formations par les organismes de financement. Nous nous adaptons à vos spécificités métiers.|
web=https://www.nord-erp-crm.fr/|
email=mailto:contact@nord-erp-crm.fr|
zip=59100|
town=Roubaix|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=|
}}

{{TemplateCompany|
name=NS-INFO90|
partner=no|
profid=79392284000020(SIRET)|
desc=Intégration, assistance, formation, développements spécifiques et hébergement de solutions Dolibarr|
web=https://www.ns-info90.fr/|
email=mailto:contact@ns-info90.fr|
zip=90360|
town=Lachapelle-sous-rougemont|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=LOGO NS-INFO90.png|
}}

{{TemplateCompany|
name=NUM'X|
partner=no|
profid=82465583100017(SIRET)|
desc=NUM'X est une entreprise de services numériques (ESN) intervenant notamment pour les TPE PME et proposant des services autour du PGI Dolibarr|
web=https://www.numx-sets.eu/dolibarr.html|
email=mailto:contact@numx-sets.eu|
zip=44590|
town=SION-LES-MINES|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=LOGO numx-sets.png|
}}

{{TemplateCompany|
name=OAS-SERVICES|
profid=829767904|
partner=no|
desc=
OAS-SERVICES est une société de service spécialisés dans la mise en place de logiciels libres sous forme de services cloud, notamment de Ma Gestion Cloud (Dolibarr, viger), la mise en place de site internet et boutique en lignes, le développement d'application et de modules en PHP (Dolibarr, Wordpress, Prestashop), mais aussi en Java (JEE, Webservices, JPA), la mise en place de systèmes d'exploitation (linux), la gestion de projet en agilité - Montpellier, Sète|
web=https://www.ma-gestion-cloud.fr|
email=[mailto:contact@oas-services.fr?subject=Contact%20from%20Dolibarr%20Suppliers%20France20page contact@oas-services.fr]|
zip=34200|
town=SETE|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
logo=logo-oas-services.png
}}

{{TemplateCompany|
name=OPEN-DSI|
partner=yes|
profid=SIRET:75130522800015|
desc=Depuis 2012, nous accompagnons les petites et moyennes structures (1 à 50 salariés) dans la mise en place de solutions basées sur les logiciels libres. Nous proposons Dolibarr pour tous les besoins de gestion.|
web=https://www.open-dsi.fr|
email=mailto:infos@open-dsi.fr|
zip=69,38,01,42|
town=LYON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=opendsi.png
}}

{{TemplateCompany|
name=Opens|
partner=no|
profid=SIRET:888 706 280 00011|
desc=Opens est spécialisée dans l'accompagnement Digital, RH et Qualité. Nous croyons que ces trois pôles sont intimement liés et œuvrons pour la souveraineté numérique de nos clients. Nous intervenons principalement dans l'Hérault et l'Occitanie.|
web=https://solutions.open-s.fr|
email=mailto:contact@open-s|
zip=34000|
town=MONTPELLIER|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_opens_solutions.png|
}}

{{TemplateCompany|
name=OIS - Open IT Store|
profid=822 430 419 00017|
desc=OIS (Open IT Store), We provide opensource instances located in Europe or North America.|
web=https://openitstore.com/dolibarr|
email=mailto:contact@openitstore.com|
zip=|
town=|
country=|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=no|
service_formation=yes|
logo=|
}}

{{TemplateCompany|
name=Oscss Shop|
partner=yes|
profid=SIRET:810 421 339 00013|
desc=Développement de modules sur mesure, interconnexions et hébergements.|
web=http://oscss-shop.fr|
email=mailto:support@oscss-shop.fr|
zip=28,45,41,72,61,27,75,69,38,01,73,74|
town=LA LOUPE|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Pascal Sené|
profid=|
desc=Logiciels libres et photographie.|
web=http://www.pascalsene.com|
email=contact@pascalsene.com|
zip=22,29,35,56|
town=Lannion|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Patas-Monkey|
profid=|
desc=Conseil, formation, développement et modules|
web=http://www.patas-monkey.com|
email=r.deschamps@patas-monkey.com|
zip=69,42,38,01,83|
town=Lyon|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Patasmonkey.jpg
}}

{{TemplateCompany|
name=Pragma-tech|
partner=no|
profid=842 325 268 00014|
desc=Intégrateur, Hébergeur et Formateur de Dolibarr pour TPE - PME |
web=https://www.pragma-tech.fr/ |
email=contact@pragma-tech.fr|
zip=|
town=PAU|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
logo=pragma-tech.png
}}

{{TemplateCompany|
name=ProbeSys|
profid=|
desc=Créée en 2003 par des passionnés du logiciel libre, [http://probesys.com ProbeSys] est une entreprise coopérative à l'image du secteur des nouvelles technologies : dynamique, réactive et participative. |
web=http://www.probesys.com|
email=mailto:contact@probesys.com|
zip=38600|
town=Fontaine|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=PRODUCTIVIX sarl|
profid=|
desc=Productivix fourni aux PMI des solutions complètes de traçabilité code-barre / rfid et développe des applications mobiles sur mesure offline (connexions intermitentes) de scan et d'impression mobiles liées à des ERP, elle travaille avec Dolibarr via ses API, paramètre les modules et fourni si nécessaire l'hébergement et les modifications ou création de modules nécessaires dans Dolibarr; Productivix founi les licences mobiles en location, et à l'achat les imprimantes et terminaux durcis avec scanner intégré- développements et installations à distance tous pays|
web=https://www.productivix.com/mot62.html|
email=https://www.productivix.com/article239.html|
zip=38|
town=Bourgoin-Jallieu|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Pro IP|
profid=|
desc=Mise en place de solutions ERP comme Dolibarr sur nos serveurs ou dans votre entreprise, assistance et formation|
web=http://wwww.proip.fr|
email=mailto:contact@proip.fr|
zip=62129|
town=Clarques|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Proxy-Media|
profid=|
desc=Services Informatiques aux artisans et independants|
email=mailto:contact@proxy-media.fr|
zip=17340|
town=Chatelaillon|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=PTMSoft SARL|
profid=520 618 646 00019|
desc=Société de services et de développement logiciel. Installation Dolibarr sur nos serveurs ou dans votre entreprise, assistance et configuration.|
web=http://www.ptmsoft.fr|
email=[mailto:contact@ptmsoft.fr?subject=Contact%20de%20la%20page%20Dolibarr%20Suppliers%20France contact@ptmsoft.fr]|
zip=68890|
town=Mulhouse, Colmar|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
logo=Logo PTMSoft.png
}}

{{TemplateCompany|
name=SIMICAR|
profid=832 284 616 00014|
desc=Société de services et de développement logiciel. Faire de Dolibarr Vote Dolibarr.|
web=http://www.simicar.fr|
email=[mailto:contact@simicar.fr]|
zip=29290|
town=Saint-Renan|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo v2.svg.png
}}

{{TemplateCompany|
name=Syllene|
profid=|
desc=We install and configure the software Dolibarr to suit your needs and train your users. We can also provide hosting and maintenance of your application.|
web=http://www.syllene.net/|
email=|
zip=|
town=|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Teclib'|
profid=513893503|
partner=yes|
desc=
Teclib est une société de services en informatique au capital de 400 000€. Implantés à Paris, Colmar (Alsace), Caen, Chartres (Région Centre). L'équipe Teclib' rassemble une quarantaine de personnes spécialisées dans l'intégration, hébergement et développements de logiciels libres tels que Dolibarr, Odoo, GLPI, Zimbra, BlueMind, Nagios, Centreon, ... |
web=http://www.teclib.com|
email=[mailto:contact@teclib.com?subject=Contact%20from%20Dolibarr%20Preferred%20Partners%20page contact@teclib.com]|
zip=75001|
town=Paris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=no|
service_formation=yes|
logo=Logo_Teclib.png
}}

{{TemplateCompany|
name=Tiaris|
partner=yes|
profid=|
desc=Solutions and services for small businesses and merchants: e-commerce, maintenance, ERP/CRM Dolibarr, development telecommuting. ecommerce - dolibarr webservice based interface. Saas Offer Dolibarr + ecommerce connection for open source caddies (OsCommerce, Zencart, Crelaoded, Prestashop and others...)|
web=http://www.tiaris.fr/|
email=http://www.tiaris.fr/spip.php?page=contact|
zip=57870|
town=WALSCHEID|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=UTOPSYS - L'Informatique, Professionnelle.|
profid=|
desc=Maintenance, dépannage, conseil, audits, Green IT, solutions open-source de travail collaboratif, installation et maintenance Dolibarr. Bordeaux, CUB, Libourne.|
web=http://www.utopsys.fr|
email=|
zip=|
town=Libourne|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=YON - Your Own Net|
profid=822 430 419 00017|
desc=YON (Your Own Net), Fournisseur de solution numérique, Nous sommes spécialisés dans la fourniture de solutions informatiques pour les professionnelles et les particuliers. Nos solutions vont de l’intégration d’outils Open Source et de logiciels libres à l'hébergement de logiciels.|
web=http://yourownnet.net/|
email=mailto:contact@yourownnet.net|
zip=79|
town=Niort et Grand Ouest|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
logo=|
}}

{{TemplateCompany|
name=Weedoo Digital|
profid=831 555 008 000 18 (SIRET)|
desc=Weedoo Digital est un fournisseur de solutions cloud et digitales pour entreprises. Nos services s’étendent de l’hébergement CLOUD aux solutions de gestion pour entreprises, en passant par le développement web et le E-marketing.|
web=https://www.weedoo.digital/|
email=https://www.weedoo.digital/contactez-nous/|
zip=01|
town=Ain et Rhône-Alpes|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=WEBINFOPRO|
profid=|
desc=Society Computers and Internet service for small businesses located in the suburbs west of Paris. One of the main activities is the integration of open source software.|
web=http://www.webinfopro.fr/|
email=|
zip=|
town=|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Z-Application|
profid=|
desc=Développement personnalisé et assistance à la installation-migration. Support sur site possible dans le département Manche (50).|
web=https://www.z-application.com/|
email=|
zip=50250|
town=Coutances - Cherbourg - Saint-Lô|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}
{{TemplateCompany|
name=Paulo Oliveira|
desc=Installation, configuration et personnalisation de dolibarr. Intégration de Dolibarr avec d'autres systèmes. Développement de modules et améliorations de l'interface utilisateur. Je suis le développeur des modules customizeforms, customizeinterface, categorizeall et pixbrasil chez dolistore|
web=https://empresalivre.com/demo2/|
zip=90460-160|
town=Porto Alegre, Rio Grande do Sul|
email=paulorcdo@gmail.com|
country=Brazil|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

Setup Other

2022-02-25T16:47:01Z

Iouston: /* Invoice Module */ add INVOICE_USE_RETAINED_WARRANTY

[[fr:Paramétrage_Divers]]
[[es:Configuración_Varios]]
[[de:Erweiterte_Einstellungen]]
[[zh:其他设置]]


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

'''Help About Screen''': Other setup

'''Menu Path''': Home ► Setup ► Other

'''Introduction'''

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

{{warning|32px}} This page contains the list of some advanced development parameters. In most cases, it is parameters for internal usage, development, external modules, features in development not stable or that may lead to security risk. For standard usage of Dolibarr, such parameters '''SHOULD NOT''' be used. All experimental options are NOT supported. They may be removed in a future, modified at any version and break stability of your application.

To enable/override a parameter you have to define the constant name and set it to 1 (unless otherwise stated) in <code>Home ► Setup ► Other Setup</code>

The options here may not be documented since they are not stable and unsupported (remember they are experimental or development options). The basic format of how the list is written is broken down in the example below:

HIDDEN_CONFIG ► ''Description of config and goal'' ► ''(specific version information) or values''
<center>
__TOC__
</center>
=Global Options=

*'''ADD_UNSPLASH_LOGIN_BACKGROUND''' ► The background image will be refreshed on every login page refresh. Background image is pulled from the popular open source image website Unsplash. If an already saved static background image exists, then this code will override it (but not delete the saved image). Warning: Using this may allow this external website to steel your login credentials ► (v10.0)

*'''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 fail by smartphone applications like [[Application Android - DoliDroid]] breaking some features when using Dolibarr from this application.

*'''MAIN_AUTOFILL_DATE''' ► If this constant is defined (to something other than <code>0</code>), the date of invoice, proposal, order or payment are auto-filled with the current date. It is highly recommended to NOT ENABLE this feature. This can create a lot of input errors with data not validated by users. This leads to incorrect values saved in the database causing confusion when you have to do your accountancy reports!

*'''MAIN_AUTO_TIMESTAMP_IN_PUBLIC_NOTES''' ► Add a timestamp and user automatically when editing the ''public'' note.

*'''MAIN_AUTO_TIMESTAMP_IN_PRIVATE_NOTES''' ► Add a timestamp and user automatically when editing the ''private'' note.

*'''MAIN_COUNTRIES_IN_EEC''' ► Country list in European Area (For VAT purpose) ► (v10.0-v13.0). From v14, do not use this anymore (remove the constant if you set it and instead set if the country is in Europe or not from the dictionary of countries).

*'''MAIN_DEFAULT_PAYMENT_TERM_ID''' ► With ID of a payment term, will use this as default payment term each time you create a new proposal, order, invoice (customer and supplier)
*'''MAIN_DEFAULT_PAYMENT_TYPE_ID''' ► With ID of a payment type, will use this as default payment type each time you create a new proposal, order, invoice (customer and supplier) ► (v12.0)

*'''MAIN_DEFAULT_LANGUAGE_FILTER''' ► Useful if you do not want to show <code>en_US</code> language option in combo boxes (other languages can easily be removed in <code>langs</code> directory but not <code>en_US</code>) ► (v10.0)

*'''MAIN_LANGUAGES_ALLOWED''' ► Is a list of languages without spaces, example : <code>fr_FR,en_US,de_DE,it_IT</code> If defined, only those languages will appear in combos. ► (v11.0)

*'''MAIN_DISABLE_NOTES_TAB''' ► Show or hide notes tab in the card page

*'''MAIN_DISABLE_CONTACTS_TAB''' ► Show or hide contacts tab in the card page

*'''MAIN_DISABLE_FULL_SCANLIST''' ► Disables the complete scan of tables to allow the pagination to show total number of pages. May be useful to activate on systems with a very high quantity of data (tables with more than 2 000 000 records).

*'''MAIN_DISABLE_JQUERY_JNOTIFY''' ► Disable usage of <code>JNotify</code> to show confirm or error messages

*'''MAIN_DISABLE_AJAX_COMBOX''' ► If you have a large number of third parties or products, you can disable the autocomplete feature on the third parties list by setting this constant to <code>1</code> ► (v3.6.0+)
*'''MAIN_DISABLE_MULTIPLE_FILEUPLOAD''' ► Disable users to upload multiple files at once.
*'''MAIN_DISABLE_TRUNC''' ► Disable all truncings in select list. ► (v7.0+)

*'''MAIN_DISABLEDRAFTSTATUS''' ► Disable the status "Draft" for some objects (project, donation, ...) so the object is directly created with status "Validated"

*'''MAIN_DOC_USE_OBJECT_THIRDPARTY_NAME''' ► Add name of thirdparty at begin of generated document.

*'''MAIN_DOC_USE_TIMING''' ► Add a timestamp at end of generated document. Value must be format of timestamp. For example: <code>%Y%m%d%H%M</code> (only for ODT files)

*'''MAIN_DOC_UPLOAD_NOT_RENAME_BY_DEFAULT''' ► Disable the auto renaming on upload file ► (v10.0)

*'''MAIN_DOL_SCRIPTS_ROOT''' ► Define directory who contains 'scripts' directory (e.g. <code>/var/www/dolibarr</code>). Value of this variable may be requested by some external script or tools.

*'''MAIN_ENABLE_LOG_TO_HTML''' ► If this constant is defined, it is possible to have logs inside pages by adding the parameter <code>&logtohtml=1</code> into URL.

*'''MAIN_ENABLE_IMPORT_LINKED_OBJECT_LINES''' ► Allow to import lines into current document from "linked" compatible documents ► (v8.0+)

*'''MAIN_FIRST_TO_UPPER''' ► Dolibarr add uppercase to Third Parties, 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_ALL_TO_UPPER''' ► Dolibarr puts uppercase for Third Parties, 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. ► (v11.0)

*'''MAIN_ALL_TOWN_TO_UPPER''' ► Dolibarr puts uppercase for town names if not done. ► (v13.0)

*'''MAIN_FILESYSTEM_ENCODING''' ► With some PHP versions, PHP is not able to detect the page code for filesystem of the server OS. To solve this, Dolibarr assumes your OS filesystem is <code>UTF-8</code> if on Linux or OSX system, and <code>ISO-8859-1</code> if on Windows. If not, for example on a Windows server with a NTFS <code>UTF-8</code> pagecode, you can set the variable <code>MAIN_FILESYSTEM_ENCODING</code> to "<code>utf-8</code>".

*'''MAIN_FORCELANGDIR''' ► Relative path of the directory holding your custom <code>langs</code> folder.

*'''MAIN_HTML_TITLE''' ► Can be used to control how the html page title is formatted. If value contains key '<code>noapp</code>', application name will not be output. If value contains '<code>thirdpartynameonly</code>', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: '<code>noapp;thirdpartynameonly</code>'

*'''MAIN_HELPCENTER_LINKTOUSE''' ► Define the URL link to use as the target page for link "I need help" onto logon page

*'''MAIN_LANDING_PAGE''' ► Can choose the first page to show after login (the landing page). This option works as a global option (<code>llx_const</code>) and per user option (<code>llx_user_param</code>). ► (v3.9+)

*'''MAIN_LOGOUT_GOTO_URL''' ► URL to which the user will be redirected after LOGOUT

*'''MAIN_MAXTABS_IN_CARD''' ► Maximum number of tabs visible. Others are grouped into a combo list.

*'''MAIN_MAXLIST_OVERLOAD''' ► Maximum number of line in space's domain.

*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► A warning saying setup of modules is not complete is shown if the number of enabled modules is lower or equal than this value (<code>1</code> if not defined)

*'''MAIN_NO_CONCAT_DESCRIPTION''' ► Allow to use only input custom description in lines (propale, order, invoice) ► (v10.0)

*'''MAIN_ONLY_LOGIN_ALLOWED''' ► Only the specified login is allowed to log in Dolibarr (maintenance mode).

*'''MAIN_OPTIMIZE_SPEED''' ► Use some speed enhancements. See page [[FAQ Increase Performance]] for more information.

*'''MAIN_PROPAGATE_CONTACTS_FROM_ORIGIN''' ► When creating an order, contract, invoice from another object, specific contacts of objects are set as specific contact of the new object when possible. ► (v4.0+)

*'''MAIN_PUBLIC_NOTE_IN_ADDRESS''' ► Show public note in address block ► (v4.0+)

*'''MAIN_REMOVE_INSTALL_WARNING''' ► Remove all security warnings that appear to administrator users if URL <code>/install</code> is public. You should solve the problem if warning occurs, instead of removing the warning! For this, create a file called <code>install.lock</code> into Dolibarr root directory. This will stop the warning but also make the page <code>/install</code> not possible to use, to protect your installation.

*'''MAIN_REPEATCONTACTONEACHTAB''' ► If added and set to <code>1</code>, this adds contacts on all tabs, not only main tab.

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

*'''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND''' ► Change way of rounding total TTC lines, rounding first of after.

*'''MAIN_SERVER_TZ''' ► If you can't set the timezone of your PHP installation, set this constant. Better is to set it to UTC. In future, this constant will be forced to '<code>UTC</code>' so PHP server timezone will not have effect anymore. Examples: <code>Europe/Paris</code>, <code>auto</code>.

*'''MAIN_SEARCH_FORM_ON_HOME_AREAS''' ► Show the search form on home page areas for core modules (Removed after v5 due to global search combo) ► (v6.0+)

*'''MAIN_SEARCH_DIRECT_OPEN_IF_ONLY_ONE''' ► If only one result is found, then setting this value to <code>1</code> will take you direct to the item (default method). Setting the value to <code>0</code> will show the result in the list as a single result ► (v5.0+)

*'''MAIN_SERVICES_ARE_ECOMMERCE_200238EC''' ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country.

*'''MAIN_SHOW_TUNING_INFO''' ► Add tuning information into javascript console. Better when xdebug is enabled.

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show also technical IDs on elements cards or some lists (not supported everywhere).

*'''MAIN_SHOWDATABASENAMEINHELPPAGESLINK''' ► Show database name in upper help menu ► (v8.0+)

*'''MAIN_USE_ALTERNATE_TRANSLATION_FOR''' ► List of fields per object that need an alternate translation. Example: <code>MAIN_USE_ALTERNATE_TRANSLATION_FOR=societe:name,town;contact:firstname,lastname</code>

*'''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_USE_JQUERY_JEDITABLE''' ► Allow to update from screen, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this feature, because it bypasses some business actions (updates on other data that should be done consistently) and ignores business controls on data you saved. Consequently this feature breaks consistency of data and possibly the stability of the 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_USE_OLD_SEARCH_FORM''' ► Display the old search form in left menu.

*'''MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS''' ► Allow to force the VAT rate to a given value (instead of higher VAT rate of country) if the VAT rate of product was not defined.

*'''MAIN_USE_VAT_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID_ARE_INDIVIDUAL''' ► If the buyer is a company that is in Europe but has no valid intracommunautary VAT ID, it is processed like if it is an individual, not a company. TODO: Must be implemented into accountancy module too instead of being set to <code>1</code> systematically into accountancy module.

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_INDIVIDUAL_CUSTOMER_OUT_OF_EEC''' ► For to use the default VAT of product for individual customers that are out E.E.C. (European Economic Community) ► (v7.0+). ''There is no reason to use this.''

*'''MAIN_VIEW_LINE_NUMBER''' ► Shows a line number for each line of products/services at documents like proposal / order / invoice. Only on screen, not on PDF.

*'''MAIN_VIEW_LINE_NUMBER_IN_LIST''' ► Shows a line number in lists ► (v12.0)

*'''MAIN_VOLUME_DEFAULT_ROUND''' ► Accuracy of volume (number of decimals)

*'''MAIN_VOLUME_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''MAIN_WEIGHT_DEFAULT_ROUND''' ► Accuracy of weight (number of decimals)

*'''MAIN_WEIGHT_DEFAULT_UNIT''' ► Default unit for weight (<code>0=kg</code>, <code>-3=g</code>, ...)

*'''USER_HIDE_INACTIVE_IN_COMBOBOX''' ► Disable display inactive users in combobox.

*'''MAIN_DISABLE_PDF_THUMBS''' ► Disable thumbs PDF in case of imagick bug

*'''MAIN_KEEP_REF_CUSTOMER_ON_CLONING''' ► Keep the Customer Reference on cloned object (Propal/Invoice)

*'''MAIN_DONT_KEEP_NOTE_ON_CLONING''' ► Remove the object notes during cloning ► (v11.0)

*'''MAIN_DOC_SORT_FIELD''' ► Set the default sorting field on document page (name by default) ► (v11.0)

*'''MAIN_DOC_SORT_ORDER''' ► Set the default sorting order (ASC or DESC) on document page (ASC by default) ► (v11.0)

*'''MAIN_USE_ZIPTOWN_DICTIONNARY''' ► Use dictionary ZIP for create card.

*'''MAIN_USE_TOP_MENU_SEARCH_DROPDOWN''' ► Show search in top menu with theme eldy ► (v11.0)

*'''MAIN_PHONE_SEPAR''' ► Separ phone number other space ► (v12.0)

*'''GRAPH_USE_FISCAL_YEAR''' ► Widgets uses fiscal year

*'''SHOW_SOCINFO_ON_PRINT''' ► Permit to add user company information on each printed document (when click on Dolibarr print button) ► (v12.0)

*'''MAIN_FEATURES_LEVEL''' ► Level of features to show: <code>-1=stable+deprecated</code>, <code>0=stable only (default)</code>, <code>1=stable+experimental</code>, <code>2=stable+experimental+development</code>

*'''MAIN_SHOW_TECHNICAL_ID''' ► Show technical id for object.

*'''MAIN_HTTP_CONTENT_SECURITY_POLICY''' ► Allows you to fill in the content security rules ► (v6.0)

*'''SOCIETE_ON_SEARCH_AND_LIST_GO_ON_CUSTOMER_OR_SUPPLIER_CARD''' ► Allow to change the link of the third party to customer/supplier card instead of contact card on List.

*'''MAIN_MODULE_SETUP_ON_LIST_BY_DEFAULT''' ► If set to "common" the setup module becomes list by defaut

*'''MAIN_PAGESIZE_CHOICES''' ► Configure select field to choose number of lines displayed on listing (<code>10:10,15:15,20:20,30:30,40:40,50:50,100:100,250:250,500:500,1000:1000,5000:5000</code>).

*'''MAIN_USE_TOP_MENU_QUICKADD_DROPDOWN''' ► Add a dropdown menu with shortcuts to create new objects ► (v13.0)

*'''MAIN_EMAILCOLLECTOR_MAIL_WITHOUT_HEADER''' ► Remove the header stored by email collector ► (v13.0)

*'''MAIN_USE_VAT_OF_PRODUCT_FOR_COMPANIES_IN_EEC_WITH_INVALID_VAT_ID'''

*'''MAIN_OPTIMIZEFORTEXTBROWSER''' ► Optimise interface for a text only browser. This variable is set to 1 automatically if your browser is lynx or links

*'''MAIN_NB_OF_YEAR_IN_WIDGET_GRAPH''' ► Set the number of years visible on some graph of some widgets (2 is default value)

*'''MAIN_CREATEFROM_KEEP_LINE_ORIGIN_INFORMATION'''

*'''API_DISABLE_LOGIN_API ►''' (v14.0)

=Security Options=

*MAIN_SECURITY_ANTI_SSRF_SERVER_IP ► Can set a complete list of IPs of server.

*MAIN_SECURITY_CSRF_WITH_TOKEN ► Activate a second anti-CSRF protection on POST (so 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 more powerful. ► (v5.0+)

*MAIN_MODULES_FOR_EXTERNAL ► Limit available modules for external users. By default value is '<code>facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda</code>'

*MAIN_ALLOW_SVG_FILES_AS_IMAGES ► Allow to use SVG file as image files. Warning: This may introduce security vulnerability (javascript can be embedded into SVG file).

*MAIN_RESTRICTHTML_ONLY_VALID_HTML ► Refused parameter if value is not a valid HTML content.

*MAIN_RESTRICTHTML_REMOVE_ALSO_BAD_ATTRIBUTES ► Sanitize also non standard attributes on HTML content.

[[#Top|(back to top)]]

=Accountancy Module=

*ACCOUNTANCY_COMBO_FOR_AUX ► Add graphic option for ACCOUNTANCY_COMBO_FOR_AUX. Having this option on may slow down and even freeze the accounting features if you have a very large number of thirdparties ► (v10.0)
*ACCOUNTING_DEFAULT_NOT_NOTIFIED_VALIDATION_DATE ► Set to 1 to avoid validating the lines with the accountancy export. ► (v14.0)

[[#Top|(back to top)]]

=Agenda Module=

*AGENDA_ALL_CALENDARS ► Change the default view of calendar pages to see all the Agenda's (instead or yours only be default)

*AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS ► To automatically set end date of event to start date + delta on event creation page.

*AGENDA_DISABLE_LOCATION ► Disable location field in action card ► (>=v5.0)

*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''''').

*MAIN_ADD_EVENT_ON_ELEMENT_CARD ► Allow to create an event from a document (proposal, order, invoice)

*AGENDA_SUPPORT_PRIORITY_IN_EVENTS ► Allow to have priorities in events ► (>=v13.0)

[[#Top|(back to top)]]

=Bank Module=

*BANK_CAN_RECONCILIATE_CASHACCOUNT ► Can reconciliate cash accounts ► (v3.8)

*BANK_DISABLE_CHECK_DEPOSIT ► Disable check deposit feature

*BANK_ASK_PAYMENT_BANK_DURING_ORDER ► Ask bank account during creation of an order

*BANK_ASK_PAYMENT_BANK_DURING_PROPOSAL ► Ask bank account during creation of a proposal

*BANK_USE_OLD_VARIOUS_PAYMENT ► To allow to enter miscellaneous payments (not covered by other modules) using old method. '''''Deprecated'''''. Entering various payment is preferred ► (<=v12.0).
*MAIN_IBAN_IS_NEVER_MANDATORY ► IBAN and BIC informations not mandatory. (V15)

[[#Top|(back to top)]]

 

=BOM and MO Module=

*ALLOW_USE_KITS_INTO_BOM_AND_MO

[[#Top|(back to top)]]

 

=Inalterable Log Module=

*BLOCKEDLOG_ADD_ACTIONS_SUPPORTED ► Can complete list of triggered action that are logged

[[#Top|(back to top)]]

 

=Contracts=

*CONTRACT_SUPPORT_PRODUCTS ► Products are also suggested into module contract.
*
*CONTRACT_ALLOW_EXTERNAL_DOWNLOAD

[[#Top|(back to top)]]

=Cron module=

*CRON_DISABLE_KEY_CHANGE ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*CRON_DISABLE_TUTORIAL_CRON ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*CRON_WARNING_DELAY_HOURS ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

[[#Top|(back to top)]]

 

=Direct Debit Orders=

*WITHDRAWAL_ALLOW_ANY_INVOICE_STATUS ► If this option is set, all invoices status (even already paid) may appear on the list of invoices qualified for a direct debit payment. This is the list of invoices with a payment request done, and not linked to a direct debit payment. By default, only "unpayed" invoices are used to avoid to pay twice the same invoice.

[[#Top|(back to top)]]

=Donation Module=

*DONATION_USE_THIRDPARTIES ► If this option is set, a thirdparty field appear on donation forms.

[[#Top|(back to top)]]
=Email and SMS=

*MAIN_MAILFORM_DISABLE_ENTERKEY ► Activate javascript code to disable the enter key in the MAIL form. ► (>= 8.0.1)

*MAIL_PREFIX_FOR_EMAIL_ID ► Prefix for the mails ID. Default value is <code>$_SERVER["SERVER_NAME"]</code> ► (>= 8.0.1)

*MAIN_MAIL_DEBUG ► Write content with header of last mail into file <code>dolibarr_mail.log</code> into directory <code>dolibarr_main_data_root</code>.

*MAIN_SMS_DEBUG ► Write content of SMS sent into file <code>dolibarr_sms.log</code> into directory <code>dolibarr_main_data_root</code>.

*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 <code>-f</code>. This option is here to ask Dolibarr to call the function mail of PHP by adding value for the option <code>-f</code>. 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 Linux 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 asks PHP to provide this parameter when sending a mail. Note that another solution is to edit the mail.force_extra_parameters=-ba into <code>php.ini</code> 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 <code>orange.fr</code> or <code>hotmail.com</code>

*MAIN_MAIL_DO_NOT_USE_SIGN ► Do not add user signature at end of suggested pre-defined email

*MAIL_FORCE_DELIVERY_RECEIPT_INVOICE ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Invoice'' module.

*MAIL_FORCE_DELIVERY_RECEIPT_ORDER ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Order'' module.

*MAIL_FORCE_DELIVERY_RECEIPT_PROPAL ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Proposal'' module.

*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 recipient 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 third party 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 third party or object, the email exchange is related to.

*MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL ► Restrict sending of 1 email message to <code>x</code> recipients for same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include 1000 recipients in 1 message. Note that MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL, MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL and MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL are also available.

*MAIN_MAIL_FORCE_CONTENT_TYPE_TO_HTML ► Force to send all email (event with text only content) as HTML formatted email.

*MAIN_MAIL_USE_MULTI_PART ► Forge email content using an alternate text part ► (for 5.0.2+). By default with 6.0+
*MAIN_INFO_SOCIETE_MAIL_ALIASES ► add address aliases for the from field on mail. Set his value with "Firstname Name <firstname.lastname@mydomain.tld, Otherfirstname OtherlastName <othermail@mydomain.tld>,..." ► (v5.0.0+)

*MAIN_MAIL_ADD_INLINE_IMAGES_IF_IN_MEDIAS ► If images were stored into the medias directory from CKEditor, then images into emails are replaced with "inline content". This may increase seriously risk of being detected as SPAM.

*MAIN_COPY_FILE_IN_EVENT_AUTO ► Add attachement document on event auto generated by sending email from dolibarr. ► (v6.0+)

*MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD.

*MAIN_MAIL_ENABLED_USER_DEST_SELECT ► Show also internal users into list of recipients of email in email sending form ► (v8.0+)
*

[[#Top|(back to top)]]

 

=Emailing Module=

*MAILING_PREFIX_FOR_EMAIL_ID ► Set the value that will be used to compose the "Email ID" into email headers. If you set this value to '<code>SERVER_NAME</code>', the virtual host of web server will be used. By default, this is not defined, so a hash key, unique to each instance, is used.

*MAILING_NO_USING_PHPMAIL ► If set, the module emailing can't be used with mail setup of "phpmail". Using a thirdparty SMTP server is required. You can complete warning message by adding an email to contact for setup help with constant <code>MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS</code>.

*MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS ► Contains the email of contact to show into the message visible to a user when he try to use emailing module without SMTP server and if option MAILING_NO_USING_PHPMAIL is set to on.

*MAILING_LIMIT_WARNING_PHPMAIL ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is on "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.

*MAILING_LIMIT_WARNING_NOPHPMAIL ► Show a warning message (var contains the '''message to show''', or '''translation key''') on emailing send form if setup is something else than "phpmail". Note: The application always try to translation the message considering the message is a translation key, before showing the translation or message if translation was not found.
*EMAILING_USE_ADVANCED_SELECTOR ► Enable the advanced selector for recipients.

*MAILING_LIMIT_SENDBYWEB ► Restrict number of emails you can send in same sending session with emailing module from GUI. The value "<code>dolibarr_mailing_limit_sendbyweb</code>" if defined into config file is used in priority for this limit. A negative value means, sending by web is forbidden.

*MAILING_LIMIT_SENDBYCLI ► Restrict number of emails you can send in same sending session with emailing module from CLI script. The value "<code>dolibarr_mailing_limit_sendbycli</code>" if defined into config file is used in priority for this limit.

[[#Top|(back to top)]]

 

=Expense Report=

*EXPENSEREPORT_ALLOW_OVERLAPPING_PERIODS ► Can enter several expense reports on same or overlapping date periods. ► (v7.0+)

*EXPENSEREPORT_OVERRIDE_VAT ► Setting this constant to 1 will allow expense reports to show VAT even if the global VAT setting is off ► (v10.0)

*EXPENSEREPORT_USE_OLD_NUMBERING_RULE ► The module Expense Report use numbering rules that you can setup (like other modules do). If you need to keep the hard-coded numbering rule of expenses report used in v6.0 set this constant to 1 ► (>=v7.0+)

*MAIN_USE_EXPENSE_IK ► This feature allows you to set index kilometers against a mileage index for different types of vehicles. ► (v7.0+)

*MAIN_USE_EXPENSE_RULE ► This feature allows you to set a variety of rules per user/group/all so they can only create reports within their limits. ► (v7.0+)

[[#Top|(back to top)]]

 

=Export Module=

*EXPORT_CSV_SEPARATOR_TO_USE ► String value to use as default separator to delimit fields of exported files (by default Dolibarr uses "<code>,</code>"). Example: EXPORT_CSV_SEPARATOR_TO_USE=<code>;</code>

*EXPORT_CSV_FORCE_CHARSET ► Choose the charset used in the output file built by the CSV exporter. By default it is ISO-8859-1. Example: EXPORT_CSV_FORCE_CHARSET= <code>utf-8</code>

*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 (<code>"</code>).
*EXPORTS_SHARE_MODELS ► Share export models between users.

[[#Top|(back to top)]]

=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 added in front of payment cell, into the page to make online subscription.

[[#Top|(back to top)]]

=Interventions Module=

*FICHINTER_CLASSIFY_BILLED► Allow to classify an intervention card as "Billed". This add also trigger <code>FICHINTER_CLASSIFY_BILLED</code> into list of possible automatic event into agenda.

*FICHINTER_DISABLE_DETAILS► Disable entry of details line on intervention. Can validate with no line.

[[#Top|(back to top)]]

=Invoice Module=

*MAIN_DEPOSIT_MULTI_TVA ► In deposits invoice, creates one line per VAT rate from the origin document ► (6.0)

*INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED* ► If a credit note was partially refunded (a refund was sent to the customer), with common situation, we wait to have the remain refunded too. With this option, it is possible to convert the remain of invoice into a discount to reuse it into another invoice.

*SUUPLIER_INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED* ► See INVOICE_ALLOW_REUSE_OF_CREDIT_WHEN_PARTIALLY_REFUNDED, but for supplier credit notes.

*INVOICE_CAN_ALWAYS_BE_EDITED ► Allow to edit invoices even if payment was started. Note: If the module "BlockedLog" is active (required in some countries for legal reasons), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*INVOICE_CAN_ALWAYS_BE_REMOVED ► Allow to always delete invoices (even if invoice is not last one). Note: If the module "BlockedLog" is active (required by some countries for legal reason), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

*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_DEPOSITS_ARE_JUST_PAYMENTS ► An old way to create initial payment. This treats deposit invoices as a special case and not as legal deposit invoice. 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. WARNING: In a lot of european countries, using this option is not allowed.

*FACTURE_SENDBYEMAIL_FOR_ALL_STATUS ► Can send invoice by email to customer even if invoice has status "draft".

*INVOICE_CREDIT_NOTE_STANDALONE ► Start implementation to allow a credit note even without invoice (dangerous) ► (v3.9)

*INVOICE_USE_SITUATION ► Enable the "situation invoice" feature. Warning, this feature is bugged and may not be compatible with the final version of the features once bug will be solved.

*INVOICE_USE_SITUATION_CREDIT_NOTE ► Enable the "situation credit note" feature (need <code>INVOICE_USE_SITUATION</code>) ► (v8.0)
*INVOICE_USE_RETAINED_WARRANTY ► Enable the retained warranty on invoice ► (v14.0)

*INVOICE_DISABLE_DEPOSIT ► Disable deposit invoices

*INVOICE_DISABLE_REPLACEMENT ► Disable replacement invoices

*INVOICE_DISABLE_CREDIT_NOTE ► Disable credit notes

*MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT ► See PDF option

*MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT_COLUMN ► See PDF options

*WORKFLOW_BILL_ON_SHIPMENT ► Change label of button with suitable label when you need to create invoice on shipments

*INVOICE_ALLOW_EXTERNAL_DOWNLOAD ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. Use the tag __DIRECTDOWNLOAD_URL_INVOICE__ in email template to insert it. ► (v7.0+)

*INVOICE_POINTOFTAX_DATE ► Add Point of Tax Date on invoices for country-specific legality reasons ► (v4.0+)
*FACTURE_ENABLE_NEGATIVE ► Can validate an invoice when amount is negative

*FACTURE_ENABLE_NEGATIVE_LINES ► Allows to add negative lines to an invoice ► (v8.0.2+)

*INVOICE_USE_DEFAULT_DOCUMENT ► Allow user to select a default invoice documents models according to invoice type. On invoice create page, the model is dynamically changed on invoice type selection. ► (v9.0+)

*FACTURE_REUSE_NOTES_ON_CREATE_FROM ► Reuse the Public Note and Private note of the previous object (Proposal,...) when creating the bill.
*FACTUREFOURN_REUSE_NOTES_ON_CREATE_FROM ► Reuse the Public Note and Private note of the previous object when creating the supplier bill ► (V13.0)
*MAIN_SHOW_FACNUMBER_IN_DISCOUNT_LIST ► Display the reference of credit notes in discount list when creating the bill.
*INVOICE_ALLOW_FREE_REF ► Capability to change reference of an invoice. This will be possible as long as the invoice has the status “Draft” and only if your country is not in Europe(V11)

*INVOICE_DISALLOW_REOPEN

*INVOICE_MAX_FUTURE_DELAY ► Numbers of seconds allowed for billing in the future ► (V14.0)
*INVOICE_AUTO_NEXT_MONTH_ON_LINES ► Increase start date and end date by one month, if an invoice line is a clone of a time based service AND if this services started on the first day of month and ended on the last day of month ► (V13.0.1)

[[#Top|(back to top)]]

=Leave=

*MAIN_NON_WORKING_DAYS_INCLUDE_SATURDAY ► Set this value to 0 if you want to have the saturday as a working day
*MAIN_NON_WORKING_DAYS_INCLUDE_SUNDAY ► Set this value to 0 if you want to have the sunday as a working day

=Look or Theme=

*MAIN_FAVICON_URL ► favicon url

*MAIN_EASTER_EGG_COMMITSTRIP ► Show a comic image from the CommitStrip website. Images are refreshed daily. ► (v6.0+)

*MAIN_STATUS_USES_CSS ► Change status design using new style ► (v10.0+)

*MAIN_APPLICATION_DISABLED_STATEBOARD ► Hide the stateboard of the main page

*MAIN_APPLICATION_DISABLED_WORKBOARD ► Hide the workboard of the main page

*MAIN_INCLUDE_GLOBAL_STATS_IN_OPENED_DASHBOARD ► This conf will auto remove global stats box item if there are already in the new dashboard of opened elements and keep displayed stats on the opened item box (not only on mouse over) ► (v11.0+)

*MAIN_USE_TOP_MENU_SEARCH_DROPDOWN ► Actually only for eldy theme, this conf move search input to top menu and use new design too ► (v11.0+)

*THEME_AGRESSIVENESS_RATIO ► This conf can be used to increase/decrease agressiveness of colors. Value 0 is medium, value is between -100 (light grey colors) to +100 (very flashy colors) ► (v11.0+)

*THEME_SHOW_BORDER_ON_INPUT
*MAIN_DISABLE_GLOBAL_WORKBOARD ► Hide the workboard of the main page ► (v13.0+)

[[#Top|(back to top)]]

=MultiCurrency=

*MAIN_MULTICURRENCY_ALLOW_SYNCHRONIZATION ► Enable CurrencyLayer API synchronization

[[#Top|(back to top)]]

=Order Module=

*MAIN_USE_PROPAL_REFCLIENT_FOR_ORDER => Copy customer reference from proposal to order. ► (v7.0+)

*ORDER_REQUIRE_SOURCE => Make the input field "Source of order" mandatory.

*ORDER_VALID_AFTER_CLOSE_PROPAL => When an order is created on a proposal close, the order is directly defined with status "Validated".

*ORDER_ALLOW_EXTERNAL_DOWNLOAD => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*ORDER_ENABLE_NEGATIVE => Can validate an order when amount is negative

*THIRDPARTY_PROPAGATE_EXTRAFIELDS_TO_ORDER => Copy also extrafields from thirdparty to order (if name match). ► (v11.0+)

[[#Top|(back to top)]]

 

=PDF Options=

*MAIN_ADD_PDF_BACKGROUND ► Define this constant with short name of a PDF file (example "<code>mypdf.pdf</code>") that must be saved into directory "<code>documents/mycompany</code>". 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_DISABLE_FORCE_SAVEAS ► If your browser always asks to save downloaded files on disk (like PDF), try this this option. File may be displayed directly in your browser.

*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 servers with low CPU.

*MAIN_DISABLE_PDF_COMPRESSION ► Disable PDF compression.

*MAIN_DOCUMENTS_LOGO_HEIGHT ► Can force height of the logo on PDF.

*MAIN_DOCUMENTS_WITH_PICTURE_WIDTH ► Can change size of picture when hidden option <code>MAIN_GENERATE_PROPOSALS_WITH_PICTURE</code> is used. By default value is <code>20</code>.

*MAIN_GENERATE_DOCUMENTS_SHOW_FOOT_DETAILS ► Adding the company address at the bottom of the page. Disabled by default

*MAIN_GENERATE_PROPOSALS_WITH_PICTURE ► Include the first image of the product into the line of the generated PDF for customer proposals.

*MAIN_GENERATE_INVOICES_WITH_PICTURE ► Include the first image of the product into the line of the generated PDF for customer invoices.

*MAIN_GENERATE_SUPPLIER_PROPOSAL_WITH_PICTURE ► Include the first image of the product into the line of the generated PDF for supplier proposals ► (v5.0.3+)

*MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT ► Disable VAT on generated documents. like for an association. (Works with crabe template)

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

*MAIN_INVERT_SENDER_RECIPIENT ► Invert sender and recipient in some PDF. Note: This option is set automatically if country if Germany.

*MAIN_ODT_AS_PDF ► Activate ODT to PDF conversion. Value can be "libreoffice" or "unoconv". Do not use value '''<nowiki/>'jodconverter'<nowiki/>''' any more, as it is declared deprecated and partly not functional, use value '''<nowiki/>'libreoffice'''' instead, it requires only '''soffice''' (OpenOffice or LibreOffice) installed on server (use '''apt install soffice libreoffice-common libreoffice-writer''').

If you got this error: javaldx failed! Warning: failed to read path from javaldx with no return to prompt when running soffice --headless -env:UserInstallation=file:"/tmp" --convert-to pdf --outdir xxx ./yyy.odt, check that directory defined into env:UserInstallation parameters exists and is writeable.

You may also have a look at this page if your server is on Windows: [[Générer automatiquement des documents PDF à partir de fichier ODT avec Doliwamp]]

*MAIN_ODT_AS_PDF_DEL_SOURCE ► For ODT generation. If set, then initial behaviour is conserved but ODT file is removed when option to convert it as PDF (see previous) is on. Disabled by default

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

*MAIN_PDF_FORCE_FONT_SIZE ► To force size of font (by default 10). For example "<code>12</code>" ► (v11.0)

*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: <code>220,220,200</code>

*MAIN_PDF_USE_LARGE_LOGO ► Use the original logo with its higher resolution into the PDF instead of the small thumb. This may lead to very very large PDF !

*MAIN_USE_BACKGROUND_ON_PDF ► Define this constant with short name of an image (example "<code>myimage.jpg</code>") that must be saved into directory "<code>documents/mycompany/logos</code>". This will add this background image into your generated PDF files.

*MAIN_USE_COMPANY_NAME_OF_CONTACT ► Use contact name and information rather than company

*MAIN_PDF_ADDALSOTARGETDETAILS ► If 1, add details of reipient on generated PDFs (email, fax, url and phone). Can be useful in cases where a printed order/invoice etc is given to a delivery driver/courier etc.

*MAIN_TVAINTRA_IN_SOURCE_ADDRESS ► Show VAT N° in source address of PDF to comply with legalities in certain countries. Note that VAT number should be already visible in footer of page ► (v8.0.1+)

*MAIN_PDF_PROPAL_USE_ELECTRONIC_SIGNING ► Add optional esign field in pdf propal ► (v8.0+)

*MAIN_PROFID1_IN_SOURCE_ADDRESS ► Show Professional ID 1 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*MAIN_PROFID2_IN_SOURCE_ADDRESS ► Show Professional ID 2 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*MAIN_PROFID3_IN_SOURCE_ADDRESS ► Show Professional ID 3 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*MAIN_PROFID4_IN_SOURCE_ADDRESS ► Show Professional ID 4 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*MAIN_PROFID5_IN_SOURCE_ADDRESS ► Show Professional ID 5 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

*MAIN_PROFID6_IN_SOURCE_ADDRESS ► Show Professional ID 6 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

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

*PDF_BOLD_PRODUCT_REF_AND_PERIOD ► Add more visibility (bold) on product ref and period of service in desc. ► (v12.0)

*PDF_HIDE_PRODUCT_REF_IN_SUPPLIER_LINES ► Modify the use/position of Supplier Ref/Internal Ref with the item Label (name) on PDF documents.

Default (constant not set or Value <code>0</code>): Internal ref followed by supplier ref in brackets."COMPANY-REF-001 (Vendor SKU SUPPLIER-REF-001) - LABEL...".

Value <code>1</code>: Supplier ref only eg."SUPPLIER-REF-001 - LABEL...".

Value <code>2</code>: Supplier ref followed by internal ref in brackets. eg."SUPPLIER-REF-001 (InternalRef COMPANY-REF-001) - LABEL...".

*PDF_INCLUDE_ALIAS_IN_THIRDPARTY_NAME ► Include alternative/alias name into name on PDF.

*PDF_SECURITY_ENCRYPTION ► Encrypt PDF produced by dolibarr ► (v?) . See additional parameters :PDF_SECURITY_ENCRYPTION_RIGHTS (block 'modify' or 'copy') - PDF_SECURITY_ENCRYPTION_USERPASS - PDF_SECURITY_ENCRYPTION_OWNERPASS (random if not specified) - PDF_SECURITY_ENCRYPTION_STRENGTH (0 = RC4 40 bit; 1 = RC4 128 bit; 2 = AES 128 bit; 3 = AES 256 bit) - PDF_SECURITY_ENCRYPTION_PUBKEYS Array of recipients containing public-key certificates ('c') and permissions ('p') - For example: array(array('c' => 'file://../examples/data/cert/tcpdf.crt', 'p' => array('print')))

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

*PDF_USE_1A ► PDF files produced by dolibarr respect PDF/A standard ► (v?)

*PDF_USE_ALSO_LANGUAGE_CODE ► The value of this constant must be a language code ('fr_FR', 'en_US', 'sa_SA', ...). If set, the PDF document will contains both language (default and the one defined by the constant).
*DOC_SHOW_FIRST_SALES_REP ► Show the sales representant on header (at least on propal azur and rubis template)
*MAIN_PDF_DASH_BETWEEN_LINES
*
*SHOW_SUBPRODUCT_REF_IN_PDF
*PDF_HIDE_PRODUCT_LABEL_IN_SUPPLIER_LINES ► hide product label in supplier order lines (V15+)

[[#Top|(back to top)]]

=Point of Sale (POS)=

*CASHDESK_SHOW_KEYPAD ► Show a mouse key pad into the 'Simple Point of Sale' module.

*POS_ADDON ► Set this value to an existing numbering module rule (for example '<code>mod_facture_terre</code>', '<code>mod_facture_mars</code>', ...) to force the numbering module to use for invoice ref definition when invoice is created by the POS. For example setting value <code>POS_ADDON</code> to '<code>mod_facture_terre</code>' will use the numbering module '<code>terre</code>' for invoice generated from POS, whatever is the numbering rule defined into invoice module setup (you can also use POS_NUMBERING_TERRE_FORCE_PREFIX and POS_NUMBERING_MARS_FORCE_PREFIX variable to change the prefix used).

*TAKEPOS_ENABLE_SUMUP ► Enable the compatibility of TakePOS with the card reader terminal [https://SumUp.fr SumUp]
*TAKEPOS_CAN_FORCE_BANK_ACCOUNT_DURING_PAYMENT ► Possibility to force the bank account during the payment in TakePOS ► (v13.0)
*
*TAKEPOS_NUMPAD_FORCE_PAYMENT_ICONS_LABELS

[[#Top|(back to top)]]

=Products Module=

*CATEGORY_GRAPHSTATS_ON_PRODUCTS ► Show graph of products with categories and totals in Products Area screen

*MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE ► Avoid customs 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.

*MAIN_DIRECT_STATUS_UPDATE ► Allows you to change the status of the product (''for sale/not for sale for purchase/not for purchase'') directly on the product page via a ''on/off'' switch button. This can be convenient for those who need to quickly disable certain statuses of products without having to go through the editing product page individually. Also can be very useful if used as a filter on the product and product search list. This option doesn't generate a MODIFY trigger, so be careful with external modules. ► (v4.0+)

*MAIN_SEARCH_PRODUCT_BY_FOURN_REF ► Allow to search a product by supplier ref in document's add line form. ► (>= 8.0)

*MAIN_DISABLE_FREE_LINES ► Disallow using free lines to add line in documents ► (>= 8.0)

*MAIN_SHOW_PRODUCT_ACTIVITY_TRIM ► Show Product and Services turnover before for all four quarters tax over recent years recent years on the product area ► (v5.0+)

*PRODUIT_DESC_IN_LIST ► Show long description of product/service into lists.

*PRODUCT_DISABLE_PROPAGATE_CUSTOMER_PRICES_ON_CHILD_COMPANIES ► Disable propagation of prices per customer from a customer to its child company.

*PRODUCT_DISABLE_PUBLIC_URL ► Disable public url in product card ► (v14.0+)
*PRODUCT_DISABLE_STOCK_LEVELS ► Disable properties of stock limits and desired optimal value on product ► (v14.0+)
*PRODUCT_DISABLE_NATURE ► Disable nature in product card ► (v14.0+)
*PRODUCT_DISABLE_WEIGHT ► Disable weight in product card ► (v14.0+)
*PRODUCT_DISABLE_PRICES ► Disable prices in product card ► (v14.0+)
*PRODUCT_DISABLE_ACCOUNTING ► Disable accounting in product card ► (v14.0+)
*PRODUCT_DISABLE_SIZE ► Disable size in product card.

*PRODUCT_DISABLE_LENGTH ► Disable length in product card ► (v4.0+)

*PRODUCT_DISABLE_SURFACE ► Disable surface in product card. ► (v4.0+)

*PRODUCT_DISABLE_VOLUME ► Disable volume in product card.

*PRODUCT_DISABLE_CUSTOM_INFO ► Disable custom info (custom code and country origin) in product/service card.

*PRODUIT_MULTIPRICES_USE_VAT_PER_LEVEL ► When option to use price per level/segment is on, this allows to also set a dedicated vat for each price level.

*PRODUIT_CUSTOMER_PRICES_BY_QTY ► If price per quantity ► ''Experimental''
*PRODUIT_CUSTOMER_PRICES_BY_QTY_MULTIPRICES ► If price per quantity and customer ► ''Experimental''
*PRODUCT_MAX_LENGTH_COMBO ► Limit the length of the label displayed when adding lines in proposals/invoices/orders

*PRODUCT_MAX_VISIBLE_PHOTO ► Show a maximum number of product photos (as thumbnails) on the product main card. Example, setting this constant to '<code>5</code>' will show the first five product photos found on the product card.

*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 ► Add another units on products (Use same dictionnary as default unit feature) and propagate this unit on line of documents.

*RESOURCE_ON_PRODUCTS_RESOURCE_ON_SERVICES ► Allow to affect ressources on products/services ► (v10.0+)
*PRODUCT_SHOW_ORIGIN_IN_COMBO ► Show origin of products when adding lines in proposals/invoices/orders ► (v12.0+)
*PRODUIT_ATTRIBUTES_HIDECHILD ► Add option hide child if variantes

*PRODUCT_ADD_FORM_ADD_TO ► Add a product to a draft proposal/order/invoice, from the product card.
*PRODUCT_DISABLE_SELLBY ► Hide the Sell by date ► (v13.0+)
*PRODUCT_DISABLE_EATBY ► Hide the Eat by date ► (v13.0+)

*PRODUCT_DENY_CHANGE_PRODUCT_TYPE ► Forbid to change the product type

*PRODUCT_SORT_BY_CATEGORY ► Sort the product by categories instead of by ID
*PRODUCT_ADD_NET_MEASURE ► Support Net Measure in product's card.php (For real weight, volume or piece; needed for some business ie fruits, vegetables....). Note brut value is already available natively, use this option only if you need 2 weights, 2 volumes, ...for each product) ► (v11.0.1+)

[[#Top|(back to top)]]

 

=Projects Module=

*PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY ► Can link an object to a project of another thirdparty
*PROJECT_ALLOW_COMMENT_ON_PROJECT ► Add comment feature on a project

*PROJECT_ALLOW_COMMENT_ON_TASK ► Add comment feature on project task

*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_CREATE_ON_OVERVIEW_DISABLED ► Hide the "create ..." button on the overview page ► (v4.0)

*PROJECT_DISABLE_UNLINK_FROM_OVERVIEW ► Enable removing the button from a link in the project overview. ► (>= v8.0.1)

*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 ► Hide the "link to" form on the overview page ► (v4.0)

*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_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_OPEN_ALWAYS_ON_TAB ► Set to value 'task', or 'preview' to always open the project on the given tab instead of main tab.
*
*
*PROJECT_ELEMENTS_FOR_MINUS_MARGIN

[[#Top|(back to top)]]

=Proposals Module=

*MAIN_GENERATE_PROPOSALS_WITH_PICTURE ► Add a picture of the product (the first one found if there are several) into the generated PDF of proposals. Note that using this will reduce the available width for the product description.

*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_PDF_PROPAL_USE_ELECTRONIC_SIGNING ► add optional esign field in pdf propal ► (v8.0+)

*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.

*PROPAL_DISABLE_SIGNATURE ► Do no show the box for signature.

*PRODUIT_PDF_MERGE_PROPAL ► When generating the proposal PDF, all PDFs linked to products linked to proposal are also included into final PDF

*PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

*PROPOSAL_AUTO_ADD_AUTHOR_AS_CONTACT ► Add Proposal Author as user contact follow proposal

*PROPOSAL_PDF_HIDE_PAYMENTTERM ► Do not show the payment term on proposal ► (v11.0+)

*PROPOSAL_PDF_HIDE_PAYMENTMODE ► Do not show the payment mode on proposal ► (v11.0+)

*WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES ► Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.
*PROPAL_REOPEN_UNSIGNED_ONLY ► Do not allow reopening of signed (or billed) proposals. (V15)
*PROPOSAL_ARE_NOT_BILLABLE ► Disable billing button on proposals (V15)

[[#Top|(back to top)]]

 

=Services Module=

*SERVICE_ARE_ECOMMERCE_200238EC ► If seller and buyer are in Europe and buyer is not a company, use the VAT of buying country. For french speaking people, see also the page [[Loi_européenne_TVA_Vente_à_Distance_VAD_et_e-commerce_BtoC]].

*MAIN_FILL_SERVICE_DATES_FROM_LAST_SERVICE_LINE ► (v13.0) On add line form add a button to fill service dates from the last service line

[[#Top|(back to top)]]

=Shipments=

*STOCK_WAREHOUSE_NOT_REQUIRED_FOR_SHIPMENTS ► If set, you can add a shipment line, with no stock source defined. ► (>= 8.0.1)

*SHIPMENT_GETS_ALL_ORDER_PRODUCTS ► Add all order lines in shipment, including the one with 0 in quantity

[[#Top|(back to top)]]

=Stocks=

*SUPPLIER_ORDER_DISABLE_STOCK_DISPATCH_WHEN_TOTAL_REACHED ► Disable stock dispatch when total expected was already received

*STOCK_EXCLUDE_VIRTUAL_PRODUCTS ► If product is a virtual product, we do not manage stock for it.

*ENTREPOT_EXTRA_STATUS ► Instead of the 2 status (Closed, Open), a Warehouse has 3 status: Closed, Open (for all movements), Open (for internal movement only). Internal movement only means you can't use the warehouse to make shipment or receptions.
*SUPPLIER_ORDER_STATUS_FOR_VIRTUAL_STOCK ► For the calculation of virtual stocks, by default supplier orders with the status 3 (ordered) and 4 (partially received) are used. You can enter the list of statuses to be taken into account separated by commas for this calculation (example: 0,1,2,3)
*STOCK_MOVEMENT_LIST_HIDE_UNIT_PRICE ► to hide unit price on some pages (V15+)

[[#Top|(back to top)]]

=Suppliers Module=

*FOURN_PRODUCT_AVAILABILITY ► On the Suppliers price page of the products, activate the supplier product availability. ''This is duplicate feature with delivery_delay introduced with 3.8.''

*RELOAD_PAGE_ON_SUPPLIER_CHANGE ► On creation of a supplier order/invoice, reload form with supplier-specific details when supplier is selected from drop-down list.

*SUPPLIER_INVOICE_WITH_PREDEFINED_PRICES_ONLY ► Restrict selection of products in supplier invoice to only those with a buying price defined for that supplier. ► (v6.0+)

*SUPPLIER_ORDER_AUTOADD_USER_CONTACT ► Add user approving supplier order as a contact automatically.

*SUPPLIER_ORDER_DEFAULT_PAYMENT_MODE_ID ► Set the default payment method for suppliers (<code>rowid</code> in table <code>llx_c_paiement</code>).

*SUPPLIER_ORDER_USE_DISPATCH_STATUS ► Add a status on each dispatch order line when receiving products from suppliers ► (v4.0+)

*SUPPLIER_ORDER_NO_DIRECT_APPROVE ► No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

*SUPPLIER_ORDER_WITH_PREDEFINED_PRICES_ONLY ► Restrict selection of products in supplier order to only those with a buying price defined for that supplier. ► (v6.0+)

*SUPPLIER_ORDER_EDIT_BUYINGPRICE_DURING_RECEIPT ► Can modify the buying price used for PMP calculation when making a stock reception on a supplier order. ► (v6.0+)

*SUPPLIER_PROPOSAL_WITH_PREDEFINED_PRICES_ONLY ► Restrict selection of products in supplier proposal to only those with a buying price defined for that supplier. ► (v6.0+)

*DISPLAY_DISCOUNTED_SUPPLIER_PRICE ► Allow to display discounted supplier price when searching product in supplier documents ► (v10.0)

*MAIN_CAN_EDIT_SUPPLIER_ON_SUPPLIER_ORDER ► Allow to change the supplier on a draft supplier order ► (v10.0)
*
*SUPPLIER_PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD

[[#Top|(back to top)]]

=Third Parties Module=

*COMPANY_AQUARIUM_CLEAN_REGEX ► Add a REGEX rule on the third parties names. It applies a regex replacement pattern on generated code if COMPANY_AQUARIUM_CLEAN_REGEX is set. Value must be a regex with parenthesis. The part into parenthesis is kept, the rest removed. For example if COMPANY_AQUARIUM_CLEAN_REGEX = '<code>^..(..)..(.*)</code>' the first char and second char are removed and the char 5 and 6 too ► (>= 8.0.1)
*SOCIETE_EMAIL_MANDATORY ► E-mail is a mandatory field when creating a thirdparty

*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"

*SOCIETE_SORT_ON_TYPEENT ► The combo list of "type of third party" is sorted on alphabetical order instead of the field "position" that appears into dictionary instead.

*SOCIETE_ASK_FOR_SHIPPING_METHOD ► Shipping method can be predefined on customer card and will be used as default on order creation
*SOCIETE_ADD_REF_IN_LIST ► Displays the code before the name in the lists ► Value 1 -> Code + name + alias ou Code + name if colone alias 2 -> Code + alias 3 -> Alias

*THIRDPARTY_CAN_HAVE_CATEGORY_EVEN_IF_NOT_CUSTOMER_PROSPECT_SUPPLIER ► Possible to add Categories to third parties that are not customer, prospect or supplier.

*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.

*THIRDPARTY_NOTCUSTOMERPROSPECT_BY_DEFAULT ► Do not set status "Customer/Prospect" to "on" when creating a new third party from menu "New third party".

*THIRDPARTY_INCLUDE_PARENT_IN_LINKTO ► Search also for elements on parent third party when using the "link to" object feature.

*THIRDPARTY_INCLUDE_PROJECT_THIRDPARY_IN_LINKTO ► Search also for elements on third party that own the project of the current element when using the "link to" object feature (if project is owned by a different thirdparty than current one).

*THIRDPARTY_LOGO_ALLOW_EXTERNAL_DOWNLOAD ► When a logo is uploaded, a share key is automatically set so the file can be downloaded using the share key.

*THIRDPARTY_SUGGEST_ALSO_ADDRESS_CREATION ► Enabled contact creation on third-party create card
*THIRDPARTY_QUICKSEARCH_ON_FIELDS ► Personalized search criterias ► Example: $conf->global->THIRDPARTY_QUICKSEARCH_ON_FIELDS = 's.nom=ThirdPartyName;s.name_alias=AliasNameShort;s.code_client=CustomerCode'
*MEMBER_CAN_CONVERT_CUSTOMERS_TO_MEMBERS ► Enabled member creation on third-party create card
*SOCIETE_DISABLE_PARENTCOMPANY ► Disables attachment to a parent company.
*THIRDPARTY_CUSTOMERPROSPECT_BY_DEFAULT ► Set the third party to customer by default
*THIRDPARTY_SUPPLIER_BY_DEFAULT ► Set the third party to supplier by default
*THIRDPARTY_CUSTOMERTYPE_BY_DEFAULT ► Set the third party type by default (3 = customer & prospect / 2 = prospect / 1 = customer )
*CONTACT_DISABLE_PERSONALINFO ► Disable Personal data on contact page
*SOCIETE_DISABLE_WORKFORCE ► Disable work force selector on society page
*SOCIETE_SHOW_VAT_IN_LIST ► display VAT number in combo list of thirdparties (V15+)

[[#Top|(back to top)]]

=Ticket Module=

*TICKET_SHOW_MESSAGES_ON_CARD ►Display all ticket related messages on the main ticket card. ► (>= 10.0)
*TICKET_AUTO_ASSIGN_CONTRACT_CREATE ►Automatically create a contract linked to the ticket ► (>= 10.0)
*TICKET_AUTO_CREATE_FICHINTER_CREATE ►Automatically create an intervention linked to the ticket ► (>= 10.0)
*WORKFLOW_TICKET_CLOSE_INTERVENTION ►On ticlet close, automatically close an intervention linked to the ticket
*TICKET_CHECK_NOTIFY_THIRDPARTY_AT_CREATION ►Automatically check "notify thirdparty at creation" ( >=16)
*TICKETS_MESSAGE_FORCE_MAIL ► Precheck email sending on ticket message (>=15)

 

=VAT Report=

*MAIN_INCLUDE_ZERO_VAT_IN_REPORTS ► Include lines with VAT to 0% (for "auto-liquidation" in EEC) ► (v8.0.3+)

[[#Top|(back to top)]]

=Website Module=

*WEBSITE_USE_WEBSITE_ACCOUNTS ► Add a table and a tab to manage some accounts for websites to a third party
*
*
*WEBSITE_ADD_CSS_TO_BODY

[[#Top|(back to top)]]

 

=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 guaranteed with this. Also if the image is removed or renamed by the image hosting service, your proposal, order or invoice will be broken.

[[#Top|(back to top)]]

=STRIPE Module=

*STRIPE_FORCE_VERSION ► Force the STRIPE version. For Example: "2019-09-09" (v11+)

[[#Top|(back to top)]]

=ClickToDial Module=

*CLICKTODIAL_FORCENEWTARGET ► Open in new page.

[[#Top|(back to top)]]

 

=For SaaS / Cloud hosting integrators=

The following options are useless for a common usage of Dolibarr. But they are usefull if you plan to host / provide Dolibarr instances as Software As A Service (SAAS) to your customers.

*CRON_DISABLE_KEY_CHANGE ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].

*CRON_DISABLE_TUTORIAL_CRON ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)

*CRON_WARNING_DELAY_HOURS ► Set this value to the frequency set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)

*To avoid bad use of the emailing module, it is recommended to set the option MAILING_NO_USING_PHPMAIL to 1 (This option is described previously). Also you can complete the message visible by customers when they try to setup the SMTP credentials of their Dolibarr by using the constant MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS (This option is described previously). For example, you can point to a FAQ on your website.

*If you set a system limit on number of recipient, you can set some option to match the same values so users will be informed: MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL ► Restrict sending of 1 email message to <code>x</code> recipients for same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include 1000 recipients in 1 message. Note that MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL, MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL and MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL are also available.

*MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE ► If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock so the administration tools like install.php and repair.php can't be used on your customer instance (until the lock file is deleted).

*MAIN_HIDE_WARNING_TO_ENCOURAGE_SMTP_SETUP ► Set to 1 by default. You can set it to 0 to show a warning to encourage admin to set its own SMTP service.

*MAILING_LIMIT_WARNING_PHPMAIL ► Set this value to a translation key. Then add translation keys into the instance so user will see a message when into the email setup page. For example, you can set a message to say ''Warning: To avoid abuse, when using default setup, you are restricted to 500 emails per day for all your application (account may be suspended in case of violation of this rule. You can setup application to use your own SMTP server for sending email so you want have no restriction at all (see menu Home-Setup-Emails)''

*MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. So when your customer go into the setup area of email:
**If he chose mail method, a message will explain him how to setup its SPF record for its email domain (showing the list of IP). This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers.
**If he chose smtp method, a message will explain him the list of IP he can use if there is restriction on IP by the SMTP agent. If you also need to add a message to help SPF setup, see option MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD.

*MAIN_EXTERNAL_SMTP_SPF_STRING_TO_ADD ► Set here the string to add in the SPF record This string will be shown into a help message when the user in in the setup of email page and has choose a method using an external SMTP server.

*MAIN_FIRST_PING_OK_ID ► Set this value to "disabled" to remove completely any ping after a complete setup.

*MAIN_FILECHECK_LOCAL_SUFFIX and MAIN_FILECHECK_LOCAL_EXT ► If you offer a customized or patched version of Dolibarr, when the user will use the tool to check the integrity of files, the default xml file name used for signature checking will be the official file provided by the Dolibarr team, so it does not includes your own changes. To have the suggested signature file being your own file, you can set the constant MAIN_FILECHECK_LOCAL_SUFFIX to a suffix. For example, set this to "'''-mysaassolution'''". So, when the user will use the file integrity tool, the default file to check for signature will be "'''/install/filelist-10.0.2-mysaassolution.xml'''" instead of "'''/install/filelist-10.0.2.xml'''". All you have to do is generate the signature file '''mysaassolution''' using the tool '''build/generate_filelist_xml.php''' and put this file into the install directory of your customer instance. Doing this, your customer, and yourself, will be able to check if a file was modified without being disturbed by false alerts due to your customized files or patches (they will be included in the signature used for check). Also, if you want to zip the customized signature file into "'''/install/filelist-10.0.2-mysaassolution.xml.zip'''", you can set the constant MAIN_FILECHECK_LOCAL_EXT to '.zip'.

*MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING ► If set to N, the warning saying modules are not activated will be shown if number of activated module is < N (Having this variable not defined is same than having it set to 1). This may be usefull if you preinstall an application with some modules already loaded by default and you want to keep the warning to be sure the user will enable other modules he need, even if some modules are already enabed.

*SYSLOG_DISABLE_LOGHANDLER_SYSLOG ► Set this to 1 to disable usage of syslog (having all customer instances logging in the same system file is not a good idea).

*WEBSITE_REPLACE_INFO_ABOUT_USAGE_WITH_WEBSERVER ► Put here a text or a translation key of a text to show when the user will use the feature "Deploy" when he want to deploy a website done with Dolibarr CMS. So you can, for example, show him a message that this feature is not part of its subscription and putting a website online may need a complementary subscription.

[[#Top|(back to top)]]

Template:TemplateListOfTriggers

2021-10-04T08:51:52Z

Iouston: add PROPAL_MODIFY and ORDER_UNVALIDATE

{|class="wikitable sortable" align="left" width="100%" border="0" cellpadding="1" cellspacing="0" class="dolbox"
|style="background-color: #e9e9ef"| Trigger code ($action)
|style="background-color: #e9e9ef"| Type object ($object)
|-
|USER_CREATE
|user.class.php
|-
|<strike>USER_CREATE_FROM_CONTACT</strike> (Removed since 3.8)
|<strike>user.class.php</strike>
|-
|USER_MODIFY
|user.class.php
|-
|USER_DELETE
|user.class.php
|-
|USER_LOGIN
|user.class.php
|-
|USER_LOGIN_FAILED
|user.class.php
|-
|USER_LOGOUT
|user.class.php
|-
|<strike>USER_UPDATE_SESSION</strike> (Removed since 3.7.1)
|<strike>user.class.php</strike>
|-
|USER_ENABLEDISABLE
|user.class.php
|-
|USER_NEW_PASSWORD
|user.class.php
|-
|USER_SETINGROUP
|user.class.php
|-
|USER_REMOVEFROMGROUP
|user.class.php
|-
|USERGROUP_CREATE ''(>= 12.0.0)
|usergroup.class.php
|-
|USERGROUP_MODIFY''(>= 12.0.0)
|usergroup.class.php
|-
|USERGROUP_DELETE''(>= 12.0.0)
|usergroup.class.php
|-
|GROUP_CREATE
|usergroup.class.php
|-
|GROUP_MODIFY
|usergroup.class.php
|-
|GROUP_DELETE ''(>= 3.3.0)''
|usergroup.class.php
|-
|COMPANY_CREATE
|societe.class.php
|-
|COMPANY_MODIFY
|societe.class.php
|-
|COMPANY_DELETE
|societe.class.php
|-
|COMPANY_SENTBYMAIL ''(>= 3.5.0)''
|societe.class.php
|-
|CONTACT_CREATE
|contact.class.php
|-
|CONTACT_MODIFY
|contact.class.php
|-
|CONTACT_DELETE
|contact.class.php
|-
|CONTACT_ENABLEDISABLE ''(>= 3.5.0)''
|contact.class.php
|-
|PRODUCT_CREATE
|product.class.php
|-
|PRODUCT_MODIFY
|product.class.php
|-
|PRODUCT_PRICE_MODIFY
|product.class.php
|-
|PRODUCT_DELETE
|product.class.php
|-
|SUPPLIER_PRODUCT_BUYPRICE_UPDATE
|fournisseur.product.class.php
|-
|SUPPLIER_PRODUCT_BUYPRICE_CREATE
|fournisseur.product.class.php
|-
|ORDER_CREATE
|commande.class.php
|-
|ORDER_VALIDATE
|commande.class.php
|-
|ORDER_SENTBYMAIL
|commande.class.php
|-
|ORDER_DELETE
|commande.class.php
|-
|ORDER_CLASSIFY_BILLED
|commande.class.php
|-
|ORDER_CLONE
|commande.class.php
|-
|ORDER_CLOSE
|commande.class.php
|-
|ORDER_CANCEL
|commande.class.php
|-
|ORDER_REOPEN ''(>= 3.3.0)''
|commande.class.php
|-
|ORDER_UNVALIDATE
|commande.class.php
|-
|COMMANDE_ADD_CONTACT
|commande.class.php
|-
|COMMANDE_DELETE_CONTACT
|commande.class.php
|-
|COMMANDE_DELETE_RESOURCE ''(>= 3.6.0)''
|commande.class.php
|-
|LINEORDER_INSERT
|commande.class.php
|-
|LINEORDER_UPDATE
|commande.class.php
|-
|LINEORDER_DELETE
|commande.class.php
|-
|LINEORDER_DISPATCH ''(>= 3.4.0)''
|commande.class.php
|-
|ORDER_SUPPLIER_CREATE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_CLONE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_VALIDATE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_SENTBYMAIL
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_APPROVE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_REFUSE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_CANCEL
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_DELETE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_DISPATCH ''(>= 3.4.0)''
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_ADD_CONTACT
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_DELETE_CONTACT
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_DELETE_RESOURCE ''(>= 3.6.0)''
|fournisseur.commande.class.php
|-
|LINEORDER_SUPPLIER_CREATE
|fournisseur.commande.class.php
|-
|LINEORDER_SUPPLIER_UPDATE
|fournisseur.commande.class.php
|-
|LINEORDER_SUPPLIER_DELETE ''(>= 3.6.0)''
|fournisseur.commande.class.php
|-
|PROPAL_CREATE
|propal.class.php
|-
|PROPAL_DELETE
|propal.class.php
|-
|PROPAL_CLONE
|propal.class.php
|-
|PROPAL_REOPEN ''(>= 3.5.0)''
|propal.class.php
|-
|PROPAL_VALIDATE
|propal.class.php
|-
|PROPAL_CLOSE_SIGNED
|propal.class.php
|-
|PROPAL_CLOSE_REFUSED
|propal.class.php
|-
|PROPAL_SENTBYMAIL
|propal.class.php
|-
|PROPAL_MODIFY
|propal.class.php
|-
|PROPAL_ADD_CONTACT
|propal.class.php
|-
|PROPAL_DELETE_CONTACT
|propal.class.php
|-
|PROPAL_DELETE_RESOURCE ''(>= 3.6.0)''
|propal.class.php
|-
|LINEPROPAL_INSERT
|propal.class.php
|-
|LINEPROPAL_UPDATE
|propal.class.php
|-
|LINEPROPAL_DELETE
|propal.class.php
|-
|CONTRACT_CREATE
|contrat.class.php
|-
|CONTRACT_VALIDATE
|contrat.class.php
|-
|CONTRACT_SERVICE_ACTIVATE
|contrat.class.php
|-
|CONTRACT_SERVICE_CLOSE
|contrat.class.php
|-
|CONTRACT_DELETE
|contrat.class.php
|-
|CONTRAT_ADD_CONTACT
|contrat.class.php
|-
|CONTRAT_DELETE_CONTACT
|contrat.class.php
|-
|CONTRAT_DELETE_RESOURCE ''(>= 3.6.0)''
|contrat.class.php
|-
|LINECONTRACT_INSERT ''(>= 3.9.0) (LINECONTRACT_CREATE >= 3.7.0)''
|contrat.class.php
|-
|LINECONTRACT_UPDATE ''(CONTRACT_LINE_MODIFY < 3.5.0) (CONTRACT_LINE_MODIFY > 3.3.0)''
|contrat.class.php
|-
|LINECONTRACT_DELETE ''(CONTRACT_LINE_DELETE < 3.5.0) (CONTRACTLINE_DELETE < 3.3.0)''
|contrat.class.php
|-
|BILL_CREATE
|facture.class.php
|-
|BILL_MODIFY
|facture.class.php
|-
|BILL_CLONE
|facture.class.php
|-
|BILL_VALIDATE
|facture.class.php
|-
|BILL_UNVALIDATE ''(>= 3.4.0)''
|facture.class.php
|-
|BILL_PAYED
|facture.class.php
|-
|BILL_UNPAYED
|facture.class.php
|-
|BILL_CANCEL
|facture.class.php
|-
|BILL_DELETE
|facture.class.php
|-
|BILL_SENTBYMAIL
|facture.class.php
|-
|FACTURE_ADD_CONTACT
|facture.class.php
|-
|FACTURE_DELETE_CONTACT
|facture.class.php
|-
|FACTURE_DELETE_RESOURCE ''(>= 3.6.0)''
|facture.class.php
|-
|LINEBILL_INSERT
|facture.class.php
|-
|LINEBILL_UPDATE
|facture.class.php
|-
|LINEBILL_DELETE
|facture.class.php
|-
|BILL_SUPPLIER_CREATE
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_MODIFY
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_DELETE ''(INVOICE_SUPPLIER_DELETE < 3.3.0)''
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_VALIDATE
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_PAYED
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_UNPAYED
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_SENTBYMAIL
|fournisseur.facture.class.php
|-
|INVOICE_SUPPLIER_ADD_CONTACT
|fournisseur.facture.class.php
|-
|INVOICE_SUPPLIER_DELETE_CONTACT
|fournisseur.facture.class.php
|-
|INVOICE_SUPPLIER_DELETE_RESOURCE ''(>= 3.6.0)''
|fournisseur.facture.class.php
|-
|LINEBILL_SUPPLIER_CREATE
|fournisseur.facture.class.php
|-
|LINEBILL_SUPPLIER_UPDATE
|fournisseur.facture.class.php
|-
|LINEBILL_SUPPLIER_DELETE ''(>= 3.4.0)''
|fournisseur.facture.class.php
|-
|PAYMENT_CUSTOMER_CREATE
|paiement.class.php
|-
|PAYMENT_DELETE (<= 3.8)
|paiement.class.php
|-
|PAYMENT_CUSTOMER_DELETE (>= 3.9)
|paiement.class.php
|-
|PAYMENT_ADD_TO_BANK
|paiement.class.php
|-
|PAYMENT_SUPPLIER_CREATE
|paiementfourn.class.php
|-
|PAYMENT_SUPPLIER_DELETE (>= 3.9)
|paiement.class.php
|-
|PAYMENT_SALARY_CREATE ''(>= 3.6.0)''
|paymentsalary.class.php
|-
|PAYMENT_SALARY_MODIFY ''(>= 3.6.0)''
|paymentsalary.class.php
|-
|PAYMENT_SALARY_DELETE ''(>= 3.6.0)''
|paymentsalary.class.php
|-
|FICHINTER_CREATE ''(FICHEINTER_CREATE < 3.3.0)''
|fichinter.class.php
|-
|FICHINTER_MODIFY ''(FICHEINTER_MODIFY < 3.3.0)''
|fichinter.class.php
|-
|FICHINTER_DELETE ''(FICHEINTER_DELETE < 3.3.0)''
|fichinter.class.php
|-
|FICHINTER_VALIDATE ''(FICHEINTER_VALIDATE < 3.3.0)''
|fichinter.class.php
|-
|FICHINTER_SENTBYMAIL ''(FICHEINTER_SENTBYMAIL < 3.3.0)''
|fichinter.class.php
|-
|FICHINTER_ADD_CONTACT
|fichinter.class.php
|-
|FICHINTER_DELETE_CONTACT
|fichinter.class.php
|-
|FICHINTER_DELETE_RESOURCE ''(>= 3.6.0)''
|fichinter.class.php
|-
|LINEFICHINTER_CREATE ''(>= 3.5.0)''
|fichinter.class.php
|-
|LINEFICHINTER_UPDATE ''(>= 3.5.0)''
|fichinter.class.php
|-
|LINEFICHINTER_DELETE ''(>= 3.5.0)''
|fichinter.class.php
|-
|MEMBER_CREATE
|adherent.class.php
|-
|MEMBER_VALIDATE
|adherent.class.php
|-
|MEMBER_SUBSCRIPTION
|adherent.class.php
|-
|MEMBER_MODIFY
|adherent.class.php
|-
|MEMBER_RESILIATE
|adherent.class.php
|-
|MEMBER_NEW_PASSWORD
|adherent.class.php
|-
|MEMBER_DELETE
|adherent.class.php
|-
|CATEGORY_CREATE
|category.class.php
|-
|CATEGORY_MODIFY
|category.class.php
|-
|CATEGORY_DELETE
|category.class.php
|-
|CATEGORY_LINK ''(>= 3.5.0)''
|category.class.php
|-
|CATEGORY_UNLINK ''(>= 3.5.0)''
|category.class.php
|-
|SHIPPING_CREATE
|expedition.class.php
|-
|SHIPPING_VALIDATE
|expedition.class.php
|-
|SHIPPING_MODIFY
|expedition.class.php
|-
|SHIPPING_DELETE
|expedition.class.php
|-
|SHIPPING_SENTBYMAIL
|expedition.class.php
|-
|DELIVERY_VALIDATE
|livraison.class.php
|-
|DELIVERY_DELETE
|livraison.class.php
|-
|ACTION_CREATE
|actioncomm.class.php
|-
|ACTION_MODIFY
|actioncomm.class.php
|-
|ACTION_DELETE
|actioncomm.class.php
|-
|ACTION_ADD_CONTACT
|actioncomm.class.php
|-
|ACTION_DELETE_CONTACT
|actioncomm.class.php
|-
|ACTION_DELETE_RESOURCE ''(>= 3.6.0)''
|actioncomm.class.php
|-
|DEPLACEMENT_CREATE
|deplacement.class.php
|-
|DON_CREATE
|don.class.php
|-
|DON_MODIFY ''(>= 3.7.0)''
|don.class.php
|-
|DON_DELETE ''(>= 3.7.0)''
|don.class.php
|-
|LOCALTAX_CREATE
|localtax.class.php
|-
|LOCALTAX_MODIFY
|localtax.class.php
|-
|LOCALTAX_DELETE
|localtax.class.php
|-
|TVA_CREATE
|tva.class.php
|-
|TVA_MODIFY
|tva.class.php
|-
|TVA_DELETE
|tva.class.php
|-
|TVA_ADDPAYMENT
|tva.class.php
|-
|PROJECT_CREATE
|project.class.php
|-
|PROJECT_MODIFY
|project.class.php
|-
|PROJECT_DELETE
|project.class.php
|-
|PROJECT_VALIDATE
|project.class.php
|-
|PROJECT_CLOSE
|project.class.php
|-
|PROJECT_ADD_CONTACT
|project.class.php
|-
|PROJECT_DELETE_CONTACT
|project.class.php
|-
|PROJECT_DELETE_RESOURCE ''(>= 3.6.0)''
|project.class.php
|-
|TASK_CREATE
|task.class.php
|-
|TASK_MODIFY
|task.class.php
|-
|TASK_DELETE
|task.class.php
|-
|TASK_TIMESPENT_CREATE
|task.class.php
|-
|TASK_TIMESPENT_MODIFY
|task.class.php
|-
|TASK_TIMESPENT_DELETE
|task.class.php
|-
|PROJECT_TASK_ADD_CONTACT
|task.class.php
|-
|PROJECT_TASK_DELETE_CONTACT
|task.class.php
|-
|PROJECT_TASK_DELETE_RESOURCE ''(>= 3.6.0)''
|task.class.php
|-
|MYECMDIR_CREATE
|ecmdirectory.class.php
|-
|MYECMDIR_MODIFY
|ecmdirectory.class.php
|-
|MYECMDIR_DELETE
|ecmdirectory.class.php
|-
|<strike>IMPORT_DELETE</strike> (Removed since 3.7.0)
|<strike>import.class.php</strike>
|-
|STOCK_MOVEMENT
|mouvementstock.class.php
|-
|PAYBOX_PAYMENT_OK
|
|-
|PAYPAL_PAYMENT_OK
|
|-
|LINK_CREATE ''(>= 3.5.0)''
|link.class.php
|-
|LINK_MODIFY ''(>= 3.5.0)''
|link.class.php
|-
|LINK_DELETE ''(>= 3.5.0)''
|link.class.php
|-
|OPENSURVEY_CREATE ''(>= 3.6.0)''
|opensurveysondage.class.php
|-
|OPENSURVEY_DELETE ''(>= 3.6.0)''
|opensurveysondage.class.php
|-
|}

Setup Other

2021-08-04T08:14:22Z

Iouston: Add Donation Module chapter with a first option (i saw this option in a V13)

Loi finances sur les logiciels de caisse et Certification NF525 ou LNE

2021-02-25T20:57:20Z

Iouston: Ajout d'un lien vers le Bofip pour obtenir un modèle d'attestation

<seo metak="loi finance 2016, loi finance 2018, loi finance 2019, NF525, logs inaltérables, logiciels de caisse, logiciels comptabilité, TPE" />
Ceci est une page d'explication de l'Article 88 de la Loi finance 2016 (n° 2015-1785 du 29 décembre 2015), communément appelée Loi anti-fraude à la TVA, applicable au 1er janvier 2018 en France (cette loi ayant donné lieu à la certification NF525 ou encore au principe d'attestation de conformité).

=Résumé=

La '''loi finances 2016, article 88 modifiant le 286 du CGI''', impose à tous les commerçants, '''assujettis à la TVA hors franchise en base de TVA''' (et seulement ces derniers) ET qui sont équipés d'un "logiciel ou système de caisse" (comprendre logiciel d'encaissement d'argent, cela inclut les logiciels de gestion) ET qui réalisent de l'encaissement de particuliers, d'utiliser un logiciel dans un cadre "conforme" à la loi finance 2016, et ce dès le 1er janvier 2018 (avec tolérance sur 2018 si l'utilisateur peut montrer qu'il a entamé une trajectoire dans le but de mise en conformité, mais n'a pas encore pu finaliser sa démarche par exemple pour cause d'attente de publication d'une version conforme, ou de délai nécessaire pour la migration technique).

La "conformité Loi Finance" dite aussi "Anti Fraude TVA" est absolument sans aucun rapport avec la notion de "Compatible avec les normes de logiciels comptables", normes requises pour établir les documents fiscaux officiels et les télétransmettre à l'administration. Ces normes (par exemple "la compatibilité avec le format FEC" obligatoire depuis le 1er janvier 2014 [https://www.legifrance.gouv.fr/affichCodeArticle.do?cidTexte=LEGITEXT000006069583&idArticle=LEGIARTI000027804775 défini ici], ou encore "la compatibilité pour télétransmission EDI") existent d'ailleurs depuis plusieurs années bien avant la loi finance 2016 et concernent uniquement le "logiciel de comptabilité" de l'expert comptable qui approuve les comptes, logiciel utilisé en fin de chaîne pour produire la liasse fiscale, et, seul ce dernier logiciel a cette contrainte de "compatibilité logiciel comptable" : le logiciel de gestion ou de suivi de l'entreprise (comme par exemple Dolibarr), même si il est utilisé pour réaliser une comptabilité interne de l'entreprise (par exemple en préparation d'export vers le logiciel de l'expert-comptable, ou utilisé pour offrir un suivi ou mâcher le travail du comptable pour réduire son coût), n'a '''aucune obligation sur le point de logiciel comptable''' si c'est un autre qui sert pour établir les documents légaux.

Par contre, le logiciel de l'entreprise peut avoir l'obligation d'être '''conforme Loi finance 2016 - Anti Fraude TVA'''. Ce qui est tout autre chose. Cette conformité s'applique à tout "logiciel d'encaissements", ce qui est différent de "logiciel comptable" (et donc s'applique aux logiciels de facturation ou de gestion avec saisie d'encaissements, aux logiciels de caisse enregistreuse (Point de Vente) et, éventuellement, aux logiciels de comptabilité si c'est lui qui est utilisé pour saisir et suivre les encaissements clients, ce qui est rarissime car cela sous-entend que la gestion de l'entreprise est faite directement dans le logiciel du comptable qui certifie les comptes).

Cette conformité "Loi Finance" pour son logiciel d'encaissement, peut s'obtenir de 3 manières différentes (une seule des 3 solutions suffit):

*Par l'utilisation d'une version '''certifiée Loi Finance''' du logiciel (Exemple via l'obtention de la certification LNE ou l'obtention de la norme NF525 de l'AFNOR). Une version certifiée l'est pour tout le monde mais, pour évoluer, il faut attendre la prochaine version certifiée, et le processus de certification est long et coûteux pour l'éditeur. Le principe de certification n'est donc plus adapté aux logiciels modernes ni aux logiciels en Cloud/SaaS qui évoluent rapidement). Le choix de conformité du logiciel par obtention d'une certification LNE ou NF525 n'est donc pas celui fait majoritairement par les éditeurs. La certification LNE ou NF525 n'est donc absolument pas obligatoire (même si les éditeurs qui ont fait ce choix essaie de sous-entendre le contraire), à condition qu'une des autres solutions pour être conforme soit mis en oeuvre (voir point suivants).

ou bien

*Par obtention d'une '''attestation individuelle de conformité Loi Finance''' décernée par une société Tiers, comme un éditeur ou intégrateur informatique (Exemple d'attestation vierge proposé par le gouvernement: http://bofip.impots.gouv.fr/bofip/10692-PGP.html). Une attestation est individuelle, chaque société utilisatrice doit en obtenir une, auprès d'un Tiers, pour elle même.

ou bien

*En '''se délivrant à soi-même cette attestation''' (sans la demander à un tiers donc), on parle d'auto-attestation, mais ce cas est limité aux sociétés qui ont, entre autre, une activité '''avérée''' d'édition de logiciel de caisse (le code Nace n'ayant qu'une valeur indicative statistique, c'est votre activité réelle, dont il vous revient d'en démontrer le côté avéré qui sera pris en compte, et non un code Nace spécifique comme cela avait été cité dans des versions intermédiaires de textes sur le travail de la loi)

Le chapitre "Historique" vous permet de voir les rebondissements et changements de direction de la loi. Connaitre ces rebondissements aide à comprendre pourquoi de nombreux acteurs se sont trompés ou continuent de se tromper sur cette loi. Le chapitre d'après "Questions / Réponses" vous offre une vue rapide de la loi '''définitive''' par une approche de questions/réponses.

==Historique de la définition de la loi et rebondissements==

Pour ceux qui ont le temps de lire, voici un flux qui décrit les documents originaux qui ont été communiqués par le gouvernement et les mises à jours qui ont suivi pour définir le périmètre et la conclusion de la loi, avec les rebondissements (pour ceux qui n'ont pas le temps, aller directement au chapitre Conclusion ou aux FAQ):

*Voici l'article '''initial''' de la loi finance, datant du 29/12/2015: [https://www.legifrance.gouv.fr/affichTexteArticle.do?cidTexte=JORFTEXT000031732865&idArticle=LEGIARTI000031734740&dateTexte=20151230 Article sur LegiFrance]
*Voici l'article, '''pour sa publication au BOFIP''', du 03/08/2016: https://bofip.impots.gouv.fr/bofip/10691-PGP.html?identifiant=BOI-TVA-DECLA-30-10-30-20160803
*Voici l'article, '''pour sa publication au BOFIP''', de la version définitive du 04/07/2018: https://bofip.impots.gouv.fr/bofip/10691-PGP.html?identifiant=BOI-TVA-DECLA-30-10-30-20180704

Pour résumer, ces 2 publications indiquent qu'il faudra, pour toute société/organisme qui ''enregistre les règlements de ses clients au moyen d'un logiciel de comptabilité ou de gestion ou d'un système de caisse, utiliser un logiciel ou un système satisfaisant à des conditions d'inaltérabilité, de sécurisation, de conservation et d'archivage des données en vue du contrôle de l'administration fiscale, attestées par un certificat délivré par un organisme accrédité dans les conditions prévues à l'article L. 115-28 du code de la consommation '''OU''' par une attestation individuelle de l'éditeur, conforme à un modèle fixé par l'administration''

[[File:Warning.png]] 15 juin 2017: Communiqué de presse du cabinet du ministère: http://proxy-pubminefi.diffusion.finances.gouv.fr/pub/document/18/22503.pdf ->
Seules les "logiciels de caisse" seraient concernés (la définition de logiciel de caisse n'est toutefois pas encore apportée, elle le sera le 15 juillet 2018, voir la suite).
Dès logiciels ERP (comme Dolibarr), ainsi que les logiciels de site ecommerce (comme Prestashop, Magento, ...) n'étant dans pas la catégorie logiciels de caisse (Les ERP sont dans la catégorie logiciels de gestion), on aurait cru que l'obligation de mise en conformité, et tout ce qui suit, semblait ne plus être avéré pour eux, mais la suite des événements (voir la suite) indiquera le contraire si vous enregistrez dans le logiciel des paiements de particuliers, quelquesoit la catégorie du logiciel (seules les sociétés encaissant exclusivement d'autres sociétés, ou ceux en tva en franchise, seront finalement exemptées)...

[[File:Warning.png]] 27 septembre 2017: Voici l'avenant publié le 27 septembre 2017 qui réduit la portée/périmètre de la loi aux seuls "logiciels de caisse": http://www.assemblee-nationale.fr/15/projets/pl0235.asp (Article 46). En d'autres terme, les applications ERP (Comme Dolibarr) semblent la encore ne plus être concernées, mais la suite des événements (voir la suite) indiquera le contraire si vous encaissez des particuliers (seules les sociétés encaissant exclusivement d'autres sociétés, ou ceux en franchises seront finalement exemptées)...

Suite aux questions, une FAQ, issue du ministère des finances, est alors parue pour tenter de clarifier le périmètre. Elle indique que tous les assujetis à TVA qui vendent à un non assujetti (particuliers) sont concernés. Si on lit tel quel cette FAQ, alors le périmètre est non seulement pas réduit, comme communiqué par le ministère dans son courrier du 15 juin, mais élargit, y compris aux sites e-commerce. Cette FAQ est le premier élément qui apporte donc une définition au terme "système de caisse" en considérant tout logiciel traçant des encaissements, comme "systeme de caisse".
Des amendements ont été rédigés pour tenter de clarifier ou restreindre cette définition, voir la suite...

[[File:Warning.png]] 14 octobre 2017: Une reformulation du texte, plus complète que la FAQ, est donnée stipulant qu'une entité est concernée... "''Si elle effectue des livraisons de biens et des prestations de services ne donnant pas lieu à facturation conformément à l’article 289 et enregistre ces opérations au moyen d’un logiciel ou d'un système de caisse'' ... ". Dans ce cas, il faut "''... utiliser un logiciel ou un système satisfaisant à des conditions d'inaltérabilité, de sécurisation, de conservation et d'archivage des données en vue du contrôle de l'administration fiscale, attestées par un certificat délivré par un organisme accrédité dans les conditions prévues à l'article L. 433-4 du code de la consommation OU par une attestation individuelle de l'éditeur, conforme à un modèle fixé par l'administration ;''"

Il est aussi précisé: ''« 2. Les assujettis bénéficiant d'une franchise de taxe mentionnée à l'article 293 B, ceux placés sous le régime du remboursement forfaitaire prévu aux articles 298 quater et 298 quinquies et ceux effectuant exclusivement des opérations ou des prestations exonérées de taxe sur la valeur ajoutée sont dispensés de l'obligation mentionnée au 3° bis du I. » ; ''

Voir: [https://www.legifrance.gouv.fr/eli/loi/2017/12/30/CPAX1723900L/jo/texte/fr#JORFARTI000036339313 Article sur LegiFrance] pour le texte complet mentionnant ces 2 points.

[[File:Warning.png]] 20 novembre 2017: Nouveaux éléments permettant de mieux cibler le périmètre. En effet, l'amendement II-CF15 = II-1649 de la loi Finance 2018 sur l'article 46 pour exclure les encaissements de particuliers qui font l'objet de fabrication d'une facture en bon et du forme (afin d'exclure les ERP et plateforme ecommerce) a été rejeté en séance à l'assemblée: Seule l'encaissement de sociétés est bien hors périmètre. En effet, considérant que l'administration a le droit de vérification chez les clients de type société, les traces fournies par les factures suffisent pour assurer un contrôle satisfaisant, mais ce droit n'existe pas en ce qui concerne la facturation des particuliers. Dans ce cas la, même la facture est peu utile à l'administration et par conséquent les contraintes d'inaltérabilité deviennent requises, même si on émet une facture en bon et du forme. Cette conclusion fait suite aux échanges suites à l'amendement II-CF15 = II-1649 de la loi Finance 2018 sur l'article 46.

Pour info, texte complet de la tentative d'amendement: http://www.assemblee-nationale.fr/15/amendements/0235C/AN/1649.asp ou en PDF http://www.assemblee-nationale.fr/15/amendements/0235C/CION_TOUTE/CF15.pdf

Et voici les extraits importants de la discussion:

D'abord, la tentative de M. Bruno Millienne pour tenter d'exclure les logiciels émettant des factures en bon et du forme:

''M. Bruno Millienne. "[...]le renvoi à l’article 289 du code général des impôts – CGI – ne vise que les cas d’émission de factures obligatoires au sens fiscal pour les opérations entre assujettis ou personnes morales. En l’état, le texte conduirait à appliquer le dispositif de certification ou d’attestation à toutes les opérations réalisées avec les particuliers, même lorsqu’elles donnent lieu à l’émission de factures conformes au CGI, par exemple dans le cadre du commerce électronique. [...] La rédaction actuelle de l’article peut conduire à requalifier en logiciel de caisse un logiciel de facturation, si des factures sont émises à l’attention d’un particulier ou d’une administration, ou un logiciel de comptabilité, si des règlements sont comptabilisés directement par l’utilisateur. L’éditeur deviendrait ainsi responsable du mode d’utilisation de son logiciel par l’assujetti. Il est impossible de transposer les exigences d’un logiciel de caisse à un logiciel de facturation : leurs fonctionnalités respectives sont totalement différentes. Actuellement, il existe des dispositifs de certification en matière de caisse, mais pas en matière de facturation."''

''...''

Réponse de ''M. Joël Giraud, rapporteur général de la commission des finances, de l’économie générale et du contrôle budgétaire: Avis défavorable. L’article 46 précise que l’obligation de certification ne vaut que pour les logiciels ou systèmes de caisse. L’obligation ne concernera plus les progiciels de gestion intégrée ou de comptabilité : pour ces logiciels multifonctions qui traitent à la fois la comptabilité, la gestion et la caisse, seuls les modules caisse enregistreuse et encaissement devront être certifiés, non l’ensemble du logiciel.''

''...''

Et enfin le complément de ''M. Benjamin Griveaux, secrétaire d’État auprès du ministre de l’économie et des finances: Avis défavorable. Une facture n’est obligatoire, au sens fiscal, que dans le cadre d’une relation B to B – business to business, c’est-à-dire d’entreprise à entreprise. L’administration fiscale peut la contrôler car elle dispose d’un droit de communication envers l’entreprise cliente. A contrario, elle ne peut exercer de droit de communication auprès des particuliers. Cet amendement conduirait donc à exclure du dispositif de sécurisation les entreprises qui émettent des factures contenant les mentions légales, qu’elles soient adressées à des entreprises ou à des particuliers. Je suis donc l’avis du rapporteur général quant au risque de fraude accrue que cet amendement ferait courir.''

La discussion complète de la séance ayant rejeté l'amendement est disponible ici: http://www.assemblee-nationale.fr/15/cri/2017-2018/20180063.asp#P1103690

'''En conclusion, l'amendement ayant été rejeté, il faut en déduire que la volonté est bien d'intégrer, dans le périmètre, toutes les parties/modules de logiciels, utilisés comme caisse enregistreuse OU pour enregistrer des paiements de particuliers (logiciel ecommerce, de caisse, de gestion,...)''' et que l'émission de facture en bon et du forme à des particuliers ne permet pas de sortir du périmètre...

[[File:Warning.png]] 30 décembre 2017:

L'article 88 qui disaient ''..toute personne assujettie à la taxe sur la valeur ajoutée (TVA) qui enregistre les règlements de ses clients au moyen d'un logiciel de comptabilité ou de gestion ou d'un système de caisse, doit utiliser un logiciel ou un système satisfaisant à des conditions d'inaltérabilité, de sécurisation, de conservation et d'archivage des données en vue du contrôle de l'administration fiscale''
est complété par l'article 105 qui remplace "''logiciel de comptabilité ou de gestion ou d'un système de caisse''" par "''logiciel ou d'un système de caisse''"

[[File:Warning.png]] 23 janvier 2018: Un représentant du projet Dolibarr, avec des représentants de l'APRIL et du logiciel libre de caisse Pasteque, ont été reçus au ministère des finances afin d'échanger sur l'interprétation du texte. Les interprétations faites sur cette page (ainsi que les réponses faites aux FAQ qui suivent) ont pu être confirmées.
Toutefois, il y a intention de réduire le périmètre aux seuls logiciels de caisse. A suivre donc. Une version de travail revue, du Bofip doit être publiée à un comité restreint d'acteurs, dont l'April, fin janvier, afin de faciliter le travail d'interprétations, pour une publication officielle au printemps. En attendant, on ne peut qu'attendre (Cette publication aura lieu finallement le 4 juillet 2018 et une grande partie de nos retours s'avèrera prise en compte).

[[File:Warning.png]] 18 mai 2018: Réponse du gouvernement à quelques questions sur le sujet: https://www.nosdeputes.fr/15/question/QE/3257 . La réponse évoque l'année de tolérance en précisant que l'utilisateur devra montrer sa diligence en cas de contrôle (Soin appliqué à la mise en oeuvre de l'obtention de l'attestation individuelle)

[[File:Warning.png]] 5 juin 2018: Réponse du gouvernement à quelques questions sur le sujet: https://www.nosdeputes.fr/15/question/QE/2736 . La réponse évoque l'année de tolérance en précisant que l'utilisateur devra montrer sa diligence en cas de contrôle (Soin appliqué à la mise en oeuvre de l'obtention de l'attestation individuelle)

[[File:Warning.png]] 4 juillet 2018: Publication de la version corrigée du texte de loi au BOFIP: https://bofip.impots.gouv.fr/bofip/10691-PGP.html?identifiant=BOI-TVA-DECLA-30-10-30-20180704. Cette version conforte tous les points évoqués (le texte clarifie la loi et confirme que les interprétations vu ci-dessus s'avéraient justes), avec toutefois 2 ajouts majeures:

*La définition de logiciel de caisse a été donnée:

''Un logiciel ou système de caisse est un système informatique doté d'une fonctionnalité de caisse, laquelle consiste à mémoriser et à enregistrer extra-comptablement des paiements reçus en contrepartie d'une vente de marchandises ou de prestations de services c'est-à-dire que le paiement enregistré ne génère pas concomitamment, automatiquement et obligatoirement la passation d'une écriture comptable.''

''Ne sont pas considérés comme enregistrés extra-comptablement, quel que soit le mode de paiement, les paiements pour lesquels le logiciel ou système déclenche obligatoirement, instantanément et automatiquement, sans intervention humaine, une écriture dans le système d’information comptable.''

''Sont visés tous les logiciels ou systèmes de caisse permettant l'enregistrement des règlements de leurs clients quel que soit le mode de règlement (espèces, chèques, CB, virements, prélèvements...).''
Cette obligation s'applique y compris en cas d'enregistrement sur un logiciel ou système accessible en ligne.

''Sans que cette liste ne soit limitative, sont concernés par l'obligation les instruments de mesures réglementés, comme les balances, mais également les rampes de boissons automatisées, les automates de paiement ou encore les distributeurs automatiques de marchandises (boissons, gâteaux…) qui disposent d'une fonctionnalité de caisse.''

''Seule cette fonctionnalité de caisse, et non les autres fonctions telles que celles relatives à la pesée, doivent être certifiées.''"

*L'article 35 qui est un allègement du périmètre: Les professionnels réalisant leur paiement avec l'intermédiation d'un établissement de crédit européen ne sont plus soumis à l'obligation de certification ou attestation. Mais attention, on parle bien de paiements "directs" (donc Virement ou Carte de Débit ou de Crédit mais pas chèques qui n'est pas "direct") et surtout via un système de paiement géré par un organisme bancaire européen. En d'autres terme, si on ne fait que du paiement CB avec un module de VAD d'une banque, on est NON soumis à la certification/attestation mais si le paiement CB (carte de crédit ou débit) se fait par un service comme Stripe ou Paypal, sauf à être exempté pour un autre motif, on l'est toujours (car l'état français n'a pas de moyen d'obtenir le listing des transactions via ces solutions, bien que le paiement soit par carte bancaire).

==Conclusion pour le logiciel Open Source Dolibarr ERP CRM==

Dolibarr ERP CRM est une application de gestion qui enregistre des factures (factures acomptes, avoirs ou standards). L'application permet aussi d'enregistrer des paiements. Le module POS (celui fourni par défaut), fonctionne aussi sur le principe de génération systématique de facture et d'enregistrement du paiement en temps réel. L'application est donc bien dans le périmètre (comme n'importe quel autre ERP, logiciel de caisse ou de Ecommerce). Mais en tant qu'utilisateur, vous n'êtes concerné que si vous n'etes pas en franchise de base ET si vous l'utilisez pour saisir des '''encaissements''' de particuliers (B2C=Business To Consumer) ou en mode mixte, à savoir encaissement aussi bien de particuliers (B2C) et d'entreprises (B2B), quelquesoit le ratio entre les 2. Si vous ne facturez QUE des professionnels, dans ce cas, vous n'êtes pas concerné par la LF2018 (Loi finance 2018).

Dans le cas où vous utilisez le module Facture, ou le module POS, pour encaisser des particuliers, et êtes assujettis à la TVA mais pas en franchise, vous êtes concerné. Il vous faut alors vous assurer que le module "Log inaltérable" ("BlockedLog") fourni avec la v10 est bien activé. Sa désactivation, une fois les premières saisies faites ne sera ensuite plus envisageable. Avec la migration en v10 et l'activation de ce module vous aurez alors une version conforme sur le plan technique et fonctionnel. Il vous faudra ensuite, obtenir une attestation de conformité auprès d'un tiers qui confirme cette conformité technique/fonctionnelle pour être conforme d'un point de vue juridique. Si vous utilisez une version en ligne Saas/Cloud fournie par un tiers, ce dernier vous la fournira surement (voir exemples sur https://saas.dolibarr.org). Dans le cas contraire, il vous faut contactez votre intégrateur informatique ou un prestataire pouvant fournir cette d'attestation.

Remarque: cette contrainte sera identique quelque soit l'ERP choisi. L'utilisation d'outils non spécialisés comme un tableur Excel ou autre, DANS LE BUT D'AVOIR UNE CONSERVATION DE TRACES DES PAIEMENTS, ne devient plus permis car le logiciel n'étant pas conforme, vous ne réussirez pas à trouver un prestataire pour fournir l'attestation de conformité. Par contre, si l'utilisation que vous faites d'Excel ou autre tableur est à des fins juste de "génération du PDF de la facture" sans ''conservation des données'' (Le texte de loi parle alors de logiciel "facturier"), vous pouvez continuer à l'utiliser ainsi. Dans le cas où l'utilisation est faite pour conserver trace de vos paiements, et si vous êtes dans le périmètre de la loi, un logiciel '''certifié OU attestable''' sur la partie encaissement (comme l'est Dolibarr) devient obligatoire.

Voyons aussi, par une autre approche, à savoir un système de question-réponse, comment synthétiser autrement tout cela:

=Questions / Réponses (FAQ)=

==J'utilise Dolibarr ou autre logiciel ERP, suis-je concerné, pour quelle fonctionnalité ?==

*Votre logiciel n'est concerné que si vous êtes '''assujetties à la TVA (et pas en franchise en base de TVA)''', ET si vous l'utilisez pour saisir des '''encaissements de particuliers''' (B2C=Business To Consumer) ou en mode mixte, à savoir encaissement aussi bien de particuliers (B2C) et d'entreprises (B2B), quelque soit le ratio entre les 2, quelque soit les modes de paiement utilisés (sauf à ne faire que du paiement direct par l'intermédiation d'un organisme bancaire européen). Donc:
**si vous n'encaissez pas d'argent, vous n'êtes PAS concerné.
**si vous êtes une association/organisme non assujettie à la TVA (association, médecin, ...), vous n'êtes PAS concerné.
**si vous êtes un professionnel bénéficiant du régime de remboursement forfaitaire de TVA agricole, vous n'êtes PAS concerné.
**si vous êtes un auto-entrepreneur, vous n'êtes PAS concerné (car assujettie en franchise en base).
**si vous êtes une entreprise dont l'intégralité des encaissements est réalisée avec l'intermédiation directe d’un établissement de crédit (système de paiement VAD d'une banque ou Virements), vous n'êtes PAS concerné. Remarque: Des encaissements par Carte bancaire via Paypal ou via Stripe ne sont pas des encaissements avec intermédiation directe d’un établissement de crédit, car ni Paypal ni Stripe ne sont des établissements de crédit (comprendre Banque).
**si vous ne facturez QUE des entreprises/professionnels, dans ce cas, vous n'êtes PAS concerné non plus par la loi finance (non B2C). Remarque: Si vous facturez des professionnels la plupart du temps et, exceptionnellement de temps en temps des particuliers via un mode de paiement non assuré par un organisme de crédit européen, si vous pouvez gérer/suivre ces facturations de particuliers à part sur papier, vous sortez alors du champ et n'êtes pas concerné.

Si vous n'êtes dans aucun des cas d'exception précédent, vous êtes concernés si vous utilisez le module Facture pour enregistrer vos paiements et/ou le module POS. Il vous faut alors vous assurer que le module "Log inaltérable" ("BlockedLog") fourni avec la v10 ou plus est bien activé. Sa désactivation, une fois les premières saisies faites ne sera ensuite plus envisageable. Avec la migration en v10 ou plus et l'activation de ce module vous aurez alors une version conforme sur le plan technique et fonctionnel. Il vous faudra ensuite, obtenir une attestation de conformité auprès d'un tiers qui confirme cette conformité technique/fonctionnelle pour être conforme d'un point de vue juridique.

Si vous utilisez une version en ligne Saas/Cloud fournie par un tiers, ce dernier vous la fournira surement (exemple: https://www.dolicloud.com ou https://www.novafirstcloud.com). Dans le cas contraire, il vous faut contactez votre intégrateur ou un prestataire pouvant fournir cette d'attestation.

Remarque: cette contrainte sera identique quelque soit l'ERP choisi. L'utilisation d'outils non spécialisés comme un tableur Excel ou autre, DANS LE BUT D'AVOIR UNE CONSERVATION DE TRACE DES PAIEMENTS, ne devient plus permis car le logiciel n'étant pas conforme, vous ne réussirez pas à trouver un prestataire pour fournir l'attestation de conformité. Par contre, si l'utilisation que vous faites d'Excel ou autre tableur est à des fins juste de "génération du PDF de la facture" sans ''conservation des données'' (Le texte de loi parle alors de logiciel ''facturier''), vous pouvez continuer à l'utiliser ainsi. Dans le cas ou l'utilisation est faite pour conserver trace de vos paiements, et si vous êtes dans le périmètre de la loi, un logiciel '''certifié OU attestable''' sur la partie encaissement (comme l'est Dolibarr) devient obligatoire (dans le cas d'un logiciel non certifié mais attestable comme Dolibarr, il vous faudra obtenir une attestation d'un Tiers).

==Je suis concerné, mais à partir de quand ?==

*Si vous êtes concerné, la loi s'applique au 1er janvier 2018. Toutefois, le texte de loi clarifié datant de juillet 2018, si on ajoute le temps requis par les logiciels pour s'adapter à la version définitive, puis le temps de migration sur la nouvelle version, une tolérance est de mise la première année (donc 2018), à condition de montrer que vous suivez le sujet et avez attendu pour avoir le texte définitif puis pour avoir la version conforme puis pour avoir le bon moment de faire votre migration. Si vous utilisez Dolibarr, les différentes évolutions de cette page montre que la démarche est engagée sur le logiciel depuis novembre 2016 et ce alors que le périmètre de la loi était encore contradictoire début novembre 2017.

A la question posée en janvier 2018 au ministère des finances: "Que pouvons nous dire aux utilisateurs qui sont en attente de texte/règle clarifiée pour agir, sachant que la loi est sensé être déjà effective ?", la réponse donnée a été que la première année (2018 donc), il y aurait tolérance, dès lors que vous montrez que vous avez pris une trajectoire sur 2018 pour bien faire. Cette année transitoire ayant été officiellement annoncée par le secrétaire d'état, dont voici les propos:

''« Je veux toutefois rassurer les entreprises : la direction générale des finances publiques les accompagnera pendant la première année d’application de ce dispositif, en vertu non pas d’une culture de la sanction ou du contrôle fondée sur le présupposé d’une malveillance des entreprises, mais d’un rôle de conseil. La DGFIP tiendra notamment compte des démarches engagées et des diligences effectuées par les entreprises pour obtenir le certificat ou l’attestation. C’est dans cet esprit que nous travaillerons. Les deux organismes certificateurs prendront également leur part de cet effort de pédagogie, qui est normal. »''

==La nécessité d'attestation ou certification disparaît-elle si on n'enregistre nos paiements que via un mode de règlement qui laisse déjà des traces, comme les chèques ou cartes ?==

Au départ, le type de règlement n'avait aucun impact sur la loi. Tous les types de paiement (chèque, carte, liquide, virement, ...) rentrent dans le périmètre de la loi et aucun ne permet d'être hors du champs d'application. L'amendement suivant https://www.nosdeputes.fr/15/amendement/235/1325C a tenté de restreindre le périmètre à un certain mode de paiement, mais a été rejeté.

Ceci se comprend dans la mesure où, même un paiement par carte, peut se faire via un système comme Paypal ou Stripe, et que l'administration fiscale française a très peu de pouvoir de contrôle sur une société étrangère.
Toutefois, il existe des cas où l'administration fiscale a un pouvoir de contrôle, c'est pourquoi, dans la re-publication au BOFIP de la loi le 4 juillet 2018, une exception a été introduite: Les professionnels réalisant leur paiement avec l'intermédiation directe d'un établissement de crédit européen ne sont plus soumis à l'obligation de certification ou attestation. Mais attention, on parle bien de paiements "directs" (donc Virement ou Carte de Débit ou de Crédit, mais pas chèques qui n'est pas "direct") et surtout via un système de paiement géré par un organisme bancaire européen. En d'autres terme, si on ne fait que du paiement CB avec un module de VAD d'une banque, on est NON soumis à la certification/attestation mais si le paiement CB (carte de crédit ou débit) se fait par un service comme Stripe ou Paypal, sauf à être exempté pour un autre motif, on l'est toujours (car l'état français n'a pas de moyen d'obtenir le listing des transactions via ces solutions, bien que le paiement soit par carte bancaire).

==Quelles sont les conditions pour une application concernée pour être conforme (conditions pour obtenir la certification OU être attestable conforme par un tiers) ?==

*Principe d'inaltérabilité
**Logs non modifiable par chaînage pour tout ce qui concerne les ventes, encaissements et impression (incluant toutes les mentions obligatoires d'une facture)
**Quand une facture est validée, la trace et les informations qui ont donné lieu au contenu de la facture ne peuvent plus être modifier. Rem: Il est toujours possible de modifier mais la trace historique (log archivé) doit rester. Si un changement est fait, ce changement doit lui aussi être tracé et reprendre toutes les nouvelles informations et être lui aussi non effaçable.
**Liens de correspondance afin de vérifier différence entre les logs/archives et les tables de factures et paiements.

*Conservation sur 6 ans ou plus (Remarque: Dolibarr conserve les données en base à vie)

*Fonction "Archiver" annuellement qui permet d'exporter dans un fichier externe dans un format lisible sans le logiciel, et par l'administration, pour consulter l'archive (et retrouver les infos qui compose la facture, les paiements).

*Fournir, soit la certification de conformité du logiciel, soit une attestation de conformité (Voir dans les FAQ plus loin "Quel éditeur peut fournir des attestations pour ma version ?" sur comment l'obtenir)

!!! En d'autres termes, il ne sera plus possible d'utiliser des logiciels tableurs comme Excel ou Google Apps, ni autre solution développée soi même pour avoir une trace et conservation de vos paiements, sans considération de cette loi (sauf à continuer de saisir en parallèle soit dans un autre système conforme, soit sur le bon vieux carnet à souche). Mais vous pouvez continuer à utiliser votre tableur à des fins de logiciel pour générer vos Factures (la loi parle de "logiciel facturier") si il n'y a pas de conservation de données (le logiciel est alors considéré comme simple facturier et donc hors périmètre).
Pour un suivi et conservation de vos encaissements via un outils informatique, des logiciels, conforme loi finance 2016 comme Dolibarr ERP CRM v10 ou + deviennent alors obligatoires, dès lors que l'on est concerné (voir FAQ '''...suis-je concerné...''').

==Quelle est la différence entre certification et attestation ?==

La certification est une procédure par laquelle une tierce partie, l’organisme certificateur (Par exemple la LNE ou L'AFNOR), donne une assurance écrite qu’un système d’organisation, un processus, une personne, un produit ou un service est conforme à des exigences spécifiées dans une norme ou un référentiel. Elle est encadrée par le Code de la Consommation. Sur un logiciel, la certification est faite pour une version donnée sur le périmètre de l'application ou d'une partie de l'application uniquement. Chaque nouvelle version devant être re-certifiée.

L'attestation de conformité est fournie par une tierce partie également, mais ce dernier n'a pas besoin d'être un organisme certifiant. Il peut s'agir de n'importe quelle société. C'est souvent l'éditeur du logiciel, mais il peut s'agir en fait de n'importe quelle société. Cette attestation est une déclaration par laquelle l’éditeur témoigne et s’engage à ce que le système d’encaissement qu’il atteste respecte les conditions d’inaltérabilité, de sécurisation, de conservation et d’archivage des données. L'attestation est elle aussi valable pour une version et éventuellement un paramétrage donné.

Dans le cadre de la loi des finances pour 2016, et si vous êtes dans le périmètre de cette loi (voir autres FAQ), vous devez, soit avoir un logiciel "certifié", soit avoir un logiciel "attesté conforme" (Notez que le terme "certifié" est souvent utilisé dans les textes (plus rarement dans le texte définitif de la loi) comme raccourci pour signifier "certifié ou attesté conforme".

==L'application Dolibarr sera-t-elle certifiée par l'éditeur ?==

Pour Dolibarr, et de nombreux logiciels Open Source, il n'y a pas un éditeur bien identifié car de nombreuses sociétés différentes contribuent à son évolution.

Au sens de la loi, l'éditeur du logiciel est le '''"dernier" qui a modifié/validé le code'''. L'entité qui postule pour une certification peut donc être, aussi bien l'association Dolibarr, comme tout intégrateur ou autre institution externe.

Il est possible que l'association Dolibarr, qui a pour rôle la promotion du logiciel, fasse les démarches pour obtenir la certification pour certaines versions majeures, celles qui sont officiellement packagées par le release manager et qui sont mises à disposition sur l'espace de téléchargement officiel par l'association. Il est fort probable que seules quelques versions bien identifiées feront l'objet d'une demande de certification. Toutefois, cette obtention de certification (Certification LNE ou certification NF525) n'est pas obligatoire pour être conforme. L'autre solution, celle de l'obtention d'une attestation s'avère plus simple.
Nous encourageons donc les utilisateurs qui ont obligation d'utiliser un logiciel conforme anti-fraude à la TVA selon la loi finance 2016 (donc les assujettis à TVA hors franchise de base, et qui facture/encaisse des particuliers) à '''se tourner vers la solution d'attestation'''. Voir point suivant.

==L'attestation de conformité, autre possibilité, sera-t-elle fournie par l'éditeur ou autre tiers ?==

L'autre solution pour être en règle est d'obtenir une attestation de conformité de votre logiciel de caisse.

En tant qu'utilisateur, et si vous êtes dans le périmètre de la loi, vous pourrez obtenir une attestation auprès de n'importe quel tiers/intégrateur prêt à la fournir (en général moyennant finance), ou vous la délivrer à vous même si vous êtes une société d'édition de logiciel. Voir les 2 FAQ suivantes pour savoir qui pourra délivrer les attestations de conformité...

==Quel éditeur peut fournir des attestations pour ma version, à quel prix ?==

N'importe quelle société qui a les compétences pour analyser le logiciel et vérifier que ses fonctionnalités sont bien en règle peut fournir une attestation à autrui. Le code d'une application libre étant ouvert, toute société compétente dans la technologie du produit, peut maîtriser le code aussi bien que les développeurs initiaux. Une telle société peut donc être qualifiée d'"éditeur", même si elle n'a pas produit ou très peu produit de code au projet final, et par conséquent, et à même de fournir un attestation individuelle à ses clients.

Le BOFIP dit clairement:

"310. Lorsque le logiciel ou système est conçu de manière ouverte pour permettre son adaptation aux besoins spécifiques des clients, on entend par « éditeur » qui peut valablement demander la certification ou fournir l'attestation individuelle."

Bref, si vous utilisez une version en ligne saas/cloud fournie par un tiers, ce dernier vous la fournira surement (Exemple avec https://www.dolicloud.com ou encore https://www.novafirstcloud.com). Dans le cas contraire, il vous faut contactez votre intégrateur ou un prestataire pouvant fournir cette d'attestation. Remarque: cette contrainte sera identique quelque soit l'outil d'enregistrements des encaissements choisi.

En ce qui concerne le prix, tout dépend du tiers qui fournit l'attestation. Certains, par exemple, pourront donner l'attestation gratuitement à condition d'héberger le logiciel attesté chez eux. D'autres vous feront payer la prestation d'audit et la délivrance de l'attestation. Cela peut être de manière récurrente si l'attestation doit être réémise régulièrement suite à modification/mise à jour de l'application.

==La loi finance est-elle compatible avec les licences libres de logiciels de caisse ?==

Si le logiciel libre n'est pas un logiciel qui réalise des encaissements ou si vous n'encaissez que des entreprises, la question ne pose même pas.

Si le logiciel libre est un logiciel d'encaissements et que les clients encaissés sont des particuliers, alors oui, le logiciel libre est parfaitement compatible:

Le paragraphe 40 du BOI le dit explicitement en reconnaissant aux utilisateurs la possibilité « ''d'adapter le logiciel à leurs besoins spécifiques'' » :

"''... Sont notamment concernés les logiciels de comptabilité ou de gestion dits "libres" ou développés en interne, c'est-à-dire développés par l'assujetti lui-même. On entend par logiciel libre un logiciel dont les utilisateurs ont un libre usage, une libre étude, une libre modification et une libre distribution. Ces libertés permettent aux utilisateurs d'adapter le logiciel à leurs besoins spécifiques. Les modifications que les utilisateurs peuvent apporter au logiciel libre ou développé en interne ne doivent pas avoir pour objet ou pour effet d'altérer le respect des conditions d'inaltérabilité, de sécurisation, de conservation et d'archivage décrites ci-dessous...''"

Par ailleurs, le paragraphe 310 évoque à nouveau le cas des logiciels « conçus de manière ouverte », c.à.d les logiciels libres.

Donc, aucune objection à utiliser des logiciels libres. Mais attention, l'autorisation de modification est restreinte au code et paramètres "triviaux". En effet, que ce soit lors d'une utilisation de la version certifiée ou d'une version rendue conforme par obtention d'une attestation de conformité, la nouvelle loi vous prive d'une partie de votre liberté de '''modifier le logiciel de caisse SUR LES PARTIES qui concernent les fonctions d'inaltérabilité, sécurisation, conservation et archivage'''. En effet, en faisant une telle modification, la version est considérée comme changée de manière "non triviale", aussi la certification n'est plus valable, l'attestation d'un tiers non plus. Les logiciels libres sont donc tout à fait légaux et compatible avec la loi, par contre, c'est à condition de ne pas faire n'importe quelle modification. Vous perdez donc une partie de votre liberté (non pas du fait de la licence du logiciel qui le permet, mais du fait de la loi qui est prioritaire sur les droits accordés par la licence. Le logiciel libre est donc bien compatible avec la loi, mais la loi vous prive d'une des 4 libertés que le logiciel libre apportait, celle de le modifier librement. Vous pouvez toujours le faire, mais à condition que cela ne porte pas sur le comportement de l'encaissement, ou, si cela porte sur celui-ci, que vous ré-obteniez soit la certification à nouveau (complexe et payant), soit une nouvelle attestation d'un éditeur ou intégrateur.

==Pour ma propre utilisation, puis-je m'auto délivré l'attestation de conformité pour une version que j'ai modifié moi même sur les parties d'encaissements==

Uniquement un nombre très restreints d'entreprise le pourront, celles qui sont dans le domaine de l''''Edition de logiciel de comptabilité ou de gestion ou de système de caisse'''. Toutefois, sur le plan juridique une telle classification n'existe que par les faits. En effet, on serait tenté de penser que les entreprises ayant le codes NACE (Code NACE = terme européen du code NAF/APE) '''58.29''' qui signifie '''Edition de logiciel autre''' et/ou '''62.01Z''' qui signifie '''Développement de logiciels''' pourrait être qualifiées. Toutefois, il faut avoir en tête que le code APE est "''attribué par l'INSEE à des fins statistiques, et ne saurait suffire à créer des droits ou des obligations pour les entreprises''" (Ceci est dans le décret qui approuve la nomenclature: décret n° 2007-1888 du 26 décembre 2007, article 5, point I). Dans la réalité, ce code est malgré tout utilisé pour avoir des présomptions d'activité au niveau fiscal ou administratif. Donc, c'est un avantage, mais aucunement une garantie et inversement, une entreprise n'ayant pas cette classification peut avoir des arguments suffisamment solide pour démontrer son activité d'"éditeur de logiciel de caisse". <ref>BOI-TVA-DECLA-30-10-30-20180704, point 375</ref>

==Je suis intégrateur ou développeur informatique, je sais que Dolibarr v10 et ultérieur répond aux exigences de conformité, puis-je délivrer l'attestation de conformité, à mon client qui est en v10 ou plus, moi même ?==

Oui. A vous de fournir/indiquer à votre client la version/paramétrage que vous attestez. Vous pouvez générez la signature de la version et paramétrage que vous attestez avec l'outil '''generate_filelist_xml.php''' fourni avec les sources de l'application.
Cette signature vous permettra de vérifier que votre client n'a pas fait de '''modification de code ou paramétrage sur les parties qui concernent l'encaissement'''. Auquel cas, il devient éditeur, et votre attestation n'est plus valide, vous n'êtes alors plus responsable d'une apparition d'une fonctionnalité non conforme dans le logiciel.

==Je suis intégrateur ou développeur informatique, quel outil ai-je à ma disposition pour m'assurer que les exigences sur le logiciel sont bien assurées par une version installée de Dolibarr==

La version 7.0 contient l'ensemble des exigences et notamment le module "Log inaltérable" qu'il vous revient d'activer (l'obligation d'activation dépend du fait que vous êtes concerné ou non, voir FAQ précédente pour cela). L'application est une application Open Source, le client utilisateur peut réussir à modifier le code (notons que ceci est aussi possible avec du propriétaire, juste plus difficile). De même, un hacker peut toujours réussir à trafiquer un logiciel. Face à cela, Dolibarr fourni, à partir de la version 6.0, un outil pour obtenir la liste de tous les fichiers qui auraient été modifiés par rapport à la version officielle, ou par rapport à une version packagée par un intégrateur tiers, ainsi que la liste des paramètres de configuration obligatoires pour la conformité (voir plus bas) et qui aurait aussi été modifiés. Le certificat étant délivré pour une version avec une configuration donnée, si un utilisateur ou hacker a pu altérer partiellement l'application sur du code ou des paramètres sensibles, l'outil de contrôle pourra le révéler, auquel cas, la responsabilité de non conformité n'est plus du ressort de l'entité qui a fournit l'attestation, puisque ce n'est plus la même application, mais de la responsabilité de celui qui est à l'origine des modifications.

Paramètres recommandées à contrôler/imposer dans une attestation:

*Pays de la société (doit rester à France). Rem: Une fois le premier encaissement fait avec le module "Log inaltérable LF 2016", sa désactivation renverra un warning.
*Constante MAIN_MODULE_BLOCKEDLOG doit être définie (Cela signifie que le module "Log inaltérable LF 2016" est bien actif).

Optionnellement, vous pouvez:

*Imposer que la constante BLOCKEDLOG_DISABLE_NOT_ALLOWED_FOR_COUNTRY soit définie et contient le code pays FR (ceci bloque la désactivation du module par erreur).

Remarque:
Vous pouvez utiliser l'outil '''build/generate_filecheck_xml.php''' pour générer un fichier emprunte de la version et/ou paramétrage donné que vous voulez imposer.
Ensuite utilisez l'outil dans le menu '''Accueil - Outils administration - Dolibarr - Files integrity check''' ou bien à distance l'API '''/setup/checkintegrity''' (le module API REST doit avoir été activée) pour vérifier qu'une version est conforme à ce fichier emprunte.

==Je suis dans le périmètre de la loi, j'ai ajouté un module externe sur mon Dolibarr, faut-il une attestation Loi Finance pour ce module ?==

Il n'y a pas notion de "certificat ou d'attestation loi finance" sur un module:

En effet, ce qui doit être certifié ou attesté, c'est la partie du logiciel qui réalise les enregistrements des paiements, pris dans le contexte de l'ensemble du système d'information, et non chaque module de votre application individuellement. Le logiciel Dolibarr v10 ou + est attestable, donc, si vous êtes dans le périmètre de la loi, ce qu'il vous faut obtenir, c'est une attestation de conformité de l'ensemble de la solution, validant les modules ajoutés qui impactent l'enregistrement des paiements. Donc,

*Si vous êtes dans le périmètre de la loi et que le module ajouté ne concerne pas l'enregistrement des paiements, il n'y a rien de particulier à faire de plus (dès lors que vous êtes dans le périmètre de la loi, vous devez obtenir l'attestation pour les fonctions encaissements de paiements de votre Dolibarr, peu importe que vous ajoutiez ce module ou pas, le module n'ayant pas d'effet sur les fonctions d'encaissements, on perle d'effet trivial ou mineur au code).
*Si toutefois, vous êtes dans le périmètre de la loi et que le module touche à la partie encaissement, il faudra que le tiers fournissant l'attestation prenne en considération ce module (si vous aviez déjà obtenu l'attestation, il vous faudra la ré-obtenir car l'ajout du module l'invalide puisque ce module touche au code de la partie encaissement des paiements).

La nature du module doit vous permettre de savoir si c'est un module qui touche à l'enregistrement des encaissements ou pas. Dans le doute, renseignez vous auprès de l'auteur du module (ce n'est pas lui qui fournira l'attestation mais pourra dire si le module doit être pris en compte ou non dans le processus d'attestation).

=Travaux dans Dolibarr pour permettre la conformité via attestation=

Et Dolibarr dans tout cela ?
Dolibarr v10+ est prêt et attestable sur l'intégralité de ses modules standard (En fait, il l'est même depuis la v7 si vous n'utilisez pas de module POS).
Voici le suivi des travaux réalisés depuis la v5: [[Loi article 88 finances 2016 et Certification NF525 - Travaux Dolibarr]]

= Où trouver un modèle d'attestation ? =
Les services des impôts proposent un modèle d'attestation individuelle que vous pouvez consulter [https://bofip.impots.gouv.fr/bofip/10692-PGP.html/identifiant%3DBOI-LETTRE-000242-20201230 dans le Bulltein Officiel des Impots du 30/12/2020]

=Notes et références=
<references />

*Synthèse détaillée du BOFIP par La Revue Fiduciaire, rédigé le 06/10/2016: [http://revuefiduciaire.grouperf.com/article/3661/hb/20160919173548859.html Article sur la revue fiduciaire]
*Synthèse courante par l'APRIL (document en évolution permanente): https://pad.april.org/p/logiciel-caisse-publication-BOI
*Article de l'APRIL: https://www.april.org/loi-de-finances-2016-une-doctrine-fiscale-qui-reconnait-les-logiciels-libres-mais-avec-une-marge-de
*Echanges sur les mailing-list de l'April: https://listes.april.org/wws/arc/comptabilite/ (réservé aux adhérents April)
*Note d'information très courte du service public: https://www.service-public.fr/professionnels-entreprises/actualites/A10279
*http://creativekara.fr/doku.php?id=pasteque:lf2016
*Réunion entre le chef de projet Dolibarr, autres représentants April et le ministère des finances en 2008 pour participation à la refonte et clarification du texte de loi.

File:Type fiche dolibarr.png

2021-02-04T15:18:23Z

Iouston:

type fiche dolibarr

File:2021-02-04 16 12 41-Tiers + multicompany.png

2021-02-04T15:13:48Z

Iouston:

icone pour personnaliser les colonnes des vues

Setup Other

2020-09-30T08:48:20Z

Iouston: /* Proposals Module */ ajout de l'option DOC_SHOW_FIRST_SALES_REP

Template:TemplateListOfTriggers

2020-07-01T08:34:42Z

Iouston: add USERGROUP trigger

{|class="wikitable sortable" align="left" width="100%" border="0" cellpadding="1" cellspacing="0" class="dolbox"
|style="background-color: #e9e9ef"| Trigger code ($action)
|style="background-color: #e9e9ef"| Type object ($object)
|-
|USER_CREATE
|user.class.php
|-
|<strike>USER_CREATE_FROM_CONTACT</strike> (Removed since 3.8)
|<strike>user.class.php</strike>
|-
|USER_MODIFY
|user.class.php
|-
|USER_DELETE
|user.class.php
|-
|USER_LOGIN
|user.class.php
|-
|USER_LOGIN_FAILED
|user.class.php
|-
|USER_LOGOUT
|user.class.php
|-
|<strike>USER_UPDATE_SESSION</strike> (Removed since 3.7.1)
|<strike>user.class.php</strike>
|-
|USER_ENABLEDISABLE
|user.class.php
|-
|USER_NEW_PASSWORD
|user.class.php
|-
|USER_SETINGROUP
|user.class.php
|-
|USER_REMOVEFROMGROUP
|user.class.php
|-
|USERGROUP_CREATE ''(>= 12.0.0)
|usergroup.class.php
|-
|USERGROUP_MODIFY''(>= 12.0.0)
|usergroup.class.php
|-
|USERGROUP_DELETE''(>= 12.0.0)
|usergroup.class.php
|-
|GROUP_CREATE
|usergroup.class.php
|-
|GROUP_MODIFY
|usergroup.class.php
|-
|GROUP_DELETE ''(>= 3.3.0)''
|usergroup.class.php
|-
|COMPANY_CREATE
|societe.class.php
|-
|COMPANY_MODIFY
|societe.class.php
|-
|COMPANY_DELETE
|societe.class.php
|-
|COMPANY_SENTBYMAIL ''(>= 3.5.0)''
|societe.class.php
|-
|CONTACT_CREATE
|contact.class.php
|-
|CONTACT_MODIFY
|contact.class.php
|-
|CONTACT_DELETE
|contact.class.php
|-
|CONTACT_ENABLEDISABLE ''(>= 3.5.0)''
|contact.class.php
|-
|PRODUCT_CREATE
|product.class.php
|-
|PRODUCT_MODIFY
|product.class.php
|-
|PRODUCT_PRICE_MODIFY
|product.class.php
|-
|PRODUCT_DELETE
|product.class.php
|-
|SUPPLIER_PRODUCT_BUYPRICE_UPDATE
|fournisseur.product.class.php
|-
|SUPPLIER_PRODUCT_BUYPRICE_CREATE
|fournisseur.product.class.php
|-
|ORDER_CREATE
|commande.class.php
|-
|ORDER_VALIDATE
|commande.class.php
|-
|ORDER_SENTBYMAIL
|commande.class.php
|-
|ORDER_DELETE
|commande.class.php
|-
|ORDER_CLASSIFY_BILLED
|commande.class.php
|-
|ORDER_CLONE
|commande.class.php
|-
|ORDER_CLOSE
|commande.class.php
|-
|ORDER_CANCEL
|commande.class.php
|-
|ORDER_REOPEN ''(>= 3.3.0)''
|commande.class.php
|-
|COMMANDE_ADD_CONTACT
|commande.class.php
|-
|COMMANDE_DELETE_CONTACT
|commande.class.php
|-
|COMMANDE_DELETE_RESOURCE ''(>= 3.6.0)''
|commande.class.php
|-
|LINEORDER_INSERT
|commande.class.php
|-
|LINEORDER_UPDATE
|commande.class.php
|-
|LINEORDER_DELETE
|commande.class.php
|-
|LINEORDER_DISPATCH ''(>= 3.4.0)''
|commande.class.php
|-
|ORDER_SUPPLIER_CREATE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_CLONE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_VALIDATE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_SENTBYMAIL
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_APPROVE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_REFUSE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_CANCEL
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_DELETE
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_DISPATCH ''(>= 3.4.0)''
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_ADD_CONTACT
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_DELETE_CONTACT
|fournisseur.commande.class.php
|-
|ORDER_SUPPLIER_DELETE_RESOURCE ''(>= 3.6.0)''
|fournisseur.commande.class.php
|-
|LINEORDER_SUPPLIER_CREATE
|fournisseur.commande.class.php
|-
|LINEORDER_SUPPLIER_UPDATE
|fournisseur.commande.class.php
|-
|LINEORDER_SUPPLIER_DELETE ''(>= 3.6.0)''
|fournisseur.commande.class.php
|-
|PROPAL_CREATE
|propal.class.php
|-
|PROPAL_DELETE
|propal.class.php
|-
|PROPAL_CLONE
|propal.class.php
|-
|PROPAL_REOPEN ''(>= 3.5.0)''
|propal.class.php
|-
|PROPAL_VALIDATE
|propal.class.php
|-
|PROPAL_CLOSE_SIGNED
|propal.class.php
|-
|PROPAL_CLOSE_REFUSED
|propal.class.php
|-
|PROPAL_SENTBYMAIL
|propal.class.php
|-
|PROPAL_ADD_CONTACT
|propal.class.php
|-
|PROPAL_DELETE_CONTACT
|propal.class.php
|-
|PROPAL_DELETE_RESOURCE ''(>= 3.6.0)''
|propal.class.php
|-
|LINEPROPAL_INSERT
|propal.class.php
|-
|LINEPROPAL_UPDATE
|propal.class.php
|-
|LINEPROPAL_DELETE
|propal.class.php
|-
|CONTRACT_CREATE
|contrat.class.php
|-
|CONTRACT_VALIDATE
|contrat.class.php
|-
|CONTRACT_SERVICE_ACTIVATE
|contrat.class.php
|-
|CONTRACT_SERVICE_CLOSE
|contrat.class.php
|-
|CONTRACT_DELETE
|contrat.class.php
|-
|CONTRAT_ADD_CONTACT
|contrat.class.php
|-
|CONTRAT_DELETE_CONTACT
|contrat.class.php
|-
|CONTRAT_DELETE_RESOURCE ''(>= 3.6.0)''
|contrat.class.php
|-
|LINECONTRACT_INSERT ''(>= 3.9.0) (LINECONTRACT_CREATE >= 3.7.0)''
|contrat.class.php
|-
|LINECONTRACT_UPDATE ''(CONTRACT_LINE_MODIFY < 3.5.0) (CONTRACT_LINE_MODIFY > 3.3.0)''
|contrat.class.php
|-
|LINECONTRACT_DELETE ''(CONTRACT_LINE_DELETE < 3.5.0) (CONTRACTLINE_DELETE < 3.3.0)''
|contrat.class.php
|-
|BILL_CREATE
|facture.class.php
|-
|BILL_MODIFY
|facture.class.php
|-
|BILL_CLONE
|facture.class.php
|-
|BILL_VALIDATE
|facture.class.php
|-
|BILL_UNVALIDATE ''(>= 3.4.0)''
|facture.class.php
|-
|BILL_PAYED
|facture.class.php
|-
|BILL_UNPAYED
|facture.class.php
|-
|BILL_CANCEL
|facture.class.php
|-
|BILL_DELETE
|facture.class.php
|-
|BILL_SENTBYMAIL
|facture.class.php
|-
|FACTURE_ADD_CONTACT
|facture.class.php
|-
|FACTURE_DELETE_CONTACT
|facture.class.php
|-
|FACTURE_DELETE_RESOURCE ''(>= 3.6.0)''
|facture.class.php
|-
|LINEBILL_INSERT
|facture.class.php
|-
|LINEBILL_UPDATE
|facture.class.php
|-
|LINEBILL_DELETE
|facture.class.php
|-
|BILL_SUPPLIER_CREATE
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_MODIFY
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_DELETE ''(INVOICE_SUPPLIER_DELETE < 3.3.0)''
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_VALIDATE
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_PAYED
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_UNPAYED
|fournisseur.facture.class.php
|-
|BILL_SUPPLIER_SENTBYMAIL
|fournisseur.facture.class.php
|-
|INVOICE_SUPPLIER_ADD_CONTACT
|fournisseur.facture.class.php
|-
|INVOICE_SUPPLIER_DELETE_CONTACT
|fournisseur.facture.class.php
|-
|INVOICE_SUPPLIER_DELETE_RESOURCE ''(>= 3.6.0)''
|fournisseur.facture.class.php
|-
|LINEBILL_SUPPLIER_CREATE
|fournisseur.facture.class.php
|-
|LINEBILL_SUPPLIER_UPDATE
|fournisseur.facture.class.php
|-
|LINEBILL_SUPPLIER_DELETE ''(>= 3.4.0)''
|fournisseur.facture.class.php
|-
|PAYMENT_CUSTOMER_CREATE
|paiement.class.php
|-
|PAYMENT_DELETE (<= 3.8)
|paiement.class.php
|-
|PAYMENT_CUSTOMER_DELETE (>= 3.9)
|paiement.class.php
|-
|PAYMENT_ADD_TO_BANK
|paiement.class.php
|-
|PAYMENT_SUPPLIER_CREATE
|paiementfourn.class.php
|-
|PAYMENT_SUPPLIER_DELETE (>= 3.9)
|paiement.class.php
|-
|PAYMENT_SALARY_CREATE ''(>= 3.6.0)''
|paymentsalary.class.php
|-
|PAYMENT_SALARY_MODIFY ''(>= 3.6.0)''
|paymentsalary.class.php
|-
|PAYMENT_SALARY_DELETE ''(>= 3.6.0)''
|paymentsalary.class.php
|-
|FICHINTER_CREATE ''(FICHEINTER_CREATE < 3.3.0)''
|fichinter.class.php
|-
|FICHINTER_MODIFY ''(FICHEINTER_MODIFY < 3.3.0)''
|fichinter.class.php
|-
|FICHINTER_DELETE ''(FICHEINTER_DELETE < 3.3.0)''
|fichinter.class.php
|-
|FICHINTER_VALIDATE ''(FICHEINTER_VALIDATE < 3.3.0)''
|fichinter.class.php
|-
|FICHINTER_SENTBYMAIL ''(FICHEINTER_SENTBYMAIL < 3.3.0)''
|fichinter.class.php
|-
|FICHINTER_ADD_CONTACT
|fichinter.class.php
|-
|FICHINTER_DELETE_CONTACT
|fichinter.class.php
|-
|FICHINTER_DELETE_RESOURCE ''(>= 3.6.0)''
|fichinter.class.php
|-
|LINEFICHINTER_CREATE ''(>= 3.5.0)''
|fichinter.class.php
|-
|LINEFICHINTER_UPDATE ''(>= 3.5.0)''
|fichinter.class.php
|-
|LINEFICHINTER_DELETE ''(>= 3.5.0)''
|fichinter.class.php
|-
|MEMBER_CREATE
|adherent.class.php
|-
|MEMBER_VALIDATE
|adherent.class.php
|-
|MEMBER_SUBSCRIPTION
|adherent.class.php
|-
|MEMBER_MODIFY
|adherent.class.php
|-
|MEMBER_RESILIATE
|adherent.class.php
|-
|MEMBER_NEW_PASSWORD
|adherent.class.php
|-
|MEMBER_DELETE
|adherent.class.php
|-
|CATEGORY_CREATE
|category.class.php
|-
|CATEGORY_MODIFY
|category.class.php
|-
|CATEGORY_DELETE
|category.class.php
|-
|CATEGORY_LINK ''(>= 3.5.0)''
|category.class.php
|-
|CATEGORY_UNLINK ''(>= 3.5.0)''
|category.class.php
|-
|SHIPPING_CREATE
|expedition.class.php
|-
|SHIPPING_VALIDATE
|expedition.class.php
|-
|SHIPPING_MODIFY
|expedition.class.php
|-
|SHIPPING_DELETE
|expedition.class.php
|-
|SHIPPING_SENTBYMAIL
|expedition.class.php
|-
|DELIVERY_VALIDATE
|livraison.class.php
|-
|DELIVERY_DELETE
|livraison.class.php
|-
|ACTION_CREATE
|actioncomm.class.php
|-
|ACTION_MODIFY
|actioncomm.class.php
|-
|ACTION_DELETE
|actioncomm.class.php
|-
|ACTION_ADD_CONTACT
|actioncomm.class.php
|-
|ACTION_DELETE_CONTACT
|actioncomm.class.php
|-
|ACTION_DELETE_RESOURCE ''(>= 3.6.0)''
|actioncomm.class.php
|-
|DEPLACEMENT_CREATE
|deplacement.class.php
|-
|DON_CREATE
|don.class.php
|-
|DON_MODIFY ''(>= 3.7.0)''
|don.class.php
|-
|DON_DELETE ''(>= 3.7.0)''
|don.class.php
|-
|LOCALTAX_CREATE
|localtax.class.php
|-
|LOCALTAX_MODIFY
|localtax.class.php
|-
|LOCALTAX_DELETE
|localtax.class.php
|-
|TVA_CREATE
|tva.class.php
|-
|TVA_MODIFY
|tva.class.php
|-
|TVA_DELETE
|tva.class.php
|-
|TVA_ADDPAYMENT
|tva.class.php
|-
|PROJECT_CREATE
|project.class.php
|-
|PROJECT_MODIFY
|project.class.php
|-
|PROJECT_DELETE
|project.class.php
|-
|PROJECT_VALIDATE
|project.class.php
|-
|PROJECT_CLOSE
|project.class.php
|-
|PROJECT_ADD_CONTACT
|project.class.php
|-
|PROJECT_DELETE_CONTACT
|project.class.php
|-
|PROJECT_DELETE_RESOURCE ''(>= 3.6.0)''
|project.class.php
|-
|TASK_CREATE
|task.class.php
|-
|TASK_MODIFY
|task.class.php
|-
|TASK_DELETE
|task.class.php
|-
|TASK_TIMESPENT_CREATE
|task.class.php
|-
|TASK_TIMESPENT_MODIFY
|task.class.php
|-
|TASK_TIMESPENT_DELETE
|task.class.php
|-
|PROJECT_TASK_ADD_CONTACT
|task.class.php
|-
|PROJECT_TASK_DELETE_CONTACT
|task.class.php
|-
|PROJECT_TASK_DELETE_RESOURCE ''(>= 3.6.0)''
|task.class.php
|-
|MYECMDIR_CREATE
|ecmdirectory.class.php
|-
|MYECMDIR_MODIFY
|ecmdirectory.class.php
|-
|MYECMDIR_DELETE
|ecmdirectory.class.php
|-
|<strike>IMPORT_DELETE</strike> (Removed since 3.7.0)
|<strike>import.class.php</strike>
|-
|STOCK_MOVEMENT
|mouvementstock.class.php
|-
|PAYBOX_PAYMENT_OK
|
|-
|PAYPAL_PAYMENT_OK
|
|-
|LINK_CREATE ''(>= 3.5.0)''
|link.class.php
|-
|LINK_MODIFY ''(>= 3.5.0)''
|link.class.php
|-
|LINK_DELETE ''(>= 3.5.0)''
|link.class.php
|-
|OPENSURVEY_CREATE ''(>= 3.6.0)''
|opensurveysondage.class.php
|-
|OPENSURVEY_DELETE ''(>= 3.6.0)''
|opensurveysondage.class.php
|-
|}

Setup Other

2020-05-14T10:27:20Z

Iouston: /* Email and SMS */ add MAIN_INFO_SOCIETE_MAIL_ALIASES options

Setup Other

2019-09-25T07:03:39Z

Iouston: /* Global Options */ add main_disable_trunc options

Dolibarr suppliers France

2019-07-30T13:06:49Z

Iouston: Update of iouston provider

{{Dolibarr_suppliers}}

{{TemplateCompany|
name=1fonet Services|
profid=|
desc=Integrations and open source development
Specialist software open source.Dolibarr, Joomla! Prestashop, Cahiers des charges ERP/CRM, Ecommerce, site web, gratuits. Complementary development of the module, component or application needs. Based in the PACA region work throughout France.|
web=http://www.1fonet.fr|
email=mailto:contact@1fonet.fr|
zip=13530|
town=Trets|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=2A2C Conseil|
profid=|
desc=CRM et Solutions e-commerce opensource pour TPM et PME, VoIP et Hosting en marque blanche, maintenance informatique, WordPress, Dolibarr, Prestashop, Formation utilisateur|
web=|
email=mailto:info@2a2c-conseil.fr|
zip=75012|
town=PARIS|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=A3SYS : MON-DOLIBARR|
profid=52456658500021 (SIRET)|
desc=Intégration, assistance et développement.
Notre société forte de plus de 20 ans d'expérience dans l'intégration de divers ERP propose ses services aux entreprises souhaitant mettre en place l'ERP Dolibarr. Une plateforme dédiée est mise en place pour proposer des services de qualité à moindre coût.|
web=http://www.mon-dolibarr.fr|
email=http://www.mon-dolibarr.fr/contact/|
zip=59310|
town=Orchies (Nord - France)|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=logo_mon-dolibarr.jpg
}}

{{TemplateCompany|
name=A6TM - SOLUTIONS|
profid=|
desc=A6TM SOLUTIONS, est une entreprise maîtrisant les technologies de l'informatique, et spécialisée dans les solutions informatiques et notamment les services tels que l'infogérance, installations et déploiements, dépannages, maintenance et réseaux informatique. Installation et maintenance CMS(Joomla, Wordpress...), Progiciel ERP/CRM (Dolibarr...)|
web=http://www.a6tm-solutions.fr|
email=mailto:contact@a6tm-solutions.fr|
zip=44|
town=Nantes et son département|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ACN - Atelier de Création Numérique|
profid=808 725 212 00019|
desc=ACN (Atelier de Création Numérique), Maîtres d’œuvres en Informatique, Nous sommes spécialisés dans le conseil, la création et l’intégration de solutions professionnelles pour les bureaux d'études. Nos solutions vont de l’intégration d’outils Open Source et de logiciels libres à la mise en place des meilleurs produits de grands éditeurs du marché.|
web=http://ateliercreationnumerique.com/|
email=mailto:contact@atlcreanum.com|
zip=44|
town=Nantes et Grand Ouest|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=acn.png|
}}

{{TemplateCompany|
name=Aplose|
partner=yes|
profid=534906698|
desc=
Aplose c'est l'Agence pour la Promotion du Libre et de l'Open Source en Entreprise, société de service et organisme de formation spécialisé dans les logiciels libres de création de site internet et boutique en ligne (wordpress, prestashop), les erp, logiciels de gestion et logiciels de caisse et point de vente (Odoo, Dolibarr), les langages de programmation (java, html5, Javascript, php), les bases de données (mysql, postgresql), les systèmes d'exploitation (linux), les méthodes des gestion de projet agiles (Scrum). Bordeaux - Montpellier|
web=http://www.aplose.fr|
email=[mailto:oandrade@aplose.fr?subject=Contact%20from%20Dolibarr%20Suppliers%20France20page oandrade@aplose.fr]|
zip=33610|
town=Cestas|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=no|
service_local=yes|
service_formation=yes|
logo=Logo_Aplose.png
}}

{{TemplateCompany|
name=Artaban Communication|
partner=no|
profid=400 396 388 00037|
desc=Artaban Communication est une SSLL. Spécialistes du CMS SPIP, nous concevons et réalisons des sites web à forte composante éditoriale. Nous prenons également en charge le webmastering et la création de contenu. Notre expertise s'étend à un certain nombre de logiciels, choisis pour leur qualité et leur intérêt, et avec lesquels nous aimons travailler et notamment Dolibarr. Artaban Communication est membre de l'April.|
web=http://www.artaban.fr|
email=mailto:contact@artaban.fr|
zip=94340|
town=Joinville-le-Pont|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Artaban_logo.png‎|
}}

{{TemplateCompany|
name=ATM Consulting|
partner=yes|
profid=753 447 481 00015|
desc=Consulting company dedicated to small and medium enterprises information system optimization, we provide to our customers open-source based solutions to improve their information system efficiency. We offer hosting and support solutions and we are Dolibarr contributor, developer and integrator. "Open-source. Custom. Freedom"|
web=http://www.atm-consulting.fr|
email=mailto:contact@atm-consulting.fr|
zip=26000|
town=Valence|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=
}}

{{TemplateCompany|
name=AB2L|
profid=|
desc=Un Alsacien à votre service. Installation et configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur notre serveur. Nous vous accompagnons pour un démarrage rapide et serein. Nous sommes une société de service en logiciel libre fournissant un équivalent open source au logiciel propriétaire de tout type. |
web=http://www.ab2l.eu|
email=mailto:contact@ab2l.eu|
zip=67000|
town=Strasbourg|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Axopen IT Services|
profid=|
desc=L'entreprise Axopen propose toute une gamme de produits et services informatiques allant du conseil en système d'informations, développement de solutions sur mesure et intégration de solutions Open Source ou propriétaires. Nous sommes spécialisé en particulier dans l'intégration de solutions de gestion de la relation client Open Source telles que Dolibarr, SugarCRM ou VTiger... |
web=http://www.axopen.com|
email=mailto:contact@axopen.com|
zip=69001|
town=Lyon|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=AKILIS|
profid=|
desc=AKILIS est une société éditrice de logiciels de gestion qui a fait le pari d’utiliser les nouvelles méthodes de travail pour développer des solutions clairs et efficaces. Notre mission est de vous proposer des solutions simples d'utilisation, ne demandant aucun entretien de votre part, ni aucune connaissance technique particulière. Notre outil est celui que VOUS utilisez quotidiennement : le Web.
AKILIS, c’est une équipe toujours disponible pour vous guider et vous écouter. Nous développons et améliorons sans cesse nos logiciels afin que ceux-ci répondent au mieux à votre activité et vos besoins.
AKILIS peut également, dans le cadre de besoin partculier, étudier avec vous un développement sur mesure. |
web=http://www.akilis.fr|
email=mailto:contact@akilis.fr|
zip=69200|
town=Vénissieux|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Altairis|
profid=|
partner=yes|
desc=Développements spécifiques, Installation, Formation, Accompagnement à la mise en oeuvre, Support, Intégration.|
web=http://www.altairis.fr|
email=contact@altairis.fr|
zip=38570|
town=Goncelin|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Auguria Conseil|
partner=yes|
profid=|
desc=You are a Small Business, a very small firm, you need tools to increase profitability, and reliability facing competition. Auguria aims to help you develop the tools of information vectors of progress.|
web=http://www.auguria.net/|
email=contact@auguria.net|
zip=44300|
town=Nantes|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Atoo.Net|
partner=yes|
profid=|
desc=Installation et configuration de l'ERP/CRM Dolibarr soit sur nos serveurs, soit en local dans votre entreprise. Aide à la prise en main et formation.|
web=http://www.atoo-net.com/|
email=contact@atoo-net.com|
zip=45160|
town=Olivet|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Blue-Click Informatique|
profid=|
desc=Nous proposons l'installation et la configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur votre hébergement Internet. De plus nous assurons la formation pour la prise en main de cet outil adapté aux TPE et PME.|
web=http://www.blue-click.fr|
email=|
zip=92,78|
town=Nanterre,Plaisir|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=CAP-REL|
profid=|
desc=Après avoir contribué au code de dolibarr dans les années 2004-2005 et l'avoir utilisé en interne pour de nombreux projets depuis cette époque je propose maintenant un service autour de Dolibarr (adaptation, accompagnement, utilisation etc.).|
web=https://www.cap-rel.fr|
email=eric.doli@cap-rel.fr|
zip=30|
town=Département du Gard|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_cap-rel.png‎|
}}

{{TemplateCompany|
name=Caribbean Consult CCC|
partner=yes|
profid=|
desc=Installation, configuration de l'ERP/CRM Dolibarr en ligne, ou en local pour votre entreprise ou association. Migration de données vers Dolibarr. Prise en main, support et formation.|
web=https://dolibarr.ccc.gp|
email=support@caribbeanconsult.com|
zip=97180|
town=Sainte Anne (Guadeloupe et Martinique) Antilles Guyane|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_CCC.png‎|
}}

{{TemplateCompany|
name=Cergy Internet|
profid=|
desc=Cergy Internet est spécialisé dans l’informatique et plus spécifiquement dans l’internet pour les PMI/PME. Nous maitrisons les technologies digitales du simple site web jusqu’au portail complète de pilotage d’entreprise. Grâce à Dolibarr nous pouvons vous donner une vision unique sur vos clients, vos produits et même votre trésorerie. Nous lions Dolibarr avec Wordpress et sur Smartphones pour créer des portails pour vos clients. Notre directeur, Thomas Carter, a fait son MBA à MIT aux USA et a géré des entreprises de plus de 100 personnes. Il met cette expérience à votre disposition. Chez Cergy Internet nous maitrisons la technologie de boute en boute. Nous avons notre propre équipe de jeunes codeurs qui baignent dans tous qui est réseaux sociaux, applications iPhone etc. ainsi qu’une plateforme de 30 serveurs pour héberger vos sites. |
web=www.cergy-internet.fr|
email=mailto:thomas.carter@cergy-internet.fr|
zip=95300|
town=Cergy-Pontoise|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Code 42|
partner=yes|
profid=793 600 735 00021|
desc=Nous vous accompagnons dans l’installation  et le développement de votre outil informatique. Code 42, c’est avant tout une démarche qualité et de conseil pour une relation durable. Vous avez la vision de votre entreprise, nous avons les moyens.|
web=www.code42.fr|
email=mailto:lareponse@code42.fr|
zip=44100|
town=NANTES|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=
}}

{{TemplateCompany|
name=D-BOG|
profid=|
desc=IT services company located in Beaune (21), moved around Dolibarr:
Installation, setup, configuration on the internal server or hosted;
Training agreement;
Outsourcing, on-site maintenance and remote.|
web=http://www.d-bog.com/|
email=|
zip=|
town=Beaune|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=DiVA-Cloud|
profid=|
desc=DiVA-Cloud propose des applications OpenSource de gestion de la communication et de l'information pour les entreprises. Notre logithèque contient des applications de WebConference, ERP, CRM, CMS, GED, et bien d'autres... Toutes ces applications pré-configurés sont mises à disposition sur un environnement privé. |
web=www.diva-cloud.com |
email=mailto:contact@diva-cloud.com |
zip=81100|
town=Castres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Elonet|
partner=yes|
profid=SIRET:52511620800022|
desc=Elonet a créé dolimail.fr , un outil qui permet de savoir quand, par qui, et quelles pages de vos fichiers PDF (devis, commande, facture) sont parcourus par vos prospects, clients ou fournisseur. Elonet est également intégrateur et développeur de solutions pour Dolibarr.|
web=https://elonet.fr|
email=mailto:contact@elonet.fr|
zip=59000|
town=LILLE|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Elonet.png
}}

{{TemplateCompany|
name=FUTUR TECH|
profid=|
desc=Prestataire de services pour artisans, TPE, PME :
Solutions open source, Internet, Sécurité, Sauvegarde, Antivirus, Gestion d'entreprise, Conseil, Formation, Installation et Paramétrage
Intervention sur site client. Situé entre Bordeaux et Libourne|
web=http://www.futur-tech.com|
email=mailto:info@futur-tech.com|
zip=33450|
town=IZON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Groupe KM|
profid=790 885 388 00013|
desc=Intégrateur,développeur et hébergeur de solutions Open Source: Progiciel ERP/CRM (Dolibarr),CMS(Joomla)et e-commerce(Prestashop). Nous déployons aussi des solutions Téléphonie (VOIP, PABX...) et Accés Internet (ADSL/VDSL, SDSL...). 
Secteur Cannes, Antibes, Sophia-Antipolis, Carros, Nice et plus généralement toutes les Alpes-Maritimes. 
Notre objectif : Vous satisfaire!|
web=https://www.groupe-km.com|
email=mailto:contact@groupe-km.com|
zip=06220|
town=Vallauris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=GWARED|
profid=804 659 027 00036|
desc=La société GWARED, est une équipe diplômée dans le domaine de l’informatique, de plus de 10 ans d’expériences dans diverses structures telles que de grandes administrations, sociétés privées mais aussi au service des particuliers. Nous sommes à l’écoute pour vous accompagner dans vos projets.

Professionnel ou particulier, nous vous proposons de nombreux services informatiques et domotiques adaptés à votre configuration et vos besoins. Nos prestations concernent la réparation et la maintenance de votre ordinateur ou de votre parc informatique, l'installation réseau (Local informatique, Internet, intranet, Wifi, CPL, etc.), l'installation d’alarmes et vidéo-surveillance, sur site, à distance ou à domicile.

Notre société se distingue en trois branches :

- L’informatique (GWARED)
- La sécurité (alarme, vidéosurveillance et protection numérique) (GWARDSECURITY)
- Les jeux vidéo (concepteur de console de jeux) (GWARDBOX)

Nous pourrons répondre à tous vos besoins dans le domaine de l’informatique.|
web=http://www.gwared.fr|
email=[mailto:support@gwared.fr?subject=Contact%20de%20Dolibarr%20Suppliers%20France support@gwared.fr]|
zip=77500|
town=Chelles et Île de France|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
logo=Logo_Gwared.png|
}}

{{TemplateCompany|
name=HELIUM TECHNOLOGIES|
profid=494 895 360 00027|
partner=yes|
desc=
Mise en place de solutions ERP Dolibarr sur nos serveurs ou dans votre entreprise avec assistance téléphonique, support technique, développement de modules spécifiques et formation.
 '''SSII basée en Guadeloupe, Martinique et Guyane''', nous proposons également des solutions libres comme GLPI, Prestashop, Joomla, Odoo, Zimbra, BlueMind, Centreon, ...|
web=http://|
email=[mailto:contact@helium-technologies.com?subject=Contact%20from%20Dolibarr%20Suppliers%20France20page contact@helium-technologies.com]|
zip=97122|
town=BAIE-MAHAULT (GUADELOUPE)|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_HeliumTechnologies.jpg
}}

{{TemplateCompany|
name=Infonel.net|
profid=|
desc=administrateur système open source indépendant:
Installation, paramétrage, configuration et sécurisation de dolibarr sur site client|
web=http://www.infonel.net|
email=|
zip=11100|
town=Narbonne|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=iNodbox|
partner=yes|
profid=|
desc=Développeur indépendant d'application web, paramétrage et installation de Dolibarr, développement de modules spécifique. Basé dans l'Ain à Bourg en Bresse (30min de Mâcon, 1h de Chalon sur Saône, 1h de Lyon), je contribue depuis de nombreuses années au développement de Dolibarr.|
web=https://www.inodbox.com/|
email=regis.houssin@inodbox.com|
zip=01000|
town=Bourg en Bresse|
country=fr|
service_hosting=(https://www.inodbox.com)|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Inovea Conseil|
partner=yes|
profid=797 613 072 00017|
desc=Développeur, Intégrateur, Hébergeur et Formateur de Dolibarr pour TPE - PME |
web=https://www.inovea-conseil.com/ |
email=https://www.inovea-conseil.com/contact/ |
zip=88,54,75|
town=Nancy|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Inoveaconseil.png
}}

{{TemplateCompany|
name=i.d & l|
profid=521 749 994 00013|
desc=Conseil et intégration de solutions logicielles libres, dont Dolibarr, pour artisans, TPE, indépendants, commerçants, PME, associations...|
web=http://idl-mp.com|
email=http://idl-mp.com/contact/|
zip=31,32,09,82,81|
town=Toulouse et région toulousaine|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=iouston informatique|
profid=792 353 005 00046|
desc=iouston informatique, situé à proximité de Nancy, Metz, Lunéville, est spécialisée auprès des associations, des TPE et des artisans commerçants. Nous installons et configurons dolibarr pour vous et nous formons vos équipes à son utilisation quotidienne. Nous proposons de nombreux autres services, associés ou non à dolibarr. Nous travaillons avec dolibarr depuis plus de 6 ans et éditons des modules supplémentaires pour dolibarr, [https://www.dolistore.com/fr/recherche?controller=search&orderby=position&orderway=desc&search_query=iouston&submit_search= disponibles sur dolistore]|
web=https://www.iouston.com|
email=allo@iouston.com|
zip=54370|
town=Einville au Jard|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ISYNUX|
profid=|
desc=Société de services en réseaux et sytèmes. ISYNUX vous propose un suivi complet pour DOLIBARR : installation, hébergement, personnalisation de vos modèles de document, formation à la carte. |
web=http://www.isynux.fr|
email=mailto:formation@isynux.fr|
zip=626100|
town=Ardres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Jeffinfo (ZenDSI)|
profid=429 625 973|
partner=yes|
desc=Jeffinfo est une société de services en informatique qui vous sert depuis plus de 15 ans dont 10 ans dans le domaine de Dolibarr. Implanté dans le nord à Ennetières en Weppes. Nous sommes à vos services pour vous proposer tous les services autour de votre ERP préféré.
web=https://shop.zendsi.com|
email=mailto:contact@zendsi.com|
zip=59320|
town=Ennetières en Weppes|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no
}}

{{TemplateCompany|
name=Kreiz IT|
partner=yes|
profid= 752 505 131 00017|
desc={{Flag_fr}}Conseils en organisation et sécurité informatique pour les TPE / PME. Dolibarr fait partie des outils informatiques structurants pour les TPE/PME proposé par Kreiz IT.

{{Flag_en}}IT management and security consultant for small to medium business. Dolibarr is part of IT's structuring tools for business used by Kreiz IT. |
web=http://www.kreiz-it.fr |
email=mailto:contact@kreiz-it.fr |
zip=56600|
town=Lanester|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=LogoKIT.jpg
}}

{{TemplateCompany|
name=LIBRE EXPERT|
partner=no|
profid=48879200300045|
desc={{Flag_fr}}Intégrateur et développeur Dolibarr, auteur de plusieurs modules complémentaires, spécialiste également de l'administration Linux.

{{Flag_en}}
Integrator and Dolibarr developer, author of several complementary modules, also specialist in Linux administration. |
web=http://www.libre-expert.com|
email=mailto:contact@libre-expert.com |
zip=63100|
town=Clermont-Ferrand|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Librethic|
partner=yes|
profid=83334801400014|
desc={{Flag_fr}}Librethic est une Société de Services en Informatique et Technologies Libres, tournée vers les entreprises et les associations. Créée en 2017, elle est portée par des professionnels aguerris aux technologies libres et open source.
L'environnement Dolibarr fait partie du cœur de compétences de Librethic (développement de modules complémentaires, hébergement SaaS, hébergement sur site, passerelle e-commerce).
{{Flag_en}}
Librethic is an IT Provider aiming at businesses and organizations, offering services in free/libre and open source software (FLOSS) and open design technologies.
Founded in 2017, Librethic is driven by libre and open source technologies seasoned professionals. Dolibarr's environment is one of Librethic's core skills (Addons and plugins development, SaaS hosting, on-premise hosting, e-commerce gateway).
web=https:/librethic.io/|
email=mailto:hello+dolibarr@librethic.io|
zip=34070|
town=Montpellier|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=logo-librethic.png
}}

{{TemplateCompany|
name=LVS Informatique|
profid=|
desc=Development Specialist php, mysql. Creation, enhancement, customization of modules and components ...
Nos modifs/nos modules :
-cashdesk : prix en ttc, possibilité de modification du prix, du libellé...
-interfaçage avec GoogleAgenda (toutes les actions apparaissent dans GoogleAgenda)
-Mails/Télécopies reçus : apparaissent dans un onglet spécifique sur le tiers en question
-qualification Tiers
-Adresse Tiers vu dans GoogleMap
-creation de nbreux template excel/pdf
|
web=http://www.lvsinformatique.com|
email=|
zip=83860|
town=NANS LES PINS|
country=fr|
service_dev=yes|
service_local=yes|
}}

{{TemplateCompany|
name=MEDIALTA|
profid=|
desc=Installation, configuration de Dolibarr sur nos serveurs, ou dans l'entreprise (Nancy, Metz, Lorraine, Grand Est). Formation, prise en main. Développement de modules sur mesure.|
web=www.medialta.com|
email=|
zip=54340|
town=Pompey|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Mephivio|
profid=|
desc=Services company with a computer located in Montpellier agglo, specializing in computer graphics, secretariat, Joomla web sites, client, opensource (Dolibarr, glpi, voip Elastix / Trixbox / PIAF etc ...)|
web=http://www.mephivio.fr/|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=MEZIANT|
profid=|
desc=MEZIANT propose aux PME, TPE, artisans, commerçants et associations de l'Ouest son expertise en informatique issue d'une expérience de plus de 15 ans en Audit de Système d'Informations, Site internet, Formation et Choix de logiciel de gestion (ERP) comme '''DOLIBARR''' dont elle peut assurer l’installation, la formation ou encore le développement de modules spécifiques sur site client.
web=http://www.meziant.fr |
email=mailto:contact@meziant.fr |
zip=22940|
town=PLAINTEL (Bretagne - France)|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Modulaweb : Technologies modulables orientées web.|
profid=|
desc=Développement d'applicatifs web, hébergement d'applications web, serveurs de fichiers et de sauvegarde, sites internet/intranet et intégration web, espaces clients, communication via internet (VoIP, messagerie instantanée), travail collaboratif. Spécialiste solutions libres pour l'entreprise (Zimbra, Dolibarr, Thaïs...) Région Languedoc-Rouissillon et voisines |
web=http://www.modulaweb.fr|
email=http://www.modulaweb.fr/portail/contact/|
zip=34000|
town=Montpellier|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Net Logic|
partner=yes|
profid=SIRET: 477 583 264 00023|
desc=Installation et configuration de l'ERP/CRM Dolibarr sur nos serveurs, ou en local dans votre entreprise. Paramétrage, personnalisation, reporting spécifique, assistance.|
web=http://www.netlogic.fr/|
email=info@netlogic.fr|
zip=93160|
town=Noisy-le-Grand|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=NLTechno|
partner=yes|
desc=NLTechno is one of the most important contributor on Dolibarr and can host for you a Dolibarr database in a SaaS (Software As A Service) mode.|
profid=493 861 496 00021|
web=http://www.nltechno.com|
email=|
zip=92500|
town=Boulogne Billancourt|
country=fr|
service_hosting=yes (https://www.dolicloud.com)|
service_onlinesupport=yes|
service_emailsupport=only for DoliCloud.com customers|
service_dev=no|
service_local=no|
service_formation=no|
logo=logo_nltechno.png}}

{{TemplateCompany|
name=NORD ERP CRM|
partner=no|
profid=83184221600010 (SIRET)|
desc=Intégration, assistance, formation et hébergement de solutions Dolibarr. Nous intervenons auprès des artisans, indépendants, TPE et associations dans le Nord Pas-de-Calais. Développement possible selon les spécificités métier. NORD ERP CRM accompagne également les commerçants pour leur système d'encaissement.|
web=https://www.nord-erp-crm.fr/|
email=mailto:contact@nord-erp-crm.fr|
zip=59100|
town=Roubaix|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=logonewcouleur.jpg|
}}

{{TemplateCompany|
name=OAS-SERVICES|
profid=829767904|
partner=no|
desc=
OAS-SERVICES est une société de service spécialisés dans la mise en place de logiciels libres sous forme de services cloud, notamment de Ma Gestion Cloud (Dolibarr, viger), la mise en place de site internet et boutique en lignes, le développement d'application et de modules en PHP (Dolibarr, Wordpress, Prestashop), mais aussi en Java (JEE, Webservices, JPA), la mise en place de systèmes d'exploitation (linux), la gestion de projet en agilité - Montpellier, Sète|
web=https://www.ma-gestion-cloud.fr|
email=[mailto:contact@oas-services.fr?subject=Contact%20from%20Dolibarr%20Suppliers%20France20page contact@oas-services.fr]|
zip=34200|
town=SETE|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
logo=logo-oas-services.png
}}

{{TemplateCompany|
name=OPEN-DSI|
partner=yes|
profid=SIRET:75130522800015|
desc=Depuis 2012, nous accompagnons les petites et moyennes structures (1 à 50 salariés) dans la mise en place de solutions basées sur les logiciels libres. Nous proposons Dolibarr pour tous les besoins de gestion.|
web=https://www.open-dsi.fr|
email=mailto:infos@open-dsi.fr|
zip=69,38,01,42|
town=LYON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=opendsi.png
}}

{{TemplateCompany|
name=OIS - Open IT Store|
profid=822 430 419 00017|
desc=OIS (Open IT Store), We provide opensource instances located in Europe or North America.|
web=https://openitstore.com/dolibarr|
email=mailto:contact@openitstore.com|
zip=|
town=|
country=|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=no|
service_formation=yes|
logo=|
}}

{{TemplateCompany|
name=Oscss Shop|
partner=yes|
profid=SIRET:810 421 339 00013|
desc=Développement de modules sur mesure, interconnexions et hébergements.|
web=http://oscss-shop.fr|
email=mailto:support@oscss-shop.fr|
zip=28,45,41,72,61,27,75,69,38,01,73,74|
town=LA LOUPE|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Pascal Sené|
profid=|
desc=Logiciels libres et photographie.|
web=http://www.pascalsene.com|
email=contact@pascalsene.com|
zip=22,29,35,56|
town=Lannion|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Patas-Monkey|
profid=|
desc=Conseil, formation, développement et modules|
web=http://www.patas-monkey.com|
email=r.deschamps@patas-monkey.com|
zip=69,42,38,01,83|
town=Lyon|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Patasmonkey.jpg
}}

{{TemplateCompany|
name=ProbeSys|
profid=|
desc=Créée en 2003 par des passionnés du logiciel libre, [http://probesys.com ProbeSys] est une entreprise coopérative à l'image du secteur des nouvelles technologies : dynamique, réactive et participative. |
web=http://www.probesys.com|
email=mailto:contact@probesys.com|
zip=38600|
town=Fontaine|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Pro IP|
profid=|
desc=Mise en place de solutions ERP comme Dolibarr sur nos serveurs ou dans votre entreprise, assistance et formation|
web=http://wwww.proip.fr|
email=mailto:contact@proip.fr|
zip=62129|
town=Clarques|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=PTMSoft SARL|
profid=520 618 646 00019|
desc=Société de services et de développement logiciel. Installation Dolibarr sur nos serveurs ou dans votre entreprise, assistance et configuration.|
web=http://www.ptmsoft.fr|
email=[mailto:contact@ptmsoft.fr?subject=Contact%20de%20la%20page%20Dolibarr%20Suppliers%20France contact@ptmsoft.fr]|
zip=68890|
town=Mulhouse, Colmar|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
logo=Logo PTMSoft.png
}}

{{TemplateCompany|
name=Syllene|
profid=|
desc=We install and configure the software Dolibarr to suit your needs and train your users. We can also provide hosting and maintenance of your application.|
web=http://www.syllene.net/|
email=|
zip=|
town=|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Teclib'|
profid=513893503|
partner=yes|
desc=
Teclib est une société de services en informatique au capital de 400 000€. Implantés à Paris, Colmar (Alsace), Caen, Chartres (Région Centre) et Bordeaux (Aquitaine). L'équipe Teclib' rassemble une quarantaine de personnes spécialisées dans l'intégration, hébergement et développements de logiciels libres tels que Dolibarr, Odoo, GLPI, Zimbra, BlueMind, Nagios, Centreon, ... |
web=http://www.teclib.com|
email=[mailto:contact@teclib.com?subject=Contact%20from%20Dolibarr%20Preferred%20Partners%20page contact@teclib.com]|
zip=75001|
town=Paris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_Teclib.png
}}

{{TemplateCompany|
name=Tiaris|
partner=yes|
profid=|
desc=Solutions and services for small businesses and merchants: e-commerce, maintenance, ERP/CRM Dolibarr, development telecommuting. ecommerce - dolibarr webservice based interface. Saas Offer Dolibarr + ecommerce connection for open source caddies (OsCommerce, Zencart, Crelaoded, Prestashop and others...)|
web=http://www.tiaris.fr/|
email=http://www.tiaris.fr/spip.php?page=contact|
zip=57870|
town=WALSCHEID|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=UTOPSYS - L'Informatique, Professionnelle.|
profid=|
desc=Maintenance, dépannage, conseil, audits, Green IT, solutions open-source de travail collaboratif, installation et maintenance Dolibarr. Bordeaux, CUB, Libourne.|
web=http://www.utopsys.fr|
email=|
zip=|
town=Libourne|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=YON - Your Own Net|
profid=822 430 419 00017|
desc=YON (Your Own Net), Fournisseur de solution numérique, Nous sommes spécialisés dans la fourniture de solutions informatiques pour les professionnelles et les particuliers. Nos solutions vont de l’intégration d’outils Open Source et de logiciels libres à l'hébergement de logiciels.|
web=http://yourownnet.net/|
email=mailto:contact@yourownnet.net|
zip=79|
town=Niort et Grand Ouest|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
logo=|
}}

{{TemplateCompany|
name=WEBINFOPRO|
profid=|
desc=Society Computers and Internet service for small businesses located in the suburbs west of Paris. One of the main activities is the integration of open source software.|
web=http://www.webinfopro.fr/|
email=|
zip=|
town=|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Z-Application|
profid=|
desc=Développement personnalisé et assistance à la installation-migration. Support sur site possible dans le département Manche (50).|
web=https://www.z-application.com/|
email=|
zip=50250|
town=Coutances - Cherbourg - Saint-Lô|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

Setup Other

2019-07-17T08:38:02Z

Iouston: add hidden options of v10.0

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

'''Help About Screen:''' Other setup

'''Menu Path:''' Home ► Setup ► Other

= '''Goal''' =
This page contains the list of advanced hidden parameters. In most cases, it is parameters for development, external modules, or hidden features which can allow some tweaking to your own Dolibarr instance.

For standard usage of Dolibarr, this parameters must not be used.

= '''Reading the List''' =
After Global Options, this list is sorted alphabetically. The basic format of how the list is written is broken down in the example below:

'''HIDDEN_CONFIG''' ► ''Description of config'' ► ''(specific version information) or values''

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

To enable/override a parameter you have to define the constant name and set it to '''1''' (unless otherwise stated) in <code>Home ► Setup -> Other Setup</code>

== '''Global Options''' ==

* '''MAIN_DISABLE_NOTES_TAB''' ►Show or hide notes tab in the card page

* '''MAIN_DISABLE_CONTACTS_TAB''' ► Show or hide contacts tab in the card page

* '''MAIN_LOGOUT_GOTO_URL''' ► URL to which the user will be redirected after LOGOUT

* '''MAIN_FILESYSTEM_ENCODING''' ► With some PHP versions, PHP is not able to detect the page code for filesystem of the server OS. To solve this, Dolibarr assumes 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 <code>MAIN_FILESYSTEM_ENCODING</code> to "<code>utf-8</code>".

* '''MAIN_SHOW_TECHNICAL_ID''' ► Show also technical IDs on elements cards or some lists (not supported everywhere).

* '''MAIN_MAXTABS_IN_CARD''' ► Maximum number of tabs visible. Others are grouped into a combo list.

* '''MAIN_ONLY_LOGIN_ALLOWED''' ► Only the specified login is allowed to log in Dolibarr (maintenance mode).

* '''MAIN_AUTO_TIMESTAMP_IN_PUBLIC_NOTES''' ► Add a timestamp and user automatically when editing the ''public'' note.

* '''MAIN_AUTO_TIMESTAMP_IN_PRIVATE_NOTES''' ► Add a timestamp and user automatically when editing the ''private'' note.

* '''MAIN_SECURITY_CSRF_WITH_TOKEN''' ► 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 powerful. ► (v5.0+)

* '''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 fail by smartphone applications like [[Application Android - DoliDroid]]

* '''MAIN_AUTOFILL_DATE''' ► If this constant is defined (to something other than 0), the date of invoice, proposal, order or payment are auto-filled with the current date. It is highly recommended to NOT ENABLE this feature. This can create a lot of input errors with data not validated by users. This leads to incorrect values saved in the database causing confusion when you have to do your accountancy reports! However some users want it, so we provide it.

* '''MAIN_DISABLE_FULL_SCANLIST''' ► Disables the complete scan of tables to allow the pagination to show total number of pages. May be useful to activate on systems with a very high quantity of data (tables with more than 500 000 records).

* '''MAIN_FIRST_TO_UPPER''' ► Dolibarr add uppercase to Third Parties, 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''' ► If this constant 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 warnings that appear to administrator users if URL <code>/install</code> is public. You should solve the problem if warning occurs, instead of removing the warning! For this, create a file called <code>install.lock</code> into Dolibarr root directory. This will stop the warning but also make the page <code>/install</code> 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 <code>xx_XX</code> is language code. If value is <code>string1:newstring1;string2:newstring2</code> then replace <code>string1</code> with <code>newstring1</code> in all translation done for language <code>xx_XX</code>.

* '''MAIN_REPEATCONTACTONEACHTAB''' ► If added and set to '''1''', this adds contacts on all tabs, not only main tab.

* '''MAIN_DISABLE_JQUERY_JNOTIFY''' ► Disable usage of <code>JNotify</code> to show confirm or error messages

* '''MAIN_USE_JQUERY_JEDITABLE''' ► Allow to update from screen, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this feature, because it bypasses some business actions (updates on other data that should be done consistently) and ignores business controls on data you saved. Consequently this feature breaks consistency of data and possibly the stability of the 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 the target page for link "I need help" onto logon page

* '''MAIN_MODULES_FOR_EXTERNAL''' ► Limit available modules for external users. By default value is '<code>facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda</code>'

* '''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. <code>/var/www/dolibarr</code>)

* '''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► A warning saying setup of modules is not complete is shown if the 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 the first sale representative into documents (at end of public notes).

* '''MAIN_DISABLE_AJAX_COMBOX''' ► If you have a large number of third parties or products, you can disable the autocomplete feature on the third parties list by setting this constant to '''1''' ► (v3.6.0+)

* '''MAIN_USE_CACHE_MANIFEST''' ► Add an HTML5 cache manifest to the page - Attention, this functionality is obsolete and removed from web standards

* '''MAIN_FORCELANGDIR''' ► Relative path of the directory holding your custom <code>langs</code> folder.

* '''MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS''' ► Allow to define a default VAT rate

* '''MAIN_HTML_TITLE''' ► Can be used to control how the html page title is formatted. If value contains key '<code>noapp</code>', application name will not be output. If value contains '<code>thirdpartynameonly</code>', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: '<code>noapp;thirdpartynameonly</code>'

* '''MAIN_LANDING_PAGE''' ► Can choose the first page to show after login (the landing page). This option works as a global option (llx_const) and per user option (llx_user_param). ► (v3.9+)

* '''MAIN_PROPAGATE_CONTACTS_FROM_ORIGIN''' ► When creating an order, contract, invoice from another object, specific contacts of objects are set as specific contact of the new object when possible. ► (v4.0+)

* '''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''' ► Show public note in address block ► (v4.0+)

* '''MAIN_DEFAULT_PAYMENT_TERM_ID''' ► With ID of a payment term, will use this as default payment term each time you create a new proposal, order, invoice (customer and supplier)

* '''MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND''' ► Change way of rounding total TTC lines, rounding first of after.

* '''MAIN_VIEW_LINE_NUMBER''' ► Shows a line number against each line in the order/invoice for products/services. On screen only, not on PDF.

* '''MAIN_DOC_USE_OBJECT_THIRDPARTY_NAME''' ► Add name of thirdparty at begin of generated document.

* '''MAIN_DOC_USE_TIMING''' ► Add a timestamp at end of generated document. Value must be format of timestamp. For example: <code>%Y%m%d%H%M</code> (only for ODT files)

* '''MAIN_DISABLEDRAFTSTATUS''' ► Disable the status Draft for some objects (project, donation, ...)

* '''MAIN_USE_OLD_SEARCH_FORM''' ► Display the old search form in left menu.

* '''MAIN_SERVER_TZ''' ► If you can't set the timezone of your PHP installation, set this constant. Better is to set it to UTC. In future, this constant will be forced to 'UTC' so PHP server timezone will not have effect anymore. Examples: <code>Europe/Paris</code>, <code>auto</code>.

* '''MAIN_SEARCH_FORM_ON_HOME_AREAS''' ► Show the search form on home page areas for core modules (Removed after v5 due to global search combo) ► (v6.0+)

* '''MAIN_SEARCH_DIRECT_OPEN_IF_ONLY_ONE''' ► If only one result is found, then setting this value to '''1''' will take you direct to the item (default method). Setting the value to '''0''' will show the result in the list as a single result ► (v5.0+)

* '''MAIN_ENABLE_IMPORT_LINKED_OBJECT_LINES''' ► Allow to import lines into current document from "linked" compatible documents ► (v8.0+)

* '''MAIN_USE_VAT_OF_PRODUCT_FOR_INDIVIDUAL_CUSTOMER_OUT_OF_EEC''' ► Allow using product VAT if customer is individual and out of E.E.C. (European Economic Community) ► (v7.0+)

* '''MAIN_SHOWDATABASENAMEINHELPPAGESLINK''' ► Show database name in upper help menu ► (v8.0+)

* '''MAIN_DISABLE_MULTIPLE_FILEUPLOAD''' ► Disable users to upload multiple files at once.

* '''USER_HIDE_INACTIVE_IN_COMBOBOX''' ► Disable display inactive users in combobox.

* '''MAIN_SERVICES_ARE_ECOMMERCE_200238EC''' ► (< 8)

* '''MAIN_DOC_UPLOAD_NOT_RENAME_BY_DEFAULT''' ► Disable the auto renaming on upload file ► (v10.0)

* '''MAIN_DEFAULT_LANGUAGE_FILTER''' ► Useful if you do not want to show en_US language option in combo boxes (other languages can easily be removed in langs directory but not en_US) ► (v10.0)

* '''NO_CONCAT_DESCRIPTION''' ► Allow to use only input custom description in lines (propale, order, invoice) ► (v10.0)

* '''ADD_UNSPLASH_LOGIN_BACKGROUND''' ► The background image will be refreshed on every login page refresh. Background image is pulled from the popular open source image website Unsplash. If an already saved static background image exists, then this code will override it (but not delete the saved image). ► (v10.0)

[[#Top|(back to top)]]

== '''Accoutancy Module''' ==

* '''ACCOUNTANCY_COMBO_FOR_AUX''' ► Add graphic option for ACCOUNTANCY_COMBO_FOR_AUX ► (v10.0)

[[#Top|(back to top)]]

== '''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)
[[#Top|(back to top)]]

== '''Bank Module''' ==
* '''BANK_CAN_RECONCILIATE_CASHACCOUNT''' ► Can reconciliate cash accounts ► (v3.8)

* '''BANK_DISABLE_CHECK_DEPOSIT''' ► Disable check deposit feature

* '''BANK_ASK_PAYMENT_BANK_DURING_ORDER''' ► Ask bank account during creation of an order

* '''BANK_ASK_PAYMENT_BANK_DURING_PROPOSAL''' ► Ask bank account during creation of a proposal
[[#Top|(back to top)]]

== '''BlockedLog''' ==
* '''BLOCKEDLOG_DISABLE_NOT_ALLOWED_FOR_COUNTRY''' ► Make disable of module "blockedlog" not possible for countries code defined into value. Example: 'FR,...'
[[#Top|(back to top)]]

== '''Contracts''' ==
* '''CONTRACT_SUPPORT_PRODUCTS''' ► Products are also suggested into module contract.
[[#Top|(back to top)]]

== '''Email and SMS''' ==
* '''MAIN_MAILFORM_DISABLE_ENTERKEY''' ► Activate javascript code to disable the enter key in the MAIL form. ► (>= 8.0.1)

* '''MAIL_PREFIX_FOR_EMAIL_ID''' ► Prefix for the mails ID. Default value is <code>$_SERVER["SERVER_NAME"]</code> ► (>= 8.0.1)

* '''MAIN_MAIL_DEBUG''' ► Write content with header of last mail into file <code>dolibarr_mail.log</code> into directory <code>dolibarr_main_data_root</code>.

* '''MAIN_SMS_DEBUG''' ► Write content of SMS sent into file <code>dolibarr_sms.log</code> into directory <code>dolibarr_main_data_root</code>.

* '''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 <code>-f</code>. This option is here to ask Dolibarr to call the function '''mail''' of PHP by adding value for the option <code>-f</code>. 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 Linux 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 asks PHP to provide this parameter when sending a mail. Note that another solution is to edit the '''mail.force_extra_parameters=-ba''' into '''<code>php.ini</code>''' 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 <code>orange.fr</code> or <code>hotmail.com</code>

* '''MAIN_MAIL_DO_NOT_USE_SIGN''' ► Do not add user signature at end of suggested pre-defined email

* '''MAIL_FORCE_DELIVERY_RECEIPT_INVOICE''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Invoice'' module.

* '''MAIL_FORCE_DELIVERY_RECEIPT_ORDER''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Order'' module.

* '''MAIL_FORCE_DELIVERY_RECEIPT_PROPAL''' ► Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Proposal'' module.

* '''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 recipient 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 third party 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 third party or object, the email exchange is related to.

* '''MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL''' ► Restrict sending of 1 email message to <code>x</code> recipients for same email message (x for To: + CC: + BCC:). If not defined, value is <code>10</code>. Required to fight against spamming that include 1000 recipients in 1 message. Note that '''MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL''', '''MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL''' and '''MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL''' are also available.

* '''MAIN_MAIL_FORCE_CONTENT_TYPE_TO_HTML''' ► Force to send all email (event with text only content) as HTML formatted email.

* '''MAIN_MAIL_USE_MULTI_PART''' ► Forge email content using an alternate text part ► (for 5.0.2+). By default with 6.0+

* '''MAIN_MAIL_ADD_INLINE_IMAGES_IF_IN_MEDIAS''' ► If images were stored into the medias directory from CKEditor, then images into emails are replaced with "inline content". This may increase seriously risk of being detected as SPAM.

* '''MAIN_COPY_FILE_IN_EVENT_AUTO''' ► Add attachement document on event auto generated by sending email from dolibarr. ► (v6.0+)

* '''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► Enter the public IP address of the server, so it appears in the help on the email setup page.

* '''MAIN_MAIL_ENABLED_USER_DEST_SELECT''' ► Show also internal users into list of recipients of email in email sending form ► (v8.0+)
[[#Top|(back to top)]]

== '''Emailing Module''' ==
* '''MAILING_PREFIX_FOR_EMAIL_ID''' ► Set the value that will be used to compose the "Email ID" into email headers. If you set this value to '<code>SERVER_NAME</code>', the virtual host of web server will be used. By default, this is not defined, so a hash key, unique to each instance, is used.

* '''MAILING_NO_USING_PHPMAIL''' ► If set, the module emailing can't be used with mail setup of "phpmail". Using a thirdparty SMTP server is required. You can complete warning message by adding an email to contact for setup help with constant '''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS'''.

* '''MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS''' ► Contains the email of contact to show into the message visible to a user when he try to use emailing module without SMTP server and if option '''MAILING_NO_USING_PHPMAIL''' is set to on.

* '''MAILING_LIMIT_WARNING_PHPMAIL''' ► Show a warning message (var contains the message to show or translation key) on emailing send form if setup is on "phpmail". For example, you can set this parameter to <code>(MAILING_LIMIT_WARNING_PHPMAIL)</code> and enter translation key for each language for this key.

* '''MAILING_LIMIT_WARNING_NOPHPMAIL''' ► Show a warning message (var contains the message to show or translation key) on emailing send form if setup is something else than "phpmail". For example, you can set this parameter to <code>(MAILING_LIMIT_WARNING_NOPHPMAIL)</code> and enter translation key for each language for this key.

* '''EMAILING_USE_ADVANCED_SELECTOR''' ► Enable the advanced selector for recipients.

* '''MAILING_LIMIT_SENDBYWEB''' ► Restrict number of emails you can send in same sending session with emailing module from GUI. The value "<code>dolibarr_mailing_limit_sendbyweb</code>" if defined into config file is used in priority for this limit. A negative value means, sending by web is forbidden.

* '''MAILING_LIMIT_SENDBYCLI''' ► Restrict number of emails you can send in same sending session with emailing module from CLI script. The value "<code>dolibarr_mailing_limit_sendbycli</code>" if defined into config file is used in priority for this limit.
[[#Top|(back to top)]]

== '''Expense Report''' ==
* '''EXPENSEREPORT_ALLOW_OVERLAPPING_PERIODS''' ► Can enter several expense reports on same or overlapping date periods. ► (v7.0+)

* '''EXPENSEREPORT_USE_OLD_NUMBERING_RULE''' ► The module Expense Report use numbering rules that you can setup (like other modules do). If you need to keep the hard-coded numbering rule of expenses report used in v6.0 set this constant to '''1''' ► (>=v7.0+)

* '''MAIN_USE_EXPENSE_IK''' ► This feature allows you to set index kilometers against a mileage index for different types of vehicles. ► (v7.0+)

* '''MAIN_USE_EXPENSE_RULE''' ► This feature allows you to set a variety of rules per user/group/all so they can only create reports within their limits. ► (v7.0+)

* '''OVERRIDE_VAT_FOR_EXPENSE_REPORT''' ► Setting constant OVERRIDE_VAT_FOR_EXPENSE_REPORT to 1 will allow expense reports to show VAT even if the global VAT setting is off ► (v10.0)

[[#Top|(back to top)]]

== '''Export Module''' ==
* '''EXPORT_CSV_SEPARATOR_TO_USE''' ► String value to use as default separator to delimit fields of exported files (by default Dolibarr uses "<code>,</code>"). Example: EXPORT_CSV_SEPARATOR_TO_USE=<code>;</code>

* '''EXPORT_CSV_FORCE_CHARSET''' ► Choose the charset used in the output file built by the CSV exporter. By default it is ISO-8859-1. Example: EXPORT_CSV_FORCE_CHARSET= <code>utf-8</code>

* '''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 (<code>"</code>).
[[#Top|(back to top)]]

== '''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 added in front of payment cell, into the page to make online subscription.
[[#Top|(back to top)]]

== '''Interventions Module''' ==
* '''FICHINTER_CLASSIFY_BILLED'''► Allow to classify an intervention card as "Billed". This add also trigger <code>FICHINTER_CLASSIFY_BILLED</code> into list of possible automatic event into agenda.

* '''FICHINTER_DISABLE_DETAILS'''► Disable entry of details line on intervention. Can validate with no line.
[[#Top|(back to top)]]

== '''Invoice Module''' ==
* '''MAIN_DEPOSIT_MULTI_TVA''' ► In deposits invoice, creates one line per VAT rate from the origin document ► (6.0)

* '''FACTURE_SHOW_SEND_REMINDER''' ► Show link "Send reminder by mail", same feature than "Send by mail" ''(obsolete feature)''.

* '''INVOICE_CAN_ALWAYS_BE_EDITED''' ► Allow to edit invoices even if payment was started. Note: If the module "'''BlockedLog'''" is active (required in some countries for legal reasons), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

* '''INVOICE_CAN_ALWAYS_BE_REMOVED''' ► Allow to always delete invoices (even if invoice is not last one). Note: If the module "'''BlockedLog'''" is active (required by some countries for legal reason), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the read-only archive log.

* '''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. WARNING: In a lot of european countries, using this option is not allowed.

* '''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 generated documents. like for an association. (Works with crabe template)

* '''INVOICE_CREDIT_NOTE_STANDALONE''' ► Can make a credit note without invoice. ► (v3.9)

* '''INVOICE_USE_SITUATION''' ► Enable the "situation invoice" feature

* '''INVOICE_USE_SITUATION_CREDIT_NOTE''' ► Enable the "situation credit note" feature (need <code>INVOICE_USE_SITUATION</code>) ► (v8.0)

* '''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

* '''INVOICE_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. Use the tag __DIRECTDOWNLOAD_URL_INVOICE__ in email template to insert it. ► (v7.0+)

* '''INVOICE_POINTOFTAX_DATE''' ► Add Point of Tax Date on invoices for country-specific legality reasons ► (v4.0+)

* '''FACTURE_ENABLE_NEGATIVE_LINES''' ► Allows to add negative lines to an invoice ► (v8.0.2+)

* '''INVOICE_USE_DEFAULT_DOCUMENT''' ► Allow user to select a default invoice documents models according to invoice type. On invoice create page, the model is dynamically changed on invoice type selection. ► (v9.0+)

* '''FACTURE_REUSE_NOTES_ON_CREATE_FROM''' ► Reuse the Public Note and Private note of the previous object (Proposal,...) when creating the bill.
[[#Top|(back to top)]]

== '''Look or Theme''' ==
* '''MAIN_OPTIMIZEFORTEXTBROWSER''' ► Optimize output rendering for usage of a text browser (useful for blind people)

* '''THEME_ELDY_DISABLE_IMAGE''' ► Disabled images of top menu for eldy theme. ► (v3.8+)

* '''MAIN_MENU_HIDE_UNAUTHORIZED''' ► Hide menu if logged in user is not authorized rather than just grey them

* '''THEME_TOPMENU_STICKY_POSITION''' ► Option to fix top menu with eldy theme ► (v7.0+)

* '''MAIN_EASTER_EGG_COMMITSTRIP''' ► Show a comic image from the CommitStrip website. Images are refreshed daily. ► (v6.0+)

* '''MAIN_STATUS_USES_CSS''' ► (v10.0+) Change status design using new style

* '''MAIN_USE_NEW_TITLE_BUTTON''' ► (v10.0+) Use new list buttons design

[[#Top|(back to top)]]

== '''MultiCurrency''' ==
* '''MAIN_MULTICURRENCY_ALLOW_SYNCHRONIZATION''' ► Enable CurrencyLayer API synchronization
[[#Top|(back to top)]]

== '''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".

* '''COMMANDE_CHANGE_THIRDPARTY''' => Can change customer on orders

* '''WAREHOUSE_ASK_WAREHOUSE_DURING_ORDER''' => When an order is created, the warehouse can be defined

* '''ORDER_ALLOW_EXTERNAL_DOWNLOAD''' => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)
[[#Top|(back to top)]]

== '''PDF Options''' ==
* '''MAIN_DISABLE_FORCE_SAVEAS''' ► If your browser always asks to save downloaded files on disk (like PDF), try this this option. File may be displayed directly in 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 servers with low CPU.

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

* '''MAIN_ADD_PDF_BACKGROUND''' ► Define this constant with short name of a PDF file (example "<code>mypdf.pdf</code>") that must be saved into directory "<code>documents/mycompany</code>". 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 "<code>DejaVuSans</code>".

* '''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: <code>220,220,200</code>

* '''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 '<code>jodconverter</code>', java and jodconverter command line tool must be available. If value is '<code>/pathto/jodconverter.jar</code>' then java and the jodconvertar jar must exist. Soffice must also be available. <code>MAIN_DOL_SCRIPTS_ROOT</code> Must also be defined to path where the "scripts" directory is stored (for example <code>/var/www/mydolibarr</code>).

* '''MAIN_ODT_AS_PDF_DEL_SOURCE''' ► For ODT generation. If set, then initial behaviour is conserved but ODT file is removed when option to convert it as PDF (see previous) is on. Disabled by default

* '''MAIN_GENERATE_DOCUMENTS_SHOW_FOOT_DETAILS''' ► Adding the company address at the bottom of the page. Disabled by default

* '''MAIN_GENERATE_PROPOSALS_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer proposals.

* '''MAIN_GENERATE_INVOICES_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for customer invoices.

* '''MAIN_GENERATE_SUPPLIER_PROPOSAL_WITH_PICTURE''' ► Include the first image of the product into the line of the generated PDF for supplier proposals ► (v5.0.3+)

* '''MAIN_DOCUMENTS_LOGO_HEIGHT''' ► Can force height of the logo on PDF.

* '''MAIN_DOCUMENTS_WITH_PICTURE_WIDTH''' ► Can change size of picture when hidden option <code>MAIN_GENERATE_PROPOSALS_WITH_PICTURE</code> is used. By default value is <code>20</code>.

* '''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 code/account number" for GB, ...) and keep only BIC/IBAN on PDF.

* '''PDF_HIDE_PRODUCT_REF_IN_SUPPLIER_LINES''' ► Modify the use/position of Supplier Ref/Internal Ref with the item Label (name) on PDF documents.
Default (constant not set or Value <code>0</code>): Internal ref followed by supplier ref in brackets."COMPANY-REF-001 (Vendor SKU SUPPLIER-REF-001) - LABEL...".

Value <code>1</code>: Supplier ref only eg."SUPPLIER-REF-001 - LABEL...".

Value <code>2</code>: Supplier ref followed by internal ref in brackets. eg."SUPPLIER-REF-001 (InternalRef COMPANY-REF-001) - LABEL...".

* '''MAIN_PDF_ADDALSOTARGETDETAILS''' ► Add particular details like the telephone number on generated PDFs. Can be useful in cases where a printed order/invoice etc is given to a delivery driver/courier etc.

* '''PDF_INCLUDE_ALIAS_IN_THIRDPARTY_NAME''' ► Include alternative/alias name into name on PDF.

* '''MAIN_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► Add optional esign field in pdf propal ► (v8.0+)

* '''MAIN_TVAINTRA_IN_SOURCE_ADDRESS''' ► Show VAT N° in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

* '''MAIN_PROFID1_IN_SOURCE_ADDRESS''' ► Show Professional ID 1 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

* '''MAIN_PROFID2_IN_SOURCE_ADDRESS''' ► Show Professional ID 2 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

* '''MAIN_PROFID3_IN_SOURCE_ADDRESS''' ► Show Professional ID 3 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

* '''MAIN_PROFID4_IN_SOURCE_ADDRESS''' ► Show Professional ID 4 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

* '''MAIN_PROFID5_IN_SOURCE_ADDRESS''' ► Show Professional ID 5 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

* '''MAIN_PROFID6_IN_SOURCE_ADDRESS''' ► Show Professional ID 6 in source address of PDF to comply with legalities in certain countries ► (v8.0.1+)

* '''ADD_HTML_FORMATING_INTO_DESC_DOC''' ► Add more visibility to important informations like reference and serial number in desc. ► (v10.0)

[[#Top|(back to top)]]

== '''Point of Sale''' ==
* '''CASHDESK_SHOW_KEYPAD''' ► Show a mouse key pad into the 'Simple Point of Sale' module.

* '''POS_ADDON''' ► Set this value to an existing numbering module rule (for example '<code>mod_facture_terre</code>', '<code>mod_facture_mars</code>', ...) to force the numbering module to us to define the invoice ref when invoice is created by the POS. For example setting value <code>POS_ADDON</code> to '<code>mod_facture_terre</code>' will use the numbering module '<code>terre</code>' for invoice generated from POS, whatever is the numbering rule defined into invoice module setup (you can also use '''POS_NUMBERING_TERRE_FORCE_PREFIX''' and '''POS_NUMBERING_MARS_FORCE_PREFIX''' variable to change the prefix used).
[[#Top|(back to top)]]

== '''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_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.

* '''PRODUCT_DISABLE_SIZE''' ► Disable size in product card.

* '''PRODUCT_DISABLE_LENGTH''' ► Disable length in product card ► v4.0+

* '''PRODUCT_DISABLE_SURFACE''' ► Disable surface in product card. ► v4.0+

* '''PRODUCT_DISABLE_VOLUME''' ► Disable volume in product card.

* '''PRODUCT_DISABLE_CUSTOM_INFO''' ► Disable custom info (custom code and country origin) in product/service card.

* '''PRODUIT_MULTIPRICES_USE_VAT_PER_LEVEL''' ► When option to use price per level/segment is on, this allows to also set a dedicated vat for each price level.

* '''MAIN_DIRECT_STATUS_UPDATE''' ► Allows you to change the status of the product (''for sale/not for sale for purchase/not for purchase'') directly on the product page via a ''on/off'' switch button. This can be convenient for those who need to quickly disable certain statuses of products without having to go through the editing product page individually. Also can be very useful if used as a filter on the product and product search list. This option doesn't generate a MODIFY trigger, so be careful with external modules. ► v4.0+

* '''PRODUCT_CHARGES''' ► Adds an extra field for adhoc charges at the product buying price stage. The cost price is then calculated with supplier price + charges if defined. Useful for extra costs for a product or certain delivery charges to the product. ► (<= v7.0)

* '''PRODUCT_MAX_VISIBLE_PHOTO''' ► Show a maximum number of product photos (as thumbnails) on the product main card. Example, setting this constant to '<code>5</code>' will show the first five product photos found on the product card.

* '''PRODUCT_MAX_LENGTH_COMBO''' ► Limit the length of the label displayed when adding lines in proposals/invoices/orders

* '''MAIN_DISABLE_FREE_LINES''' ► Disallow using free lines to add line in documents ► (>= 8.0)

* '''MAIN_SHOW_PRODUCT_ACTIVITY_TRIM''' ► Show Product and Services turnover before for all four quarters tax over recent years recent years on the product area ► (v5.0+)

* '''CATEGORY_GRAPHSTATS_ON_PRODUCTS''' ► Show graph of products with categories and totals in Products Area screen
[[#Top|(back to top)]]

== '''Projects Module''' ==
* '''PROJECT_DISABLE_UNLINK_FROM_OVERVIEW''' ► Enable removing the button from a link in the project overview. ► (>= 8.0.1)

* '''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''' ► Hide the "link to" form on the overview page ► (4.0)

* '''PROJECT_CREATE_ON_OVERVIEW_DISABLED''' ► Hide the "create ..." button on the overview page ► (4.0)

* '''PROJECT_ALLOW_TO_LINK_FROM_OTHER_COMPANY''' ► Can link an object to a project of another thirdparty

* '''PROJECT_ALLOW_COMMENT_ON_TASK''' ► Add comment feature on project task
[[#Top|(back to top)]]

== '''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 a picture of the product (the first one found if there are several) into the generated PDF of proposals. Note that using this will reduce the available width for the 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

* '''PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD''' ► When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key. ► (v7.0+)

* '''MAIN_PDF_PROPAL_USE_ELECTRONIC_SIGNING''' ► add optional esign field in pdf propal ► (v8.0+)
[[#Top|(back to top)]]

== '''Services Module''' ==
* '''SERVICE_ARE_ECOMMERCE_200238EC''' ► If this option is enabled, services are processed like eServices according to directive 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.
[[#Top|(back to top)]]

== '''Shipments''' ==
* '''STOCK_WAREHOUSE_NOT_REQUIRED_FOR_SHIPMENTS''' ► If set, you can add a shipment line, with no stock source defined. ► (>= 8.0.1)

* '''SHIPMENT_GETS_ALL_ORDER_PRODUCTS''' ► Add all order lines in shipment, including the one with 0 in quantity
[[#Top|(back to top)]]

== '''Stocks''' ==
* '''CASHDESK_FORCE_STOCK_ON_BILL''' => Option to force decrease of stock whatever is user setup. ► (>= 8.0.1)

* '''SUPPLIER_ORDER_DISABLE_STOCK_DISPATCH_WHEN_TOTAL_REACHED''' ► Disable stock dispatch when total expected was already received.
[[#Top|(back to top)]]

== '''Suppliers Module''' ==
* '''FOURN_PRODUCT_AVAILABILITY''' ► On the Suppliers price page of the products, activate the supplier product availability. ''This is duplicate feature with delivery_delay introduced with 3.8.''

* '''RELOAD_PAGE_ON_SUPPLIER_CHANGE''' ► On creation of a supplier order/invoice, reload form with supplier-specific details when supplier is selected from drop-down list.

* '''SUPPLIER_ORDER_AUTOADD_USER_CONTACT''' ► Add user approving supplier order as a contact automatically.

* '''SUPPLIER_ORDER_DEFAULT_PAYMENT_MODE_ID''' ► Set the default payment method for suppliers (<code>rowid</code> in table <code>llx_c_paiement</code>).

* '''SUPPLIER_ORDER_USE_DISPATCH_STATUS''' ► Add a status on each dispatch order line when receiving products from suppliers ► (v4.0+)

* '''SUPPLIER_ORDER_NO_DIRECT_APPROVE''' ► No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

* '''SUPPLIER_ORDER_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier order to only those with a buying price defined for that supplier. ► (v6.0+)

* '''SUPPLIER_ORDER_EDIT_BUYINGPRICE_DURING_RECEIPT''' ► Can modify the buying price used for PMP calculation when making a stock reception on a supplier order. ► (v6.0+)

* '''SUPPLIER_PROPOSAL_WITH_PREDEFINED_PRICES_ONLY''' ► Restrict selection of products in supplier proposal to only those with a buying price defined for that supplier. ► (v6.0+)

* '''DISPLAY_DISCOUNTED_SUPPLIER_PRICE''' ► Allow to display discounted supplier price when searching product in supplier documents ► (v10.0)

* '''MAIN_CAN_EDIT_SUPPLIER_ON_SUPPLIER_ORDER''' ► Allow to change the supplier on a draft supplier order ► (v10.0)

[[#Top|(back to top)]]

== '''Third Parties Module''' ==
* '''COMPANY_AQUARIUM_CLEAN_REGEX''' ► Add a REGEX rule on the third parties names. It applies a regex replacement pattern on generated code if COMPANY_AQUARIUM_CLEAN_REGEX is set. Value must be a regex with parenthesis. The part into parenthesis is kept, the rest removed. For example if COMPANY_AQUARIUM_CLEAN_REGEX = '<code>^..(..)..(.*)</code>' the first char and second char are removed and the char 5 and 6 too ► (>= 8.0.1)

* '''MAIN_FORCE_DEFAULT_STATE_ID''' ► <code>rowid (integer)</code> of a state/province as defined in <code>llx_c_departements</code>. On the creation of a third party/contact, the state/province corresponding to this rowid is preselected in the dropdown list. ► (>= 8.0.1)

* '''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 dictionary instead of alphabetical order.

* '''THIRDPARTY_DEFAULT_CREATE_CONTACT''' ► With this setting as '''1''' the option is set for third parties to be created WITH the child contact ► (v5.0+)

* '''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.

* '''THIRDPARTY_INCLUDE_PARENT_IN_LINKTO''' ► Search also for elements on parent third party when using the "link to" object feature.

* '''THIRDPARTY_INCLUDE_PROJECT_THIRDPARY_IN_LINKTO''' ► Search also for elements on third party that own the project of the current element when using the "link to" object feature (if project is owned by a different thirdparty than current one).

* '''SOCIETE_ASK_FOR_SHIPPING_METHOD''' ► Shipping method can be predefined on customer card and will be used as default on order creation

* '''THIRDPARTY_LOGO_ALLOW_EXTERNAL_DOWNLOAD''' ► When a logo is uploaded, a share key is automatically set so the file can be downloaded using the share key.

* '''MAIN_DISABLE_RESTRICTION_ON_THIRDPARTY_FOR_EXTERNAL''' ► External users are always restricted on the thirdparty of their contact record. With this option, permission "see all thirdparty" may works also for external user. Not implemented yet...

* '''THIRDPARTY_CAN_HAVE_CATEGORY_EVEN_IF_NOT_CUSTOMER_PROSPECT_SUPPLIER''' ► Possible to add Categories to third parties that are not customer, prospect or supplier.
[[#Top|(back to top)]]

== '''VAT Report''' ==
* '''MAIN_INCLUDE_ZERO_VAT_IN_REPORTS''' ► Include lines with VAT to 0% (for "auto-liquidation" in EEC) ► (v8.0.3+)
[[#Top|(back to top)]]

== '''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 guaranteed with this. Also if the image is removed or renamed by the image hosting service, your proposal, order or invoice will be broken.
[[#Top|(back to top)]]

Table llx subscription

2018-07-04T06:36:46Z

Iouston: Ajout du nouveau nom de la table (llx_subscription)

[[Category:Table SQL]]
[[Category:Foundations]]
[[Category:Adhérent]]
[[Category:Miembros]]

{{ListOfTables}}

= Content/Contenu/Contenido =
{{flag en}} Contains the afiliations of members of the association module. In version 7.xx of dolibarr, the table is now called llx_subscription

{{flag fr}} Contient les cotisations des adhérents du module association. Dans la version 7.xx de dolibarr, la table s'appelle désormais llx_subscription

{{flag sp}} Contiene las cotizaciones de los miembros del módulo miembros. En la versión 7.xx de dolibarr, la tabla se llama ahora llx_subscription

= Structure =
== Table ==
{| align="left" width="100%" border="0" cellpadding="1" cellspacing="0" class="dolbox"
|style="background-color: #e9e9ef"| Field
|style="background-color: #e9e9ef"| Type
|style="background-color: #e9e9ef"| Null
|style="background-color: #e9e9ef"| Key
|style="background-color: #e9e9ef"| Default
|style="background-color: #e9e9ef"| Extra
|style="background-color: #e9e9ef"| Description
|-
| rowid
| int(11)
| NO
| PRI
|
| auto_increment
| technical index
{{FieldTms}}
|-
| datec
| datetime
| YES
|
| NULL
|
| date of creation
|-
| fk_adherent
| int(11)
| YES
| UNI
| NULL
|
| ID of member ([[Table llx_adherent|llx_adherent]]->rowid)
|-
| dateadh
| datetime
| YES
| UNI
| NULL
|
| date of afiliation
|-
| datef
| date
| YES
|
| NULL
|
| date of end afiliation
|-
| cotisation
| double
| YES
|
| NULL
|
| amount of afiliation
|-
| fk_bank
| int(11)
| YES
|
| NULL
|
| ID of bank to pay ([[Table llx_bank_account|llx_bank_account]]->rowid)
|-
| note
| text
| YES
|
| NULL
|
| notes
|} 

== Keys ==
{| align="left" width="100%" border="0" cellpadding="1" cellspacing="0" class="dolbox"
|style="background-color: #e9e9ef"| Key
|style="background-color: #e9e9ef"| Type
|style="background-color: #e9e9ef"| Fields
|-
| PRIMARY
| PRIMARY
| rowid
|-
| uk_cotisation
| UNIQUE
| fk_adherent,dateadh
|}

DevCamp Nancy 2018 Organization

2018-02-03T21:12:25Z

Iouston: subscription for julien marchand

__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
* 17:00 - Presentation "Dolibarr - What's new in 7.0 - Devcamp Nancy 2018" (new features) => video streaming available (en french)
* 18:00 - Presentation "Dolibarr - Information for developers and partners - Devcamp Nancy 2018" (new Module website + Module builder) => video streaming available (in french)
* 20:00 - Dinner
* 21:00 - Bug tracking and closing issues - also called "The night, the Pull Request validator sleeps, except for bug fixes"

== Day 2 (Saturday) ==
* 8:00 - 12:00 - Bug tracking and closing issues
* 12:00 - Lunch
* 15:00 - Dolibarr Foundation assembly
* 16:00 - Presentation: "Dolibarr - The new architecture of Dolibarr foundation tools - Devcamp Nancy 2018" (new architecture, password management, ...) => video streaming available (in french)
* 20:00 - Dinner
* 21:00 - Bug tracking and closing issues - also called "The night, the Pull Request validator sleeps, except for bug fixes"

== 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:
* Age:
* Coming from (town, country):
* Arrival date and hour:
* Departure date and hour:
* Transportation (Train/Bus/Car/Plane):
* Food (Special diet, allergies, vegetarian, none…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Contact email:

= 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…): Common booked hotel
* Book hotel for me (yes/no): yes
* Email for contact: bafbes@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

[]
* Firstname Lastname:[[Claude Castellano]]
* Age: 69
* Coming from (town, country): Le Vigan(30120), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Voiture
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Je regarde
* Book hotel for me (yes/no): no
* Contact email: claude@cigaleaventure.com

[]
* Firstname Lastname:[[Rachid HRICH]]
* Age: 45
* Coming from (town, country): Rabat (10000), Morocco
* Arrival date and hour: Friday 15: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…): Hotel Mercure
* Book hotel for me (yes/no): yes
* Contact email: rachid.hrich@gmail.com

* Lastname Firstname: Eric GROULT
* Age: 37
* Coming from (town, country): NANTES (44100), France
* Arrival date and hour: Friday 15:00
* Departure date and hour: Sunday 17:00
* 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: eric@code42.fr

* Lastname Firstname: David MOYON
* Age: 32
* Coming from (town, country): NANTES (44100), France
* Arrival date and hour: Friday 15:00
* Departure date and hour: Sunday 17:00
* 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: eric@code42.fr

* Lastname Firstname: Julien Marchand
* Age: 35
* Coming from (town, country): Einville au Jard (54370), France
* Arrival date and hour: Saturday morning
* Departure date and hour: Sunday 17:00
* Transportation (Train/Bus/Car/Plane): Tramway
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): in my house
* Book hotel for me (yes/no): no
* Email for contact: julien.marchand@iouston.com

Setup Other

2018-01-31T08:41:20Z

Iouston: add a warning on MAIN_USE_CACHE_MANIFEST

[[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 which can allow some tweaking to your own Dolibarr instance.

For 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 are 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_SHOW_TECHNICAL_ID => Show also technical IDs on elements cards or some lists (not supported everywhere).

* MAIN_MAXTABS_IN_CARD => Max number of tabs visible. Others are grouped into a combo list.

* MAIN_ONLY_LOGIN_ALLOWED => Only the specified login is allowed to log in Dolibarr (maintenance mode)

* MAIN_AUTO_TIMESTAMP_IN_PUBLIC_NOTES => Add a timestamp and user automatically when editing the ''public'' note.

* MAIN_AUTO_TIMESTAMP_IN_PRIVATE_NOTES => Add a timestamp and user automatically when editing the ''private'' note.

* 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 powerful.

* 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 uppercase 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 should 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 screen, 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 on other data that should be done consistently) and ignore business controls on data you saved. So this feature breaks consistency 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 the target page for link "I need help" onto logon page

* MAIN_MODULES_FOR_EXTERNAL => Limit available modules for external users. By default 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 the first sale representative into documents (at end of public notes).

* MAIN_DISABLE_AJAX_COMBOX => If you have a large number of third parties or products, you can disable the autocomplete feature on the third parties 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 - Attention, this functionality is obsolete and removed from web standards

* 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 formatted. 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 (the landing page). 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

* MAIN_DEFAULT_PAYMENT_TERM_ID => With id of a payment term, will use this as default payment term each time you create a new proposal, order, invoice (customer and supplier)

* MAIN_ROUNDOFTOTAL_NOT_TOTALOFROUND => Change way of rounding total TTC lines, rounding first of after

* MAIN_VIEW_LINE_NUMBER => Shows a line number against each line in the order/invoice for products/services. On screen only, not on PDF.

* MAIN_DOC_USE_OBJECT_THIRDPARTY_NAME => Add name of thirdparty at begin of generated document

* MAIN_DOC_USE_TIMING => Add a timestamp at end of generated document. Value must be format of timestamp. For example: %Y%m%d%H%M

* MAIN_DISABLEDRAFTSTATUS => Disable the status Draft for some object (project, donation, ...)

* MAIN_USE_OLD_SEARCH_FORM => Display the old search form in left menu

== 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 logged in user is 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 Linux 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 pre-defined email

* MAIL_FORCE_DELIVERY_RECEIPT_INVOICE => Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Invoice'' module.

* MAIL_FORCE_DELIVERY_RECEIPT_ORDER => Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Order'' module.

* MAIL_FORCE_DELIVERY_RECEIPT_PROPAL => Set default as "Yes" on requesting delivery receipt when sending email through the ''Customer Proposal'' module.

* 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 third party 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 third party or object, the email exchange is related to.

* MAIL_MAX_NB_OF_RECIPIENTS_IN_SAME_EMAIL => Restrict sending of 1 email message to x recipients for same email message (x for To: + CC: + BCC:). If not defined, value is 10. Required to fight against spamming that include 1000 recipients in 1 message. Note that MAIL_MAX_NB_OF_RECIPIENTS_TO_IN_SAME_EMAIL, MAIL_MAX_NB_OF_RECIPIENTS_CC_IN_SAME_EMAIL and MAIL_MAX_NB_OF_RECIPIENTS_BCC_IN_SAME_EMAIL are also available.

* MAIN_MAIL_FORCE_CONTENT_TYPE_TO_HTML => Force to send all email (event with text only content) as HTML formatted email.

* MAIN_MAIL_USE_MULTI_PART => Forge email content using an alternate text part (for 5.0.2+). By default with 6.0+

* MAIN_MAIL_ADD_INLINE_IMAGES_IF_IN_MEDIAS => If images were stored into the medias directory from CKEditor, then images into emails are replaced with "inline content". This may increase seriously risk of being detected as SPAM.

* MAIN_COPY_FILE_IN_EVENT_AUTO => Add attachement document on event auto generated by sending email from dolibarr. (v6.0+)

== 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 dictionary instead of alphabetical order.
* THIRDPARTY_DEFAULT_CREATE_CONTACT (Dolibarr 5.0+) => Default Third party create are individual
* MAIN_THIRDPARTY_CREATION_INDIVIDUAL (Dolibarr <5.0) => Default Third party 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.
* THIRDPARTY_INCLUDE_PARENT_IN_LINKTO => Search also for elements on parent third party when using the "link to" object feature.
* THIRDPARTY_INCLUDE_PROJECT_THIRDPARY_IN_LINKTO => Search also for elements on third party that own the project of the current element when using the "link to" object feature (if project is owned by a different thirdparty than current one).
* SOCIETE_ASK_FOR_SHIPPING_METHOD => Shipping method can be predefined on customer card and will be used as default on order creation

== 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 a picture of the product (the first one found if there are several) into the generated PDF of proposals. Note that using this will reduce the available width for the 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
* PROPOSAL_ALLOW_EXTERNAL_DOWNLOAD => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key.

== 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".
* COMMANDE_CHANGE_THIRDPARTY => Can change customer on orders
* ORDER_ALLOW_EXTERNAL_DOWNLOAD => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key.

== Invoice module ==
* MAIN_DEPOSIT_MULTI_TVA => In deposits invoice, creates one line per VAT rate from the origin document (6.0)
* FACTURE_SHOW_SEND_REMINDER => Show link "Send reminder by mail", same feature than "Send by mail" (obsolete feature).
* INVOICE_CAN_ALWAYS_BE_EDITED => Allow to edit invoices even if payment was started. Note: If the module "'''BlockedLog'''" is active (required by some countries for legal reason), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the non reversible archive log.
* INVOICE_CAN_ALWAYS_BE_REMOVED => Allow to always delete invoices (even if invoice is not last one). Note: If the module "'''BlockedLog'''" is active (required by some countries for legal reason), this will not change content of archived logs tracked by this module. By definition there is no way to change or remove archived records. It will just update data in your application and a new record to track your change into the non reversible archive log.
* 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
* INVOICE_ALLOW_EXTERNAL_DOWNLOAD => When a PDF is generated, a share key is automatically set so the file can be downloaded using the share key.

== Expense Report ==
* EXPENSEREPORT_ALLOW_OVERLAPPING_PERIODS => Can enter several expense reports on same or overlapping date periods.

== 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_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.
* PRODUIT_MULTIPRICES_USE_VAT_PER_LEVEL => When option to use price per level/segment is on, this allows to also set a dedicated vat for each price level.
* MAIN_DIRECT_STATUS_UPDATE => Allows you to change the status of the product (''for sale/not for sale for purchase/not for purchase'') directly on the product page via a ''on/off'' switch button. This can be convenient for those who need to quickly disable certain statuses of products without having to go through the editing product page individually. Also can be very useful if used as a filter on the product and product search list. v4.0+

* PRODUCT_CHARGES => Adds an extra field for adhoc charges at the product buying price stage. The Cost price is then calculated with supplier price + charges if defined. Useful for extra costs for a product or certain delivery charges to the product.

* PRODUCT_MAX_VISIBLE_PHOTO => Show a maximum number of product photos (as thumbnails) on the product main card. Example, setting this constant to '5' will show the first five product photos found on the product card.
* PRODUCT_MAX_LENGTH_COMBO => limit the length of the label displayed when adding lines in proposals/invoices/orders

== Services module ==
* SERVICE_ARE_ECOMMERCE_200238EC => If this option is enabled, services are processed like eServices according to directive 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 ==
* SUPPLIER_ORDER_DISABLE_STOCK_DISPATCH_WHEN_TOTAL_REACHED => Disable stock dispatch when total expected was already received.

== Shipments ==

== 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_ALLOW_TO_LINK_FROM_OTHER_COMPANY => Can link an object to a project of another thirdparty

== 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 added in front off payment cell, 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, activate 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 when receiving products from suppliers (v4.0+)
* 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. (v6.0+)
* SUPPLIER_ORDER_EDIT_BUYINGPRICE_DURING_RECEIPT => Can modify the buying price used for PMP calculation when making a stock reception on a supplier order. (v6.0+)

== Bank module ==
* BANK_CAN_RECONCILIATE_CASHACCOUNT (3.8) => Can reconciliate cash accounts
* BANK_DISABLE_CHECK_DEPOSIT => Disable check deposit feature
* BANK_ASK_PAYMENT_BANK_DURING_ORDER => Ask bank account during creation of order

== Emailing module ==
* MAILING_PREFIX_FOR_EMAIL_ID => Set the value that will be used to compose the "Email Id" into email headers. If you set this value to 'SERVER_NAME', the virtual host of web server will be used. By default, this is not defined, so a hash key, unique to each instance, is used.
* MAILING_NO_USING_PHPMAIL => If set, the module emailing can't be use with mail setup of "phpmail". Using a thirdparty SMTP server is required. You can complete warning message by adding an email to contact for setup help with constant MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS.
* MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS => Contains an email to show in a message visible to user when he try to use emailing module without SMTP server and if option MAILING_NO_USING_PHPMAIL is set to on.
* MAILING_LIMIT_WARNING_PHPMAIL => Show a warning message (var contains the message to show or translation key) on emailing send form if setup is on "phpmail". For example, you can set this parameter to 'MAILING_LIMIT_WARNING_PHPMAIL' and enter translation key for each language for this key.
* MAILING_LIMIT_WARNING_NOPHPMAIL => Show a warning message (var contains the message to show or translation key) on emailing send form if setup is something else than "phpmail". For example, you can set this parameter to 'MAILING_LIMIT_WARNING_NOPHPMAIL' and enter translation key for each language for this key.
* EMAILING_USE_ADVANCED_SELECTOR => Enable the advanced selector for destinaries

* MAILING_LIMIT_SENDBYWEB => Restrict number of emails you can send in same sending session with emailing module from GUI. The value "dolibarr_mailing_limit_sendbyweb" if defined into config file is used in priority for this limit. A negative value means, sending by web is forbidden.
* MAILING_LIMIT_SENDBYCLI => Restrict number of emails you can send in same sending session with emailing module from CLI script. The value "dolibarr_mailing_limit_sendbycli" if defined into config file is used in priority for this limit.

== 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 servers 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_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 but odt file is removed when option to convert it as PDF (see previous) is on. Disabled by default

* MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Include the first image of the product into the line of the generated PDF for customer proposals.

* MAIN_GENERATE_INVOICES_WITH_PICTURE => Include the first image of the product into the line of the generated PDF for customer invoices.

* MAIN_GENERATE_SUPPLIER_PROPOSAL_WITH_PICTURE => Include the first image of the product into the line of the generated PDF for supplier proposals (v5.0.3+)

* 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.

* PDF_HIDE_PRODUCT_REF_IN_SUPPLIER_LINES => Value 1 or 2 change the way product ref is show (1 = show supplier ref only and not internal ref, 2 = show supplier then internal). Without, internal ref then supplier is shown.

* MAIN_PDF_ADDALSOTARGETDETAILS => Add particular details like the telephone number on generated PDFs. Can be useful in cases where a printed order/invoice etc is given to a delivery driver/courier etc.

* PDF_INCLUDE_ALIAS_IN_THIRDPARTY_NAME => Include alternative/alias name into name 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.

== BlockedLog ==

* BLOCKEDLOG_DISABLE_NOT_ALLOWED_FOR_COUNTRY => Make disable of module "blockedlog" not possible for countries code defined into value. Example: 'FR,...'

List of modules id

2018-01-23T08:40:31Z

Iouston:

[[Category:Core]]
{{TemplateDocDevEn}}
{{TemplateDocDevEs}}
{{TemplateDocDevFr}}

{{Flag en}} This page list all reserved modules numbers / ID. If you build or want to build your own modules (like this [[:Category:Complementary_modules|complementary module]]), you should take an ID range here.

{{Flag fr}} Cette page recense tous les numéros / ID réservés de modules. Si vous avez réalisé ou voulez réaliser vos propres modules (comme les [[:Category:Modules complémentaires|modules complémentaires suivant]]), vous devriez prendre une plage d'ID ici.

{{Flag sp}} Esta página contiene un listado de todos los id reservados para los módulos. Si ha creado o quiere realizar sus propios módulos, (como estos [[:Category:Módulos_complementarios|módulos complementarios]]), deberá reservarse un rango de ID aquí.

= ID 0 - 99999 =
{{Flag en}} Reserved for Dolibarr's internal modules.

{{Flag fr}} Réservé aux modules internes de Dolibarr.

{{Flag sp}} Reservado a los módulos internos de Dolibarr.

= ID 100000 - 499999 =
{{Flag en}} Reserved area for editors in need for an ID range. You can edit this page to add your own range (limited to 1000 values per editor)

{{Flag fr}} Zone réservé aux éditeurs qui ont besoin d'une plage d'ID spécifiques. Vous pouvez modifier cette page pour réserver votre plage (limité à 1000 valeurs par éditeur)

{{Flag sp}} Área reservada para los partners que necesiten un rango de ID. Puede modificar esta página para reservar su rango (limitado a 1000 valores por editor)

* ID 100000 - 100999: OpenThink (http://www.openthink.be)
* ID 101000 - 101999: NLTechno (https://www.nltechno.com)
* ID 102000 - 102999: Tiaris (http://www.tiaris.fr)
* ID 103000 - 103999: Open-concept.pro (http://www.open-concept.pro)
* ID 104000 - 104999: ATM Consulting (http://www.atm-consulting.fr)
* ID 105000 - 105999: GPC.solutions
* ID 106000 - 106999: PHPASSO
* ID 107000 - 107999: TecLib (http://www.teclib.com) / Auguria (http://www.auguria.net)
* ID 108000 - 108999: ETHICWEB
* ID 109000 - 109999: Aplose (http://www.aplose.fr)
* ID 110000 - 110999: Aternatik
* ID 111000 - 111999: Asset IT (www.assetit.ch)
* ID 112000 - 112999: Aarboard AG (www.aarboard.ch)
* ID 113000 - 113999: Asilib - Alexandre Spangaro
* ID 114000 - 114999: Iceleaf OÜ
* ID 115000 - 115999: 2A2C Conseil - Cyril ZEKSER
* ID 116000 - 116999: Wolftec GmbH
* ID 117000 - 117999: Oscim (http://www.oscim.fr)
* ID 118000 - 118999: Oarces Web (dev.oarces.com)
* ID 119000 - 119999: Manuel Berrocal - Absolacom
* ID 120000 - 120999: Régis Houssin (http://www.inodbox.com)
* ID 121000 - 121999: Oscss - Shop
* ID 122000 - 122999: MrSof - la Nation du Web
* ID 123000 - 123999: Bruno Généré (webiseasy.org)
* ID 124000 - 124999: backbone internet service (www.backbone.co.at)
* ID 125000 - 125999: ProgSI (www.progsi.ma)
* ID 126000 - 126999: Catalanet
* ID 127000 - 127999: Virgilio Filho pt-BR Brasil (@dolibarr.br)
* ID 128000 - 128999: Nicolas Frappé France (www.sospc.info)
* ID 130000 - 130999: Technicks ICT (http://www.technicks.eu)
* ID 140000 - 140999: Altairis
* ID 150000 - 150999: Jeffinfo
* ID 160000 - 160999: Charles-François BENKE (http://www.patas-monkey.com)
* ID 162000 - 162999: Jacques Rébiscoul
* ID 163000 - 163999: Open-DSI (https://www.open-dsi.fr)
* ID 170000 - 170999: TRIDENT CONSULTING LTD (www.tridentdxb.com)
* ID 180000 - 180999: Triangle Ingénierie
* ID 190000 - 190999: Diciannove (http://19.coop)
* ID 199000 - 199999: RFMS
* ID 200000 - 200999: Noxiome
* ID 201000 - 201999: Sasa Ostrouska (saxa)
* ID 202000 - 202999: Z-Application
* ID 203000 - 203099: Elidee - elidee.com
* ID 203100 - 203999: Garcia MICHEL (soamichel.fr)
* ID 204000 - 204999: Ari Elbaz elarifr - accedinfo.com
* ID 205000 - 205999: Kreiz IT
* ID 206000 - 206999: GBINFO (www.gbinfo.fr)
* ID 300000 - 300999: AtooNet (http://www.atoo-net.com)
* ID 400000 - 400999: 2byte.es (http://www.2byte.es)
* ID 401000 - 401999: B&D Informática
* ID 402000 - 402999: Marcos García de La Fuente (marcosgdf)
* ID 403000 - 403999: Sergibyte (http://www.sergibyte.com)
* ID 404000 - 404999: Aikhan
* ID 405000 - 405999: AIME (http://www.aime.mx)
* ID 409000 - 409999: LliureTIC (www.lliuretic.cat)
* ID 420000 - 420099: BBS Concept
* ID 420100 - 420199: LeMousticProduction (www.lemousticproduction.info) -< module DoliRH
* ID 420200 - 421199: VatCheck (www.abnc.be)
* ID 422200 - 422999: Artaban (http://artaban.fr)
* ID 423000 - 423050: cyberesprit
* ID 424000 - 424999: A3sys - Mon-Dolibarr (http://www.mon-dolibarr.fr)
* ID 425000 - 425999: Sébastien SERRE Thivinfo (www.thivinfo.com)
* ID 426000 - 426099: Arkesis-Solution
* ID 426100 - 426149: GetLandy (www.getlandy.com)
* ID 426150 - 426649: OOB Software
* ID 426650 - 426849: Soft-Task Serviços e Sistemas (www.soft-task.com.br)
* ID 426850 - 427000: Bruno Caldas (https://github.com/BCaldas)
* ID 427001 - 427999: Kevin GUERRIER (alias xcl.saian)
* ID 428000 - 428099: af83
* ID 429000 - 429999: induslab
* ID 430000 - 430099: Mixity sprl (www.mixity.be)
* ID 430100 - 430199: sgiraud
* ID 430200 - 430299: Merlion TI (www.merlion-si.com.br)
* ID 430300 - 431299: Libre Expert (www.libre-expert.com)
* ID 431300 - 431399: ptibogxiv (www.ptibogxiv.net)
* ID 431400 - 431499: Befox (www.befox.fr)
* ID 431500 - 431599: rue Béjo (www.ruebejo.fr)
* ID 431600 - 431699: Avizzeo (www.avizzeo.com)
* ID 431700 - 432199: Multisistemas (www.multisistemas.com.sv)
* ID 432200 - 432399: Burbuja - Chile (www.burbuja.cl)
* ID 432400 - 433399: INOVEA CONSEIL (https://www.inovea-conseil.com)
* ID 433400 - 434399: Rachid HRICH - Maroc (HricH ServiceS.)
* ID 434400 - 435399: Lance Bleakley - LanceIT (www.lanceit.net)
* ID 436400 - 437399: Mohamed AHERDANE - Morocco - IT Consultant ( www.wave.ma )
* ID 438400 - 439399: Tetras Libre - France - Développement logiciels libres (www.tetras-libre.fr)
* ID 439400 - 440399: Dolibarr-pro - France - Développement Dolibarr (www.dolibarr-pro.com)
* ID 440400 - 441399: Quidlab Co., Ltd - Thailand - ( www.quidlab.com )
* ID 441400 - 442399: Ide@log - France - (https://www.idealog-info.net) - Laurent Leblanc
* ID 442400 - 443399: Valerio Bianchi (www.valeriobianchi.com)
* ID 443400 - 444399: delassalle - France - (www.delassalle.fr) - Joseph Delassalle
* ID 444400 - 445399: Webartis - Maroc - (www.webartis.net) - François Dry
* ID 445400 - 445499: SCOP Au-delà des nuages - France
* ID 446000 - 446999: iouston (http://www.iouston.com) - France - Julien Marchand

= ID > 500000 =
{{Flag en}} If you don't already have reserved ids and need some, please don't use hazardous number and use a number higher than 500000, but it is better to ask a wiki account, and reserve your own range by editing the 100000 - 499999 range (1000 ids maximum per partner).

{{Flag fr}} Si vous n'avez pas de numéros réservés et en avez besoin, n'utilisez pas de chiffres au hasard et utilisez une valeur supérieure à 500000, toutefois, il est préférable d'obtenir un compte wiki, et réserver vous-même votre plage en ajoutant votre entrée dans la zone 100000 - 499999 (pas plus de 1000 numéros par partenaire).

{{Flag sp}} Si no dispone de número reservado y necesita, no use cifras redondeadas y usa un valor superior a 500000. Si tiene una cuenta wiki, puede reservarse usted mismo sus id añadiendo su entrada en la zona 100000 - 499999 (no más de 1000 id por partner).

List of modules id

2018-01-23T08:37:38Z

Iouston: ajout d'une tranche de 1000 id pour iouston 446000

[[Category:Core]]
{{TemplateDocDevEn}}
{{TemplateDocDevEs}}
{{TemplateDocDevFr}}

{{Flag en}} This page list all reserved modules numbers / ID. If you build or want to build your own modules (like this [[:Category:Complementary_modules|complementary module]]), you should take an ID range here.

{{Flag fr}} Cette page recense tous les numéros / ID réservés de modules. Si vous avez réalisé ou voulez réaliser vos propres modules (comme les [[:Category:Modules complémentaires|modules complémentaires suivant]]), vous devriez prendre une plage d'ID ici.

{{Flag sp}} Esta página contiene un listado de todos los id reservados para los módulos. Si ha creado o quiere realizar sus propios módulos, (como estos [[:Category:Módulos_complementarios|módulos complementarios]]), deberá reservarse un rango de ID aquí.

= ID 0 - 99999 =
{{Flag en}} Reserved for Dolibarr's internal modules.

{{Flag fr}} Réservé aux modules internes de Dolibarr.

{{Flag sp}} Reservado a los módulos internos de Dolibarr.

= ID 100000 - 499999 =
{{Flag en}} Reserved area for editors in need for an ID range. You can edit this page to add your own range (limited to 1000 values per editor)

{{Flag fr}} Zone réservé aux éditeurs qui ont besoin d'une plage d'ID spécifiques. Vous pouvez modifier cette page pour réserver votre plage (limité à 1000 valeurs par éditeur)

{{Flag sp}} Área reservada para los partners que necesiten un rango de ID. Puede modificar esta página para reservar su rango (limitado a 1000 valores por editor)

* ID 100000 - 100999: OpenThink (http://www.openthink.be)
* ID 101000 - 101999: NLTechno (https://www.nltechno.com)
* ID 102000 - 102999: Tiaris (http://www.tiaris.fr)
* ID 103000 - 103999: Open-concept.pro (http://www.open-concept.pro)
* ID 104000 - 104999: ATM Consulting (http://www.atm-consulting.fr)
* ID 105000 - 105999: GPC.solutions
* ID 106000 - 106999: PHPASSO
* ID 107000 - 107999: TecLib (http://www.teclib.com) / Auguria (http://www.auguria.net)
* ID 108000 - 108999: ETHICWEB
* ID 109000 - 109999: Aplose (http://www.aplose.fr)
* ID 110000 - 110999: Aternatik
* ID 111000 - 111999: Asset IT (www.assetit.ch)
* ID 112000 - 112999: Aarboard AG (www.aarboard.ch)
* ID 113000 - 113999: Asilib - Alexandre Spangaro
* ID 114000 - 114999: Iceleaf OÜ
* ID 115000 - 115999: 2A2C Conseil - Cyril ZEKSER
* ID 116000 - 116999: Wolftec GmbH
* ID 117000 - 117999: Oscim (http://www.oscim.fr)
* ID 118000 - 118999: Oarces Web (dev.oarces.com)
* ID 119000 - 119999: Manuel Berrocal - Absolacom
* ID 120000 - 120999: Régis Houssin (http://www.inodbox.com)
* ID 121000 - 121999: Oscss - Shop
* ID 122000 - 122999: MrSof - la Nation du Web
* ID 123000 - 123999: Bruno Généré (webiseasy.org)
* ID 124000 - 124999: backbone internet service (www.backbone.co.at)
* ID 125000 - 125999: ProgSI (www.progsi.ma)
* ID 126000 - 126999: Catalanet
* ID 127000 - 127999: Virgilio Filho pt-BR Brasil (@dolibarr.br)
* ID 128000 - 128999: Nicolas Frappé France (www.sospc.info)
* ID 130000 - 130999: Technicks ICT (http://www.technicks.eu)
* ID 140000 - 140999: Altairis
* ID 150000 - 150999: Jeffinfo
* ID 160000 - 160999: Charles-François BENKE (http://www.patas-monkey.com)
* ID 162000 - 162999: Jacques Rébiscoul
* ID 163000 - 163999: Open-DSI (https://www.open-dsi.fr)
* ID 170000 - 170999: TRIDENT CONSULTING LTD (www.tridentdxb.com)
* ID 180000 - 180999: Triangle Ingénierie
* ID 190000 - 190999: Diciannove (http://19.coop)
* ID 199000 - 199999: RFMS
* ID 200000 - 200999: Noxiome
* ID 201000 - 201999: Sasa Ostrouska (saxa)
* ID 202000 - 202999: Z-Application
* ID 203000 - 203099: Elidee - elidee.com
* ID 203100 - 203999: Garcia MICHEL (soamichel.fr)
* ID 204000 - 204999: Ari Elbaz elarifr - accedinfo.com
* ID 205000 - 205999: Kreiz IT
* ID 206000 - 206999: GBINFO (www.gbinfo.fr)
* ID 300000 - 300999: AtooNet (http://www.atoo-net.com)
* ID 400000 - 400999: 2byte.es (http://www.2byte.es)
* ID 401000 - 401999: B&D Informática
* ID 402000 - 402999: Marcos García de La Fuente (marcosgdf)
* ID 403000 - 403999: Sergibyte (http://www.sergibyte.com)
* ID 404000 - 404999: Aikhan
* ID 405000 - 405999: AIME (http://www.aime.mx)
* ID 409000 - 409999: LliureTIC (www.lliuretic.cat)
* ID 420000 - 420099: BBS Concept
* ID 420100 - 420199: LeMousticProduction (www.lemousticproduction.info) -< module DoliRH
* ID 420200 - 421199: VatCheck (www.abnc.be)
* ID 422200 - 422999: Artaban (http://artaban.fr)
* ID 423000 - 423050: cyberesprit
* ID 424000 - 424999: A3sys - Mon-Dolibarr (http://www.mon-dolibarr.fr)
* ID 425000 - 425999: Sébastien SERRE Thivinfo (www.thivinfo.com)
* ID 426000 - 426099: Arkesis-Solution
* ID 426100 - 426149: GetLandy (www.getlandy.com)
* ID 426150 - 426649: OOB Software
* ID 426650 - 426849: Soft-Task Serviços e Sistemas (www.soft-task.com.br)
* ID 426850 - 427000: Bruno Caldas (https://github.com/BCaldas)
* ID 427001 - 427999: Kevin GUERRIER (alias xcl.saian)
* ID 428000 - 428099: af83
* ID 429000 - 429999: induslab
* ID 430000 - 430099: Mixity sprl (www.mixity.be)
* ID 430100 - 430199: sgiraud
* ID 430200 - 430299: Merlion TI (www.merlion-si.com.br)
* ID 430300 - 431299: Libre Expert (www.libre-expert.com)
* ID 431300 - 431399: ptibogxiv (www.ptibogxiv.net)
* ID 431400 - 431499: Befox (www.befox.fr)
* ID 431500 - 431599: rue Béjo (www.ruebejo.fr)
* ID 431600 - 431699: Avizzeo (www.avizzeo.com)
* ID 431700 - 432199: Multisistemas (www.multisistemas.com.sv)
* ID 432200 - 432399: Burbuja - Chile (www.burbuja.cl)
* ID 432400 - 433399: INOVEA CONSEIL (https://www.inovea-conseil.com)
* ID 433400 - 434399: Rachid HRICH - Maroc (HricH ServiceS.)
* ID 434400 - 435399: Lance Bleakley - LanceIT (www.lanceit.net)
* ID 436400 - 437399: Mohamed AHERDANE - Morocco - IT Consultant ( www.wave.ma )
* ID 438400 - 439399: Tetras Libre - France - Développement logiciels libres (www.tetras-libre.fr)
* ID 439400 - 440399: Dolibarr-pro - France - Développement Dolibarr (www.dolibarr-pro.com)
* ID 440400 - 441399: Quidlab Co., Ltd - Thailand - ( www.quidlab.com )
* ID 441400 - 442399: Ide@log - France - (https://www.idealog-info.net) - Laurent Leblanc
* ID 442400 - 443399: Valerio Bianchi (www.valeriobianchi.com)
* ID 443400 - 444399: delassalle - France - (www.delassalle.fr) - Joseph Delassalle
* ID 444400 - 445399: Webartis - Maroc - (www.webartis.net) - François Dry
* ID 445400 - 445499: SCOP Au-delà des nuages - France
* ID 446000 - 446999: iouston (www.iouston.com) - France - Julien Marchand

= ID > 500000 =
{{Flag en}} If you don't already have reserved ids and need some, please don't use hazardous number and use a number higher than 500000, but it is better to ask a wiki account, and reserve your own range by editing the 100000 - 499999 range (1000 ids maximum per partner).

{{Flag fr}} Si vous n'avez pas de numéros réservés et en avez besoin, n'utilisez pas de chiffres au hasard et utilisez une valeur supérieure à 500000, toutefois, il est préférable d'obtenir un compte wiki, et réserver vous-même votre plage en ajoutant votre entrée dans la zone 100000 - 499999 (pas plus de 1000 numéros par partenaire).

{{Flag sp}} Si no dispone de número reservado y necesita, no use cifras redondeadas y usa un valor superior a 500000. Si tiene una cuenta wiki, puede reservarse usted mismo sus id añadiendo su entrada en la zona 100000 - 499999 (no más de 1000 id por partner).

Setup Other

2016-09-06T20:51:07Z

Iouston: MAIN_PUBLIC_NOTE_IN_ADDRESS

[[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_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_OVERWRITE_TRANS_xx_YY => You can use this to change value of a translation key for language xx_YY (ie: en_US) without editing language files. For example: "TranslationKey1:New value1,TranslationKey2:New value 2". Note that using this option slow down seriously your instance. If you can, it is better to edit directly the language files into htdocs/lang/xx_YY.

* 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_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE => Avoid Custom code and country of origin to be set as product description when added to Propal/Order/Invoice

* 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_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_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 => Show field BCC into email forms.

* MAIN_MAIL_AUTOCOPY_PROPOSAL_TO, MAIN_MAIL_AUTOCOPY_ORDER_TO, MAIN_MAIL_AUTOCOPY_INVOICE_TO => Send a BCC to the recipients when sending email for proposal, order or invoice. If option MAIN_EMAIL_USECCC is also set, you will see recipient email of BCC into email form on same line used to enter BCC.

* 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 thirdparty from menu "New thirdparty".
* THIRDPARTY_NOTSUPPLIER_BY_DEFAULT => Do not set status "Supplier" to "on" when creating a new thirdparty from menu "New thirdparty".
* MAIN_THIRDPARTY_CREATION_INDIVIDUAL => Default Thirparty create are individual
* SOCIETE_SORT_ON_TYPEENT = The combo list of "type of thirpdarty" is sorted on a field "position" that appears into dictionnary instead of alphabetical order.

== 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 ==
* PRODUCT_ADD_TYPE_IN_DOCUMENTS => Add text "Product" or "Service" at beginning of details lines on built PDF documents.
* PRODUCT_SHOW_WHEN_CREATE => Old option no more supported (create problems) to be able to add lines of product during first step of element creation.
* 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.

Module Assortiment

2013-07-25T18:09:34Z

Iouston: /* Exemple */

[[Category:Modules complémentaires]]
[[Category:Assortiment]]
{{TemplateDocDev}}
{{TemplateDocUtil}}
= Informations =
{{TemplateModuleInfo
|editor=[[Florian Henry]]
|status=stable
|minversion=3.0.0
|maxversion=3.3.0
|note=
|web=
}}

= Fonctionnalités =
Ce module est utilisé pour définir un assortiments de produits pour les client/fournisseur.
Autrement dit filtrée a la commande ou a la facturation les produit disponible pour un client/fournisseur.
En options : utilisation des catégories, limitation des produits proposés lors de la commandes/facturation à ces assortiments.

= Installation =
{{InstallModuleFr}}

Compatible avec la 3.0: Télécharger sur sourceforge [http://www.dolistore.com/lang-fr/modules/72-Assortiments.html]

= Configuration =
{{ActivationModuleFr}}

= Usage =
Un nouvel onglet Assortiment est disponible dans les fiches Client/Fournisseur et les fiches Produits.
Vous pouvez associer un produit (ou optionnellement une catégorie de produit) a l’assortiment du client/fournisseur, via ces onglet.
Cela permet si l'option est activé, de filtré les produit a la commande pour ne proposé que les produits présent dans l'assortiment.

= Exemple =
Typiquement vous avez une gamme de produits pour les distributeur et une autre pour les détaillants.

Configurez le module Assortiment comme suit :
Gestion des assortiments par catégorie : OUI
Limitez la sélection des produits aux assortiments définis pour les commandes clients : OUI

Activez le module Categories dans Module complémentaire

Allez sur la fiche Client et créez 2 catégories, distributeurs et détaillants
Affectez à vos client les bonnes catégories

Allez dans la fiche d'un produit que vous ne destiner a être vendu qu'aux détaillants, allez dans l'onglet assortiment, puis ajoutez ce produit dans les assortiments des clients de la catégorie détaillants.

Lors de la création d'une nouvelle commande, seul ce produit sera disponible a la sélection.

= Développement =
N'hesitez pas me contacter florian.henry@open-concept.pro

Setup Other

2013-05-25T10:20:23Z

Iouston: /* Invoice module */ ajout de la variable MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT

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

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

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

= Goal =
This page is build to add/edit new parameters without a dedicated page build 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''':

== Global options ==

* MAIN_APPLICATION_TITLE => This will change the title of software (that appears on the login page by default).

* 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_LOGTOHTML => 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_OVERWRITE_TRANS_xx_YY => You can use this to change value of a translation key for language xx_YY (ie: en_US) without editing language files. For example: "TranslationKey1:New value1,TranslationKey2:New value 2". Note that using this option slow down seriously your instance. If you can, it is better to edit directly the language files into htdocs/lang/xx_YY.

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

* MAIN_USE_ADVANCED_PERMS => Active advanced permissions functionality. You will get more details permission but you loose the homogeneity of permission rules.

* 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).

* MAIN_HELPCENTER_LINKTOUSE => Define a target 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_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE => Avoid Custom code and country of orign to be set as product description when added to Propal/ORder/Invoice

== 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.

* 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 be be modified and become correct during sending, solving any problem. 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

== Module Tiers ==
* 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"

== Commercial proposal 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.

== 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
* MAIN_USE_LOCALTAX_TYPE_7 => Enable local tax type 7 into dictionnary of vat types (disabled by default because implementation still need works).
* MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT => Disable VAT on genrated documents. like for an association. (it's work with crabe template)

== 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

== 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).

== Product module ==
* PRODUCT_ADD_TYPE_IN_DOCUMENTS => Add text "Product" or "Service" at beginning of details lines on built PDF documents.
* PRODUCT_SHOW_WHEN_CREATE => Old option no more supported (create problems) to be able to add lines of product during first step of element creation.
* 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.

== Service 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.

== Foundation module ==
* MEMBER_URL_REDIRECT_SUBSCRIPTION => Link called and shown when a member account is autocreated in member module by a guest user.

== Intervention module ==
* FICHEINTER_CLASSIFY_BILLED => Allow to classify a intervention card as "Billed"

== Suppliers module ==
* FOURN_PRODUCT_AVAILABILITY => On the Suppliers price page of the products, active the supplier product availability.

== 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.

* 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_ADDALSOSOURCEDETAILS => Shows all contact information in PDF files of your own company (< 3.2)

* 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 onot title line. Example: '220,220,200'

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

Langages et normes

2013-05-19T16:08:56Z

Iouston:

{{TemplateDocDev}}

Voici les quelques règles sur le langage, la syntaxe et normes de développement en vigueur pour le projet Dolibarr:

= Versions =

* Dolibarr doit fonctionner sur:
# Tous OS (Windows, Linux, MACOS...)
# PHP {{PHPMinVersion}} (Doit fonctionner sans aucun module PHP complémentaire hors les modules d'accès base de donnée).
# Mysql {{MySqlMinVersion}}

= Normes Copyright =
* Tout fichier PHP doit avoir un en-tête selon le masque suivant
<source lang="php">
<?php
/* Copyright (C) YYYY John Doe <email@email.com>
*
* Licence information
*/
...
</source>
Quand vous éditer un fichier existant du projet, ajouter une ligne Copyright sous celles existantes.

= Normes PHP =

* Dolibarr est écrit en PHP et supporte toutes versions PHP supérieures à la {{PHPMinVersion}}. Les fichiers doivent tous comporter l'extension .php

* L'appel aux variables superglobales PHP doit passer par les opérateurs dédiés $_COOKIES, $_SERVER, $_ENV mais par la fonction dolibarr GETPOST() pour récupérer les contenus de $_GET ou $_POST.
Les autres opérateurs ($HTTP_SERVER_GET, ...) ayant été passés en deprecated au sein de PHP, ne doivent plus être utilisés. Ainsi le code doit fonctionner y compris quand l'option '''register_long_arrays''' est à off.
De plus, le code doit fonctionner quand l'option PHP '''register_globals''' est à off (recommandé par PHP) aussi bien que quand l'option '''register_globals''' à on (par défaut sur de nombreuses installations).

* Les smart tags PHP ne sont pas utilisés. Les sections de code doivent commencer par '''<?php'''

* Pas d'utilisation de la variable '''PHP_SELF'''. Utiliser a la place $_SERVER["PHP_SELF"]

* Quand plusieurs variables doivent être initialisées avec la même valeur, il faut utiliser plusieurs lignes
<source lang="php">
$var1=1;$var2=1;$var3=1;
</source>
plutôt que
<source lang="php">
$var1=$var2=$var3=1;
</source>
qui est moins performant.

* Les chaines doivent être encadrées de simple quote et les variables sorties de la chaine.
<source lang="php">
print 'Mon texte affiche ma '.$variable.' !';
</source>

* Les commentaires doivent suivre la syntaxe C, ie un double antislash pour un commentaire d'une ligne et utilisation slash-étoile pour ouvrir un bloc de plusieurs lignes
<source lang="php">
/* Bloc de commentaire
*
* Fin du bloc
*/

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

for ($i = 1 , $i < 2 ; $i++)
{
// commentaire sur une ligne
print $i;
}

</source>

* Les fichiers doivent être sauvés en format Unix (LF) et non Windows (CR/LF). Le format Unix étant compatible sur les OS Unix like, Windows, Mac, alors que le format fichier texte Windows pose problème sous certains PHP sous Unix.

* Les fonctions doivent retourner une valeure strictement > à 0 en cas de succès, et un nombre < à 0 en cas d'erreur.

* Pas de code mort (non utilisé) dans le code principal de Dolibarr (le code utilisé uniquement par un module externe doit être inclus dans le module externe).

* Utiliser "include_once" pour l'inclusion de tout fichier contenant des définitions de fonction ou de classes (donc fichiers *.class.php et *.lib.php), utiliser "include" pour tout inclusion de fichier de type template ou contenant un mixte de HTML et PHP (donc fichiers *.inc.php et *.tpl.php).

= Normes SQL =

== Structure des tables et champs ==
* Toutes les tables sont préfixées pour éviter les conflits de nommage. Aujourd'hui, le préfixe est modifiable au moment de l'installation. Sa valeur par défaut est <tt>llx_</tt>.

* Structure des tables.
Lorsque vous créez une table, il est recommandé de prendre les même conventions de nommages de tables que les autres tables Dolibarr. Avec, à minima les champs suivant:
- rowid integer pour l'id
- tms timestamp qui sera un champ contenant la date de chaque mise à jour (la base de donnée le gère tout seul, pas besoin de le gérer par le code)
- import_key qui contiendra le code d'import YYYYMMDDHHMMSS si vous faites des imports en masse dans la table.
Eventuellement
- datec timestamp qui est la date de création de l'enregistrement
- fk_user_creat integer qui est l'id du user de création
- fk_user_modif integer qui est l'id du user de modif

* Type des champs
Dans la pratique, afin d'etre compatible avec toutes les précisions des pays, syntaxes des bases, on utilisera uniquement les types suivants:
- integer pour tout nombre entier, id ou clé étrangère
- double(24,8) pour tout montant
- double(6,3) pour les taux de tva
- real pour une quantité
- varchar pour une chaine (y compris de longueur 1, le type char est de plus en plus déprécié)
- timestamp pour un champ date+heure devant être mis a jour automatiquement
- datetime pour un champ date+heure
- date pour un champ date

== Clé primaire ==
La clé primaire d'une table s'appelle <tt>rowid</tt>.

Il y a quelques tables qui échappent à cette règle actuellement (ex [[Table llx_c_actioncomm]]), pour des raisons historiques. Une évolution pourra être étudiée pour une prochaine version.

== Clés étrangères ==
Le nom d'une clé étrangère commence par le préfixe <tt>fk_</tt> suivi du nom de la table liée (requis pour éviter doublons globales à la base, problématiques sous certains SGBD comme postgresql) puis du champ lié (pour permettre plusieurs clés étrangères différentes sur une même table).

Exemple:
fk_facture_fourn_fk_soc

Note: Si vous développez votre propre module externe, il ne doit pas y avoir de clé étrangère depuis vos tables qui pointent sur les tables standards de Dolibarr. Ceci casserait les fonctionnalités de mise à jour, de réparation, de sauvegardes et de restauration.

== Clés alternatives ==
Parfois, il n'y a pas que la clé primaire qui doit être unique. On peut donc ajouter aussi un index clé alternative unique. Un tel index est nommé par un nom qui commence par le préfixe <tt>uk_</tt> suivi du nom de la table d'un underscore (requis pour éviter doublons d'index globals à la base, problématiques sous certains SGBD comme postgresql) puis d'un suffixe qui caractérise la clé (pour permettre plusieurs index uniques sur une même table).

Exemple:
uk_societe_code_client

== Index performance ==
Certains champs sont souvent utilisés comme critère de recherche, de tri ou de jointure. Il convient dans ce cas, d'y mettre un index de performance. De tels indexes seront nommés avec un préfix <tt>idx_</tt> puis le nom de la table et le nom du champ sur lequel porte l'index.

Exemple:
idx_societe_user_creat

== Format de fichier DDL ==
Les fichiers qui contiennent la définition de la structure de la base (DDL) doivent être au nombre de 2 par tables:
Chaque table est définie dans son propre fichier dont le nom est <tt>llx_''matable''.sql</tt>.
On mettra un commentaire à côté de chaque champ pour en expliquer la signification.
Les clés étrangères et index de performance ou autres contraintes d'unicité sont définies dans un fichier séparé dont le nom est <tt>llx_''matable''.key.sql</tt>

Ces fichiers sont placés dans le répertoire '''install/mysql/tables''' pour les fichiers standards ou '''monmodule/tables''' pour les tables amenées par un module.

Exemple '''fichier table llx_matable.sql''':

<source lang="sql">
-- ===========================================================================
-- Copyright (C) 2008 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 2 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_matable
(
rowid integer AUTO_INCREMENT PRIMARY KEY,
field_one integer,
field_two integer NOT NULL,
fk_field integer,
field_date datetime,
tms timestamp
)type=innodb;
</source>

Exemple '''fichier clés/index llx_matable.key.sql''':

<source lang="sql">
-- ===========================================================================
-- Copyright (C) 2008 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 2 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>

== Règles de codage SQL ==
* Utilisation des alias/nommage de champs
Dans le cas des select on pourra utiliser les alias pour simplifier l'écriture des requêtes:
<source lang="sql">
select chp1, chpxxx2 as chp2 from table2 as t1, table2 as t2 where t1.chpx = t2.chpy
</source>
Toutefois, il ne faut pas utiliser ces alias sur des requêtes update car non compatible avec mysql 3.1.

* Les SELECT * sont interdits ! Chaque SELECT doit spécifier la liste complète des champs à récupérer. Cela permet d'éviter les confusions. Exemple:
<source lang="sql">
SELECT field_a, field_b, field_c FROM table_1 WHERE field_d = '$id'
</source>

* Dans les requêtes SQL, on quote les champs mais pas les numériques qui contiennent des montants destinés à être stockés dans des champs de type double ou real. Les quotes sur les numériques de type float provoquent parfois un stockage d'une valeur différente. Par exemple 412.62 dans le insert sera en fait stocké avec la valeur 412.61999512 en base (suite à des conversions chaines-numériques implicites) si le champ est de type double(24,8). Et seul le PHP voit 412.61999512. Les autres outils verront 412.62 donnant l'impression qu'il n'y a pas de problème. Et c'est le PHP qui a raison, il y a problème en base. En supprimant les quotes sur les numériques, cela va mieux.

Exemple:
<source lang="sql">
Bon: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', 412.62)
Mauvais: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', '412.62')
</source>

Remarque, le problème des float est général et pas seulement sur les accès base, il est présent dans tous les languages quand on travaille sur des nombres réels, aussi ils doivent être, dès que affectés, nettoyés par la fonction price2num avec le 2eme paramètre renseigné à:
'MU' (si il s'agit d'un prix unitaire), 'MT' (s'il s'agit d'un prix total) ou 'MS' (autres cas) selon le besoin.
Voir aussi le chapitre "Les nombres réels, montants et calculs" plus bas.

* Les fonctions NOW ou SYSDATE sont interdites au sein des ordres SQL. S'il faut saisir la date du moment dans un champ, la valeur doit venir du PHP et non du moteur de base de données. Ceci afin d'avoir une meilleure portabilité du code mais surtout d'avoir une gestion correcte des TimeZone.

== Règles de migration de base ==
* Les scripts de migration de structure sont les fichiers de type '''install/mysql/migration/a.b.c-x.y.z.sql'''. Dans un fichier de migration de n vers n+1, on ne détruit une table (DROP TABLE) qui n'est plus utilisée en n+1 que lors de la migration de la version n+1 vers n+2. Ceci afin de toujours conserver les tables deprecated le temps d'une version pour réparer une situation en cas d'erreur de migration.

== Spécificités MySQL ==
* Les tables doivent être au format InnoDB.
En effet, ce format gère les clés étrangères, les éventuelles restrictions qui y sont attachées et la notion d'intégrité de transactions requise pour avoir des données en base cohérente entre tables.

* Dolibarr doit fonctionner même avec les options '''strict''' de Mysql active.
Pour l'activer, ajouter la ligne suivante dans le fichier config du serveur Mysql (my.cnf)
<source lang="ini">
sql-mode="STRICT_ALL_TABLES,ONLY_FULL_GROUP_BY,NO_ZERO_DATE"
</source>

== Spécificités PostgreSQL ==
Seuls les fichiers pour Mysql doivent être maintenus.
Les fichiers pour les autres bases sont convertis "à la volée" par le driver Dolibarr de la base.

Il existe une exception.
Les requêtes "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>

Il n'en existe pas dans Dolibarr, mais pour vos modules Vous devriez faire tel que :
<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>

= Normes HTML =

* Tous les attributs dans les balises HTML doivent être *en minuscule* et quotés avec des *doubles quote*.

* Les liens href doivent être absolus en se basant sur la fonction dol_buildpath() pour obtenir un chemin absolu depuis un chemin relatif au répertoire htdocs. Pour les tags img, il faut faire appel à la fonction img_picto().
Par example:
<source lang="php">
print '<a href="'.dol_buildpath('/monrep/mapage.php').'">'.img_picto('Texte alt','nompictopng','').'</a>';
</source>

* Les tables HTML doivent avoir des colonnes sans valeures forcées, excepté pour les colonnes qui contiennent une information dont la longueur est non variable. Par exemple, une colonne avec un picto peut etre forcée à with="20px". Dans les autres cas, il faut éviter de forcer la largeur des colonnes. La raison est que, dans la plupart des cas, le navigateur fait un meilleur travail pour définir automatiquement la bonne largeur des colonnes qu'en forçant manuellement les largeurs. Et ceci marche quelquesoit la résolution de l'écran.

* Le javascript/ajax et l'appel aux scripts java dans les pages php est à proscrire. Si toutefois du code javascript est inclus, il doit être conditionné par le test sur "$conf->use_javascript_ajax"
<source lang="php">
if ($conf->use_javascript_ajax) {
... // Le code php qui génère du javascript est ici
}
</source>

* Les popups windows ne doivent pas être utilisées, sauf pour des tooltips (et restent conditionnées par le point ci-dessus).

* Les scripts externes sont écrits en Perl s'ils ne peuvent l'être en php, l'utilisation d'un autre langage n'est pas interdit mais doit être discuté au préalable dans la mailing list des développeurs.

= Normes Dolibarr et squelettes de code =

== Squelettes de code ==
Afin d'uniformiser le code et d'accélérer le développement de nouveaux composants dans Dolibarr, se trouvent dans le répertoire '''dev/skeletons''', 4 squelettes de code tout préparés.

* 1 qui sert d'exemple de descripteur de module: '''myModule.class.php'''
* 1 qui sert d'exemple de code pour faire une nouvelle classe: '''skeleton_class.class.php'''
* 1 qui sert d'exemple de code pour faire une nouvelle page: '''skeleton_page.php'''
* 1 qui sert d'exemple de code pour faire un script à exécuter en ligne de commande: '''skeleton_script.php'''

Servez-vous en comme exemple.
Notons que ces squelettes sont aussi utilisés par le générateur de code PHP qui est décrit dans la chapitre de développement de module Dolibarr pour accélérer vos développement.

== Les dates et TimeZone ==
Dolibarr se veut une application multi-utilisateur et multi-localisation. Il convient donc de stocker les dates dans le bon format. Pour éviter les problèmes de conversion, les règles suivantes doivent être appliquées:
* Une date en mémoire doit être au format Timestamp GMT.
* Une date stockée en base de données contient le Timestamp issue de la date soumise dans la requête en heure locale du serveur PHP. Cela ne concerne pas les dates mises à jour automatiquement par la base (champ '''tms''' en base).
Ainsi le 1er janvier 1970, 3 heures à Paris (TZ=+1) = 1er janvier 1970, 2 heures à Greenwich (TZ=0) sera stocké en mémoire par 7200 et sera soumis à la base de données avec la chaine '19700101030000' (PHP convertit en heure de son TZ et la base déconvertit avec son TZ qui est le même que celui de PHP).

Les méthodes select doivent donc traduire les champs dates lus qui sont au format chaine TZ de la base ('19700101030000') par appel de la méthode db->jdate afin de récupérer une information en mémoire au format Timestamp GMT. Et les méthodes insert doivent lors de la génération de la requête convertir la date mémoire connue en variable, par la méthode db->idate (Voir exemples générés par le squelette).

* Les dates mises à jour automatiquement par la base (champ '''tms''' en base) contiennent le Timestamp où la modification est faite selon le timezone de la base de donnée. Les méthodes select récupèrent cette donnée en mémoire au format Timestamp GMT en appliquant également le db->jdate. Si le timezone de la base de donnée diffère de celui du PHP (un des 2 est mal réglé), il peut donc y avoir des écarts entre date de création et modification.

* La manipulation de dates en PHP doit être faite en utilisant les fonctions dates de Dolibarr: '''dol_now(), dol_mktime(), dol_stringtotime(), dol_getdate(), dol_time_plus_duree()'''. Vous trouverez également d'autres fonctions prêtes à l'emploi dans le fichier '''date.lib.php'''.

== L'encodage UTF8/ISO ==
Dolibarr stocke les informations de manière suivante:
* En base de donnée, les données sont en UTF8 ou ISO. Cela dépend du pagecode de la base, donc des options à la création de cette base. Dans tous les cas le driver d'accès base Dolibarr (dans /lib/database) s'arrange à la lecture et insertion pour convertir vers et depuis de l'UTF8.
* Les données en mémoires sont donc stockées en UTF8 (instances d'objets PHP).
* Les pages web affichées à l'écran sont au format UTF8 (avec les versions < 2.5.1, c'est le vieux paramètre $character_set du fichier conf.php qui définissait le format de sortie).

== Les nombres réels, montants et calculs ==
En PHP comme dans d'autres langages (Java par exemple), les données non entières (float, real, double) ne sont pas fiables.
Essayer de faire par exemple
<source lang="php">
print 239.2 - 229.3 - 9.9;
</source>
Vous n'obtiendrez pas zéro mais un nombre très petit en puissance de 10 négative. Si vous obtenez zéro, vous pourrez trouvez d'autres exemples qui ne fonctionnent pas.
Le problème des float est général, une variable résultante de calcul de nombre réels doit SYSTEMATIQUEMENT être nettoyée par la fonction '''price2num()''' avec le 2eme paramètre renseigné à: 'MU', 'MT' ou 'MS' selon le besoin (voir doc fonction).
<source lang="php">
print price2num(239.2 - 229.3 - 9.9, 'MT');
</source>
S'il ne s'agit pas d'un prix sur lequel s'adapte les paramètres MU, MT ou MS, il faut utiliser la fonction '''round()'''.

== Création de tables ==
Ne pas créer de table à l'utilisation, c'est-à-dire à la '''première utilisation''' du module.
Si vous créez un module qui utilise des tables qui ne sont pas intégrées en standard dans le code de Dolibarr, veillez à suivre le didacticiel [[Développement module]] qui explique comment joindre des tables qui se créent à l'activation du module et non à son utilisation (voir plus haut).

== Logs ==
Ajouter des traces dans votre code avec la fonction
<source lang="php">
dol_syslog($yourmessage, LOG_INFO|LOG_DEBUG|LOG_WARNING|LOG_ERR);
</source>

== Répertoires de travail ==
Si vous avez besoin de créer un répertoire de travail, dans votre code, faites référence à ce répertoire par
'''DOL_DATA_ROOT.'/monmodule''''

Le répertoire peut être créé dans votre code à l'exécution par le code suivant:
<source lang="php">
$mymoduledir=DOL_DATA_ROOT.'/monmodule';
dol_mkdir($mymoduledir);
</source>

Si vous avez besoin d'un répertoire qui contiendra des données temporaires, ce répertoire doit être''' DOL_DATA_ROOT.'/monmodule/temp''''

= Design patterns et programmation objet =

== Design patterns de Création (GoF) ==
Design patterns défini par le Gang Of Four (voir la wikipédia sur les [[wikipedia:Patron de conception|Design patterns]]).
Dans Dolibarr, pas de mise en oeuvre de design patterns de création particulier.
On trouve des objets proches des Singletons et Fabriques conforme à 100% dans l'esprit mais pas dans la syntaxe, ceci afin d’être compatible avec le PHP 4 qui n'est pas un langage objet complet.

== Design patterns de Structure (GoF) ==
Design patterns défini par le Gang Of Four (voir la wikipédia sur les [[wikipedia:Patron de conception|Design patterns]]).
Dans Dolibarr, pas de mise en oeuvre de design patterns de structure particulier.

== Design patterns de Comportement (GoF) ==
Design patterns défini par le Gang Of Four (voir la wikipédia sur les [[wikipedia:Patron de conception|Design patterns]]).
Dans Dolibarr, pas de mise en oeuvre de design patterns de comportement particulier.

== Design patterns d'entreprises (Martin Fowler) ==

=== Mode d'organisation du code ===
[[wikipedia:Martin_Fowler|Martin Fowler]] a identifié 3 méthodes d'organisation du code appelées '''patterns''' ('''motifs'''):
* Le '''Transaction Script''' (Le code est linéaire en fonction d'une action utilisateur).
C'est le motif à l'ancienne utilisé dans les langages procéduraux.
Inconvénient: Redondance du code. Nécessité de connaitre le modèle physique pour développer les parties métiers.
* Le '''Domain Model'''
C'est un concept possible depuis les langages objets. Ce sont les procédures métiers (qui doivent être identifiés avant) qui servent de bases pour les classes objets.
Inconvénient: Motif complexe à maintenir.
* Le '''Table Module'''
Un intermédiaire entre les 2 précédents où l'on a une instance unique de classe par table de la base de données.

-> Comme le montre les squelettes de code (voir point précédent), Dolibarr se base sur le principe du '''Table Module'''.

=== Communication Logique métier - Données (ORM) ===
Il existe 3 modes de liaisons:
* Le '''Table And Row Data Gateway'''
C'est le plus simple. On crée une classe par table et chaque classe est un pont avec la table correspondante et propose les méthodes CRUD sur cette table (Create, Read, Update, Delete). Une instance de classe étant alors un enregistrement de la table. La classe ne contient que du code d'accès aux lignes ou colonnes de tables. Le code métier doit alors être ajouté dans d'autres classes. Les liens entre ces classes tables et les classes métiers devant être connues ou déduite de la connaissance du développeur.

Exemple: C'est le mode mis en oeuvre quand on utilise certains Frameworks d'ORM comme '''iBatis''' (http://ibatis.apache.org/).

* Le '''Active Record'''
Identique au précédent, mais on se permet d'ajouter quelques fonctions métiers sur la classe, à conditions que ces fonctions soient propres à la table ou à l'enregistrement. C'est le pattern qui offre le meilleur rapport fonctionnalité/complexité.

Exemple: C'est le mode choisi pour les développements Dolibarr et de nombreuses autres applications PHP qui ont leur propre framework et pratiques de développements.

* Le '''Data Mapper'''
Les classes représentent les entités du problème et non les données. Il faut donc doubler, tripler... ces classes avec des classes Mapper pour accéder aux données.
Plus "puriste" sur le papier car plus proche du métier, ce mode a aussi l'inconvénient d'être plus complexe sur le plan pratique.

Exemple: C'est le choix si on utilise le Framework d'ORM '''Propel''' (http://propel.phpdb.org/trac/). On le trouve donc sur des applications plus lourdes basées sur cet ORM entre autres.

-> Pour les développements Dolibarr, il est recommandé d'utiliser le mode de liaison '''Active Record''' qui offre les avantages d'un modèle proche du métier sans en avoir la complexité et sans trop masquer non plus la technique. C'est dans ce mode que le développement, la compréhension du code et la maintenance technique et/ou fonctionnelle semble la plus productive (ceci est toutefois un éternel débat entre les puristes et les pragmatiques, débat dans lequel personne ne peut vraiment avoir raison, car tout dépend des objectifs à atteindre).

Dolibarr suppliers France

2013-05-03T15:27:27Z

Iouston:

{{Dolibarr_suppliers}}

{{TemplateCompany|
name=1fonet Services|
profid=|
desc=Integrations and open source development
Specialist software open source.Dolibarr, Joomla! Oscommerce and creloaded. Complementary development of the module, component or application needs. Based in the PACA region work throughout France.|
web=http://www.1fonet.fr|
email=mailto:contact@1fonet.fr|
zip=13530|
town=Trets|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=A3SYS|
profid=|
desc=Intégration, assistance et développement.
Notre société forte d'une expérience de 20 ans dans l'intégration de divers ERP propose ses services aux entreprises souhaitant mettre en place l'ERP Dolibarr. Une plateforme dédiée est mise en place pour proposer des services de qualité à moindre coût.|
web=http://www.mon-dolibarr.fr|
email=mailto:courrier@mon-dolibarr.fr|
zip=59310|
town=Aix-les-Orchies (Nord - France)|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ATM Consulting [[File:Dolibarr_preferred_partner_int.png|120px]] |
profid=753 447 481 00015|
desc=Consulting company dedicated to small and medium enterprises information system optimization, we provide to our customers open-source based solutions to improve their information system efficiency. We offer hosting and support solutions and we are Dolibarr contributor, developer and integrator. "Open-source. Custom. Freedom"|
web=http://www.atm-consulting.fr|
email=mailto:contact@atm-consulting.fr|
zip=26000|
town=Valence|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=
}}

{{TemplateCompany|
name=AB2L|
profid=|
desc=Un Alsacien à votre service. Installation et configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur notre serveur. Nous vous accompagnons pour un démarrage rapide et serein. Nous sommes une société de service en logiciel libre fournissant un équivalent open source au logiciel propriétaire de tout type. |
web=http://www.ab2l.eu|
email=mailto:contact@ab2l.eu|
zip=67000|
town=Strasbourg|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Axopen IT Services|
profid=|
desc=L'entreprise Axopen propose toute une gamme de produits et services informatiques allant du conseil en système d'informations, développement de solutions sur mesure et intégration de solutions Open Source ou propriétaires. Nous sommes spécialisé en particulier dans l'intégration de solutions de gestion de la relation client Open Source telles que Dolibarr, SugarCRM ou VTiger... |
web=http://www.axopen.com|
email=mailto:contact@axopen.com|
zip=69001|
town=Lyon|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Adminrezo|
profid=|
desc=Computer Consulting and Services Company. WManagement computer. Designer / Integrator of computer solutions. Network Specialist, Commercial Management, Solution POS (cash). Based in Ile de France - Val de Marne (94)
|
web=http://www.adminrezo.eu|
email=|
zip=|
town=|
country=|
}}

{{TemplateCompany|
name=AKILIS|
profid=|
desc=AKILIS est une société éditrice de logiciels de gestion qui a fait le pari d’utiliser les nouvelles méthodes de travail pour développer des solutions clairs et efficaces. Notre mission est de vous proposer des solutions simples d'utilisation, ne demandant aucun entretien de votre part, ni aucune connaissance technique particulière. Notre outil est celui que VOUS utilisez quotidiennement : le Web.
AKILIS, c’est une équipe toujours disponible pour vous guider et vous écouter. Nous développons et améliorons sans cesse nos logiciels afin que ceux-ci répondent au mieux à votre activité et vos besoins.
AKILIS peut également, dans le cadre de besoin partculier, étudier avec vous un développement sur mesure. |
web=http://www.akilis.fr|
email=mailto:contact@akilis.fr|
zip=69200|
town=Vénissieux|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Altairis|
profid=|
desc=Développements spécifiques, Installation, Formation, Accompagnement à la mise en oeuvre, Support, Intégration.|
web=http://www.altairis.fr|
email=contact@altairis.fr|
zip=38,73|
town=Goncelin|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Auguria Conseil|
profid=|
desc=You are a Small Business, a very small firm, you need tools to increase profitability, and reliability facing competition. Auguria aims to help you develop the tools of information vectors of progress.|
web=http://www.auguria.net/|
email=contact@auguria.net|
zip=44300|
town=Nantes|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Atoo.Net|
profid=|
desc=Installation et configuration de l'ERP/CRM Dolibarr soit sur nos serveurs, soit en local dans votre entreprise. Aide à la prise en main et formation.|
web=http://www.atoo-net.com/|
email=contact@atoo-net.com|
zip=45160|
town=Olivet|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Blue-Click Informatique|
profid=|
desc=Nous proposons l'installation et la configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur votre hébergement Internet. De plus nous assurons la formation pour la prise en main de cet outil adapté aux TPE et PME.|
web=http://www.blue-click.fr|
email=|
zip=92,78|
town=Nanterre,Plaisir|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Cap-Networks|
profid=|
desc=Développeur indépendant d'application web, paramétrage et installation de Dolibarr, développement de modules spécifique. Basé dans la Saône et loire à Tournus (40min de Bourg en Bresse, 20min de Mâcon, 30min de Chalon sur Saône, 1h de Lyon), je contribue depuis 4 ans au développement de Dolibarr.|
web=http://www.dolibox.fr|
email=regis.houssin@cap-networks.com|
zip=71700|
town=Tournus|
country=fr|
service_hosting=(http://www.dolibox.fr)|
service_onlinesupport=(http://www.cap-networks.com/telemaintenance.php)|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=CRMPLUS.ME|
profid=|
desc=Consulting and Integration of Open Source ERP (Dolibarr and Vtiger) for VSE / SMEs and craftsmen: 3 simple steps to improve your productivity, protect your data and save time in your daily tasks.|
web=http://www.crmplus.me|
email=|
zip=|
town=|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Cyberlix-Consulting|
profid=|
desc=Assistance and service in computer science, specializing in free software. Located in Lille, Cyberlix Consulting offers hosting solutions, technical support and development for many open source software which Dolibarr.|
web=http://www.cyberlix-consulting.fr|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=D-BOG|
profid=|
desc=IT services company located in Beaune (21), moved around Dolibarr:
Installation, setup, configuration on the internal server or hosted;
Training agreement;
Outsourcing, on-site maintenance and remote.|
web=http://www.d-bog.com/|
email=|
zip=|
town=Beaune|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=D'Clic|
profid=|
desc=Conseil, Formation, Installation et Paramétrage pour les PME et les associations
Intervention sur site client. Situé à Annecy pour sa région|
web=http://www.dclic-erp.fr|
email=mailto:contact@dclic-erp.fr|
zip=74000|
town=Annecy|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=DiVA-Cloud|
profid=|
desc=DiVA-Cloud propose des applications OpenSource de gestion de la communication et de l'information pour les entreprises. Notre logithèque contient des applications de WebConference, ERP, CRM, CMS, GED, et bien d'autres... Toutes ces applications pré-configurés sont mises à disposition sur un environnement privé. |
web=www.diva-cloud.com |
email=mailto:contact@diva-cloud.com |
zip=81100|
town=Castres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=FUTUR TECH|
profid=|
desc=Prestataire de services pour artisans, TPE, PME :
Solutions open source, Internet, Sécurité, Sauvegarde, Antivirus, Gestion d'entreprise, Conseil, Formation, Installation et Paramétrage
Intervention sur site client. Situé entre Bordeaux et Libourne|
web=http://www.futur-tech.com|
email=mailto:info@futur-tech.com|
zip=33450|
town=IZON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=GPC.solutions|
profid=RCS de Pau 528 995 921|
desc={{Flag_fr}}Spécialiste Open Source et Logicel Libre et revendeur Agréé PME Google Apps for Business.

Nous proposons un gamme complète de services autour de Dolibar parmis lesquels l'hébergement cloud, le développement sur mesure, l'assistance et la formation.

Nous travaillons aussi à une intégration forte dans l'écosystème Google Apps.

{{Flag_en}}Open Source and Libre Software specialist and Authorized Google Apps for Business™ SMB reseller.

We offer a full range of services around Dolibarr including cloud hosting, custom development, support and training.

We're also working on a tight integration into the Google Apps ecosystem.|
web=http:// gpcsolutions.fr|
email=mailto:contact@gpcsolutions.fr|
zip=64000|
town=Pau|
country=fr|
service_hosting=http:// gpcsolutions.fr/dolibarr|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=gpcsolutions.png|
}}

{{TemplateCompany|
name=Infonel.net|
profid=|
desc=administrateur système open source indépendant:
Installation, paramétrage, configuration et sécurisation de dolibarr sur site client|
web=http://www.infonel.net|
email=|
zip=11100|
town=Narbonne|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=i.d & l - informatique durable & libre|
profid=|
desc=Conseil et intégration de solutions logicielles libres, dont Dolibarr, pour artisans, TPE, indépendants, commerçants, PME, associations...|
web=http://idl-mp.com|
email=http://idl-mp.com/contact/|
zip=31,32,09,82,81|
town=Toulouse et région toulousaine|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=iouston informatique|
profid=792 263 683 00015|
desc=iouston informatique, située à proximité de Nancy, Metz, Lunéville, est une société spécialisée auprès des assoiations, des TPE et des artisans commerçants. Nous installons et configurons dolibarr pour vous et nous formons vos équipes à son utilisation quotidienne.
Nous proposons de nombreux autres services, associés ou non à dolibarr.|
web=http://www.iouston.com|
email=mailto:allo@iouston.com|
zip=54370|
town=Bauzemont|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=LVS Informatique|
profid=|
desc=Development Specialist php, mysql. Creation, enhancement, customization of modules and components ...
Nos modifs/nos modules :
-cashdesk : prix en ttc, possibilité de modification du prix, du libellé...
-interfaçage avec GoogleAgenda (toutes les actions apparaissent dans GoogleAgenda)
-Mails/Télécopies reçus : apparaissent dans un onglet spécifique sur le tiers en question
-qualification Tiers
-Adresse Tiers vu dans GoogleMap
-creation de nbreux template excel/pdf
|
web=http://www.lvsinformatique.com|
email=|
zip=83860|
town=NANS LES PINS|
country=fr|
service_dev=yes|
service_local=yes|
}}

{{TemplateCompany|
name=Mephivio|
profid=|
desc=Services company with a computer located in Montpellier agglo, specializing in computer graphics, secretariat, Joomla web sites, client, opensource (Dolibarr, glpi, voip Elastix / Trixbox / PIAF etc ...)|
web=http://www.mephivio.fr/|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=Modulaweb : Technologies modulables orientées web.|
profid=|
desc=Développement d'applicatifs web, hébergement d'applications web, serveurs de fichiers et de sauvegarde, sites internet/intranet et intégration web, espaces clients, communication via internet (VoIP, messagerie instantanée), travail collaboratif. Spécialiste solutions libres pour l'entreprise (Zimbra, Dolibarr, Thaïs...) Région Languedoc-Rouissillon et voisines |
web=http://www.modulaweb.fr|
email=http://www.modulaweb.fr/portail/contact/|
zip=34000|
town=Montpellier|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=NLTechno [[File:Dolibarr_preferred_partner_int.png|120px]] |
desc=NLTechno is one of the most important contributor on Dolibarr and can host for you a Dolibarr database in a SaaS (Software As A Service) mode.|
profid=493 861 496 00021|
web=http://www.nltechno.com|
email=|
zip=92500|
town=Rueil Malmaison|
country=fr|
service_hosting=yes (http://www.dolicloud.com)|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=no|
service_formation=no|
logo=logo_nltechno.png}}

{{TemplateCompany|
name=Open-Concept.pro [[File:Dolibarr_preferred_partner_int.png|120px]] |
profid=537 828 717 00018|
desc=Open-concept.pro ([[Florian Henry]]) is dedicated to Open-Source ERP/CRM solition. Open-concept.pro ([[Florian Henry]]) is a contributor of Dolibarr sine 2010, and modules builder also|
web=http://www.open-concept.pro|
email=mailto:florian.henry@open-concept.pro|
zip=77380|
town=COMBS-LA-VILLE|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_openconcept.png}}

{{TemplateCompany|
name=Pascal Sené|
profid=|
desc=Logiciels libres et photographie.|
web=http://www.pascalsene.com|
email=contact@pascalsene.com|
zip=22,29,35,56|
town=Lannion|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ProbeSys|
profid=|
desc=Créée en 2003 par des passionnés du logiciel libre, [http://probesys.com ProbeSys] est une entreprise coopérative à l'image du secteur des nouvelles technologies : dynamique, réactive et participative. |
web=http://www.probesys.com|
email=mailto:contact@probesys.com|
zip=38600|
town=Fontaine|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Process Evolution|
profid=|
desc=Département Gecinfo: Société de Services et d'Ingénierie en Informatique.|
web=http://www.process-evolution.fr/|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=Syllene|
profid=|
desc=We install and configure the software Dolibarr to suit your needs and train your users. We can also provide hosting and maintenance of your application.|
web=http://www.syllene.net/|
email=|
zip=|
town=|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Teclib'|
profid=|
desc=
Teclib est une société de services en informatique au capital de 50 000€. Nous sommes implantés à Paris, Colmar (Alsace) et à Chartres (Région Centre). L'équipe teclib' rassemble 8 personnes au 31 juillet 2010. Spécialisée dans l'intégration de logiciels libres tels que Dolibarr, GLPI, Quotero, Nagios, Centreon, Zimbra... |
web=http://www.teclib.com|
email=mailto:contact@teclib.com|
zip=75010|
town=Paris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Tiaris|
profid=|
desc=Solutions and services for small businesses and merchants: e-commerce, maintenance, ERP/CRM Dolibarr, development telecommuting. ecommerce - dolibarr webservice based interface. Saas Offer Dolibarr + ecommerce connection for open source caddies (OsCommerce, Zencart, Crelaoded, Prestashop and others...)|
web=http://www.tiaris.fr/|
email=http://www.tiaris.fr/spip.php?page=contact|
zip=57870|
town=WALSCHEID|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=UTOPSYS - L'Informatique, Professionnelle.|
profid=|
desc=Maintenance, dépannage, conseil, audits, Green IT, solutions open-source de travail collaboratif, installation et maintenance Dolibarr. Bordeaux, CUB, Libourne.|
web=http://www.utopsys.fr|
email=|
zip=|
town=Libourne|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=WEBINFOPRO|
profid=|
desc=Society Computers and Internet service for small businesses located in the suburbs west of Paris. One of the main activities is the integration of open source software.|
web=http://www.webinfopro.fr/|
email=|
zip=|
town=|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

Dolibarr suppliers France

2013-05-03T15:25:46Z

Iouston:

{{Dolibarr_suppliers}}

{{TemplateCompany|
name=1fonet Services|
profid=|
desc=Integrations and open source development
Specialist software open source.Dolibarr, Joomla! Oscommerce and creloaded. Complementary development of the module, component or application needs. Based in the PACA region work throughout France.|
web=http://www.1fonet.fr|
email=mailto:contact@1fonet.fr|
zip=13530|
town=Trets|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=A3SYS|
profid=|
desc=Intégration, assistance et développement.
Notre société forte d'une expérience de 20 ans dans l'intégration de divers ERP propose ses services aux entreprises souhaitant mettre en place l'ERP Dolibarr. Une plateforme dédiée est mise en place pour proposer des services de qualité à moindre coût.|
web=http://www.mon-dolibarr.fr|
email=mailto:courrier@mon-dolibarr.fr|
zip=59310|
town=Aix-les-Orchies (Nord - France)|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ATM Consulting [[File:Dolibarr_preferred_partner_int.png|120px]] |
profid=753 447 481 00015|
desc=Consulting company dedicated to small and medium enterprises information system optimization, we provide to our customers open-source based solutions to improve their information system efficiency. We offer hosting and support solutions and we are Dolibarr contributor, developer and integrator. "Open-source. Custom. Freedom"|
web=http://www.atm-consulting.fr|
email=mailto:contact@atm-consulting.fr|
zip=26000|
town=Valence|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=
}}

{{TemplateCompany|
name=AB2L|
profid=|
desc=Un Alsacien à votre service. Installation et configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur notre serveur. Nous vous accompagnons pour un démarrage rapide et serein. Nous sommes une société de service en logiciel libre fournissant un équivalent open source au logiciel propriétaire de tout type. |
web=http://www.ab2l.eu|
email=mailto:contact@ab2l.eu|
zip=67000|
town=Strasbourg|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Axopen IT Services|
profid=|
desc=L'entreprise Axopen propose toute une gamme de produits et services informatiques allant du conseil en système d'informations, développement de solutions sur mesure et intégration de solutions Open Source ou propriétaires. Nous sommes spécialisé en particulier dans l'intégration de solutions de gestion de la relation client Open Source telles que Dolibarr, SugarCRM ou VTiger... |
web=http://www.axopen.com|
email=mailto:contact@axopen.com|
zip=69001|
town=Lyon|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Adminrezo|
profid=|
desc=Computer Consulting and Services Company. WManagement computer. Designer / Integrator of computer solutions. Network Specialist, Commercial Management, Solution POS (cash). Based in Ile de France - Val de Marne (94)
|
web=http://www.adminrezo.eu|
email=|
zip=|
town=|
country=|
}}

{{TemplateCompany|
name=AKILIS|
profid=|
desc=AKILIS est une société éditrice de logiciels de gestion qui a fait le pari d’utiliser les nouvelles méthodes de travail pour développer des solutions clairs et efficaces. Notre mission est de vous proposer des solutions simples d'utilisation, ne demandant aucun entretien de votre part, ni aucune connaissance technique particulière. Notre outil est celui que VOUS utilisez quotidiennement : le Web.
AKILIS, c’est une équipe toujours disponible pour vous guider et vous écouter. Nous développons et améliorons sans cesse nos logiciels afin que ceux-ci répondent au mieux à votre activité et vos besoins.
AKILIS peut également, dans le cadre de besoin partculier, étudier avec vous un développement sur mesure. |
web=http://www.akilis.fr|
email=mailto:contact@akilis.fr|
zip=69200|
town=Vénissieux|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Altairis|
profid=|
desc=Développements spécifiques, Installation, Formation, Accompagnement à la mise en oeuvre, Support, Intégration.|
web=http://www.altairis.fr|
email=contact@altairis.fr|
zip=38,73|
town=Goncelin|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Auguria Conseil|
profid=|
desc=You are a Small Business, a very small firm, you need tools to increase profitability, and reliability facing competition. Auguria aims to help you develop the tools of information vectors of progress.|
web=http://www.auguria.net/|
email=contact@auguria.net|
zip=44300|
town=Nantes|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Atoo.Net|
profid=|
desc=Installation et configuration de l'ERP/CRM Dolibarr soit sur nos serveurs, soit en local dans votre entreprise. Aide à la prise en main et formation.|
web=http://www.atoo-net.com/|
email=contact@atoo-net.com|
zip=45160|
town=Olivet|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Blue-Click Informatique|
profid=|
desc=Nous proposons l'installation et la configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur votre hébergement Internet. De plus nous assurons la formation pour la prise en main de cet outil adapté aux TPE et PME.|
web=http://www.blue-click.fr|
email=|
zip=92,78|
town=Nanterre,Plaisir|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Cap-Networks|
profid=|
desc=Développeur indépendant d'application web, paramétrage et installation de Dolibarr, développement de modules spécifique. Basé dans la Saône et loire à Tournus (40min de Bourg en Bresse, 20min de Mâcon, 30min de Chalon sur Saône, 1h de Lyon), je contribue depuis 4 ans au développement de Dolibarr.|
web=http://www.dolibox.fr|
email=regis.houssin@cap-networks.com|
zip=71700|
town=Tournus|
country=fr|
service_hosting=(http://www.dolibox.fr)|
service_onlinesupport=(http://www.cap-networks.com/telemaintenance.php)|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=CRMPLUS.ME|
profid=|
desc=Consulting and Integration of Open Source ERP (Dolibarr and Vtiger) for VSE / SMEs and craftsmen: 3 simple steps to improve your productivity, protect your data and save time in your daily tasks.|
web=http://www.crmplus.me|
email=|
zip=|
town=|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Cyberlix-Consulting|
profid=|
desc=Assistance and service in computer science, specializing in free software. Located in Lille, Cyberlix Consulting offers hosting solutions, technical support and development for many open source software which Dolibarr.|
web=http://www.cyberlix-consulting.fr|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=D-BOG|
profid=|
desc=IT services company located in Beaune (21), moved around Dolibarr:
Installation, setup, configuration on the internal server or hosted;
Training agreement;
Outsourcing, on-site maintenance and remote.|
web=http://www.d-bog.com/|
email=|
zip=|
town=Beaune|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=D'Clic|
profid=|
desc=Conseil, Formation, Installation et Paramétrage pour les PME et les associations
Intervention sur site client. Situé à Annecy pour sa région|
web=http://www.dclic-erp.fr|
email=mailto:contact@dclic-erp.fr|
zip=74000|
town=Annecy|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=DiVA-Cloud|
profid=|
desc=DiVA-Cloud propose des applications OpenSource de gestion de la communication et de l'information pour les entreprises. Notre logithèque contient des applications de WebConference, ERP, CRM, CMS, GED, et bien d'autres... Toutes ces applications pré-configurés sont mises à disposition sur un environnement privé. |
web=www.diva-cloud.com |
email=mailto:contact@diva-cloud.com |
zip=81100|
town=Castres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=FUTUR TECH|
profid=|
desc=Prestataire de services pour artisans, TPE, PME :
Solutions open source, Internet, Sécurité, Sauvegarde, Antivirus, Gestion d'entreprise, Conseil, Formation, Installation et Paramétrage
Intervention sur site client. Situé entre Bordeaux et Libourne|
web=http://www.futur-tech.com|
email=mailto:info@futur-tech.com|
zip=33450|
town=IZON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=GPC.solutions|
profid=RCS de Pau 528 995 921|
desc={{Flag_fr}}Spécialiste Open Source et Logicel Libre et revendeur Agréé PME Google Apps for Business.

Nous proposons un gamme complète de services autour de Dolibar parmis lesquels l'hébergement cloud, le développement sur mesure, l'assistance et la formation.

Nous travaillons aussi à une intégration forte dans l'écosystème Google Apps.

{{Flag_en}}Open Source and Libre Software specialist and Authorized Google Apps for Business™ SMB reseller.

We offer a full range of services around Dolibarr including cloud hosting, custom development, support and training.

We're also working on a tight integration into the Google Apps ecosystem.|
web=http:// gpcsolutions.fr|
email=mailto:contact@gpcsolutions.fr|
zip=64000|
town=Pau|
country=fr|
service_hosting=http:// gpcsolutions.fr/dolibarr|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=gpcsolutions.png|
}}

{{TemplateCompany|
name=Infonel.net|
profid=|
desc=administrateur système open source indépendant:
Installation, paramétrage, configuration et sécurisation de dolibarr sur site client|
web=http://www.infonel.net|
email=|
zip=11100|
town=Narbonne|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=i.d & l - informatique durable & libre|
profid=|
desc=Conseil et intégration de solutions logicielles libres, dont Dolibarr, pour artisans, TPE, indépendants, commerçants, PME, associations...|
web=http://idl-mp.com|
email=http://idl-mp.com/contact/|
zip=31,32,09,82,81|
town=Toulouse et région toulousaine|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=iouston informatique|
profid=792 263 683 00015|
desc=iouston informatique, située à proximité de Nancy, Metz, Lunéville, est une société spécialisée auprès des assoiations, des TPE et des artisans commerçants. Nous installons et configurons dolibarr pour vous et nous formons vos équipes à son utilisation quotidienne.
Nous proposons de nombreux autres services, associés ou non à dolibarr.|
web=http://www.iouston.com|
email=allo@iouston.com|
zip=54370|
town=Bauzemont|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=LVS Informatique|
profid=|
desc=Development Specialist php, mysql. Creation, enhancement, customization of modules and components ...
Nos modifs/nos modules :
-cashdesk : prix en ttc, possibilité de modification du prix, du libellé...
-interfaçage avec GoogleAgenda (toutes les actions apparaissent dans GoogleAgenda)
-Mails/Télécopies reçus : apparaissent dans un onglet spécifique sur le tiers en question
-qualification Tiers
-Adresse Tiers vu dans GoogleMap
-creation de nbreux template excel/pdf
|
web=http://www.lvsinformatique.com|
email=|
zip=83860|
town=NANS LES PINS|
country=fr|
service_dev=yes|
service_local=yes|
}}

{{TemplateCompany|
name=Mephivio|
profid=|
desc=Services company with a computer located in Montpellier agglo, specializing in computer graphics, secretariat, Joomla web sites, client, opensource (Dolibarr, glpi, voip Elastix / Trixbox / PIAF etc ...)|
web=http://www.mephivio.fr/|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=Modulaweb : Technologies modulables orientées web.|
profid=|
desc=Développement d'applicatifs web, hébergement d'applications web, serveurs de fichiers et de sauvegarde, sites internet/intranet et intégration web, espaces clients, communication via internet (VoIP, messagerie instantanée), travail collaboratif. Spécialiste solutions libres pour l'entreprise (Zimbra, Dolibarr, Thaïs...) Région Languedoc-Rouissillon et voisines |
web=http://www.modulaweb.fr|
email=http://www.modulaweb.fr/portail/contact/|
zip=34000|
town=Montpellier|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=NLTechno [[File:Dolibarr_preferred_partner_int.png|120px]] |
desc=NLTechno is one of the most important contributor on Dolibarr and can host for you a Dolibarr database in a SaaS (Software As A Service) mode.|
profid=493 861 496 00021|
web=http://www.nltechno.com|
email=|
zip=92500|
town=Rueil Malmaison|
country=fr|
service_hosting=yes (http://www.dolicloud.com)|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=no|
service_formation=no|
logo=logo_nltechno.png}}

{{TemplateCompany|
name=Open-Concept.pro [[File:Dolibarr_preferred_partner_int.png|120px]] |
profid=537 828 717 00018|
desc=Open-concept.pro ([[Florian Henry]]) is dedicated to Open-Source ERP/CRM solition. Open-concept.pro ([[Florian Henry]]) is a contributor of Dolibarr sine 2010, and modules builder also|
web=http://www.open-concept.pro|
email=mailto:florian.henry@open-concept.pro|
zip=77380|
town=COMBS-LA-VILLE|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_openconcept.png}}

{{TemplateCompany|
name=Pascal Sené|
profid=|
desc=Logiciels libres et photographie.|
web=http://www.pascalsene.com|
email=contact@pascalsene.com|
zip=22,29,35,56|
town=Lannion|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ProbeSys|
profid=|
desc=Créée en 2003 par des passionnés du logiciel libre, [http://probesys.com ProbeSys] est une entreprise coopérative à l'image du secteur des nouvelles technologies : dynamique, réactive et participative. |
web=http://www.probesys.com|
email=mailto:contact@probesys.com|
zip=38600|
town=Fontaine|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Process Evolution|
profid=|
desc=Département Gecinfo: Société de Services et d'Ingénierie en Informatique.|
web=http://www.process-evolution.fr/|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=Syllene|
profid=|
desc=We install and configure the software Dolibarr to suit your needs and train your users. We can also provide hosting and maintenance of your application.|
web=http://www.syllene.net/|
email=|
zip=|
town=|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Teclib'|
profid=|
desc=
Teclib est une société de services en informatique au capital de 50 000€. Nous sommes implantés à Paris, Colmar (Alsace) et à Chartres (Région Centre). L'équipe teclib' rassemble 8 personnes au 31 juillet 2010. Spécialisée dans l'intégration de logiciels libres tels que Dolibarr, GLPI, Quotero, Nagios, Centreon, Zimbra... |
web=http://www.teclib.com|
email=mailto:contact@teclib.com|
zip=75010|
town=Paris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Tiaris|
profid=|
desc=Solutions and services for small businesses and merchants: e-commerce, maintenance, ERP/CRM Dolibarr, development telecommuting. ecommerce - dolibarr webservice based interface. Saas Offer Dolibarr + ecommerce connection for open source caddies (OsCommerce, Zencart, Crelaoded, Prestashop and others...)|
web=http://www.tiaris.fr/|
email=http://www.tiaris.fr/spip.php?page=contact|
zip=57870|
town=WALSCHEID|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=UTOPSYS - L'Informatique, Professionnelle.|
profid=|
desc=Maintenance, dépannage, conseil, audits, Green IT, solutions open-source de travail collaboratif, installation et maintenance Dolibarr. Bordeaux, CUB, Libourne.|
web=http://www.utopsys.fr|
email=|
zip=|
town=Libourne|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=WEBINFOPRO|
profid=|
desc=Society Computers and Internet service for small businesses located in the suburbs west of Paris. One of the main activities is the integration of open source software.|
web=http://www.webinfopro.fr/|
email=|
zip=|
town=|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

Dolibarr suppliers France

2013-05-03T11:10:09Z

Iouston:

{{Dolibarr_suppliers}}

{{TemplateCompany|
name=1fonet Services|
profid=|
desc=Integrations and open source development
Specialist software open source.Dolibarr, Joomla! Oscommerce and creloaded. Complementary development of the module, component or application needs. Based in the PACA region work throughout France.|
web=http://www.1fonet.fr|
email=mailto:contact@1fonet.fr|
zip=13530|
town=Trets|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=A3SYS|
profid=|
desc=Intégration, assistance et développement.
Notre société forte d'une expérience de 20 ans dans l'intégration de divers ERP propose ses services aux entreprises souhaitant mettre en place l'ERP Dolibarr. Une plateforme dédiée est mise en place pour proposer des services de qualité à moindre coût.|
web=http://www.mon-dolibarr.fr|
email=mailto:courrier@mon-dolibarr.fr|
zip=59310|
town=Aix-les-Orchies (Nord - France)|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ATM Consulting [[File:Dolibarr_preferred_partner_int.png|120px]] |
profid=753 447 481 00015|
desc=Consulting company dedicated to small and medium enterprises information system optimization, we provide to our customers open-source based solutions to improve their information system efficiency. We offer hosting and support solutions and we are Dolibarr contributor, developer and integrator. "Open-source. Custom. Freedom"|
web=http://www.atm-consulting.fr|
email=mailto:contact@atm-consulting.fr|
zip=26000|
town=Valence|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=
}}

{{TemplateCompany|
name=AB2L|
profid=|
desc=Un Alsacien à votre service. Installation et configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur notre serveur. Nous vous accompagnons pour un démarrage rapide et serein. Nous sommes une société de service en logiciel libre fournissant un équivalent open source au logiciel propriétaire de tout type. |
web=http://www.ab2l.eu|
email=mailto:contact@ab2l.eu|
zip=67000|
town=Strasbourg|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Axopen IT Services|
profid=|
desc=L'entreprise Axopen propose toute une gamme de produits et services informatiques allant du conseil en système d'informations, développement de solutions sur mesure et intégration de solutions Open Source ou propriétaires. Nous sommes spécialisé en particulier dans l'intégration de solutions de gestion de la relation client Open Source telles que Dolibarr, SugarCRM ou VTiger... |
web=http://www.axopen.com|
email=mailto:contact@axopen.com|
zip=69001|
town=Lyon|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Adminrezo|
profid=|
desc=Computer Consulting and Services Company. WManagement computer. Designer / Integrator of computer solutions. Network Specialist, Commercial Management, Solution POS (cash). Based in Ile de France - Val de Marne (94)
|
web=http://www.adminrezo.eu|
email=|
zip=|
town=|
country=|
}}

{{TemplateCompany|
name=AKILIS|
profid=|
desc=AKILIS est une société éditrice de logiciels de gestion qui a fait le pari d’utiliser les nouvelles méthodes de travail pour développer des solutions clairs et efficaces. Notre mission est de vous proposer des solutions simples d'utilisation, ne demandant aucun entretien de votre part, ni aucune connaissance technique particulière. Notre outil est celui que VOUS utilisez quotidiennement : le Web.
AKILIS, c’est une équipe toujours disponible pour vous guider et vous écouter. Nous développons et améliorons sans cesse nos logiciels afin que ceux-ci répondent au mieux à votre activité et vos besoins.
AKILIS peut également, dans le cadre de besoin partculier, étudier avec vous un développement sur mesure. |
web=http://www.akilis.fr|
email=mailto:contact@akilis.fr|
zip=69200|
town=Vénissieux|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Altairis|
profid=|
desc=Développements spécifiques, Installation, Formation, Accompagnement à la mise en oeuvre, Support, Intégration.|
web=http://www.altairis.fr|
email=contact@altairis.fr|
zip=38,73|
town=Goncelin|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Auguria Conseil|
profid=|
desc=You are a Small Business, a very small firm, you need tools to increase profitability, and reliability facing competition. Auguria aims to help you develop the tools of information vectors of progress.|
web=http://www.auguria.net/|
email=contact@auguria.net|
zip=44300|
town=Nantes|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Atoo.Net|
profid=|
desc=Installation et configuration de l'ERP/CRM Dolibarr soit sur nos serveurs, soit en local dans votre entreprise. Aide à la prise en main et formation.|
web=http://www.atoo-net.com/|
email=contact@atoo-net.com|
zip=45160|
town=Olivet|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Blue-Click Informatique|
profid=|
desc=Nous proposons l'installation et la configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur votre hébergement Internet. De plus nous assurons la formation pour la prise en main de cet outil adapté aux TPE et PME.|
web=http://www.blue-click.fr|
email=|
zip=92,78|
town=Nanterre,Plaisir|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Cap-Networks|
profid=|
desc=Développeur indépendant d'application web, paramétrage et installation de Dolibarr, développement de modules spécifique. Basé dans la Saône et loire à Tournus (40min de Bourg en Bresse, 20min de Mâcon, 30min de Chalon sur Saône, 1h de Lyon), je contribue depuis 4 ans au développement de Dolibarr.|
web=http://www.dolibox.fr|
email=regis.houssin@cap-networks.com|
zip=71700|
town=Tournus|
country=fr|
service_hosting=(http://www.dolibox.fr)|
service_onlinesupport=(http://www.cap-networks.com/telemaintenance.php)|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=CRMPLUS.ME|
profid=|
desc=Consulting and Integration of Open Source ERP (Dolibarr and Vtiger) for VSE / SMEs and craftsmen: 3 simple steps to improve your productivity, protect your data and save time in your daily tasks.|
web=http://www.crmplus.me|
email=|
zip=|
town=|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Cyberlix-Consulting|
profid=|
desc=Assistance and service in computer science, specializing in free software. Located in Lille, Cyberlix Consulting offers hosting solutions, technical support and development for many open source software which Dolibarr.|
web=http://www.cyberlix-consulting.fr|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=D-BOG|
profid=|
desc=IT services company located in Beaune (21), moved around Dolibarr:
Installation, setup, configuration on the internal server or hosted;
Training agreement;
Outsourcing, on-site maintenance and remote.|
web=http://www.d-bog.com/|
email=|
zip=|
town=Beaune|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=D'Clic|
profid=|
desc=Conseil, Formation, Installation et Paramétrage pour les PME et les associations
Intervention sur site client. Situé à Annecy pour sa région|
web=http://www.dclic-erp.fr|
email=mailto:contact@dclic-erp.fr|
zip=74000|
town=Annecy|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=DiVA-Cloud|
profid=|
desc=DiVA-Cloud propose des applications OpenSource de gestion de la communication et de l'information pour les entreprises. Notre logithèque contient des applications de WebConference, ERP, CRM, CMS, GED, et bien d'autres... Toutes ces applications pré-configurés sont mises à disposition sur un environnement privé. |
web=www.diva-cloud.com |
email=mailto:contact@diva-cloud.com |
zip=81100|
town=Castres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=FUTUR TECH|
profid=|
desc=Prestataire de services pour artisans, TPE, PME :
Solutions open source, Internet, Sécurité, Sauvegarde, Antivirus, Gestion d'entreprise, Conseil, Formation, Installation et Paramétrage
Intervention sur site client. Situé entre Bordeaux et Libourne|
web=http://www.futur-tech.com|
email=mailto:info@futur-tech.com|
zip=33450|
town=IZON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=GPC.solutions|
profid=RCS de Pau 528 995 921|
desc={{Flag_fr}}Spécialiste Open Source et Logicel Libre et revendeur Agréé PME Google Apps for Business.

Nous proposons un gamme complète de services autour de Dolibar parmis lesquels l'hébergement cloud, le développement sur mesure, l'assistance et la formation.

Nous travaillons aussi à une intégration forte dans l'écosystème Google Apps.

{{Flag_en}}Open Source and Libre Software specialist and Authorized Google Apps for Business™ SMB reseller.

We offer a full range of services around Dolibarr including cloud hosting, custom development, support and training.

We're also working on a tight integration into the Google Apps ecosystem.|
web=http:// gpcsolutions.fr|
email=mailto:contact@gpcsolutions.fr|
zip=64000|
town=Pau|
country=fr|
service_hosting=http:// gpcsolutions.fr/dolibarr|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=gpcsolutions.png|
}}

{{TemplateCompany|
name=Infonel.net|
profid=|
desc=administrateur système open source indépendant:
Installation, paramétrage, configuration et sécurisation de dolibarr sur site client|
web=http://www.infonel.net|
email=|
zip=11100|
town=Narbonne|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=i.d & l - informatique durable & libre|
profid=|
desc=Conseil et intégration de solutions logicielles libres, dont Dolibarr, pour artisans, TPE, indépendants, commerçants, PME, associations...|
web=http://idl-mp.com|
email=http://idl-mp.com/contact/|
zip=31,32,09,82,81|
town=Toulouse et région toulousaine|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=iouston informatique|
profid=792 263 683 00015|
desc=iouston informatique, située à proximité de Nancy, Metz, Lunéville, est une société spécialisée auprès des assoiations, des TPE et des artisans commerçants. Nous installons et configurons dolibarr pour vous et nous formons vos équipes à son utilisation quotidienne.
Nous proposons de nombreux autres services, associés ou non à dolibarr.|
web=|
email=allo@iouston.com|
zip=54370|
town=Bauzemont|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=LVS Informatique|
profid=|
desc=Development Specialist php, mysql. Creation, enhancement, customization of modules and components ...
Nos modifs/nos modules :
-cashdesk : prix en ttc, possibilité de modification du prix, du libellé...
-interfaçage avec GoogleAgenda (toutes les actions apparaissent dans GoogleAgenda)
-Mails/Télécopies reçus : apparaissent dans un onglet spécifique sur le tiers en question
-qualification Tiers
-Adresse Tiers vu dans GoogleMap
-creation de nbreux template excel/pdf
|
web=http://www.lvsinformatique.com|
email=|
zip=83860|
town=NANS LES PINS|
country=fr|
service_dev=yes|
service_local=yes|
}}

{{TemplateCompany|
name=Mephivio|
profid=|
desc=Services company with a computer located in Montpellier agglo, specializing in computer graphics, secretariat, Joomla web sites, client, opensource (Dolibarr, glpi, voip Elastix / Trixbox / PIAF etc ...)|
web=http://www.mephivio.fr/|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=Modulaweb : Technologies modulables orientées web.|
profid=|
desc=Développement d'applicatifs web, hébergement d'applications web, serveurs de fichiers et de sauvegarde, sites internet/intranet et intégration web, espaces clients, communication via internet (VoIP, messagerie instantanée), travail collaboratif. Spécialiste solutions libres pour l'entreprise (Zimbra, Dolibarr, Thaïs...) Région Languedoc-Rouissillon et voisines |
web=http://www.modulaweb.fr|
email=http://www.modulaweb.fr/portail/contact/|
zip=34000|
town=Montpellier|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=NLTechno [[File:Dolibarr_preferred_partner_int.png|120px]] |
desc=NLTechno is one of the most important contributor on Dolibarr and can host for you a Dolibarr database in a SaaS (Software As A Service) mode.|
profid=493 861 496 00021|
web=http://www.nltechno.com|
email=|
zip=92500|
town=Rueil Malmaison|
country=fr|
service_hosting=yes (http://www.dolicloud.com)|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=no|
service_formation=no|
logo=logo_nltechno.png}}

{{TemplateCompany|
name=Open-Concept.pro [[File:Dolibarr_preferred_partner_int.png|120px]] |
profid=537 828 717 00018|
desc=Open-concept.pro ([[Florian Henry]]) is dedicated to Open-Source ERP/CRM solition. Open-concept.pro ([[Florian Henry]]) is a contributor of Dolibarr sine 2010, and modules builder also|
web=http://www.open-concept.pro|
email=mailto:florian.henry@open-concept.pro|
zip=77380|
town=COMBS-LA-VILLE|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_openconcept.png}}

{{TemplateCompany|
name=Pascal Sené|
profid=|
desc=Logiciels libres et photographie.|
web=http://www.pascalsene.com|
email=contact@pascalsene.com|
zip=22,29,35,56|
town=Lannion|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ProbeSys|
profid=|
desc=Créée en 2003 par des passionnés du logiciel libre, [http://probesys.com ProbeSys] est une entreprise coopérative à l'image du secteur des nouvelles technologies : dynamique, réactive et participative. |
web=http://www.probesys.com|
email=mailto:contact@probesys.com|
zip=38600|
town=Fontaine|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Process Evolution|
profid=|
desc=Département Gecinfo: Société de Services et d'Ingénierie en Informatique.|
web=http://www.process-evolution.fr/|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=Syllene|
profid=|
desc=We install and configure the software Dolibarr to suit your needs and train your users. We can also provide hosting and maintenance of your application.|
web=http://www.syllene.net/|
email=|
zip=|
town=|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Teclib'|
profid=|
desc=
Teclib est une société de services en informatique au capital de 50 000€. Nous sommes implantés à Paris, Colmar (Alsace) et à Chartres (Région Centre). L'équipe teclib' rassemble 8 personnes au 31 juillet 2010. Spécialisée dans l'intégration de logiciels libres tels que Dolibarr, GLPI, Quotero, Nagios, Centreon, Zimbra... |
web=http://www.teclib.com|
email=mailto:contact@teclib.com|
zip=75010|
town=Paris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Tiaris|
profid=|
desc=Solutions and services for small businesses and merchants: e-commerce, maintenance, ERP/CRM Dolibarr, development telecommuting. ecommerce - dolibarr webservice based interface. Saas Offer Dolibarr + ecommerce connection for open source caddies (OsCommerce, Zencart, Crelaoded, Prestashop and others...)|
web=http://www.tiaris.fr/|
email=http://www.tiaris.fr/spip.php?page=contact|
zip=57870|
town=WALSCHEID|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=UTOPSYS - L'Informatique, Professionnelle.|
profid=|
desc=Maintenance, dépannage, conseil, audits, Green IT, solutions open-source de travail collaboratif, installation et maintenance Dolibarr. Bordeaux, CUB, Libourne.|
web=http://www.utopsys.fr|
email=|
zip=|
town=Libourne|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=WEBINFOPRO|
profid=|
desc=Society Computers and Internet service for small businesses located in the suburbs west of Paris. One of the main activities is the integration of open source software.|
web=http://www.webinfopro.fr/|
email=|
zip=|
town=|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}