nextcloud / nextcloud/calendar

The invited attendee can invite others to someone else's personal calendar (but in reality, he cant)

Open
#6,735 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce
  1. User A invites B to an event in personal A calendar.
  2. B accepts
  3. B invites user C to the event.
Expected behavior

User C receives the invitation, or user B receives an error saying he cannot invite attendees

Actual behavior

User B sees that the invitation was sent, but in reality, it was not. User С doesn't know anything about this event.
Additionally, for user A, the participants remain unchanged. After some time, user B also sees that participant C is no longer in the event.

Calendar app version

5.0.9

CalDAV-clients used

No response

Browser

No response

Client operating system

No response

Server operating system

No response

Web server

None

Database engine version

None

PHP engine version

None

Nextcloud version

No response

Updated from an older installed version or fresh install

None

List of activated apps

Nextcloud configuration

Web server error log

Log file

Browser log

Additional info

In my case, if B is indeed able to invite other attendees.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are identified. Start by reproducing the invitation flow described for users A, B, and C, then inspect the related calendar invitation and permission handling; done means user C receives the invitation or user B gets a clear error, with participants remaining consistent.

Written by the indexing model from the issue text.

Assessment

Domain
authorization, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.