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

Collision detection for group folder target #648

Closed
rullzer opened this issue Oct 21, 2019 · 4 comments · Fixed by #1239
Closed

Collision detection for group folder target #648

rullzer opened this issue Oct 21, 2019 · 4 comments · Fixed by #1239
Labels
1. to develop Issues that are ready for development bug

Comments

@rullzer
Copy link
Member

rullzer commented Oct 21, 2019

With the revert in #647 we have the following issue again:

  1. Create a folder 'foo' for user 'bar'
  2. Add some files
  3. Now an admin sets up a group folder 'foo'
  4. 'bar' loses access to their original 'foo'

@icewind1991 any idea how to solve this?

@PVince81
Copy link
Member

also see #1246

@ChristophWurst
Copy link
Member

Potential fix at #1239

@KodoGit
Copy link

KodoGit commented Sep 2, 2021

Looks like #1246 leads here. The problem still exists with NC 21.0.4 docker (nextcloud:21-apache) with GF 9.0.3
Just updated from 20.

@fschrempf
Copy link
Contributor

Looks like #1246 leads here. The problem still exists with NC 21.0.4 docker (nextcloud:21-apache) with GF 9.0.3

#1246 and #681 are about collisions between two groupfolders with the same name. This issue is still unresolved.
Whereas this issue seems to be about name collisions between a normal directory and a groupfolder. This issue is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop Issues that are ready for development bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants