LedgerSMB 1.3.25 released

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.3.25. With this release we mostly have focused on cosmetic changes for the software, thus reducing the sorts of user interface issues that are likely to cause minor headaches for users of the software.

There are, however, three significant issues that have been corrected in this release which make an upgrade recommended for everyone:

1: In previous versions, term of payment on sales orders and purchase orders were not properly respected.

I want to upgrade PostgreSQL from 8.3 to 8.4+. How does that work?

First of all, you need to backup all your company databases followed by an upgrade of your PostgreSQL installation. There are plenty of places on the web to explain how to do that. The high-level process is to install the two versions in parallel and run the pg_upgradecluster command.

When the technical upgrade has succeeded, however, you're not ready to see the performance improvements promised by the 8.4+ versions of PostgreSQL with respect to the menu-generation. This is because the database doesn't automatically use the new 8.4+ code definitions.

LedgerSMB 1.3.24 released, FCGI and PSGI support

The LedgerSMB development team is proud to release 1.3.24. This release contains a fairly large number of polishing bug-fixes, but also important Plack-related fixes for folks wanting to use LedgerSMB in FCGI and PSGI environments. These fixes ensure that LedgerSMB can be run caching some of the dependencies and thus will be far more responsive than when run as a simple CGI application.

How do I change the templates to my liking?

The templates use the Template Toolkit scripting language to generate actual content.
Depending on the typesetting language, the files use
* (Xe)LaTeX; or
* plain text
as the typesetting system.

While LaTeX and XeLaTeX are extremely similar, some differences exist, mainly in the area of font selection and document preamble.

Latex cheat sheet - http://www.stdout.org/~winston/latex/

Did anybody document their 1.2 to 1.3 upgrade process?

Yes; there's at least one known (relatively current) story at https://wiki.koumbit.net/LedgerSmbUpgrade#A1.2.25_to_1.3.18 (written by 'anarcat' on irc)

Should I install LedgerSMB modules in /usr/share or /usr/local?

In general: neither. The advice is to have the full source tree in /opt/ledgersmb/<version>.

I just installed LedgerSMB, but http://localhost/ledgersmb/login.pl says "Forbidden"

The default configuration limits access to the /ledgersmb/login.pl page to connections from localhost ( only for maximum security.

If you want to allow connections from other locations, it's highly advisable to use encrypted (VPN) connections to access your ledger in order to maintain good security.

How do I submit my changes to the project?

# diff -u "original file" "new edited file" > “diff file”

Submit your patches ( “diff file” through the Sourceforge project tracker. If you are going to do somewhat largish changes, it's best to discuss how to do them on the developers list. That increases chances for acceptance which is in general the best solution for you and the lsmb community.

Select all parts in orders

All parts in order, from '2012-04-21' and '2012-04-22':

select p.partnumber, count(*), sum(qty) from orderitems o join parts p on p.id = o.parts_id where trans_id in (select id from oe where not closed and transdate between '2012-04-21' and '2012-04-22') group by p.partnumber;

Grant permission to manage users (on a terminal)

GRANT lsmb_"your company"__users_manage TO "your username";


Subscribe to 1.3