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

Only VEVENT for birthday calendar and default order to 1 #28011

Merged
merged 2 commits into from Jul 7, 2017

Conversation

tomneedham
Copy link
Member

@tomneedham tomneedham commented May 25, 2017

Description

New calendars are given a default order of 1, to always be after the default birthday calendar.

The system birthday calendar is created with VEVENT only, not VTODO as this is not possible.

Motivation and Context

Causes issues when the birthday calendar is used for accepting events or if TODOs are created in that calendar.

How Has This Been Tested?

  • New install and observing the created calendars
    before:
    screen shot 2017-05-25 at 14 17 58
    after:
    screen shot 2017-05-25 at 14 43 50

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@tomneedham tomneedham added this to the 10.0.2 milestone May 25, 2017
@tomneedham tomneedham force-pushed the fix-cal-birthday branch 2 times, most recently from 7eec4f0 to 66dca8c Compare May 25, 2017 13:42
@tomneedham
Copy link
Member Author

@DeepDiver1975 I can't find the code path for accepting an event from another user and where it is inserted into your calendar? Wanted to check where the logic is for choosing the calendar to insert it into.

@tomneedham
Copy link
Member Author

@DeepDiver1975 hmm so I see there is already a migration to fix this - https://github.com/owncloud/core/pull/25636/files but annoyingly the fix didn't work. How often is that repair step called - as we still have corrupt birthday calendars

@DeepDiver1975
Copy link
Member

fixes #26746

@DeepDiver1975
Copy link
Member

@DeepDiver1975 I can't find the code path for accepting an event from another user and where it is inserted into your calendar? Wanted to check where the logic is for choosing the calendar to insert it into.

It is within the sabre dav libs:

this propfind handles the calendar selection - https://github.com/fruux/sabre-dav/blob/master/lib/CalDAV/Schedule/Plugin.php#L240
this is where the local delivery happens - https://github.com/fruux/sabre-dav/blob/master/lib/CalDAV/Schedule/Plugin.php#L444

@DeepDiver1975
Copy link
Member

@DeepDiver1975 hmm so I see there is already a migration to fix this - https://github.com/owncloud/core/pull/25636/files but annoyingly the fix didn't work. How often is that repair step called - as we still have corrupt birthday calendars

best would be to add a migration from my pov

@tomneedham
Copy link
Member Author

fixes #26746

yes should do - since I just push the birthday to the bottom of the users list

->execute();

$output->info("$updated birthday calendars updated.");
Copy link
Member

Choose a reason for hiding this comment

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

lets keep the logging in here

@DeepDiver1975 DeepDiver1975 self-assigned this Jul 7, 2017
@lock
Copy link

lock bot commented Aug 3, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants