nextcloud / nextcloud/groupquota
Quota is not displayed until the user performs the first login
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 35
- Forks
- 10
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
I'm adding users via API
curl -s -X POST https://admin:password@$mydomain.com/ocs/v1.php/cloud/users \
-H "OCS-APIRequest: true" \
-d userid="username" \
-d password="password"
then create group for him and configure group quota
curl -s -X POST https://admin:password@$mydomain.com/ocs/v1.php/cloud/groups \
-H "OCS-APIRequest: true" \
-d groupid="groupname"
curl -X POST https://admin:password@$mydomain.com/apps/groupquota/quota/groupname -H "OCS-APIRequest: true" -d 'quota=3GB'
<?xml version="1.0"?>
<ocs>
<meta>
<status>ok</status>
<statuscode>100</statuscode>
<message>OK</message>
<totalitems></totalitems>
<itemsperpage></itemsperpage>
</meta>
<data>
<quota_bytes>3221225472</quota_bytes>
<quota_human>3 GB</quota_human>
<used_bytes>0</used_bytes>
<used_human>0 B</used_human>
<used_relative>0</used_relative>
</data>
</ocs>
But in interface I see Unlimited quota for this user (user is single user of the group)
In the same time occ reports right quota:
sudo -u www-data php /var/www/nextcloud/occ groupquota:get groupname
3221225472
In interface Unlimited value will be changed after first login.
Tested on Nextcloud v26.0.2 with Group Qouta v0.1.11 on fresh instance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue on Nextcloud v26.0.2 with Group Quota v0.1.11 using the API commands in the report, then compare the interface with occ groupquota:get groupname before and after the user's first login. Done means the interface displays the configured group quota immediately after the user and group are created, without requiring a login.
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
- Mostly clear
- Newbie friendliness
- 35/100