[Tickets #3232] NEW: history functionality broken without sql backend, and it gets enabled automatically with upgrade

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3232
-----------------------------------------------------------------------
 Ticket             | 3232
 Created By         | glen at delfi.ee
 Summary            | history functionality broken without sql backend, and it gets enabled automatically with upgrade
 Queue              | IMP
 Version            | 4.1-RC1
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


glen at delfi.ee (2006-01-08 15:17) wrote:

i've disconfigured sql backend from horde as i don't have any. see ticket
2754 (https://dev.horde.org/horde/whups/ticket/?id=2754)

as a result conf.php contains:
# grep sql conf.php
$conf['sql']['phptype'] = false;

but lib/Horde/History.php contains check for $conf['sql']:
        if (empty($conf['sql'])) {
            Horde::fatal('You must configure a SQL backend to use History.',
__FILE__, __LINE__);
        }

and when if open message from imp i get error:
[Mon Jan  9 01:11:35 2006] [error] PHP Fatal error:  Call to undefined
function:  setoption() in /usr/share/horde/lib/Horde/History.php on line 61

so either there's bug in
1. disabling sql backend
2. check for sql backend in History.php

in any case the history should be turned off if sql database is not
available, but it was automatically enabled when i upgrade