Ok in case somebody else is wondering same thing, this happened due to UNTIL declaration and missing timezone. So when there was UNTIL=21001231T000000 it should have been UNTIL=21001231T000000Z. Interesting.
On Apr 28, 7:49 pm, petteri <[email protected]> wrote: > Thanks for your answer. However I don't think this has anything to do > with this issue. Google, could you please look into the original > problem. > > On 28 huhti, 19:42, Ray Baxter <[email protected]> wrote: > > > There are some patent issues around the technology of implementing > > recurrent events. You can read about this > > here:http://67central.com/bc/2007/06/05/limitation-on-recurring-events-in-... > > > Based on what you report, the issue has improved since 2 years ago, > > but this may be as far a Google is currently willing or able to go. > > > Ray > > > On Tue, Apr 28, 2009 at 8:33 AM, petteri <[email protected]> wrote: > > > > This is really critical, any ideas? > > > > On 26 huhti, 13:36, petteri <[email protected]> wrote: > > >> Hi, > > > >> Over year of the first report of this bug and still this seems to > > >> exists. I reported this to Google UI but got nothing back. No > > >> confirmation whatsoever. > > > >> Can this happen because I'm using Batch commands? I've noticed that > > >> e.g. Thunderbird Lightning Google calendar plug-in sends recurring > > >> events and they appear correctly in Google Calendar. I'm however doing > > >> exactly like in documentation and can only get first instance to > > >> appear. Please could you look into this ASAP. > > > >> - Petteri > > > >> ---------- Forwarded message ---------- > > >> From: "Austin (Google)" <[email protected]> > > >> Date: Apr 8 2008, 6:46 am > > >> Subject: Only first instance of recurring event is shown on calendar > > > >> view > > >> To: Google Calendar Data API > > > >> Hi, > > > >> I used your recurrence string and created the recurrence just as you > > >> did and I noticed what you were talking about, that only the > > >> firstrecurringinstance seems to be visible and all the subsequent ones > > >> aren't. But I think I realized what is going on, you should try, move > > >> the event to the second occurence of where you think you should be and > > >> click on that date (even tho it's not invisble there). This should > > >> trigger a reload and pop up that recurrence. > > > >> So yea, I think this isn't a problem with the API, therecurring > > >> instances are all there. I think it is an issue of how quickly the > > >> calendar UI is refreshing events that are far out in the future (in > > >> this case it is one year away). This behavior also surfaces when you > > >> add this recurrence manually from the UI. Perhaps, you and I are > > >> moving too quickly down the calendar and it's not refreshing quick > > >> enough.I think you should report this to the Calendar Help Center > > >> (they handle UI issue there). Thanks for feedback!! > > > >> Calendar Help Center -http://www.google.com/support/calendar/bin/ > > >> request.py?contact_type=fe... > > > >> Austin > > > >> On Mon, Apr 7, 2008 at 11:46 AM, petteri <[email protected]> wrote: > > > >> > Hi, > > > >> > When posting followingrecurringevent: > > > >> > <?xml version='1.0' encoding='UTF-8'?><feed xmlns='http://www.w3.org/ > > >> > 2005/Atom' xmlns:batch='http://schemas.google.com/gdata/batch' > > >> > xmlns:gCal='http://schemas.google.com/gCal/2005'><category > > >> > scheme='http://schemas.google.com/g/2005#kind'term='http:// > > >> > schemas.google.com/g/2005#event'></category> > > >> > <entry xmlns='http://www.w3.org/2005/Atom'xmlns:gd='http:// > > >> > schemas.google.com/g/2005'> > > >> > <batch:id>25</batch:id> > > >> > <batch:operation type='insert' /> > > >> > <category scheme='http://schemas.google.com/g/2005#kind'term='http:// > > >> > schemas.google.com/g/2005#event'> > > >> > </category> > > >> > <title type='text'>foobar</title> > > >> > <content type='text'></content> > > >> > <gd:transparency value='http://schemas.google.com/g/ > > >> > 2005#event.opaque'></gd:transparency> > > >> > <gd:eventStatus value='http://schemas.google.com/g/ > > >> > 2005#event.confirmed'></gd:eventStatus> > > >> > <gd:where valueString=''></gd:where> > > >> > <gd:recurrence>DTSTART;VALUE=DATE:20080420 > > >> > DTEND;VALUE=DATE:20080420 > > >> > RRULE:FREQ=YEARLY;WKST=MO;UNTIL=21001231T000000;INTERVAL=1 > > >> > </gd:recurrence> > > >> > <gd:extendedProperty name='SymbianCalLocalUID' value='982' /> > > >> > <gd:extendedProperty name='SymbianCalGlobalUID' > > >> > value='P7FQc24W4EE5l818X2GVU1' /> > > >> > </entry> > > >> > </feed> > > > >> > it seems that only first instance is visible on calendar view (UI) but > > >> > when clicking "edit event details"recurringevent looks like > > >> > correctly set. If I save event again (click some check box on and off > > >> > to trigger modification and hit "save"),recurringevent is now > > >> > correctly shown in UI (all the instances are visible). > > > >> > Any ideas what could be the problem? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
