nextcloud / nextcloud/updater

Exclude custom themes from write permissions check

Open
#70 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: writability
Dominant language
PHP
Stars
51
Forks
40
Avg merge
2d 19h
Merged PRs (30d)
3

Description

bildschirmfoto 2016-12-14 um 17 24 53

Custom themes should be excluded from the write permission check, as they are not going to be part of the update anyway.

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

The issue names no files, tests, or entry points. Start by locating the updater's write-permission check and trace how custom themes are included in the update set. Done means custom themes no longer affect that check while other update targets retain the existing permission validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.