1.11

1.11.2 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. Many thanks
to John Imrie (@ThePilgrim on GitHub.com) for fixing Locale::CLDR not
to depend on the 'bignum' module! We now depend on this latest release
of Locale::CLDR. This release contains the following fixes and improvements:

Changelog for 1.11.2

* Fix trial balance drill down showing partial results (#7657)
* Specify Locale::CLDR minimum version to fix numbers shown as 'HASH()' (#7671)

1.11.1 Released

Submitted by LedgerSMB_Team on

The LedgerSMB development team is happy to announce a new
line of releases of its open source ERP and accounting
application: 1.11. This mail announces both 1.11.1 as well
as 1.11.0. Due to bad interaction with one of the Perl
dependencies shipped with Perl 5.36+ and the fact that the
Docker images are based on Debian Bookworm (shipping 5.36),
the general announcement of the new release series was held
back after the release of 1.11.0. 1.11.1 should fix this
issue.

Highlights of changelog for 1.11.0

Installing LedgerSMB 1.11

Submitted by ehu on

Installation from tarballs

This page contains the comprehensive version with the installation instructions for LedgerSMB 1.7 targetting a production installation from release tarballs and deals with these steps:

  • Installing the LedgerSMB Perl module dependencies
  • Configuring the PostgreSQL server
  • Configuring a webserver
  • Configuring LedgerSMB

If you already have all of the above, please proceed to the "Preparing for first use" guide.

1.11 release notes

Submitted by ehu on

 Be sure to check the UPGRADE NOTES below!

What's new in LedgerSMB 1.11

This release features a new, fresh logo! Next to that, there are:

  • Barcode reader support added (back) to invoices
  • Reclassification of negative (current) assets to liabilities
  • Tracking of the relationship between reversed and reversing transactions

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.

Does LedgerSMB support "sub-accounts"?

Submitted by ehu on

Yes. LedgerSMB has a mechanism called "Account headings". The headings are the opposite of what Intuit explains about Quickbooks for their subaccount support: Quickbooks splits an account into multiple and aggregates those new accounts into the old one for reporting. To achieve the same in LedgerSMB, you create multiple accounts and one or more headings. LedgerSMB then aggregates the totals of the accounts per heading. The system used by LedgerSMB closely resembles what MYOB describes about their accounts and headers.

Yes.

Subscribe to 1.11