Thanks Ryan and Charlie.
I'd like to update our QA team to be aware of this issue, can you provide any guidance regarding what factors are involved in the manifestation of these recurrence issues? Any and all recurring events, specific TZ/times... Thanks in advance, Derek. http://www.calgoo.com Ryan Boyd (Google) wrote:
I think I accidently hit 'Reply to author' on this one. I have been able to successfully recreate this issue -- thanks to Charlie and all the information he provided. While we will work to resolve this issue on our side, I did notice during my testing that there is a way for the client to check whether the event was properly created. The gd:recurrence element in the response does include an incorrect value for those times when the time for the event is offset. For instance, after submitting the following: DTSTART;TZID=America/Chicago:20061231T080000 the following was returned: DTSTART;TZID=America/Chicago:20061231T070000 If you wish to handle this issue before the bug is resolved, you could look at the resulting gd:recurrence element and edit the event if necessary. Thanks again Charlie. Cheers, -Ryan
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
