You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the quota of an existing user is changed from the web interface to the default or unlimited quota, the message "An error occurred during the request. You cannot continue.
Invalid quota value null".
From the command line it does work.
Steps to reproduce
1.. From Web interface, select existing user and edit.
2. Change quota to "Default" or unlimit quota.
3. Error messages show ""An error occurred during the request. You cannot continue. Invalid quota value null"".
Expected behavior
No errors should be displayed and the user should have the default or unlimited quota assigned.
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
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?
I've been trying a few things. I restored an image of the same server before upgrading to version 28.0.1. I confirm that in version 27.1.4 and 27.1.5 and the problem does not occur. It works correctly.
Bug description
When the quota of an existing user is changed from the web interface to the default or unlimited quota, the message "An error occurred during the request. You cannot continue.
Invalid quota value null".
From the command line it does work.
Steps to reproduce
1.. From Web interface, select existing user and edit.
2. Change quota to "Default" or unlimit quota.
3. Error messages show ""An error occurred during the request. You cannot continue. Invalid quota value null"".
Expected behavior
No errors should be displayed and the user should have the default or unlimited quota assigned.
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
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?
None
What user-backends are you using?
Configuration report
List of activated Apps
# sudo -u www-data php /var/www/nextcloud/occ app:list Enabled: - activity: 2.20.0 - admin_audit: 1.18.0 - bruteforcesettings: 2.8.0 - circles: 28.0.0-dev - cloud_federation_api: 1.11.0 - comments: 1.18.0 - contacts: 5.5.1 - contactsinteraction: 1.9.0 - dashboard: 7.8.0 - dav: 1.29.1 - federatedfilesharing: 1.18.0 - federation: 1.18.0 - files: 2.0.0 - files_accesscontrol: 1.18.0 - files_automatedtagging: 1.18.0 - files_external: 1.20.0 - files_fulltextsearch: 28.0.0 - files_pdfviewer: 2.9.0 - files_reminders: 1.1.0 - files_sharing: 1.20.0 - files_trashbin: 1.18.0 - files_versions: 1.21.0 - fulltextsearch: 28.0.0 - fulltextsearch_elasticsearch: 28.0.0 - impersonate: 1.15.0 - jitsi: 0.18.0 - logreader: 2.13.0 - lookup_server_connector: 1.16.0 - nextcloud_announcements: 1.17.0 - notifications: 2.16.0 - oauth2: 1.16.3 - onlyoffice: 9.0.0 - password_policy: 1.18.0 - photos: 2.4.0 - previewgenerator: 5.4.0 - privacy: 1.12.0 - provisioning_api: 1.18.0 - recommendations: 2.0.0 - related_resources: 1.3.0 - serverinfo: 1.18.0 - settings: 1.10.1 - sharebymail: 1.18.0 - support: 1.11.0 - survey_client: 1.16.0 - systemtags: 1.18.0 - text: 3.9.1 - theming: 2.3.0 - twofactor_backupcodes: 1.17.0 - updatenotification: 1.18.0 - user_ldap: 1.19.0 - user_status: 1.8.1 - viewer: 2.2.0 - workflowengine: 2.10.0 Disabled: - encryption: 2.16.0 - files_retention: 1.16.0 (installed 1.16.0) - files_rightclick: 0.15.1 (installed 1.6.0) - firstrunwizard: 2.17.0 (installed 2.16.0) - suspicious_login: 6.0.0 - twofactor_totp: 10.0.0-beta.2 (installed 8.0.0-alpha.0) - weather_status: 1.8.0 (installed 1.6.0)
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: