| LedgerSMB

Screenshots for 1.5

Submitted by ehu on Sat, 01/07/2017 - 08:57

This content is outdated and kept here for reference only!

1.5 Screenshots

Read more about Screenshots for 1.5

Upgrading to LedgerSMB 1.5

Submitted by ehu on Fri, 12/23/2016 - 13:27

Before starting to update to 1.5, the following are differences to be aware of between 1.4 and 1.5:

JavaScript in the browser
Additional data constraints
PSGI / Apache configuration
Printed document templates (e.g. invoice templates)
Database schema maintenance

See below for explanations of each of these differences.

Important note: before trying to migrate your database to a new version of LedgerSMB, create a backup of the database!

Read more about Upgrading to LedgerSMB 1.5

1.5.0 Released

Submitted by ehu on Sun, 12/18/2016 - 04:05

The LedgerSMB project is proud to announce the release of 1.5.0, the start of a new line of maintenance releases.

This release can be summarized as a major user experience boost through improvements in performace, look and stability. Performance improvements are being achieved by moving from per-request-invoked CGI-scripts to a preloaded-PSGI application as well as moving to a single-page web application using the Dojo toolkit.

Read more about 1.5.0 Released

1.4.36 Released

Submitted by ehu on Sat, 12/10/2016 - 01:09

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application. This release
fixes a regression of the 1.4.30 release where the use of overpayments
was incorrectly accounted for in the customer balance (over all balance
is correctly accounted). We have a FAQ to help you repair your customer
balance in case your books were affected by this bug:

Read more about 1.4.36 Released

How do I fix out-of-balance overpayments?

Submitted by freelock on Wed, 12/07/2016 - 09:03

How do I clean up my books as a result of Issue #2346, URGENT: Use Overpayments creates accounting errors?

What you need to do is look for rows in payment_links which have type=0

Then, in acc_trans, you need to identify those rows which have an entry_id of a row which has a 0 amount. That row is probably an fx_transaction row.

The preceding entry_id row is likely one for the same transaction, with a non-zero, non-fx_transaction amount.

You need to insert a new row into the payment_links table with:

Read more about How do I fix out-of-balance overpayments?