Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mass deletions when syncing from iCal to Google #1649

Closed
Mattyc106 opened this issue May 12, 2023 · 11 comments
Closed

Mass deletions when syncing from iCal to Google #1649

Mattyc106 opened this issue May 12, 2023 · 11 comments
Assignees
Labels
enhancement New feature resolved Working hotfix available
Milestone

Comments

@Mattyc106
Copy link

Are you already using OGCS?
Provide the version number.
2.9.0.0
Describe the question you have
A clear and concise description of your question and what you would like clarifying.
I have an iCal in Outlook and need to sync to Google. Whenever the iCal is refreshed, OGCS sees all the entries as new ones and so needs to do a mass delete in Google and of course prompts to do this.

Can this mass deletion protection be removed? I am happy to make a healthy donation if you can.

Many thanks

Mat

@phw198
Copy link
Owner

phw198 commented May 20, 2023

This will be the same cause as #447 - Apple are idiots and continually change an ID that should never change.

Are you able to turn on two-way sync? If so, that allows OGCS to rely on the Google ID instead in order to match calendar items up.

@Mattyc106
Copy link
Author

Hi, Thanks for the suggestion, but unfortunately a 2 way sync causes errors as per the below screenshot.

Sorry to ask again, but is there anyway to get a release that does not prompt about mass deletions? The iCal is the source and we dont care what is deleted from the Google Calendar. Again, happy to make a nice donation if you are able to do this.

Thanks in advance.

Screenshot 2023-05-22 134433

@phw198 phw198 added enhancement New feature and removed question labels May 25, 2023
@phw198 phw198 self-assigned this May 25, 2023
@phw198
Copy link
Owner

phw198 commented May 25, 2023

I'm not too keen on the idea of just allowing OGCS to delete and recreate everything on every sync - if there's a reasonable number of items in your calendar, this will unnecessarily chew up API quota and potentially annoy the Google overlords.

However, I maybe able to provide an alternative mechanism for syncing - let me see what I can do....

phw198 added a commit that referenced this issue May 25, 2023
Direct to wiki for iCal KB article on mass deletions.
#1649
@phw198
Copy link
Owner

phw198 commented May 25, 2023

📦 OK, please have a go with hotfix v2.9.7.10.zip (see instructions for applying).

Once you get prompted about the mass deletion and you proceed with "Yes", you should get another prompt about viewing a wiki document about a possible resolution - let me know how it goes!

@Mattyc106
Copy link
Author

Mattyc106 commented May 26, 2023 via email

@phw198
Copy link
Owner

phw198 commented May 26, 2023

Thanks for trying - the patch needs to be applied on top of the latest alpha v2.9.7 though.

@Mattyc106
Copy link
Author

Mattyc106 commented May 26, 2023 via email

@Mattyc106
Copy link
Author

Mattyc106 commented May 26, 2023 via email

@phw198
Copy link
Owner

phw198 commented May 27, 2023

Thanks for the quick feedback and generous support - fingers crossed final testing is successful too 🙂

@phw198
Copy link
Owner

phw198 commented Jun 6, 2023

Judging by your second donation, I'm assuming testing went well! I'm glad this release has proved useful and thanks for your generosity 👍

@Mattyc106
Copy link
Author

Mattyc106 commented Jun 6, 2023 via email

@phw198 phw198 added this to the v2.10.1 milestone Jun 17, 2023
@phw198 phw198 added the resolved Working hotfix available label Jul 23, 2023
@phw198 phw198 closed this as completed in 1fd1625 Jul 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature resolved Working hotfix available
Projects
None yet
Development

No branches or pull requests

2 participants