6.0.0-beta1
7/23/25

[#5340] Fatal error checking for new versions with alarms disabled
Summary Fatal error checking for new versions with alarms disabled
Queue Horde Framework Packages
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners chuck (at) horde (dot) org
Requester selsky (at) columbia (dot) edu
Created 05/08/2007 (6651 days ago)
Due
Updated 06/18/2007 (6610 days ago)
Assigned 05/09/2007 (6650 days ago)
Resolved 06/18/2007 (6610 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
06/18/2007 04:03:53 PM Chuck Hagenbuch Comment #7
Assigned to Chuck Hagenbuch
State ⇒ Resolved
Reply to this comment
06/15/2007 03:24:36 AM Chuck Hagenbuch Comment #6 Reply to this comment
To reproduce:

1. Start with alarms enabled.
2. Go to Horde setup screen and disable alarms.  Do not log out.
3. Ask Horde to check versions.
4. See errors about calling function on non-object since
$this->_alarm isn't an object anymore.
These are the steps I followed and I didn't see this.
05/21/2007 09:47:03 PM Matt Selsky Comment #5 Reply to this comment
Yes, that would cause this, but I can't reproduce this either. Did
you write the config successfully, or did you copy/paste it?
I wrote the config successfully.



To reproduce:



1. Start with alarms enabled.

2. Go to Horde setup screen and disable alarms.  Do not log out.

3. Ask Horde to check versions.

4. See errors about calling function on non-object since $this->_alarm 
isn't an object anymore.
05/13/2007 03:30:08 AM Chuck Hagenbuch Comment #4
Taken from Jan Schneider
Reply to this comment

[Show Quoted Text - 14 lines]
Yes, that would cause this, but I can't reproduce this either. Did you 
write the config successfully, or did you copy/paste it?
05/09/2007 06:45:52 AM Jan Schneider Comment #3
State ⇒ Feedback
Reply to this comment
I can't reproduce this.
05/09/2007 01:58:52 AM Chuck Hagenbuch Assigned to Jan Schneider
State ⇒ Assigned
 
05/08/2007 11:29:10 PM Matt Selsky Comment #2 Reply to this comment
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?
05/08/2007 11:23:44 PM Matt Selsky Comment #1
Priority ⇒ 1. Low
State ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ Fatal error checking for new versions with alarms disabled
Type ⇒ Bug
Reply to this comment
When I check for new versions from the admin screen with alarms disabled, aka:



$conf['alarms']['driver'] = false;



I get the following error:



Fatal error: Call to a member function notify() on a non-object in 
/etc/httpd/htdocs/horde/framework/Notification/Notification.php on 
line 210

Saved Queries