[Bug]: Cannot save custom share permissions when all permissions are selected
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
When selecting Custom Permissions in the shared users list and granting Read, Create, Edit, Share, and Delete permissions all at once, the settings cannot be saved.
The settings can only be saved if at least one permission is removed.
Steps to reproduce
When selecting Custom Permissions in the shared users list and granting Read, Create, Edit, Share, and Delete permissions all at once, the settings cannot be saved.
The settings can only be saved if at least one permission is removed.
Expected behavior
Description:
When selecting Custom Permissions in the shared users list and granting Read, Create, Edit, Share, and Delete permissions all at once, the settings cannot be saved.
The settings can only be saved if at least one permission is removed.
Nextcloud Server version
32
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Nginx
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
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
Start by reproducing the custom-permission save failure in Nextcloud Server 32 with all five permissions selected. Trace the share-permission save flow to identify why the complete permission set is rejected, then verify that the settings save successfully and remain correct after reloading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100