<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Reminders sent from non-subscribed Calendar</title> 
  <pubDate>Fri, 10 Apr 2026 09:20:46 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/649</link> 
  <atom:link rel="self" type="application/rss+xml" title="Reminders sent from non-subscribed Calendar" href="https://bugs.horde.org/ticket/649/rss" /> 
  <description>Reminders sent from non-subscribed Calendar</description> 
 
   
   
  <item> 
   <title>While we&#039;re starting to test the sharing of calendars full-s</title> 
   <description>While we&#039;re starting to test the sharing of calendars full-scale, we ran into a

could-be issue with the reminder script.



Mats Djärf (&quot;the iconizer and themer&quot;) has allowed my user to show/read his

calendar. I am not &quot;subscribed&quot; to it (i.e. it shows as &quot;- Mats Djärf&#039;s

calendar&quot; in Kronolith. When he enters an item in his private calendar with a

reminder (alarm) attached to it, I too am served with the reminder.



(HEAD20040929)</description> 
   <pubDate>Thu, 30 Sep 2004 09:30:22 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/649#t2377</link> 
  </item> 
   
  <item> 
   <title>This is how reminders work at the moment. Change this to a e</title> 
   <description>This is how reminders work at the moment. Change this to a enhancement request because we might implement the reminder differently in the future.</description> 
   <pubDate>Tue, 02 Nov 2004 21:45:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/649#t2753</link> 
  </item> 
   
  <item> 
   <title>Bounty added: http://www.horde.org/bounties/details.php#kron</title> 
   <description>Bounty added: http://www.horde.org/bounties/details.php#kronolith_remindersubscriptions</description> 
   <pubDate>Sun, 20 Feb 2005 22:01:42 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/649#t5711</link> 
  </item> 
   
  <item> 
   <title>Thoughts on how to implement this?  I don&#039;t care about the b</title> 
   <description>Thoughts on how to implement this?  I don&#039;t care about the bounty, but as more people begin using the calendar in our organization, I had three independent inquries this week about why people were receiving notifications for other people&#039;s calendars.



Since there is now an &#039;event_notification&#039; preference in Kronolith, would the proper way be to check the user&#039;s preference for that, before building the list of recipients?</description> 
   <pubDate>Wed, 27 Jul 2005 23:24:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/649#t10088</link> 
  </item> 
   
  <item> 
   <title>Sounds like a good solution. The preference description need</title> 
   <description>Sounds like a good solution. The preference description needs to be changed then of course.</description> 
   <pubDate>Thu, 28 Jul 2005 07:37:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/649#t10092</link> 
  </item> 
   
  <item> 
   <title>Ok, I have something that works currently, and that takes in</title> 
   <description>Ok, I have something that works currently, and that takes into account the event_notification preference.  However, that creates a problem:



I do want to get reminders.  I don&#039;t want to get a notification every time I make a modification to my own calendar.  So I can see doing one of two things:



Modifying the event_notification process, so that if the creator/modifier of an event is the share owner, no notification is sent, OR creating a separate preference (event_reminder) that allows you to set a preference for reminders.  Thoughts on the proper way to handle that?</description> 
   <pubDate>Thu, 28 Jul 2005 15:00:04 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/649#t10129</link> 
  </item> 
   
  <item> 
   <title>Ah, true. In this case a separate pref makes more sense to m</title> 
   <description>Ah, true. In this case a separate pref makes more sense to me.</description> 
   <pubDate>Thu, 28 Jul 2005 15:26:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/649#t10130</link> 
  </item> 
   
  <item> 
   <title>Ok, the attached patch works in my limited testing.  A new p</title> 
   <description>Ok, the attached patch works in my limited testing.  A new preference, event_reminder is added and the value of this is consulted to determine if a reminder should be sent.



Starting from an initial list of all users that have PERMS_READ for a share:



There are three conditions a reminder should be sent:



If the value is owner, it should be sent if you are the share owner,

If the value is show, it should be sent if the share is in your list of subscribed calendars,

If the value is read, it should be shown (and since the list of initial users is built from whoever has PERMS_READ, no other checks are needed).



No claims that this is right, or that its the most eloquent way to handle this, but it should work nonetheless.</description> 
   <pubDate>Thu, 28 Jul 2005 15:51:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/649#t10131</link> 
  </item> 
   
  <item> 
   <title>Committed, thanks.</title> 
   <description>Committed, thanks.</description> 
   <pubDate>Fri, 21 Oct 2005 17:24:56 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/649#t12682</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
