nextcloud / nextcloud/groupfolders

Collision between names of two or more groupfolders

Open
#681 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug hot spot: collisions
Dominant language
PHP
Stars
343
Forks
106
Avg merge
2d 3h
Merged PRs (30d)
34

Description

Hello and thanks,

here is my process description of group folders.

I don’t want to have the users create their own folders. So I keep their contingent at 0 Bytes.
This works perfect. So they are only able to see the folders, which are shared over the group folders app. So no personal folders.

I create a user group, let’s say customername.projectname
I add a project user to the newly created group
I go to group folders settings in the admin panel.
I create a new folder like customername.projectname and add the newly created group.
Now the issue is, that I’m able to create the same foldername again an again again …
So this is really misleading. The System should tell me, that the folder with the same name already exists, not more. Like in Unix or Windows. This is a basic requirement, which does not meet in group folders.

Frankly I could not understand your technical solution exactly, could please explain it in detail.

Many thanks
image

Haydar

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the duplicate-name behavior through the Group folders settings in the admin panel, using the creation process described in the issue. Trace the PHP code handling folder creation and its validation; done means attempting an existing name produces a clear error and does not create another folder.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.