Trevor - I'm seeing this and I believe the RRULE looks correct to me: DTSTART;TZID=Australia/Perth:20090901T074000 DTEND;TZID=Australia/Perth:20090901T075000 RRULE:FREQ=WEEKLY;WKST=MO;BYDAY=MO,TU,WE,TH,FR
Yet we're getting "Exception during update". On Sep 2, 8:14 pm, Rick DeNatale <[email protected]> wrote: > On Wed, Sep 2, 2009 at 8:28 PM, Trevor Johns<[email protected]> wrote: > > this time I don't have an ETA for a fix. > > > > > To be clear: This appears to be caused when the created event contains > > a gd:recurrence element containing invalid data. For example: lacking > > an RRULE, or having a DSTART value that is impossible given the > > provided > > RRULE. > > > The workaround right now is to make sure that gd:recurrence data is > > correct. I realize this isn't ideal, and again, we're investigating > > solutions to this problem. > > But also to be clear, RFC2445 clearly allows the DTSTART to be outside > of the recurrence rules, and gives specific examples of this case. > > The first occurrence of an event ALWAYS starts with DTSTART unless > that time is specifically excluded by an EXRULE or EXDATE. > > So such events are correct from the standpoint of the current standard. > > And I just went back and looked at the latest version of RFC2445bis > and it appears that the change about DTSTART not matching the > recurrence rules was less draconian that I thought, while it now says > that "The "DTSTART" property value SHOULD be synchronized with the > recurrence rule, if specified." (original emphasis). Not MUST be > synchronized, so it is not invalid. Now it also goes on to say "The > recurrence set generated with a "DTSTART" property value not > synchronized with the recurrence rule is undefined." Which in my many > years of experience in standardese means that implementers are free to > vary in the set of occurences they generate from such an event. > > -- > Rick DeNatale > > Blog:http://talklikeaduck.denhaven2.com/ > Twitter:http://twitter.com/RickDeNatale > WWR:http://www.workingwithrails.com/person/9021-rick-denatale > LinkedIn:http://www.linkedin.com/in/rickdenatale --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
