nextcloud / nextcloud/server

[Bug]: Sharing records are not deleted after a file/folder has been permanently deleted

Open
#49,932 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 28-feedback bug feature: sharing 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

Right now, deleting a file/folder does not delete its corresponding sharing records. After a file/folder has been deleted, sharing records should also be deleted.

Steps to reproduce
  1. Create a file/folder
  2. Share the created file/folder
  3. Permanently delete that file/folder
  4. Check table oc_share
    Expect: It's sharing records deleted
    Actual: It's sharing records still exist
Expected behavior

Sharing records should also be removed from the oc_share table.

Nextcloud Server version

28

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

Reproducible on 28, 29, 30, master

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 reproducing the four listed steps on a supported Nextcloud version and inspect the oc_share table after permanent deletion. Trace the file or folder deletion path and its sharing-record handling; done means the corresponding sharing records are removed, with regression coverage for the reported behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.