The LedgerSMB development team is happy to announce another new
version in the stable 1.5 release series of its open source ERP
and accounting application. This release includes all relevant
fixes from 1.4.37 and further polishes the 1.5 user experience.
Changelog for 1.5.1
Getting all the development dependencies and a working copy for LedgerSMB can be time consuming and complex. However, using our Docker Compose infrastructure reduces this to four simple steps:
The LedgerSMB development team is happy to announce yet another new
release of its open source ERP and accounting application. This release is
one in the Long Term Support 1.4 series and will be followed shortly with a
release in the current stable series (1.5). This release
contains the following fixes and improvements:
Changelog for 1.4.37
This content is outdated and kept here for reference only!
1.5 Screenshots
Before starting to update to 1.5, the following are differences to be aware of between 1.4 and 1.5:
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!
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.
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:
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:
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application. This release
contains the following fixes and improvements:
Changelog for 1.4.35
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application. This release
contains the following fixes and improvements: