search

sawhney17 / logseq-calendars-plugin

MIT License
128 stars 17 forks source link

Imported events don't match current calendar state #32

Open mkosma opened 2 years ago

mkosma commented 2 years ago

Not sure why, but I have several cases where the data imported doesn't match the current state of my calendar:

This isn't a time lag - my calendar entries imported for today are showing entries that I adjusted over a week ago.

lsharkey commented 2 years ago

I am having this or a similar issue as well, (using Google Calendar) and from the testing I did, it seems like it has to do with when an instance of a recurring event is modified, and the change is made for only that instance, and not for "All Events."

The details of what I did to test are below.

Environment:

This is everything I tried:

  1. Import calendar for the day - works as expected.
  2. I change a meeting time directly on my google calendar
  3. Import calendar again - the new import still shows the old meeting time.
  4. Close Logseq, shut down computer, wait 12 hours
  5. Try import again - the new import still shows the old meeting time.
  6. Tried a change from 12 hour to 24 hour format in the plugin; made no difference.
  7. Uninstalled plugin
  8. Removed logseq-calendars-plugin_layouts from /.logseq/settings (verified all other files were already gone from /.logseq/settings and /.logseq/plugins
  9. Did a system-wide search for basic.ics - it doesn't exist anywhere on the system.
  10. Reset the "secret" link on my calendar.
  11. Re-installed the plugin.
  12. Added the "secret" link and a calendar name, but left all other settings as default.
  13. Run import.
  14. Meeting still shows with old time.
  15. Just to test: changed the time of the meeting again, and this time chose to change time for "All Events"
  16. Close Logseq; relaunch
  17. Run import - time is set accurately to the new time. :heavy_exclamation_mark: :heavy_exclamation_mark: :heavy_exclamation_mark:
  18. Change meeting time again, this time for "Only this event".
  19. Run import - time not correct; reflects time previously, for All Events.
  20. Change meeting time again, this time for "All Events".
  21. Run import - time is set accurately to the new time.

So it looks like, at least in part, it has to do with recurring events that have an exception set?

sawhney17 commented 1 year ago

Would it be possible for you to supply me a test calendar for debugging. On 29 Jun 2022 at 6:37 PM +0400, Monty Kosma @.***>, wrote:

Not sure why, but I have several cases where the data imported doesn't match the current state of my calendar:

• deleted events show up • rescheduled events always seem to show up at the originally scheduled time • recurring events that are cancelled on a single date still showing up

This isn't a time lag - my calendar entries imported for today are showing entries that I adjusted over a week ago. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>