1.9.18 Released

Submitted by LedgerSMB_Team on

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

* Fix '<< Return' link on the e-mail screen being broken in some cases (#6858)
* Improve query performance by declaring stored functions STABLE (#6872)
* Fix added line being dropped from invoice while deleting another (#6788)

1.10.1 Released

Submitted by LedgerSMB_Team on

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)

1.9.17 Released

Submitted by LedgerSMB_Team on

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

* Fix HTML-encoding values on (PDF) printed documents (#6861)
* Fix removal of invoice line breaking entire UI interaction (#6807)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.9.17/README.md

Session expired immediately after logging in

Submitted by ehu on

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.

1.10.0 Released

Submitted by LedgerSMB_Team on

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:

Upgrade to LedgerSMB 1.10

Submitted by ehu on

Overview

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.