[Tickets #5340] Re: Fatal error checking for new versions with alarms disabled

[bugs at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=5340
-----------------------------------------------------------------------
 Ticket             | 5340
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | Fatal error checking for new versions with alarms disabled
 Queue              | Horde Framework Packages
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
-Owners             | Jan Schneider
+Owners             | 
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2007-05-12 20:30) wrote:

> This happens right after updating the conf to disable alarms.  So:
>
> var_dump($GLOBALS['conf']['alarms']['driver']);
>
> string(3) "sql"
>
> But,
>
> var_dump($this->_alarm)
>
> NULL
>
> Is the bug that $conf is not being reloaded even though the 
> $this->_alarm object is getting destroyed?

Yes, that would cause this, but I can't reproduce this either. Did you
write the config successfully, or did you copy/paste it?