[Bug]: Resharing broken
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 I try to reshare a file on c.nc.com I see a spinner for ever. When I reload the browser I get a error message that the file couldn't be shared by the new recipient is now in the list.
If I want to unshare it again nothing happens at all when I click on "delete share"
Steps to reproduce
- Try to re-share a file which was shared with your on c.nc.com
- You see a endless spinner on the "Share" button
- After reload the new recipient is in the share list
- Now try to unshare it again
- Clicking on "delete share" gets completely ignored
Expected behavior
Re-sharing should be super fast without an error. It is "just" a entry in our share table and maybe in the activity table for three users (owner, person who reshared, recipient)
Nextcloud Server version
31
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
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
No files, tests, or entry points are named. Reproduce the resharing and delete-share steps from the issue, then trace the Nextcloud Server sharing flows and their browser behavior; done means resharing completes without a persistent spinner or error and the new share can be deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100