nextcloud / nextcloud/calendar

Can't hide some deck calendars due to permissions

Open
#4,347 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Steps to reproduce
  1. Have access to a bunch of deck cards - discover you can't disable viewing them.
Expected behavior

When you click to hide them, they should hide.

Actual behaviour

They don't and you get an error

Calendar app version

latest on cloud.nc.c on 4-7-2022

CalDAV-clients used

web

Browser

firefox and chrome

Client operating system

Never Arch linux.

Server operating system

No clue

Web server

No response

Database engine version

No response

PHP engine version

No response

Nextcloud version

latest, 24.something

Updated from an older installed version or fresh install

No response

List of activated apps

No response

Nextcloud configuration

No response

Web server error log

No response

Log file

No response

Browser log
https://cloud.nextcloud.com/s/xwFH2tewmSxsdit
Additional info

Raimond said:

Deck boards are generally not writable, since this is not implemented in Deck yet. This might prevent changing their visibility in the Calendar app.

-> I think this should not prevent users from changing visibility in the Calendar...

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

Start by reproducing the problem with a user who can view Deck cards but cannot modify them, using the web client and the reported Firefox or Chrome setup. Trace how hiding a Deck calendar checks permissions and compare that behavior with ordinary calendars; done means an authorized user can hide the calendar without an error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authorization, frontend
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.