[chora] Problem setting up Chora (solved)

Graeme Merrall graeme at inetix.com.au
Tue Jun 24 17:41:01 PDT 2003


On Sat, Jun 21, 2003 at 04:31:30PM -0400, Chuck Hagenbuch wrote:
> Quoting Graeme Merrall <graeme at inetix.com.au>:
> 
> > By poking around in the code, it seems to fall over in
> > $registry->pushApp() if that's of any help and running 'php -l' against
> > config files doesn't reveal any hidden typos that may have snuck in when
> > editing.
> >
> > Any clues as to where to look next?
> 
> PHP's error log, Horde's log, etc... make sure you have error_reporting all the
> way up.
> 

Found the problem. It was the @include buried in importConfig in the
horde libs which didn't show up because of the @. I noticed that some
classes check that a file exists but others don't. Is there a plan to
make this more consistent?
If a user misdefines some path information in the applications, it would
be friendlier to have a useful error message if it can't find the files
when registering the application.

Cheers,
 Graeme


More information about the chora mailing list