nextcloud / nextcloud/server

[Bug]: Users With 0B Quota Cannot Delete Folders In External Storage

Open
#57,375 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 32-feedback bug feature: external storage feature: trashbin
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

We have a use case where some users are given a quota of 0 (zero) bytes and have access to an external storage folder. This keeps all departmental files together and allows for sharing continuity when users leave employment. They are not allowed to upload or share from their "home" directory and must use the external storage. In version 32.0.3 using this technique they can go into the external storage, they can create folders, they can upload files and share. BUT, if they then delete the folder it gives them an error of [Delete folder: Failed]. The UI then does not refresh at all. However if you refresh the page with the browser it gives you a message [The file could not be found] and the folder is actually gone. If I give the user even a 1KB quota, it all works as expected. So for sure this is an issue with quota and deleting folders in external storage.

Steps to reproduce

1.Give user access to an external storage folder
2.Set their quota to zero bytes
3.Create a folder in the external storage folder
4. Delete that folder and receive the [Delete folder: failed] error

Expected behavior

The user should receive no error, the folder should delete and the UI should refresh.

Nextcloud Server version

32

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.

Research direction

No source file or test is named. Start by reproducing the failure with a zero-byte quota and an external-storage folder, then trace the quota and folder-delete handling; done means deletion succeeds without an error and the UI refreshes correctly.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.