nextcloud / nextcloud/groupfolders

FQ/BUG: Shared Links within Teamfolders break when the user who created them gets deactivated/deleted

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

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
PHP
Stars
343
Forks
106
Avg merge
2d 3h
Merged PRs (30d)
34

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • 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.
Steps to reproduce

Prerequituses
Set Up "Groupfolder 1"
Set up User A
Have Both Of them in "Group 1"

  1. As user A > Create a file in "Groupfolder 1" and create a public link for it.
  2. As "anonymous User from the Web" > Open the link in a new browser to chek if its working (it is)
  3. As "Nextcloud Administrator" deacitvate/delete User A
Expected behaviour

Link from Step 2. shall still be valid and Working

Actual behaviour

Link is no longer Valid ("Site not found")

Server configuration

Operating system:
Linux 6.8.0-87-generic x86_64
Web server:

Database:
mysql
Version: 10.11.15

PHP version:
8.3.27
Nextcloud version: (see Nextcloud admin page)
Nextcloud Hub 10 (31.0.10)

Team folders version:
Version 19.1.12

Updated from an older Nextcloud/ownCloud or fresh install:
fresh install

Where did you install Nextcloud from:
Hoster

Are you using external storage, if yes which one: local/s3/smb/sftp/...
no
Are you using encryption: yes/no
no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/Saml/...
no

Client configuration

Browser:
FF / Opera
Operating system:
Windows

Logs

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 files or tests are named in the issue. Reproduce the Team folders public-link flow with a user who is then deactivated or deleted, and trace the link handling to determine why access changes; done means the existing link remains valid afterward.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
authorization, backend
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.