| Summary | history functionality broken without sql backend, and it gets enabled automatically with upgrade |
| Queue | IMP |
| Queue Version | 4.1-RC1 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | glen (at) delfi (dot) ee |
| Created | 01/08/2006 (7090 days ago) |
| Due | |
| Updated | 01/10/2006 (7088 days ago) |
| Assigned | |
| Resolved | 01/10/2006 (7088 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ history functionality broken without sql backend, and it gets enabled automatically with upgrade
Queue ⇒ IMP
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