[Tickets #6675] calendar/import method doesn't track creator_id

bugs at horde.org bugs at horde.org
Fri May 2 10:57:52 UTC 2008


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

Ticket URL: http://bugs.horde.org/ticket/6675
-----------------------------------------------------------------------
 Ticket             | 6675
 Created By         | almarin at um.es
 Summary            | calendar/import method doesn't track creator_id
 Queue              | Kronolith
 Version            | HEAD
 Type               | Bug
 State              | Unconfirmed
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             |
+New Attachment     | api.php.patch
-----------------------------------------------------------------------


almarin at um.es (2008-05-02 06:57) wrote:

Scenario:

An invitation is sent by USER_A to USER_B. USER_B accepts it in IMP and
selects "Add to my calendar" 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->setCreatorId($existing_event->getCreatorId());







More information about the bugs mailing list