Hi Ryle,
It appears to me that you are trying to run LedgerSMB directly
under windows, and that you are trying to set it up as a CGI
application.
In theory, running under windows should still be possible,
However, we don't recommend you run as CGI anymore.
W
As a note, if you do this, you will not be able to assign groups to the new
instance unless you assign them to the old instance. This limitation is
removed in branches/1.4 and will be fixed in 1.4.1. If you need to fix in
the meantime you can run this on the copy of the db via psql:
select setti
Hi Louis,
On Tue, Sep 16, 2014 at 7:26 PM, Louis wrote:
>
> Is there a tool for copying a production lsmb db into a fresh development
> db.
>
>
Yes, with setup.pl you can copy your production database to a new database
which you can use to test/develop your business. One remark applies: roles
ar
I'm now up to the database upgrade, and after entering some vendor
numbers and customer numbers that the system seemed to be asking for,
and the country/default accounts, I click "upgrade" and I get a
premature end of script from setup.pl
The old data base seems to be trashed, because if I re
Thanks, Chris!
Brian
Brian Wolf
Phone: 410.367.2958
Email: br...@activustech.com
Try out Activus
Secure Pa
On Sat, Dec 1, 2012 at 5:21 PM, Brian Wolf wrote:
> One of our clients started with LedgerSMB just a few weeks ago. They
> have been "practicing" with LedgerSMB, and now they'd like to really start
> using it. They would like us to clear the database of transactions,
> orders, etc. Deleting r
You are running SVN /trunk. The user management aspects of SVN /trunk have
not been completed yet. If you would like to install LedgerSMB for
production, I would suggest 1.2.13. If you are interested in development
and would like assistance with this, please ak on the -devel list.
Sorry for any
I noticed a new AM.pm (#1938) in branches/1.2/ and tried it out. It
fixes the backup file problem I noted below on Mac OS X 10.11. Many
thanks for the prompt fix!
Paul Bente
On Dec 4, 2007, at 2:13 PM, Paul Bente wrote:
> Executing pg_dump -Fc on the database from the command line
> produce
On further research this is not a PostgreSQL bug. I upgraded to
PostgreSQL 8.2.5 using Marc Liyanage's package (http://
www.entropy.ch) and used AM.pm rev 1866 to make sure I was using
latest versions on Mac OS X 10.4.11 (PPC).
Executing pg_dump -Fc on the database from the command line produ
Paul Bente wrote:
> Before posting to pgsql-hackers I thought it would be clearer to
> state the specific pg_dump command used by ledgersmb to create the
> backup file. Please edit the following to the correct translation of
> the Perl code. It was not clear to me how or where the file spec w
Before posting to pgsql-hackers I thought it would be clearer to
state the specific pg_dump command used by ledgersmb to create the
backup file. Please edit the following to the correct translation of
the Perl code. It was not clear to me how or where the file spec was
included, but I know
On Nov 28, 2007, at 13:28 PM -0500, Seneca wrote:
>I'm running on PostgreSQL 8.1.3 (yes, I know I should upgrade) on OS X
>10.4 and have never seen pg_restore work (same error as you). Anyway,
>in the file LedgerSMB/AM.pm on (or near, I'm working of of svn here)
>lines 1629 and 1658 there are
On Wed, Nov 28, 2007 at 12:32:24PM -0500, Paul Bente wrote:
> Any ideas on how to troubleshoot this? I can't go much farther with
> ledgersmb until I have a reliable backup / restore.
I'm running on PostgreSQL 8.1.3 (yes, I know I should upgrade) on OS X
10.4 and have never seen pg_restore work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 12:32:24 -0500
Paul Bente <[EMAIL PROTECTED]> wrote:
> Ledgersmb-1.2.9 + latest AA.pm, CT.pm, OE.pm, and Sysconfig.pm;
> PostgreSQL 8.2.4; Mac OSX 10.4.10
> Use System > Backup > Save to File to create a backup file. Attempt
>
This sounds like the Pg-database.sql did not import smoothly for some
reason.
Most likely reason is that plpgsql may not be available. To correct this,
you can log in as the db superuser (usually "postgres") and run the command:
create language plpgsql;
Then try to run the db import scripts agai
15 matches
Mail list logo