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
Import: check if UID already exists, check which one is newest and update if necessary. #1508
Comments
I'm guessing you mean when importing data in an existing calendar, it makes little sense when creating a new one (UIDs are only unique in their calendar - even though there should be globally unique). |
Yes, only for existing calendars. |
(Is this why I've been beating my head against a wall trying to update events via import?) The iCal spec (ref 5545) says that event updates should occur based on UID and SEQUENCE (and/or based on DTSTAMP and/or LAST-MODIFIED). If we're doing an import, shouldn't one or more of those fields be referenced? It's a common enough use-case (I believe) for a user to upload an updated (externally-provided) (I think my only workaround at the moment is to either delete all updated events and reimport them, ignoring all import failures. Sadly, this means I need to know which have been changed. Lacking that, I often end up deleting all events in that category and time-span and re-importing everything. It works well enough and all other users of that calendar eventually get what they need, I think ... but it defies the RFC/spec, and I'm not 100% certain that some client won't out-smart this somehow, such as based on UID.) |
Currently the API returns this error when a user tries to import an updated event invitation.
In the calendar web interface it looks like this |
A related issue in server nextcloud/server#30096 was closed last year, though it is still happening. Can a dev comment please? |
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: