We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug The button "open in collectives" in the files app is visible in every folder, I tested. Even in folders not in a collective.
Clicking on the button will trigger an error message.
I only have a reduced account on the instance (guest account?). That might make a difference.
To Reproduce Steps to reproduce the behavior:
Expected behavior The button should only be visible on real collections.
Screenshots If applicable, add screenshots to help explain your problem.
This is the root folder of my guest account in the cloud.nextcloud.com instance:
Client details:
The text was updated successfully, but these errors were encountered:
fix(FileListInfo): Don't show info header if collectivesFolder is /
/
0b80ac4
This fixes the info header being always displayed for guest users. Fixes: #893 Signed-off-by: Jonas <jonas@freesources.org>
db3f8e7
Successfully merging a pull request may close this issue.
Describe the bug
The button "open in collectives" in the files app is visible in every folder, I tested. Even in folders not in a collective.
Clicking on the button will trigger an error message.
I only have a reduced account on the instance (guest account?). That might make a difference.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The button should only be visible on real collections.
Screenshots
If applicable, add screenshots to help explain your problem.
This is the root folder of my guest account in the cloud.nextcloud.com instance:
Client details:
The text was updated successfully, but these errors were encountered: