Screenshots for 1.10
This content is outdated and kept here for reference only!
- Read more about Screenshots for 1.10
- Log in or register to post comments
This content is outdated and kept here for reference only!
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.4
For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.10.4/README.md
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.9.19
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.9.18
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
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.9.17
For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.9.17/README.md
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: