There rare two issues here: (1) duplicated events, and (2) what happens when you delete one of the duplicates. Let's handle them in reverse order.
(2) If you have a duplicated event in iCal but not in Google Calendar, it's likely that both of the iCal instances correspond to a single Google instance. Deleting either one of them will tell Spanning Sync to delete the event on Google. Since there wasn't a duplicate on Google to begin with, the event is now gone from Google altogether. Clearly not what you want. So the solution is to not have duplicates in iCal. Which leads us to... (1) Duplicates are the bane of all sync software, so both the Spanning Sync server and client contain lots of code to prevent duplicates form ever happening. To oversimplify, before an event is created in either iCal or Google Calendar Spanning Sync checks to make sure there's not already an event with the same name and start date/time in the target calendar. If Spanning Sync was responsible for the duplicates in your calendar, this logic failed at some point. (In fact, I found a bug in my server code yesterday afternoon that could allow duplicates to be created when the client sent events that had been "changed" in Sync Services but had no Google ID, and which fell outside the range of the earliest and latest "added" events sent during the sync. That bug has now been fixed.) The bottom line is that duplicates should never happen, and if they do, there's a bug so please let us know ASAP. Which still leaves the question of what to do if you find duplicate events. Obviously, just deleting one of them and syncing won't necessarily fix the problem. We recommend turning off syncing (by setting your sync period to Manual), cleaning up the duplicates (manually or using Spanning Tools or some other utility), then replacing data on Google (Advanced > Replace Data on Google > Calendars). This will ensure that Google has an exact copy of what's in iCal. Please let me know if you have any questions or run into any problems. Thanks, Charlie On Aug 15, 3:21 am, Joey Connick <[email protected]> wrote: > Okay, so this happens to me on a semi-regular basis. The latest case > is this: I had duplicates show up of a handful of yearly recurring > events in iCal but not in Google. I went into iCal and deleted the > ones which were in error (they were missing alarms). Then I Spanning > Synced. > > Result? The good events in iCal were wiped out and all trace of the > events also vanished from Google. > > So I went into iCal and went back a year or two, found the recurring > events, changed their end date to "never" and now I'm planning to sync > again, but I'm not convinced this will actually fix anything. > > As I've said, this has happened to me more than once--there seems to > be a real problem between handling recurring events in Google and iCal > and synching them properly. I still have no clue why the duplicates > which were missing alarm information got created. Is it something to > do with needing to back to the very first occurrence of the recurring > event in iCal to make modifications which are picked up properly? > Because that does seem to have some sort of effect/impact but really, > it shouldn't. I should be able to go into any instance of recurrence > and make changes, apply them to all instances or all future instances, > and not have duplicates show up or things get frakked. > > Any assistance would be most welcome, because this is getting damn > frustrating. I'm really ready for things to be seamless. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Spanning Sync" 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/spanningsync?hl=en -~----------~----~----~----~------~----~------~--~---
