Ryan, Will any fixes regarding this issue also be applied retroactively to events that are already affected by this bug, or only to events created in the future?
Ricky On Mar 7, 10:57 am, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote: > Hi Charlie, > > I'm actually having a problem recreating the bug as you described. > Based on the current code base, what should be happening (and is for > me) is that the deleted instance will not appear as an entry in the > feed. > > The calendar I've tried to recreate this on is: > http://www.google.com/calendar/feeds/[EMAIL > PROTECTED]/public/full?updated-min=1970-01-01&q=2recurring2 > > You'll notice only one entry (containing an EXDATE in the icalendar > syntax) even though the instance on 3/6/2007 has been deleted. > > Alternatively, if you look at: > http://www.google.com/calendar/feeds/[EMAIL > PROTECTED]/public/full?updated-min=1970-01-01&q=5recurring5 > > You'll notice 2 entries (one containing an EXDATE in the icalendar > syntax). The second entry (without the gd:recurrence) does not > contain a gd:originalEvent, but is noted as 'canceled'. However, the > gd:when doesn't represent the date I deleted either. This was caused > by creating a single event and modifying it to be a recurring event. > Because of the way recurring events are handled, these actions cause > the original event to be deleted and a new event (the recurring event) > to be created. Is this possibly what happened in your testing? > > Although I'm having problems recreating the bug as you described, > there still is an issue present that likely effects your application > -- deleted instances of recurring events are not appearing in the > feeds. This problem occurred due to another bug fix (at the time > EXDATE elements were added to the icalendar syntax). That fix is > being reverted, so EXDATE elements will no longer appear and deleted > instances of recurring events will reappear in the feeds when an > updated-min parameter is passed. > > I understand the problems this causes with syncing deleted instances > of recurring events -- we will resolve this problem with the next > release. While I realize this is not ideal, you could delete any > instances on your side which appear in EXDATE syntax in the meantime > (which will be removed at the time deleted events begin reappering in > the feeds). > > I will be posting a separate thread to the groups making the > announcement re the removal of EXDATE syntax in the next release to > make it known to a wider audience. > > Our apologies, > > -Ryan > > On Mar 7, 5:02 am, "Charlie Wood" <[EMAIL PROTECTED]> wrote: > > > Any news on this? This is actually a serious bug, at least for us. It > > means that deleted recurrences, which are quite common, don't sync. > > > Thanks, > > Charlie > > > On Mar 5, 12:18 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote: > > > > Hi Charlie, > > > > Thanks again for your continued reports. You mentioned the > > > gd:originalEvent is not appearing in the deleted instance of the > > > event. Is there an entry object representing that deleted instance? > > > What, if any, query parameters are you using to retrieve the feed? > > > > Thanks, > > > > -Ryan > > > > On Mar 5, 7:04 am, "Charlie Wood" <[EMAIL PROTECTED]> wrote: > > > > > In a full, authenticated feed an exception to a recurring event has > > > > previously included a <gd:originalEvent /> element with information > > > > about the event to which the containing event is an exception. It > > > > looks like that element has disappeared for exceptions where the event > > > > has been deleted. However, it's still there for exceptions where the > > > > event was modified but not deleted. > > > > > Could this be related to the earlier problem with deletes not being > > > > included in the feed (http://groups.google.com/group/google-calendar- > > > > help-dataapi/browse_thread/thread/c52d9a0f63b89ef3)? > > > > > Regardless, to reproduce the problem just create a recurring event and > > > > delete one of the recurrences. Fetch the full, authenticated feed and > > > > look at the entry for the deleted recurrence. It's missing the > > > > <gd:originalEvent /> element. Move one of the recurrences to another > > > > time and fetch the feed again. You'll see the <gd:originalEvent /> > > > > element included. > > > > > This is a big deal for us, so your (continued) help is greatly > > > > appreciated. > > > > > Thanks, > > > > Charlie --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
