Today we'were fighting against a weird behaviour of our koha instalation. Finally we found what was hapenning: somebody change the owner of /etc/koha.conf. I've added a Warning that lets us guess were the problem cames from. Andres --- /usr/local/koha2/intranet/modules/C4/Context.pm 2005-01-19 10:09:02.365398944 -0300 +++ Context.pm 2005-01-24 16:40:37.043682496 -0300 @@ -19,8 +19,9 @@ # Revision History: # 2004-08-11 A. Tarallo: Added the function db_escheme2dbi, tested my bugfixes, # further details about them in the code. -# 2004-11-23 A. Tarallo, E. Silva: Bugfixes for running in a mod_perl environment. -# Clean up of previous bugfixes, better documentation of what was done. +# 2004-11-23 A. Tarallo, E. Silva: Bugfixes for running in a mod_perl +# environment.Clean up of previous bugfixes, better documentation of what was +# done. package C4::Context; use strict; @@ -226,6 +227,10 @@ # Load the desired config file. $self->{"config"} = &read_config_file($conf_fname); + # A. Tarallo 2005-01-24: You can work with an empty config. + # This warning might help you to find that this is the origin of + # many weird problems. + warn "read_config_file($conf_fname) returned undef" if !defined($self->{"config"}); return undef if !defined($self->{"config"}); $self->{"dbh"} = undef; # Database handle