1.2.21 Available for Download

Submitted by Chris Travers on

LedgerSMB 1.2.21 has been released. The complete changelog is as follows:

Changelog for 1.2.21
* Corrected a number of templates with HTML issues (Luke)
* AR/AP Aging Report fixed, ignores payment after report date (Chris T)
* Minor documentation updates (Chris T)
* Fixed bug saving SIC (Adam T)

Architecture Approach (2010)

Submitted by Anonymous (not verified) on

1: Base Architecture Goals

The new architecture is designed to solve the following problems with the current codebase:

A) Maintenance difficulty. The current codebase is quite unstructured and difficult to maintain. 1.2.x has already been a bit of a mess due to the issues of fixing something one place and having it break something else.

Security advisory: Multiple Vulnerabilities

Submitted by Chris Travers on

Hi all;

It has been brought to our attention that a number of security vulnerabilities have been noted in SQL-Ledger. Several of these affect earlier versions of LedgerSMB, and three hotfixes have been released for problems that continue to affect the LedgerSMB codebase.

As always, we highly recommend testing all hotfixes before applying them to a production environment.

The CVE's mentioned here are the ones attached to SQL-Ledger. Subtle differences as to how these affect LedgerSMB are noted below.

Screenshots for 1.3

Submitted by Chris Travers on

This content is outdated and kept here for reference only!

We have been working long and hard on 1.3 for some time, so it is time we show some screenshots showing how things will be different. I have chosen three screen shots to highlight our new approach:

1) Bank Reconciliation has been entirely redesigned in 1.3 with a new workflow and it is better designed to handle large numbers of transactions. Additionally you can go back later and review a reconciliation set to see what cleared and what was outstanding. This screen shot shows a report for a work in progress.

2) The contact management section is redone. Customers/vendors can now have multiple accounts, contact information, shipping and billing info, notes, etc. This screen shot shows how this looks with Javascript enabled. Here Javascript is used to clean up the interface, and the links at the top switch between visible divs.

3) Payment screen, for single customer/vendor payments

4) Batch payment screen for paying or receiving money from several customers or vendors.

5) Order entry (in this case sales order)

Subscribe to