No description

Find a file

w3houde aebf05486b Fix #38386 restore origin from db before reception line update handler (#38558 ) * Fix #38386 restore origin from db before reception line update handler PR #36134 (standalone reception, commit `dc4a28cd0b`) changed the $origin / $origin_id init at the top of htdocs/reception/card.php so that an empty origin no longer falls back to 'reception' and the origin_id fallbacks are gated on a non-empty $origin. The earlier block that restored $origin from the loaded $object->origin (still on 22.0 at line 136) was dropped at the same time, leaving the restoration only in the render section that runs much later (around line 1953 on develop). When the line edit form on an existing reception submits, it posts action=updateline and id=N with no origin field, so $origin stays empty when the action handler at line 762 is reached. The standalone branch requires the global RECEPTION_STANDALONE to be set and the origin branch requires $origin and $origin_id > 0, so a regular reception falls through both branches and the line update (quantity, comment, batch, extrafields) is silently dropped. Header data and status changes still work because they use other handlers. Re-introduce the post-fetch restoration right after actions_fetchobject.inc.php so the action handler sees the same origin context the page had when the form was rendered. The fix is minimal: only restore when an id was loaded and the local variable is still empty, so flows that genuinely carry an origin in the POST (the create-from-supplier-order form) are untouched. Reported by @AndiFoFFN on 23.0.3. Same regression on develop. Signed-off-by: Dolicraft <contact@dolicraft.com> * Fix #38386 address standalone-mode regression and refresh view after save Address review feedback from @sonikf on PR #38558: - Gate the post-fetch origin restore on $object->origin_id > 0 so a standalone reception (origin_id = 0) is not affected. With the prior version, Reception::fetch hydrated $object->origin to the literal 'commande' fallback (line 548 'For compatibility'), and the restore block then assigned 'commande' to the local $origin, breaking the standalone branch of the updateline handler. - Prefer $object->origin_type over the deprecated $object->origin alias. - Redirect after a successful updateline so the page leaves edit mode and re-reads the saved values, matching the cancel path and the header-data save handlers. Without it the view stayed on the edit form even after the row was correctly written. Signed-off-by: Dolicraft <contact@dolicraft.com> * Fix #38386 drop redundant isset on origin_id to satisfy phpstan CommonObject::$origin_id is declared @var int non-nullable, so the isset() guard around the int comparison was redundant and phpstan rejects 'Property in isset() is not nullable'. The > 0 test alone is equivalent for the original intent (skip the restore for standalone receptions, whose origin_id is 0). Signed-off-by: Dolicraft <contact@dolicraft.com> --------- Signed-off-by: Dolicraft <contact@dolicraft.com> Co-authored-by: Dolicraft <contact@dolicraft.com>		2026-06-02 17:42:45 +02:00
.github	Fix ci file	2026-04-13 16:32:49 +02:00
.phan
.tx
dev	Merge branch '22.0' of git@github.com:Dolibarr/dolibarr.git into 23.0	2026-05-25 01:07:38 +02:00
doc	Clean files	2026-01-07 19:01:54 +01:00
htdocs	Fix #38386 restore origin from db before reception line update handler (#38558 )	2026-06-02 17:42:45 +02:00
scripts	Clean files	2026-01-07 19:01:54 +01:00
test	Fix #GHSA-5cfw-655w-vqp8	2026-03-29 20:31:54 +02:00
.codeclimate.yml
.editorconfig
.gitattributes
.gitignore
.mailmap
.pre-commit-config.yaml	Disable beautysh. Overload of work with this is 100x higher than the	2026-02-27 14:32:47 +01:00
.travis.yml	Automated merge from 22.0 to 23.0 by tool pullmerge.sh	2026-03-16 10:20:01 +01:00
ChangeLog	Merge branch '22.0' of git@github.com:Dolibarr/dolibarr.git into 23.0	2026-05-25 01:07:38 +02:00
composer.json.disabled
COPYING
COPYRIGHT	FIX update COPYRIGHT file to reflect removed libraries	2026-03-07 18:53:20 +01:00
DCO
phpstan.neon.dist	Fix CI	2026-01-19 18:16:57 +01:00
pyproject.toml
README.md
robots.txt	Clean files	2026-01-07 19:01:54 +01:00
SECURITY.md	Doc	2026-04-03 23:21:17 +02:00

README.md

DOLIBARR ERP & CRM

Dolibarr ERP & CRM is a modern software package that helps manage your organization's activities (contacts, quotes, invoices, orders, stocks, agenda, human resources, ecm, manufacturing…).

It's an Open-Source Software suite (written in PHP with JavaScript enhancements) designed for small, medium or large companies, foundations and freelancers.

You can freely use, study, modify or distribute it according to its license.

You can use it as a standalone application or as a web application to access it from the Internet or from a LAN.

Dolibarr has a large community ready to help you, free forums and preferred partners ready to offer commercial support should you need it

LICENSE

Dolibarr is released under the terms of the GNU General Public License as published by the Free Software Foundation; either Version 3 of the License, or (at your option) any later version (GPL-3+).

See the COPYING file for a full copy of the license.

Other licenses apply for some included dependencies. See COPYRIGHT for a full list.

INSTALLING

There is a lot of different solutions to install Dolibarr.

Using packages

If you have low technical skills and you're looking to install Dolibarr ERP/CRM with just few clicks, you can use one of the packaged versions (see next chapter if you have IT knowledge) :

DoliWamp for Windows
DoliDeb for Debian, Ubuntu
DoliRpm for Red Hat, Fedora, OpenSuse, Mandriva or Mageia
The Docker image (see chapter "Using Docker")

Releases can be downloaded from official website.

Using the generic step by step setup (recommended for IT users)

You can use any web server supporting PHP (Apache, Nginx, ...) and a supported database (MariaDB, MySQL or PostgreSQL) to install the standard version:

Verify that your installed PHP version is supported see PHP support.
Uncompress the downloaded .zip archive to copy the dolibarr/htdocs directory and all its files inside your web server root or get the files directly from GitHub (recommended if you know git as it makes it easier if you want to upgrade later):

git clone https://github.com/dolibarr/dolibarr -b x.y (where x.y is the main version like 9.0, 19.0, ...)
Set up your web server to use dolibarr/htdocs as root if your web server does not already define a directory to point to.
Create an empty htdocs/conf/conf.php file and set write permissions for your web server user (write permission will be removed once install is finished)
From your browser, go to the dolibarr "install/" page

The URL will depend on how your web configuration directs to your dolibarr installation. It may look like:

http://localhost/dolibarr/htdocs/install/

or

http://localhost/dolibarr/install/

or

http://yourdolibarrvirtualhost/install/
Follow the installer instructions

Using Docker images

Dolibarr is also available as a Docker image. Installation instructions are available here.

Using ready to use SaaS/Cloud offers

If you lack the time to install it yourself, consider exploring commercial 'ready-to-use' Cloud offerings (refer to https://saas.dolibarr.org). Keep in mind that this third option comes with associated costs.

UPGRADING

Dolibarr supports upgrading, usually without the need for any (commercial) support (depending on if you use any commercial extensions). It supports upgrading all the way from any version after 2.8 without breakage. This is unique in the ERP ecosystem and a benefit our users highly appreciate!

Follow these step-by-step instructions to seamlessly upgrade Dolibarr to the latest version:

At first make a backup of your Dolibarr files & then see
Verify that your installed PHP version is supported by the new version see PHP support.
Overwrite all old files from the 'dolibarr' directory with files provided in the new version's package.
At your next access, Dolibarr will redirect you to the "install/" page to follow the upgrade process. If an install.lock file exists to lock any other upgrade process, the application will ask you to remove the file manually (you should find the install.lock file in the directory used to store generated and uploaded documents, in most cases, it is the directory called "documents").

WHAT'S NEW

See the ChangeLog file.

FEATURES

Main application/modules (all optional)

Third-Parties Management: Customers, Prospects (Leads) and/or Suppliers + Contacts
Members/Membership/Foundation management

Product Management

Products and/or Services catalogue
Stock / Warehouse management + Inventory
Barcodes
Batches / Lots / Serials
Product Variants
Bill of Materials (BOM)
Manufacturing Orders (MO)
Workstations / Workplaces

Customer/Sales Management

Customers/Prospects + Contacts management
Opportunities or Leads management
Commercial proposals management (online signing)
Customer Orders management
Contracts/Subscription management
Interventions management
Ticket System (+ Knowledge management)
Partnership management
Shipping management
Customer Invoices/Credit notes and payment management
Point of Sale (POS)

Supplier/Purchase Management

Suppliers/Vendors + Contacts
Supplier (pricing) requests
Purchase Orders management
Delivery/Reception
Supplier Invoices/Credit notes and payment management
INCOTERMS

Finance/Accounting

Invoices/Payments
Bank accounts management
Direct debit and Credit transfer management (European SEPA)
Accounting management
Donations management
Loan management
Margins
Reports

Collaboration

Shared calendar/agenda (with ical and vcal import/export for third-party tools integration)
Projects & Tasks management
Event organization
Ticket System
Surveys

HR - Human Resources Management

Employee leave management
Expense reports
Recruitment management
Employee/staff management
Timesheets

Other application/modules

Electronic Document Management (EDM)
Bookmarks
Reporting
Data export/import
Barcodes
LDAP connectivity
Click-To-Dial integration
Mass emailing
RSS integration
Social platforms linking
Payment platforms integration (PayPal, Stripe, Paybox...)
Email-Collector
AI support via API

(around 100 modules available by default, 1000+ addons at the official marketplace Dolistore.com)

Other general features

Multi-Language Support (Localization in most major languages)
Multi-users and groups with finely-grained rights
Multi-Currency
Multi-Company (by adding an external module)
Very user-friendly and easy to use
Customizable dashboards
Highly customizable: enable only the modules you need, add user personalized fields, choose your skin, several menu managers (can be used by internal users as a back-office with a particular menu, or by external users as a front-office with another one)
APIs (REST, SOAP)
Code that is easy to understand, maintain and develop (PHP with no heavy framework; trigger and hook architecture)
Support a lot of country-specific features:
- Spanish Tax RE and IRPF
- French NPR VAT rate (VAT called "Non Perçue Récupérable" for DOM-TOM)
- Canadian double taxes (federal/province) and other countries using cumulative VAT
- Tunisian tax stamp
- Argentina invoice numbering using A,B,C...
- Greece fetch customer vat details from AADE, all invoice types, MyData(external free module)
- ZATCA e-invoicing QR-Code
- Compatible with European directives (2006/112/CE ... 2010/45/UE)
- Compatible with data privacy rules (Europe's GDPR, ...)
- ...
Flexible PDF & ODT generation for invoices, proposals, orders...
...

System Environment / Requirements

PHP
MariaDB, MySQL or PostgreSQL
Compatible with all Cloud solutions that match PHP & MySQL or PostgreSQL prerequisites.

See exact requirements on the Wiki

Extending

Dolibarr can be extended with a lot of other external applications or modules from third-party developers available at the DoliStore.

WHAT DOLIBARR CAN'T DO YET

These are features that Dolibarr does not yet fully support:

Tasks dependencies in projects
Payroll module
Native embedded Webmail, but you can send email to contacts in Dolibarr with e.g. offers, invoices, etc.
Dolibarr can't do coffee (yet)

DOCUMENTATION

Administrator, user, developer and translator's documentation are available along with other community resources in the Wiki.

CONTRIBUTING AND RELEASE PROCESS

This project exists thanks to all the people who contribute. Please read the instructions on how to contribute (report a bug/error, a feature request, send code, ...) [Contributing]

A View on Contributors:

The release process is described into the file dev/build/makepack-howto.md

CREDITS

Dolibarr is the work of many contributors over the years and uses some fine PHP libraries.

See COPYRIGHT file.

Follow Dolibarr project on: