Skip to content

No access to Team folders created with option "Do not grant any advanced permissions by default"聽#4495

Closed
#4564
Closed
No access to Team folders created with option "Do not grant any advanced permissions by default"#4495
#4564
Labels
0. Needs triageIssues that need to be triagedbug

Description

@jonasv1
jonasv1
opened on Mar 9, 2026

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

  1. Create new Team folder with option 芦Do not grant any advanced permissions by default禄, share with group (write/share/delete) and activate Advanced Permissions.
Image
  1. Add new Advanced permission rule for group: allow read/write/create/delete
Image
  1. Try to upload / create a new file or folder in this Team folder, as a member of the group with read/write/create/delete rights via Advanced permissions.

Expected behaviour

I should be able to upload and create new files or folders.

Actual behaviour

It is not possible to upload / create a new file or folder.

Image

Server configuration

Nextcloud version: 33.0.0

Team folders version: 21.0.6

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

Are you using encryption: no

Activity

  1. jonasv1
    added
    bug
    0. Needs triageIssues that need to be triaged
    on Mar 9, 2026

  2. jonasjelonek commented on Mar 27, 2026

    @jonasjelonek
    jonasjelonek
    on Mar 27, 2026

    This needs a fix in the stable branch or however. I ran Claude over this and it suggested the following change:

    diff --git a/lib/Mount/MountProvider.php b/lib/Mount/MountProvider.php
index 891f7043..1a332d4e 100644
--- a/lib/Mount/MountProvider.php
+++ b/lib/Mount/MountProvider.php
@@ -307,7 +307,7 @@ class MountProvider implements IMountProvider, IPartialMountProvider {
                                $loader,
                                $user,
                                $aclManager,
-                               $folder->acl ? $aclManager->getRulesByFileIds([$folder->rootId]) : [],
+                               $folder->acl ? $aclManager->getRulesByFileIds([$folder->rootId])[$folder->storageId] ?? [] : [],
                        );
                }

    And I can confirm this works on a running instance with Nextcloud 33.0.1.

    @nickvergessen @provokateurin Might one of you take care of such a backport? I would have to fill the PR and commit description what Claude explained to me, and it's not really a backport due to the large commit this change was part of in master branch.
    How about a new release then so this fix gets official?

  3. nickvergessen commented on Mar 27, 2026

    @nickvergessen
    nickvergessen
    on Mar 27, 2026
    Member

    I'm not affiliated with this app

  4. provokateurin commented on Apr 15, 2026

    @provokateurin
    provokateurin
    on Apr 15, 2026
    Member

    Fix is at #4564. This was already fixed on master, but forgotten to backport to stable33.

  5. provokateurin
    linked a pull request that will close this issue[stable33] fix(MountProvider): Fix ACL no permissions by default #4564on Apr 15, 2026

  6. jonasjelonek commented on Apr 15, 2026

    @jonasjelonek
    jonasjelonek
    on Apr 15, 2026

    Fix is at #4564. This was already fixed on master, but forgotten to backport to stable33.

    Thank you!

  7. provokateurin
    closed this as completedon Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    0. Needs triageIssues that need to be triagedbug

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions