[horde] Progress with "You must configure a Category backend to use Horde." error

[Shane Boulter]

Well I just went through and checked my conf.php again.  From what I can 
see all looks well.  To be sure I redid it all from scratch and I didn't 
get any further with it.

Craig the first test I did to see where I was getting me error triggered 
was I did a very simple modification to this line.

Original
Horde::fatal(sprintf(_("You must configure a Category backend to use 
%s."), $GLOBALS['registry']->getParam('name')), __FILE__, __LINE__);

Modified
Horde::fatal(sprintf(_("Shane You must configure a Category backend to 
use %s."), $GLOBALS['registry']->getParam('name')), __FILE__, __LINE__);

I then went so far as to see what was actually returned when 
$conf['category']['driver'] was called.  This again was an easy 
modification.

// put this after the global $conf declaration
$mytest = $conf['category']['driver'];

Horde::fatal(sprintf(_("Shane::$mytest You must configure a Category 
backend to use %s."), $GLOBALS['registry']->getParam('name')), __FILE__, 
__LINE__);

This returned a null value.  So after that I tried to get ANY paramter 
from the conf paramter.

$mytest = $conf['sql']['phptype'] = 'mysql';

Again this produced a blank value.  Having failed all that I then said 
to myself I wonder what would happen if I comment out the check to see 
if the category backend is declared and hard coded the $driver value to sql.

/**
         if (!isset($conf['category']['driver'])) {
             Horde::fatal(sprintf(_("You must configure a Category 
backend to use %s."), $GLOBALS['registry']->
getParam('name')), __FILE__, __LINE__);
         }

         $driver = $conf['category']['driver'];
*/
         $driver = 'sql';

This gave me an error of

A fatal error has occurred
Required 'phptype' not specified in categories SQL configuration.
The file /usr/horde/config/../config/conf.php should contain a 
$conf['storage']['params']['phptype'] setting.
Details have been logged for the administrator.

That about as far as I've gotten with it so far.  Hopefully this will 
assist you with your troubleshooting.

Shane

Bo Daley wrote:

> On Sun, 11 Jan 2004, Shane Boulter wrote:
> 
> 
>>Ok I've been reading the mailing list's regarding this error message and 
>>I've gotten about as far as everyone else having this problem.  I did 
>>however find out where and why the message is happening. I just don't 
>>have enough php programming experience to fix it.
> 
> 
> I think that the most likely cause of this problem is that you have a 
> syntax error in your conf.php file somewhere. You might need to go through 
> the conf.php file making sure you haven't missed anything (like a closing 
> ' mark maybe) anywhere inside the file.
> 
> bo.
> 
> 
>