LedgerSMB failed to print to printer. I did the following changes in BP.pm, :-

#open( OUT, '>', $form->{OUT} ) or $form->error("$form->{OUT} : $!");
#by fhng
# 16/4/08
#--------
open( OUT, "|$form->{OUT} >/dev/null 2>&1") or $form->error("$form->{OUT} : $!");

Then, it print.

Also, the error message is not helpful, e.g. if LATEX is not installed, printing will fail with out much debug info but just display Error

Thanks.

Make sure you have TexLive installed. Older TeTeX was recommended but according to Ubuntu repositories, TexLive is the new package to install.

Hi

I am currently building an online travel suite for a client of mine who is interested to integrate with a full accounts package.

Is this software similiar to Sage ?

Awaiting your replies

Thanks and best regards
Justin Fenech

Hi, is this project still on ???? what is the latest version ?

any body can reply to my post a couple of dayss ago ?

Thanks

Hi

I am currently building an online travel suite for a client of mine who is interested to integrate with a full accounts package.

Is this software similiar to Sage ?

Awaiting your replies

Thanks and best regards
Justin Fenech

Guys, if you turn on the Tracker module one will more easily find what they've posted and/or commented on.

I found LedgerSMB after my search for an Open Source accounting package. But truthfully, I am completely puzzled by the installation process of LedgerSMB. I've searched and searched only find instructions that were line after line of command line instructions (none of which were familiar). However, in defense of what I found, they were written back in Nov 2007.

Here are just a couple of the examples that I found:
http://www.howtoforge.com/ledgersmb_debian_etch

Q: How could I set it up ledgersmb to support SSL connection?

SSL support on Apache is handled by configuring Apache. For having LedgerSMB connect to PostgreSQL using SSL, you can set the PGSSLMODE environment variable to 'require' in the ledgersmb.conf. Note that by default, LedgerSMB will try to connect to PostgreSQL via SSL and fall back to unsecured connections if this is not available.

I foresee problem here, password could be misused.