OK thanks. I've starred the issue in question and will add some detail after I finish some testing.
-c On Sep 10, 5:20 pm, "Lane LiaBraaten (Google)" <[EMAIL PROTECTED]> wrote: > Hi Charlie, > > Tracking issues through gdata-issues[1] is still new so I'm open to > suggestions. IMHO, it's probably best to post something in the group > describing the issue, then after some discussion and confirmation of > the issue, someone can create an issue for tracking. In this case, I > created the issue, but anyone can create issues in the gdata-issues > project [1]. > > I'd also like to encourage everyone to add comments to issues with > code samples and details on how to recreate bugs. Issues with clear > descriptions are easier to debug and fix, and it also lets me know how > severe the issue is. Even if you don't have anything to add, go ahead > and star a bug if it affects you, or star a feature request if you'd > like to see it implemented. > > Thanks for the question, > Lane > > [1]http://code.google.com/p/gdata-issues/issues/list > > On Sep 10, 3:00 pm, Charlie Wood <[EMAIL PROTECTED]> wrote: > > > Thanks, Lane. And to be clear, should I be entering things like this > > directly in the bug reporting system or here on the forum? > > > -c > > > On Sep 10, 4:49 pm, "Lane LiaBraaten (Google)" > > > <[EMAIL PROTECTED]> wrote: > > > Hi Charlie and Kulvinder, > > > > Thanks for your posts - this new behavior is not intentional. I've > > > filed a bug here: > > > >http://code.google.com/p/gdata-issues/issues/detail?id=103 > > > > Please feel free to comment more on the issue there. > > > > Cheers, > > > Lane > > > > On Sep 10, 10:39 am, Kulvinder Singh <[EMAIL PROTECTED]> wrote:> Google > > > Guys, > > > > > Please reply to this. There are a lot of posts on this including by > > > > myself unanswered. > > > > > Thanks > > > > > ----- Original Message ---- > > > > From: Charlie Wood <[EMAIL PROTECTED]> > > > > To: Google Calendar Data API > > > > <[email protected]> > > > > Sent: Monday, September 10, 2007 10:55:14 PM > > > > Subject: Phantom attendees being created by API > > > > > It looks like the behavior of updating attendee status on event update > > > > has changed (for the worse) in the past week or so. The new behavior > > > > is causing a "phantom" attendee (whose name is the name of the > > > > calendar) to show up on modified events in non-primary calendars. > > > > While this is mostly a cosmetic bug, it's a quite noticeable one. The > > > > previous behavior would be much preferred. > > > > > Thanks, > > > > Charlie > > > > > For additional info, please see the message here: > > > > >http://groups.google.com/group/google-calendar-help-dataapi/browse_th... > > > > > > > > > ___________________________________________________________________________ > > > > _________ > > > > Park yourself in front of a world of choices in alternative vehicles. > > > > Visit the Yahoo! Auto Green Center.http://autos.yahoo.com/green_center/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
