Guests can't see files when Collectives are enabled

[enoch85]

Actual behavior

When using the guests app in combination with Collectives newly invited guest can only see this:

Creating a regular user (non admin or admin) doesn't have this behavior, everything shows up as normal.

We checked the Collectives app as a guest user, and even if a Collective is created, it still aren't aware of the mapping for the Collectives folder. It just says something like "Please create a Collective to be able to choose location". Non-guest users doesn't have this issue though.

What we tried:

1. Remove all the limitations in the Guests app
2. Disable Collectives app

In both cases, the same issue appears.

Expected behavior

When a new user is invited, they should be able to see everything, just as a normal user.

Settings:

Nextcloud version
27.0.2

PHP
8.2

Server
Ubuntu server 22.04

[small1]

To add information.

If you are a guest you typically dont have any rights to create folders or files. But if someone shares something to you you have that.

The skeleton folder doesn't seem to be copied in for guests. And apps like collectives cant create the /Collectives folder that is necessary for the app to work as it should.

There need to be some special handling for apps that needs a folder to be there for mount points. Like Collectives or if you create a special folder where content should be shared to.

Not sure if this belongs here or if we should create bugs in the other repositories as well.

[juliushaertl]

I would move this to the collectives app, as the fix should be applied there

[small1]

@juliushaertl it also affects if you have files shared to a folder we have one called "/Shared with me" in this case. That doesnt work either.

[juliushaertl]

In that case a separate bug report in server (for the files_sharing app) would be appreciated

[enoch85]

@small1 Can you create the issue report on server an link it here please?

[max-nextcloud]

Removed the logs from the description as the exception thrown there is tracked in #828 and fixed now.

@enoch85 Could you check if the latest release of collectives (2.7.1) also fixed this issue for you?

[enoch85]

@max-nextcloud It's 50% solved.

Users can now see shared documents, but they still get the message "This folder is best shown in Collectives", and "You don't have permission to upload anything here".

[max-nextcloud]

How did you invite the guest users?
My understanding is that they typically are granted access by sharing a file with them. Is that what you did? Which file did you share? Is it part of a collectives folder or so?

The message "You don't have permission to upload anything here" is correct, right? I mean these are guest accounts and they are not in a writeable share folder.

[small1]

We invite them in the guests app. What happens is that the collective folder can't be created and thus thinks that / should be the folder to store everything in.

If we create that manually and scan the users files it will work as it should

[enoch85]

@max-nextcloud

Yes, user was "created" (rather activated) by sharing Testdockument.txt through email to my own user [email redacted].

I'm not sure about the permissions, but you're probably right. Though the file is not part of Collectives and has nothing to do with Collectives at all.

[max-nextcloud]

Hum... just a wild guess. Maybe collectives cannot create the folder for it's mountpoints - falls back to the root folder and from there on thinks all folders are belong to it.

Funny thing is that we have not observed this behavior on our own instance with guest users.

[max-nextcloud]

@enoch85 Could you share the Collectives folder with them? I'd be curious what happens then:

• The user should now have a folder with the correct name to put collectives into. So maybe it stops treating the root folder as one?
• The folder contains the mount points of your own collectives. I don't know if they will be shared as well. Would be curious to hear.

[small1]

@max-nextcloud I did that test when we filed the bug. Folder wasn't created. It started working correctly after we created the collective folder manually