1.10

1.10.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.
This release contains the following fixes and improvements:

Changelog for 1.10.2

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)

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

This content is outdated and kept here for reference only!

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.

Installing LedgerSMB 1.10

Submitted by ehu on

This content is outdated and kept here for reference only!

Installation from tarballs

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:

1.10 release notes

Submitted by ehu on

 What's new in LedgerSMB 1.10

  • Ability to delete user login accounts
  • US/Washington tax module
  • User-modified workflows
  • Full support for running in a schema other than "public"
  • Batch aging statements printing and mailing with language selection
  • Webservices for GIFIs, SICs, Types of Business, Pricegroups, Warehouses and Languages
  • Experimental webservice for invoices
  • Default printer selection in user preferences
  • Language names in drop-downs in the language of the user

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.10