Skip to content

Conversation

@SebastianKrupinski
Copy link
Contributor

@SebastianKrupinski SebastianKrupinski commented Dec 16, 2025

Summary

  • Resolves User Data Migration calendar#7793
  • refactored dav calendar export to use export service to prevent memory exhaustion
  • refactored dav calendar export to calendar add meta data to archive
  • refactored dav calendar import to use import service to prevent memory exhaustion
  • refactored dav calendar import to use calendar meta data from archive
  • made import backwards compatible to import version 1 archives.

Checklist

Comment on lines +310 to +314
if (str_starts_with($line, 'X-WR-CALNAME:')) {
$calendarName = substr($line, 13);
} elseif (str_starts_with($line, 'X-APPLE-CALENDAR-COLOR:')) {
$calendarColor = substr($line, 23);
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why relying on non-standard properties since you've already got this information in the calendar meta?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is for compatibility... the first version of the migrator only created a single ICS file with custom properties for the name... part of the improvements is the ".meta" file.

Signed-off-by: SebastianKrupinski <[email protected]>
@SebastianKrupinski SebastianKrupinski force-pushed the feat/improve-calendar-migrator branch from d27c7f9 to 1899e5f Compare January 12, 2026 18:05
@nextcloud-bot nextcloud-bot mentioned this pull request Jan 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews

Projects

Status: 🏗️ In progress

Development

Successfully merging this pull request may close these issues.

User Data Migration

3 participants