Dolibarr 24.0.1: the first bug-fix release of Dolibarr 24

A bug-fix release published under three weeks after 24.0.0

The Dolibarr project released version 24.0.1 on 7 September 2026. It follows 24.0.0, which came out on 20 August 2026, eighteen days earlier. It is the first bug-fix release of the 24 branch. The changelog compares it directly with 24.0.0 and contains only fix entries. No new feature appears in it. For an SME, the message is simple: this version does not change the way you work. It removes defects found by the first users of version 24. It also welcomes five new contributors, which shows that the release was tested by a wide group of people. If you read our article on the release of Dolibarr 24 and 23.0.4, you know that 24.0.0 is recent. The sources we read give no figures or overall assessment, so we stick to the list of fixes published on the release page.

Access rights and administrator accounts

Several fixes concern permissions. One stops non-administrator users from deleting administrator accounts, with compatibility planned for multi-company setups. Another enforces write permission on the website in the old file manager. A third fixes an access denied message that appeared when changing the account type in the bank account creation form. Finally, a file transfer error used to be reported as successful even though the upload had been refused. That is no longer the case. These points concern the governance of your instance. If several colleagues hold extended rights, this is a good reason not to stay on 24.0.0. The sources describe no security flaw and no CVE identifier for this release, and we do not invent any. For the rest of your practices, our guide on securing Dolibarr in production remains the reference.

Donations, contracts, leave and interventions

The donations module receives three fixes: a variable used before it was defined in the list, a defect in the creation of the donations table, and a missing statistics page. On the contracts side, cloning excluded pure supplier companies in the third-party filter, and service lines had no background on the card. Overlapping leave requests are now rejected. Interventions get back their new statistics layout, which was missing. A charity that manages donations, a services company that clones its contracts or a team that approves leave may therefore meet these defects on 24.0.0. They are everyday details, rarely blocking, but they waste time when they come back every week. A user who has already worked around them with manual entry should check the behavior after the update.

Finance, banking and reports

A report on cash-basis revenue could cause a division by zero. This is fixed. The result of the remaining-to-pay calculation during a bulk payment is now converted to a floating-point number. SEPA mandate output respects the configured directory. The name of a foreign key in an accounting template is shortened. A clone link for miscellaneous payments used a file system path instead of a URL. A CSRF check is fixed on cheque deposits, where a filter was wrong. In practice, administrative and accounting teams benefit most. If you then export to an accounting tool, these fixes limit the discrepancies you have to justify at month end. For statement matching, you can reread our article on bank reconciliation in Dolibarr. Again, this is about reliability, not new functionality.

Installation, multi-entity and table prefix

Several fixes concern the infrastructure. Some queries used a hard-coded llx_ table prefix, notably in the contract list, in the API token list and in the ticket contact check. If your database uses another prefix, these screens could fail. Some installation SQL scripts never created their table. Broken SQL concatenations are repaired. The local taxes class handles multi-entity better, and dictionary lines from another entity could no longer be edited from a child entity. That defect is fixed. In the API, the switch that counts calls had no effect, and it now works. Finally, a log file used to grow too large. Multi-company environments and databases with a custom prefix are therefore the first concerned by this release.

Products, manufacturing, printing and emails

On the product side, the default is now to generate no document template. Attribute variant items are correctly linked. In manufacturing, the bill of materials calculation ignored the quantity of lines with a fixed quantity. This is fixed. Printing uses the configured printer when testing a template. In emails, the template sender is kept after an attachment is added, and the references in the sender field are restored. The quantity of an edited line is localized according to the language, and dates get support in editable fields. A workshop that launches manufacturing orders or a sales team that sends quotes by email may feel these fixes in the first week. Nothing says they affect every use, so test the ones that are yours.

Planning the update to 24.0.1

If you are still on version 23, note that 23.0.4 was released on 20 August 2026, at the same time as 24.0.0. Nothing in the sources forces you to change branch, so choose according to your own schedule. If you already run 24.0.0, moving to 24.0.1 is the reasonable step. Proceed in this order.

• Back up the database and the documents directory before any operation.
• Apply the update first to a copy of your instance, with the same modules and the same table prefix.
• Test the screens you really use: donations, contracts, financial reports, SEPA mandates, emails and the API.
• Schedule the switch to production outside data entry hours, then check the logs the next day.
• Get support if your instance has custom modules: our maintenance team prepares and validates these updates. Reach us through the contact page.