Installation and upgrades

• A Dolibarr installation, version 19.0 or later. The version is shown under HomeAbout, and at the bottom of every page.
• PHP 7.4 or later, the minimum version declared by all six descriptors.
• The external modules folder, htdocs/custom/, present and writable if you use the interface.
• The Dolibarr module that the installed module depends on — Commercial proposals or Third parties, depending on the case. Each module page states it.
• An administrator account, for the time it takes to activate the module.

This is the shortest route, and the one to try first.

1. Download the module’s zip file from the DoliStore to your computer.
2. In Dolibarr, open HomeSetupModules/Applications.
3. Open the “Deploy/install external app/module” tab, choose the zip and upload it. Dolibarr unpacks it into htdocs/custom/ itself.
4. The module appears in the list. Enable it with the switch on its row.

If this tab is missing or the upload fails, module uploads have been disabled on this installation, or the custom folder is not writable. Use the file method instead.

For shared hosting where uploading through the interface is blocked, or for a server you access over SSH.

1. Unzip the file on your computer.
2. Upload the resulting folder to htdocs/custom/, without renaming it. You should end up with, for example, htdocs/custom/dolixmasse/core/modules/…, and not htdocs/custom/dolixmasse/dolixmasse/….
3. Check that the files can be read by the web server’s account. After an FTP upload, this is the check that settles most cases.
4. Reload HomeSetupModules/Applications: the module is in the list. Enable it.

Activation creates what the module needs to create — its history table when it has one, its complementary attribute when it adds one. It deletes nothing.

Permissions are then granted under HomeUsers & Groups, on the Permissions tab of the user or group concerned.

1. Get the new version from the DoliStore.
2. Disable the module in the module list. Disabling deletes no data: not the tables, not the settings, not the values entered.
3. Replace the module’s folder in htdocs/custom/ with the new one, or upload the zip again through the deployment tab.
4. Enable the module again. The settings and the history are found exactly as they were.

The version history on each module page is taken from the ChangeLog.md file shipped with the module: there cannot be two different stories.

Disabling a module removes its screens and its columns. What it wrote to the database stays — that is deliberate, so that disabling by mistake destroys nothing. Here is what that covers, module by module.

Five checks, in this order. They cover most cases.

1. Is the folder in the right place? The module folder must sit directly in htdocs/custom/ and bear exactly its technical name — the one given on its page. A folder nested twice (custom/dolixmasse/dolixmasse) is the most common cause.
2. Can the web server read the files? After unpacking over FTP or SSH, the files sometimes belong to an account other than the web server’s. The module then stays invisible in the list.
3. Is the Dolibarr version recent enough? All six modules require Dolibarr 19.0 or later and PHP 7.4 or later. The Dolibarr version is shown under HomeAbout.
4. Is the module it depends on enabled? Each module page states the Dolibarr module to enable first — Commercial proposals or Third parties, depending on the case. Without it, the expected screen does not appear.
5. Have the permissions been granted? A module that is enabled but has no permission granted stays invisible to the user. Permissions are granted under HomeUsers & Groups, on the Permissions tab.