[Tickets #4770] Don't send notifications to modifier of event

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=4770
-----------------------------------------------------------------------
 Ticket             | 4770
 Created By         | steven.deboeck at excentis.com
 Summary            | Don't send notifications to modifier of event
 Queue              | Kronolith
 Version            | HEAD
 Type               | Enhancement
 State              | New
 Priority           | 1. Low
 Owners             | 
+New Attachment     | notifications_exclude_modifier.patch
-----------------------------------------------------------------------


steven.deboeck at excentis.com (2006-12-12 07:14) wrote:

Synopsis:
Currently, if a user enables notifications of new, edited or deleted
events in Kronolith, he even gets a notification for events he has added,
modified or deleted himself. It would be nice if the user could change
this behaviour, i.e. only receive notifications if other users add, edit
or delete events.

Motivation:
Personally, I find it a bit annoying to receive notifications for events
I've just added to my own (or someone else's) calendar. I only want to be
notified if someone else adds, changes or deletes an event in a calendar
I'm interested in, so that I can examine the changes. For events I've
added, changed or deleted myself, I don't need to examine the changes.

Solution:
I've added a new option to the Calendar - Notifications section. When
checked, the user won't receive notifications for events he has added,
edited or deleted. He'll still receive notifications if others modify
events. See attached patch.
Changes to conf/prefs.php.dist: added extra option.
Changes to lib/Kronolith.php: changed function _notificationPref. If the
supplied user equals the currently logged in user and the new option is
checked, the method returns false.

If you think this is a useful option and are happy with how it's
implemented, feel free to add it to the code :-) Also, I've overlooked
something, please let me now.


Best regards,

Steven