-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Closed
Labels
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
After an ownership transfer (via the web interface), sub shares can be broken and it's impossible to restore.
Steps to reproduce
- userA shares a folder D1 with userB
- userB creates and shares a subfolder D2 and shares it with userC
- userA revoke the share of D1 with userB
- userA transfers ownership of D1 to userD
After userD accepts the transfer:
- userC loses access to the folder D2
- if userD tries to share the folder D2 with userC : error message "Node for share not found, fileid: 132472"
Expected behavior
My suggestion for expected behavior:
Re-share should be deleted if restore failed to not block creating new share for the same user.
Installation method
Community Docker image
Nextcloud Server version
master
Operating system
None
PHP engine version
None
Web server
None
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
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
☑️ Done