No problem David. Let us know if this problem occurs again. Cheers, -Ryan
On Apr 6, 12:55 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi > No problem today, > I don't understand .... > Perhaps, I was tired .... > > Sorry. > > David. > > On Apr 5, 11:42 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote: > > > Hi David, > > > I tried recreating this problem, but was unable to do so. I followed > > your instructions (using the same dates), and I always got a > > gd:reccurrenceException element for each entry I deleted. > > > Is there possibly a proxy server caching copies of the feeds? Can you > > verify that the 'updated' (child of 'feed) date has changed when you > > delete an instance? Also, try doing a query against the full > > projection with a query parameter singleevents=true-- to see if that > > includes only the entries that should still exist, or also the deleted > > entries? You <em>should</em> see one <entry> for each instance of the > > recurring event. Each entry should contain 1 <gd:when> element. > > > Cheers, > > > -Ryan > > > On Apr 5, 2:03 pm, "[EMAIL PROTECTED]" > > > <[EMAIL PROTECTED]> wrote: > > > Ok to get gd:recurrenceException > > > It's more usable than EXDATE.... > > > > But retrieving the composite projection feed return the same > > > exceptions. > > > The last deleted single ocurrency is missing too. > > > > David. > > > > On Apr 5, 9:47 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote: > > > > > Hello David, > > > > > Try retrieving the composite projection feed [1] to see > > > > gd:recurrenceException elements. These should contain the canceled > > > > instances. > > > > > Sorry the EXDATE elements aren't appearing correctly. The EXDATE > > > > elements are being deprecated in the full feed. Deleted instances of > > > > recurring events will once again appear as separate entry elements in > > > > the full feed. As Philipp has pointed out in the groups, they should > > > > probably only be represented as gd:recurrenceException elements in the > > > > composite feed and should not be represented in the full feed. We are > > > > taking his suggestion into consideration, but it will not occur with > > > > the next release. > > > > > Please follow up here if you have any additional questions. > > > > > Thanks, > > > > > -Ryan > > > > > [1] -http://code.google.com/apis/calendar/reference.html#Projection > > > > > On Apr 5, 10:52 am, "[EMAIL PROTECTED]" > > > > > <[EMAIL PROTECTED]> wrote: > > > > > Hi > > > > > The recurrent events returned by the API are not uptodate: > > > > > The last deleted single occurency is always missing > > > > > > In google calendar (web UI), I create a recurrent event : > > > > > from 10:00 to 11:00 > > > > > daily from 07/04/03 to 07/04/08 > > > > > so 6 days > > > > > > I delete a single occurrency in Google Calendar (web UI) (for example > > > > > 07/04/04), a query on this event does not return any exception > > > > > (EXDATE) for this deleted occurrency. > > > > > > I delete another single occurrency in Google Calendar (web UI) (for > > > > > example 07/04/05), a query on this event returns only one exception > > > > > (EXDATE) for this deleted occurrency. > > > > > The EXDATE contains the first deleted occurrency (07/04/04), but not > > > > > the last (07/04/05) > > > > > I delete a third single occurrency in Google Calendar, EXDATE contains > > > > > these exceptions : 07/04/04 and 07/04/05, but not the third. > > > > > Etc..... > > > > > > I hope I'm understandable... > > > > > > I have the same problem with gdata-python-client-library, > > > > > pygooglecalendar and calgoo (java UI) > > > > > > David. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
