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

[stable20] Scheduling plugin not updating responding attendee status #29387

Merged
merged 2 commits into from
Oct 25, 2021

Conversation

backportbot-nextcloud[bot]
Copy link

@backportbot-nextcloud backportbot-nextcloud bot commented Oct 22, 2021

⚠️ This backport had conflicts and is incomplete ⚠️

backport of #28997

Copy link
Member

@st3iny st3iny left a comment

Choose a reason for hiding this comment

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

I tested it like I did in #28997 (review) and it worked fine.

The conflict is irrelevant. It's just a single blank line that is already there.

@st3iny
Copy link
Member

st3iny commented Oct 22, 2021

PS: I believe that static code failure is unrelated.

@MichaIng
Copy link
Member

Incomplete backport is only due to a non-backported empty line which is still present in stable20 (got removed in stable21): https://github.com/nextcloud/server/pull/28997/files#diff-2735671fbe0b06cc294667b7fb4cef974bdf33fbb1d196b409a7f8568595d884

miaulalala and others added 2 commits October 24, 2021 20:23
For local users it's possible to select their calendar via the principal url and first update their own attendance status.
External users have no calendar event hence the recipient is the organizer.

Signed-off-by: Daniel Kesselberg <[email protected]>
@kesselb kesselb merged commit ea92f78 into stable20 Oct 25, 2021
@kesselb kesselb deleted the backport/28997/stable20 branch October 25, 2021 06:56
@blizzz blizzz mentioned this pull request Nov 3, 2021
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants