1.10.3 Released
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:
Changelog for 1.10.3
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:
Changelog for 1.10.3
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:
Changelog for 1.10.2
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:
Changelog for 1.10.1
* Fix batch details screen failing to load (#6850)
* Update 1.10.0 Perl dependency changes in Changelog
* Fix wrong taxes being applied to invoices (#6857)
* Fix HTML-encoding values on (PDF) printed documents (#6861)
When I log in, LedgerSMB 1.8 or higher immediately says my session has expired. What can I do to fix this?
Short answer: add the "--preload-app" flag to the Starman command line.
Long answer: As of LedgerSMB 1.8, session information is stored in an encrypted cookie. To make sure the encryption key is unique for every installation, a new encryption secret is being generated each time LedgerSMB is started. However, Starman (without the "--preload-app" flag) loads the application in each forked worker separately, leading to different encryption secrets in each worker with the indicated behaviour as a result.
The LedgerSMB development team is happy to announce the first release
of a new release branch: 1.10.0. This series features a wide variety
of new features, improvements, bug fixes and cleanup. To name a few:
This content is outdated and kept here for reference only!
Company database upgrades are supported all the way back from 1.4 directly to 1.10, using the 1.10 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.9 structure, while upgrades adjust the existing structure for 1.10.
This content is outdated and kept here for reference only!
This page contains the comprehensive version with the installation instructions for LedgerSMB 1.10 targetting a production installation from release tarballs and deals with these steps:
This content is outdated and kept here for reference only!
This page explains how to set up LedgerSMB's first company after having completed installation, e.g. through the docker-compose.yml file. Please note that your full URL may differ depending on your installation method.
When upgrading from 1.8 or older, please read the 1.9 release notes.
I'm writing this script in bash that I want to use to invoke functionality in LedgerSMB. Can I use curl and the webservices API to do that?
Yes you can. In order to do so, you must first create a valid session for your follow-up requests by authenticating: