Closed mueller-tobias closed 1 year ago
this seems to be fixed in version 26.0.5 - at least it worked for us. See https://github.com/nextcloud/server/commit/2124fb9ff25529b069dee4ca946969252ab5ef8a
Thanks! I can confirm that the bug is fixed with 26.0.5.
⚠️ This issue respects the following points: ⚠️
Bug description
An user have a quota of 0B as he don't need to upload on his personal folder but only in a group folder (with quota of 500MB)
If both quotas are full, any upload would return an error. Thats fine.
But any other upload as long as the group folder has quota left should complete. I can upload files smaller 10 MB sucessfully. After that nextcloud will try a multi part upload. I've already increase the s3 parameter for putSizeLimit, uploadPartSize and the Files max_chunk_size configuration. But the max file upload when a user has no quota was still 10 MB. With a higher Quota i can automtically upload files according to the limit of the user.
After the upload the file counts correctly against the group folder and not the user quota.
I think it is related to #37436. The user describes the same problem but with an other focus.
With the old "assemble" upload system on nextcloud 25 we had this bug not.
Steps to reproduce
Expected behavior
The upload should complete if there's enough free quota inside the group folder. It shouldn't necessary to give the user a personal quota to upload files to a group folder.
Installation method
Community Docker image
Nextcloud Server version
26
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response