1.3

LedgerSMB 1.3.22 released

Submitted by hasorli on

We have released LedgerSMB 1.3.22 in response to significant installation issues with new databases under 1.3.21. If you are planning on setting up additional companies, you should probably upgrade.

This release also corrects an issue with midsized databases where certain screens are slow. This was caused by the selection for all years being slow due to a missing index. If the AR/AP transaction screens are very slow, try upgrading here.

The complete changelog is below.

Best Wishes,
Chris Travers

LedgerSMB 1.3.20 has been released

Submitted by Chris Travers on

The LedgerSMB core team is pleased to announce the release of LedgerSMB 1.3.20. As time has progressed, bug reports have slowed as expected, and so we have an opportunity to address issues more rough edges. This process will continue as more people continue to discuss with us what would be needed to make their lives easier with the software.

LedgerSMB 1.3.19 has been released

Submitted by Chris Travers on

LedgerSMB 1.3.19 has been released. This release corrects two
significant issues and makes the application generally easier to use.
The two significant issues it fixes is that voided transactions were
including the original payments again, and that CSV exports had no
data. A large number of more minor problems were fixed including the
fact that some reports were requiring that the date be set in ISO
format, and fixed an encoding issue that caused corruption on
retrieval of some attached files (the files were stored correctly so

LedgerSMB 1.3.18 released

Submitted by Chris Travers on

This release corrects a few bugs that are specific to 1.3 and a few bugs which have been longstanding since before the fork. Additionally pricelists are now exported in ODS format. XLS output which has been broken for some time was removed.

The most important bugfixes are that ODS output now works, and selecting from the year and month dropdowns doesn't result in bogus dates being printed at the top of the report. Additionally an internal server error when running monthly requirements reports was corrected.

How do I "undo" or reverse a payment to a vendor?

Submitted by Anonymous (not verified) on

I have made a payment to a vendor, but entered an incorrect date, far in
the future. Consequently the payment does not show when I try to reconcile
the relevant bank statement.

How do I back-out the incorrectly entered payment?

Cash/Vouchers/Reverse Payment.

Then when you are done adding the payments you want to reverse,
approve the batch.

LedgerSMB 1.3.17 released

Submitted by Chris Travers on

This release corrects the internal server error on tax lookup issue, and it also corrects an issue that was found in file uploads. Additionally for those running the latest Math::BigInt and Math::BigFloat packages, one is_zero issue was found and fixed. A number of more minor bugfixes are included as well.

LedgerSMB 1.3.16 has been released.

Submitted by Chris Travers on

This release corrects a number of issues regarding international support, including an issue with UTF-8
characters not showing up properly in HTML invoices, some corrections in the aging report so that invoices are clustered by currency (with subtotals per currency), new user screen not respecting default country, and some enhancements for local tax rules support.

Please see the changelog below for more details.

Best Wishes,
Chris Travers

Changelog for 1.3.16

LedgerSMB 1.3.15 has been released.

Submitted by Chris Travers on

This release corrects a few bugs in installation and setup as well as early payment discounts. It also provides a means to print pricelists for a customer as PDF, or exporting as CSV so that they may be imported into a spreadsheet of your choice.
Please see the complete changelog below.

Best Wishes,
Chris Travers

1.3.14 released

Submitted by Chris Travers on

The LedgerSMB core team is proud to announce LedgerSMB 1.3.14. This
release corrects the final outstanding missing feature from 1.3.x,
namely the ability to edit pricelists per customer or vendor. At
this point there are no known features from 1.2.x that are missing in
1.3.x.

This release corrects a number of bugs including reconciliation
mappings not being set by default, the point of sale always using TCP
to communicate with the host for pole display purposes, unknown
databases incorrectly detected as SQL-Ledger, and more.