As posted in another thread... Hi everyone, Sorry for the delay in responding to this thread. We're aware of this issue, and are currently investigating solutions. Unfortunately, at 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. Updates will be posted here: http://groups.google.com/group/google-calendar-help-dataapi/browse_thread/thread/4ce30940e1841303 -- Trevor Johns On Sep 1, 12:39 am, getaceres <[email protected]> wrote: > Is there a way to get a stack trace from the Google server so I can > know exactly what's wrong with my entry. It doesn't seem to be the > same as you, since I'm setting it as daily and so, the start date is > included in the recurrence rule. > > On Aug 31, 4:09 pm, Angelbert Morales <[email protected]> wrote: > > > > > Hello rick can we exchange links > > > On Mon, Aug 31, 2009 at 6:57 AM, Rick DeNatale > > <[email protected]>wrote: > > > > On Mon, Aug 31, 2009 at 1:14 AM, Ray Baxter<[email protected]> wrote: > > > > > On Sun, Aug 30, 2009 at 7:38 PM, Dave Riggle<[email protected]> wrote: > > > > >> I think Google is unhappy that the start date would not be included in > > > >> the recurrence rule (September 7, 2008 was a Sunday). CanTrevoror > > > >> somebody confirm that is what's going on? > > > > >> If that is indeed the case, Google is being overly pedantic. Nowhere > > > >> in RFC 2445 does it say the start date must fit the recurrence rule. > > > > > Alternately, you could say that Google is being under pedantic. RFC > > > > 2445 specifically recognizes that recurring events can start on dates > > > > or time that do not conform to the recurrence rules. In section > > > > 4.8.5.4 you can find this example: > > > > > Every other week on Monday, Wednesday and Friday until December 24, > > > > 1997, but starting on Tuesday, September 2, 1997: > > > > > DTSTART;TZID=US-Eastern:19970902T090000 > > > > RRULE:FREQ=WEEKLY;INTERVAL=2;UNTIL=19971224T000000Z;WKST=SU; > > > > BYDAY=MO,WE,FR > > > > ==> (1997 9:00 AM EDT)September 2,3,5,15,17,19,29;October > > > > 1,3,13,15,17 > > > > (1997 9:00 AM EST)October 27,29,31;November 10,12,14,24,26,28; > > > > December 8,10,12,22 > > > > > If indeed, Google is throwing 500s because of that, it is an error. > > > > Note that RFC2445 is currently under revision by the IETF Calsify > > > group, and there's a draft RFC2445bis spec. > > > > One of the changes in this spec is that the start date WILL need to be > > > covered by the recurrence rules. > > > > But you're right, in that the current RFC2445 allows this. It did add > > > a bit of complication to my RiCal Ruby icalendar library. > > > > -- > > > 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 -~----------~----~----~----~------~----~------~--~---
