<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>calendar/import method doesn't track creator_id</title>
  <pubDate>Sat, 05 Jul 2008 18:17:53 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/6675</link>
  <atom:link rel="self" type="application/rss+xml" title="calendar/import method doesn't track creator_id" href="http://bugs.horde.org/ticket/6675/rss" />
  <description>calendar/import method doesn't track creator_id</description>

  
  
  <item>
   <title>Scenario:

An invitation is sent by USER_A to USER_B. USER</title>
   <description>Scenario:

An invitation is sent by USER_A to USER_B. USER_B accepts it in IMP and selects &quot;Add to my calendar&quot; the event attached. An new event is created in backend, but creator_id is USER_B, instead USER_A.

That behaviour doesn't occur when you import an entire iCalendar, throw WebDAV, for instance.

That happens because IMP uses calendar/import API method, which is focused to import only one event given in iCal format. When you publish a calendar throw WebDAV, calendar/put method is used.

So, I think that calendar/import should respect creator_id as calendar/put does.

I attach a patch to show a way to solve it. Mainly I use a similar instruction found in _kronolith_put function, line 556:

  // Don't change creator/owner.
  event-&gt;setCreatorId($existing_event-&gt;getCreatorId());


</description>
   <pubDate>Fri, 02 May 2008 06:57:51 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6675#t45098</link>
  </item>
  <item>
   <title>This doesn't seem right to me. I think we want to make the s</title>
   <description>This doesn't seem right to me. I think we want to make the same change we made to _kronolith_put - check if the event exists on the calendar we're importing to. I've done that in CVS.</description>
   <pubDate>Mon, 05 May 2008 00:29:29 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6675#t45163</link>
  </item>
  

 </channel>
</rss>
