6.0.0-beta6
3/23/26

[#6820] Daily Agenda isn't sent after setting daily_agenda to read
Summary Daily Agenda isn't sent after setting daily_agenda to read
Queue Horde Framework Packages
Queue Version HEAD
Type Bug
State Resolved
Priority 2. Medium
Owners chuck (at) horde (dot) org
Requester 80602 (at) heygel (dot) ch
Created 6/2/08 (6503 days ago)
Due
Updated 6/3/08 (6502 days ago)
Assigned 6/3/08 (6502 days ago)
Resolved 6/3/08 (6502 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
06/03/2008 12:47:49 AM Chuck Hagenbuch Comment #5
State ⇒ Resolved
Reply to this comment
Fixed.
06/03/2008 12:44:40 AM Chuck Hagenbuch Comment #3
State ⇒ Assigned
Queue ⇒ Horde Framework Packages
Version ⇒ HEAD
Reply to this comment
This is actually a bug in the Prefs package.
06/02/2008 10:28:38 PM Jan Schneider Priority ⇒ 2. Medium
 
06/02/2008 09:47:07 PM Chuck Hagenbuch Comment #2
State ⇒ Feedback
Assigned to Chuck Hagenbuch
New Attachment: prefs.diff Download
Reply to this comment
It's actually a bug in the preferences system that this would be 
necessary. Please try this patch for Prefs.php (in your lib/ or 
framework/ directory) instead.
06/02/2008 07:47:10 PM 80602 (at) heygel (dot) ch Comment #1
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Daily Agenda isn't sent after setting daily_agenda to read
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
I didn't get a daily agenda after setting daily_agenda to 'read'. 
After some debugging I found, that in line 319 of 
lib/Scheduler/kronolith.php the wrong user's preferences were loaded. 
For each user in $users, the preferences of the *first* user in $users 
were loaded.



After adding the three arguments '', NULL and FALSE to the call of 
&Prefs::singleton in function agenda(), the problem was solved. The 
updated line now looks like this:



$prefs = &Prefs::singleton($GLOBALS['conf']['prefs']['driver'], 
'kronolith', $user, '', NULL, FALSE);



Was this a bug or is my horde system misconfigured?

Saved Queries