Can not create folders with a unique name when not having update permissions

[nickvergessen]

Steps

1. As UserA create a folder FolderA
2. As UserA share FolderA with UserB with read+create permissions
3. As UserB try to create a FolderB inside FolderA
4. The folder New folder gets created and due to lack of update permissions you can not rename it:

[skjnldsv]

Suggestion:

• If current folder does not have Update permission
• OR if files_accesscontrol is enabled

we open a modal to request the name instead of creating before and renaming

[sorbaugh]

While this in't good from a UX perspective, due to the lack of Update permissions, Nextcloud is technically behaving "correctly" here, I suppose? Did the behavior change with NC 28?

[nickvergessen]

Nextcloud is technically behaving "correctly" here, I suppose?

The backend yes. The frontend needs to adapt and should only send the MKDIR/PUT request once the user had the chance to give the folder/file name

Did the behavior change with NC 28?

Yes, its a regression from Files2vue migration, immediatelly creating the folder/file as "New folder" instead of taking user input.

[szaimen]

cc @nextcloud/files

[come-nc]

Even without the permission situation, using create+rename instead of just create is annoying, for instance it looks weird in activity:

And users could have flows running at folder creation also.