The LedgerSMB team has released LedgerSMB 1.3.7. The bugfix list is
very long but this release moves the backup tools to the database
administration utility (setup.pl) and corrects a number of other
issues. Additionally default languages can now be set for invoices
both per company database and per customer. The complete changelog
is below.
Best Wishes,
Chris Travers
The LedgerSMB team has released LedgerSMB 1.3.6. This release
corrects a significant number of issues involving a couple report
issues, some permissions a couple of translation strings, and more,
and it adds sample XeLaTeX templates for those who may wish to use
them. The complete changelog is below. Many thanks to the
contributors to this release.
Best Wishes,
Chris Travers
Username and password have to be sent via auth fields.
company= is an accepted argument.
This works:
http://localhost/ledgersmb/login.pl?company=database_name
I manage several companies on LedgerSMB, can I login to any of these companies with one user?
Applies to LedgerSMB 1.3.x -->
V. 0.1 - 22. Nov 2011
I have 100 companies though on my system and decide to change my password, wouldn't I have to change it a 100 times (one for each company)? What would be the best approach to setting up a user that could be used on several companies (databases)?
Hi all;
The LedgerSMB core team has released version 1.3.5. This is a
maintenance/bugfix release which corrects a significant number of
bugs, particularly for users of extended character sets. A number of
other i18n issues were fixed, as were some issues with sales order
generation from timecards, permissions and menu issues, and more. The
complete changelog is included below.
IBest Wishes,
Chris Travers
Is there a place where we could buy some consulting for LedgerSMB?
or a minimal setup according to our specs?
Take a look at Commercial Support
Short error:
Math::BigInt: couldn't load specified math lib(s), fallback to Math::BigInt::FastCalc
Hi all;
This release corrects a number of localization bugs regarding number
handling, updates some documentation, fixes one minor database
creation/upgrade bug, and more. Because it involves a few database
changes, it does require running the setup.pl against each database.
Best Wishes,
Chris Travers
The complete changelog is:
Sql ledger has the option to add a barcode to a part.
In 1.4, you will be able to add a barcode per make/model record.
How are barcodes added when using LedgerSMB?
Sort term solution:
It's not optimal for a UPC management but it solves the immediate problem:
Add a space separated list with the barcodes to the partnumber field
The partnumber is the "Number" filed on the same line as "Description" in the "Add Part" page.
And yes, "space separated list" works in the POS interface. (If you scan one of the codes in the space separated list )
We don't know enough about the ideosyncracies with your laws to evaluate that. But quite frankly Free Software sometimes poses an issue with local regulation. If you go with LedgerSMB, I'd recommend working with us to detail any shortcomings and get those resolved.
You can help us to make a list over "X country" laws and LedgerSMB shortcomings according your countrys law.