News

1.3.4 released

Submitted by Chris Travers on

Hi all;

This release corrects a number of localization bugs regarding number
handling, updates some documentation, fixes one minor database
creation/upgrade bug, and more. Because it involves a few database
changes, it does require running the setup.pl against each database.

Best Wishes,
Chris Travers

The complete changelog is:

1.3.3 released

Submitted by Chris Travers on

Hi all;

LedgerSMB 1.3.3 has been released. It corrects a number of important
bugs. Users of 1.3.x are likely to benefit considerably from moving
to this new version. The most important fix is for internal server
errors when the most recent Math::BigFloat and Math::BigInt libraries
are used with LedgerSMB. Other fixes address changing countries for
employees, a few user interface glitches, and some localization fixes.

LedgerSMB 1.3.2 released

Submitted by Chris Travers on

Hi all;

The LedgerSMB core team is proud to announce the release of 1.3.2. This release corrects a number of UI glitches, a fix to our translation templates, a few fixes to the test cases, and more. It is recommended that all users of 1.3.x upgrade to this version as soon as possible.

The complete changelog is:

Changelog for 1.3 Series
Initial Release: Monday, Oct 12 2011
Supported Presently

1.3.1 released

Submitted by Chris Travers on

LedgerSMB 1.3.1 has been released. Fixes include changes to allow multi-language printing of invoices and several fixes to time cards and proiect reports.

The complete changelog is as follows:

LedgerSMB 1.3.0 Released

Submitted by Chris Travers on

The LedgerSMB development team is very proud to release LedgerSMB
1.3.0. This release continues our strong commitment to security, data
integrity, and and robustness, introducing improved functionality in
many core areas, and adding new features that many businesses will
find necessary.

1.2.25 Released

Submitted by Chris Travers on

Hi all;

LedgerSMB 1.2.25 has been released. This code has been reviewed for a
the type of SQL injection issues recently reported and all
questionable cases addressed. While some cases are believed to be
exploitable, others have been fixed as a mere precaution.

SQL injection issues on 1.2.x should generally be presumed to be
severe unless we offer reasons otherwise.

Users 1.2.x are advised to upgrade as soon as possible.

Best Wishes,
Chris Travers