Robert James Clay just wrote the -users list to make the following announcement:
The 1.3.15-2 package for LedgerSMB has been accepted into Debian
unstable. I expect that version of the package to migrate to Debian
testing (wheezy) by the end of this month.
LedgerSMB Debian source package page:
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.
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
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
This content is outdated and kept here for reference only!
Check the 1.5 installation instructions up to date instructions.
=============================================================
Update: mai 2012
This content is outdated and kept here for reference only!
IMPORTANT NOTE: The instructions on this page, are retained for historical purposes only.
For Up To Date installation instructions please refer to Installing LedgerSMB
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.
A lot of people are wondering how to manage their migration to LedgerSMB from SQL-Ledger. While there is no one simple answer that will suit everyone's situation, there is some general advice.
First thing to know is - you are among friends. LedgerSMB is built on a community of people who want to see the software and it's users succeed. Information is freely shared, and as long as you are prepared to have a go at helping yourself, we are happy to jump right in and help you do that!
We now have a mailing list, whether you are actively working on migrating to LedgerSMB or even if you are staying with SQL-Ledger for now and want some friendly community support, join up the User List to get SQL-Ledger to LedgerSMB migration help
The best course of action depends on your situation:
I had created a second database. To delete it, do I just drop the database from postgresql?
On a GNU-ish *nix platform use the script:
tools/delete-company-database.sh
it'll remove the roles and the database.
But I'm glad to be able to deny your conclusion above: the system will search on any partial match, both on the customer number or on the customer name. So, there's no need to spell them quite exactly.
Also, if you want the drop downs back, there's a setting in the System -> Defaults screen (third item below the currency settings input box; "Max per dropdown"). If you enter 99999 into that (assuming you don't have that many customers), you'll be presented the selection list you're used to.