6.0.0-git
2019-03-20

[#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 2007-05-08 (4334 days ago)
Due
Updated 2007-06-18 (4293 days ago)
Assigned 2007-05-09 (4333 days ago)
Resolved 2007-06-18 (4293 days ago)
Milestone
Patch No

History
2007-06-18 16:03:53 Chuck Hagenbuch Comment #7
Assigned to Chuck Hagenbuch
State ⇒ Resolved
Reply to this comment
2007-06-15 03:24:36 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.
2007-05-21 21:47:03 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.
2007-05-13 03:30:08 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?
2007-05-09 06:45:52 Jan Schneider Comment #3
State ⇒ Feedback
Reply to this comment
I can't reproduce this.
2007-05-09 01:58:52 Chuck Hagenbuch Assigned to Jan Schneider
State ⇒ Assigned
 
2007-05-08 23:29:10 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?
2007-05-08 23:23:44 Matt Selsky Comment #1
Type ⇒ Bug
State ⇒
Priority ⇒ 1. Low
Summary ⇒ Fatal error checking for new versions with alarms disabled
Queue ⇒ Horde Framework Packages
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