Skip to content
New issue

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

Inconsitent handling of shared folders that is inaccessible #588

Closed
mickenordin opened this issue Aug 30, 2024 · 1 comment
Closed

Inconsitent handling of shared folders that is inaccessible #588

mickenordin opened this issue Aug 30, 2024 · 1 comment

Comments

@mickenordin
Copy link

This is similar to #97 but I think behaviour has changed enough to warrant a new report.

Steps to reproduce

  1. Create a tag
  2. Create a flow that denies access to the tag (but perhaps not to yourself)
  3. Create a folder with said tag
  4. Share the folder with someone

Expected behaviour

Folder is never visible anywhere OR folder is visible and greyed out (and a limited details view is accessible). I think I prefer the latter solution, because then at least user can get some indication that there is some access issue. Having the folder there, but greyed out would solve any other issues with confused clients as well.

Actual behaviour

Folder is visible in dashboard and in "shares" meny in files app, but not visible in the list in the files app

Server configuration

Nextcloud 29 with files_accesscontrol

Below are screenshots from this scenario where ''Admin" shares a folder with "Ordinary User":

Create folder with tag and share it

2024-08-30T16:15:43,925091604+02:00

Create flow to block

2024-08-30T16:16:36,650880916+02:00

User logs in and sees folder

2024-08-30T16:12:07,451974240+02:00

User sees folder in overview but not list

2024-08-30T16:11:47,351516017+02:00

User sees folder in shares, but cannot access details

2024-08-30T16:11:23,402776230+02:00

@nickvergessen
Copy link
Member

Duplicate of #544
Most important details in #544 (comment)

@nickvergessen nickvergessen closed this as not planned Won't fix, can't repro, duplicate, stale Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants