[Tickets #6606] Re: Problem with attend.php and getByUID()

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6606
-----------------------------------------------------------------------
 Ticket             | 6606
 Updated By         | almarin at um.es
 Summary            | Problem with attend.php and getByUID()
 Queue              | Kronolith
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             |
-----------------------------------------------------------------------


almarin at um.es (2008-05-01 04:53) wrote:

Ok, I think I got it. So some conclusions so far:

- In attend.php there is no way to know the organizer, because we are not
talking about iCal. We only know an UID given as GET parameter.

- Anyway, I think that organizer information from an imported iCal is lost
because function Driver.php: fromiCalendar doesn't parse ORGANIZER
attribute, so even if you would know the organizer information at
attend.php, it is impossible retrieving  the correct event from backend,
because at least in sql, that information doesn't exists (only creator_id,
but as you said, organizer an creator_id are different concepts ).

- To solve the problem of retrieving the correct event at attend.php, I
think we should keep our attention at the creator_id. The scenario
described (I mean, when you get tree links pointing to attend.php to
accept, accept tentatively or decline) happens always because the event was
created in Kronolith, and the event (if not deleted) MUST exists in
backend, with a creator_id). So maybe the solution should be adding that
information in that links (with another GET parameter called creator=ID).

- Finally, I think that the issue described before about the tracking of
creator_id done by import and put api methods should be fixed (maybe I
should create another ticket), specially if the previous solution proposed
is done.


- About the creator_id in import/put api methods a still thinking that is
an issue that should be fixed, but i understand that, because