The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application. Please note
that this release fixes an important translation bug that was introduced
in 1.7.0, where only the menu was translated, instead of the entire UI.
This release contains the following fixes and improvements:
Changelog for 1.7.6
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.7.5
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.7.4
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.7.3
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.7.2
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.7.1
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release brings support for multiple exchange rates per currency
per day -- before, only a single rate per currency was supported.
Additionally, a lot of effort went into quality assurance and code
cleanup.
Short answer: Due to differences in the database schema in relation to storing foreign currency transactions.
Long answer: The database schema before 1.7 required 2 database rows in the acc_trans table to store functional currency and foreign currency amounts. As of 1.7, the schema stores these two amounts - which relate to the same journal line - into one database row. When migrating data from the old schema to the new one, the migration routine tries hard to identify pairs of rows which can be combined into a single row in the new schema.
This page contains the comprehensive version with the installation instructions for LedgerSMB 1.7 targetting a production installation from release tarballs and deals with these steps:
If you already have all of the above, please proceed to the "Preparing for first use" guide.
There are two steps to upgrading a LedgerSMB 1.5.x/1.6.x to 1.7:
The last step must be executed for each company database that's set up.