nextcloud / nextcloud/calendar
Hidden task still visible in embedded calendar
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Have a Nextcloud calendar supporting tasks
- Create a new task with a due date
- Set that task to don't display when shared

- Embed that calendar to a website like the following example:
<iframe src="https://mynextcloud.example.com/apps/calendar/embed/crypticcode123/listMonth/now"></iframe>
Expected behavior
A task that is set not to be displayed when shared should not be displayed publicly when the calendar is shared (via embedding).
Actual behaviour
The task will be displayed publicly in that calendar on that website.

Calendar app version
3.4.0
CalDAV-clients used
no client
Browser
Firefox 102.0.1
Client operating system
Windows 10
Server operating system
No response
Web server
No response
Database engine version
No response
PHP engine version
No response
Nextcloud version
23.0.6
Updated from an older installed version or fresh install
No response
List of activated apps
* calendar
* tasks
* contacts
* group folders
* TOTP
Nextcloud configuration
No response
Web server error log
No response
Log file
No response
Browser log
No response
Additional info
This is a managed Nextcloud instance, managed by hosting.de. Therefore I do not have access to server versions, logs, etc..
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the embedded-calendar case described in the issue, using a task marked not to display when shared. Trace the embedded calendar and task-sharing handling, then verify that the task is absent from the public embed while other calendar content remains visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100