nextcloud / nextcloud/server

Fix or retire legacy notifications in the Updater to avoid constant updater notifications if the Notifications app is disabled

Open
#43,645 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: activity and notification feature: install and update papercut technical debt
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
Yes, when there is a brand new update that I can't update to, because some of my extensions aren't yet compatible with it, I keep getting annoying popups that are telling me I should update to new version every single time I load any page, or refresh it. I need to disable this.

Describe the solution you'd like
I want to be able to disable all those annoying update notifications.

Describe alternatives you've considered
I was looking through the admin configuration, couldn't see any option to disable it.

Additional context
image

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 tracing the Updater's legacy notification path and how it behaves when the Notifications app is disabled. The issue names no files or tests, so first locate the Updater entry point and related Notifications app handling. Done means the repeated updater notifications no longer appear in that state, with the intended supported behavior agreed.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.