[Tickets #6183] Re: Kronolith gives premature notifications

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6183
-----------------------------------------------------------------------
 Ticket             | 6183
 Updated By         | michael.redinger at uibk.ac.at
 Summary            | Kronolith gives premature notifications
 Queue              | Kronolith
 Version            | 2.2-RC2
 Type               | Bug
 State              | Assigned
 Priority           | 2. Medium
 Milestone          | 
 Patch              | 
 Owners             | Horde Developers, Jan Schneider
-----------------------------------------------------------------------


michael.redinger at uibk.ac.at (2008-03-19 10:14) wrote:

I am experiencing exactly the same problem:

- notifications are created as soon as a task or event is created
- if the notification method is a popup, the popup keeps reappearing every
time I select a page.
  changing the alarm method does not help - only deleting the event or
task or deleting the alarm in the database.
- if the method is email, I immediately get an email
- I used a clean account
- the alarm entry in horde_alarms seems to be quite ok (at least for me)

I am using the latest RCs (RC3 for horde, RC2 for nag and kronolith; I 
also tried kronolith CVS).

As this happens both with kronolith and turba, I suppose the problem is
somewhere in the horde code.