nextcloud / nextcloud/server

[Bug]: Delete permission is always disabled on files

Open
#52,954 3 comments 0 reactions 1 assignee View on GitHub

@artonge is already working on this.

Since May 19, 2025.

0. Needs triage 30-feedback bug feature: files feature: sharing
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

Delete permission is auto-disabled on files, and becomes grayed out randomly. Seems like a bug.

https://private-user-images.githubusercontent.com/6960329/426956272-87545375-e26a-48bc-b883-e5afac2934e1.mov?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDc2NTI0MzIsIm5iZiI6MTc0NzY1MjEzMiwicGF0aCI6Ii82OTYwMzI5LzQyNjk1NjI3Mi04NzU0NTM3NS1lMjZhLTQ4YmMtYjg4My1lNWFmYWMyOTM0ZTEubW92P1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDUxOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTA1MTlUMTA1NTMyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NGE5ZTFjYjlhZTE4NjJlZjkyNDkxYTY3OTRjMzU1MDM0OWNlNWMwODNmNjAxNDZiZGZkMzdkOWVjNjc0YjlhNCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.eHPuHVlcsj0Rml8eL35c2_zYnw1l57g-sSLjgOW0uxE

Steps to reproduce
  1. Create user share on file
  2. Observe
Expected behavior

Should not be showing. On mobile clients it is not showing.

Nextcloud Server version

30

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.