I just upgraded from 1.3.7 to 1.3.9, ran setup.pl for my database, and now
went to the login page. It still shows version 1.3.7 on the login page
even after clearing my browser cache. Did I miss an upgrade step, or does
this sound like a bug I should write up? I also noticed that a previous
bug that was fixed in this version (i.e. Logout page displaying in
appropriate locale) still appears to be broken, so I want to make sure that
my upgrade was successful before moving forward. I did notice the
following from my Apache error_log:
[Thu Dec 15 12:12:21 2011] [error] [client 192.168.1.53] DBD::Pg::st
execute failed: ERROR: column "version" does not exist, referer:
http://192.168.1.10/ledgersmb/setup.pl
[Thu Dec 15 12:12:21 2011] [error] [client 192.168.1.53] LINE 1: SELECT
version FROM defaults, referer: http://192.168.1.10/ledgersmb/setup.pl
[Thu Dec 15 12:12:21 2011] [error] [client 192.168.1.53] ^
at /usr/lib/perl5/site_perl/5.14.2/LedgerSMB/Database.pm line 298.,
referer: http://192.168.1.10/ledgersmb/setup.pl
[Thu Dec 15 12:12:21 2011] [error] [client 192.168.1.53] DBD::Pg::st
fetchrow_hashref failed: no statement executing at
/usr/lib/perl5/site_perl/5.14.2/LedgerSMB/Database.pm line 299., referer:
http://192.168.1.10/ledgersmb/setup.pl
[Thu Dec 15 12:12:21 2011] [error] [client 192.168.1.53] Issuing rollback()
due to DESTROY without explicit disconnect() of DBD::Pg::db handle
dbname=StallusBoutique_Test at scripts/setup.pl line 61., referer:
http://192.168.1.10/ledgersmb/setup.pl
--
Best Regards,
Steven Marshall
------------------------------------------------------------------------------
10 Tips for Better Server Consolidation
Server virtualization is being driven by many needs.
But none more important than the need to reduce IT complexity
while improving strategic productivity. Learn More!
http://www.accelacomm.com/jaw/sdnl/114/51507609/
_______________________________________________
Ledger-smb-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
