nextcloud / nextcloud/deck

Own deck card actions not handled correctly

Open
#4,303 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug feature: activity feature: notification
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

https://github.com/nextcloud/deck/blob/5669bd73cc6d735984c1afac1ab189f21bbfc082/lib/Activity/DeckProvider.php#L89

$this->userId is mostlikely not set in background jobs and when sending activity emails.
Should use \OCP\Activity\IManager>getCurrentUserId() instead.

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 in lib/Activity/DeckProvider.php at line 89 and inspect how the user ID is obtained for own deck card actions. Check the background-job and activity-email paths mentioned in the issue. Done means those paths use the current activity user ID reliably instead of an unset $this->userId.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.