The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.13 which is available from the SourceForge download page.
This release corrects all known issues with running LedgerSMB 1.2.x on PostgreSQL 8.3 and although other issues may surface, we will fix those as they are brought to our attention.

Please click 'Read more' to view the change log for 1.2.13.

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.11 which is available from the SourceForge download page. Some of these fixes are important for Canadian users, as it fixes some tax issues that are affected by the GST change.

Please click 'Read more' to view the change log for 1.2.11.

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.10 which is available from the SourceForge download page.

The changelog for this release is quite long, please click 'Read more' for all the details.

This release corrects a number of SQL injection issues as well as a number of other bugs. The changelog is:

Changelog for 1.2.8

• Fix SQL errors saving customer price lists (Chris T, 1754172)
• Fixed AR/AP reversal issues (Victor S, 1752439, 1753358)
• Fixed various scoping errors (Chris T, 1703347, 1753360)
• Fixed: Timecards ignore price matrix (Chris T, 1754099)
• Fixed scoping issues in IS.pm (Chris T, 1754576, 1754579, 1768678)
• Fixed bugs with reversing invoices (Victor S, 1756387, 1755928, 1755355)

(From Chris Travers' post to LedgerSMB-devel list)

We have opted to release a milestone release on sourceforge with the changes towards 1.3.0 to-date. Please note that this release is largely aimed as a community update and is not suited well to either active development (due to rapid changes of the codebase) or for production use.

Highlights include:

• a new template system (Seneca)
• RESTful web services interface code (Jason)
• Normalized Contact Management schema to be basis for other CRM functionality (Josh D)

The LedgerSMB team is pleased to announce that version 1.2.6 was released on June 28th

The following issues have been corrected:

• customer_id field error in AP transactions
• invalid HTML in ca.pl
• Error searching for customer by address
• Error saving orders, projects, etc. with custom fields.
• Error saving project with NULL customer id.
• .po header information showing up on balance sheet.

Additionally, the following preventative measures were included:

• Meta tags were added to force the use of utf-8 by default
  

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.5 which is available from the SourceForge download page.

This release includes major bugfixes for users of 1.000,00 and 1000,00
number formats. Users with these number formats are urged to upgrade
as soon as possible.

The release also includes a number of UTF-related fixes. Users who
require umlauts, multibyte charaters, and accents should also upgrade.

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.4 which is available from the SourceForge download page.

What's changed since 1.2.3 (click 'Read More' to see all):

• Fixed internal functions avgcost() and lastcost() to not use float
• Fixed error posting vendor invoice with fraction costs
• Fixed sales tax display issue on invoice/order entry screen
• Fixed inconsistant error when setting to recur 0 times

What has been fixed (since 1.2.0):
1) Backups created from the user interface were sending out blank backups.
2) Sales tax was selecting the wrong acounts for invoices and printing.
3) Data entry screens were showing incorrect amounts for sales tax.
4) Logos were not printing.
5) Data update script was not using correct password.
6) Account deletion was giving a database error
7) Some 1.2.1 users were unable to log in after upgrading

All the above items have been corrected

Known issues:
1) All localization is currently using the ledgersmb.conf entry which

LedgerSMB 1.2.1 has been released. This release corrects a very
serious bug in the new sales tax system and all users who collect
sales tax are advised to upgrade as soon as absolutely possible. We
have also fixed the following more minor issues: