-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
Split up recurring event [Request] #439
Comments
In theory yes. |
Thank you for an insight! Which part of the script will I need to change to add this? Will be grateful, if you can lead me |
Try this:
right above Line 291 in 3c36a55
|
I can't reproduce that, have you done any other changes to the script? |
Default settings, default script. Only with changes you provided. I delete the calendar and let the script create a calendar from scratch. Seems like it's happening if one event in reccuring series is changed |
That makes sense, i'll look into it. |
Give this version a try. There have been changes in various places, i think it's easier to share the whole script than list all changes here. |
Thank you very much! Duplicating of events stopped. I'm noticed one issue. Again only happening with edited events in reccuring series. Its not picking up the change in the timezones, when expanding. I moved to another country and changed the Google calendar timezone. The expanded event (from edited event in recurring series) haven't picked up the change. So there is difference between original event time and expanded event time. |
Can you share a minimal *.ics you are testing this with? |
I unfortunately deleted the event that was causing the issue. |
Any work around that Google discards timezones from recurrence exceptions? |
No, that's just the way google handles it. Nevertheless the events should all be at the correct timeslot (albeit in a wrong timezone) in regards to the timezone set in your target calendar. Is that the case? |
I can't reproduce the issue that I was having yet. The events were appearing in different timeslots |
Started receiving this error on execution. |
In this version it's duplicating reccuring exception events with each execution |
Still testing it. Works like a charm so far. The only thing, that I'm noticing, as I understand from looking on a calendar, that for reccuring exception events it first create event in an original position (default time from reccuring event) and then moves to a proper time. The problem, that I'm noticing, that sometimes it is stuck in an original position for a whole time of execution cycle. And with the next execution it moves itself to a proper place. Don't really know what causing it. Is there a way to make sure event is not stuck in an original position? Thank you very much! |
Script from above is updated. |
Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
Is it possible to sync recurring event not as a recurring event but split it up into individual events?
Additional context
No response
The text was updated successfully, but these errors were encountered: