nextcloud / nextcloud/server

[Bug]: The share settings of a folder are changed automatically

Open
#58,284 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 32-feedback bug
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

I created a "Root Test" folder in the root directory of Nextcloud, which I own, and then I also created a "Level 1" sub-folder within "Root Test". I wanted to share the sub-folder with my colleague GS.
I noticed a bug when I tried to share a folder with my colleague GS. I selected "Custom permissions" so he could also share the "Level 1" folder with someone else: see "Screenshot... Test 1.png" and "Screenshot... Test 2.png". Then I browsed through the Nextcloud folders and finally returned to the "Level 1" sub-folder. I then realized that GS only had edit access to the "Level 1" folder instead of the "Custom permissions" I had initially granted him, as shown on "Screenshot... Test 3.png".
Is it a real bug or a misconfiguration on our Nextcloud server?

Image Image Image
Steps to reproduce
  1. Create a folder A.
  2. Create a sub-folder B in the folder A.
  3. Share the sub-folder B with custom permissions including share permission.
  4. Go to other folder.
  5. Go back to the folder B and look at the share settings.
Expected behavior

I expected to have always the same settings for the shared folder.

Nextcloud Server version

32

Operating system

Debian/Ubuntu

PHP engine version

None

Web server

None

Database engine version

MySQL

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

Updated from a MINOR version (ex. 32.0.1 to 32.0.2)

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 files or tests are named. Start by reproducing the folder-sharing flow: grant custom permissions including share permission to sub-folder B, navigate to another folder, and return to B. Trace where the share settings are loaded and persisted, then verify that the custom permission remains unchanged after navigation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.