nextcloud / nextcloud/groupfolders
Multiple regressions in TeamFolders > 21.0.0 : Can’t override more than one inherited ACL
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 343
- Forks
- 106
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 34
Description
Hello,
Since Teamfolders > 21.0.0, it is not possible to correctly override inherited permissions.
Steps to reproduce
- Having a TF configured with two groups, a reader group (R----) and an updater group (RWCD-). We have a root dir with those permissions, and a ‘subdir’ directory inside
- On the subdir, open the share panel and browse the Advanced permissions for Team folder
- Edit one permission from one of the two groups (eg. Adding SHARE to ‘updater’). A new line is then created.
As such, we are not able to override more than a single rule in a teamfolder subdirectory.
Expected behaviour
We should be able to override every rules as before, to fine tune our folder structures. Hopefully rules from previous versions are kept, but we haven’t checked.
Actual behaviour
We are not able to override more than a single rule in a teamfolder subdirectory, preventing us to create fine tuned folder structures like before.
Server configuration
• NC 33.0.3
• TF 21.0.7
◦ acl-inherit-per-user is true
Tested on multiple Nextcloud Instances
Reported by @ThibautPlg
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Team folder share panel's Advanced permissions flow and reproduce the issue with reader and updater groups on a subdirectory, using the reported Nextcloud 33.0.3 and TeamFolders 21.0.7 configuration. Trace how inherited ACL rules are overridden when a second group permission is edited; done means multiple inherited rules can each be overridden without creating an unusable extra line.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authorization, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100