[Bug]: moving shared folders take really long
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
Moving a folder shared with me takes really long, but it should only change the "mount point" in the share table so it should be super fast
Steps to reproduce
- Tried on c.nc.com
- Try one of our larger company wide shares
- Move them to a different folder (using the "move or copy"-operation of the web interface), in my case I want to organize all the important folders in a top-level folder "company"
- The moving folder notification with a spinner is visible for minutes:
- If I open the target folder, in my case "company" the share is already there.
Either is is just a bug in the notification, that it doesn't disapear or the server does some strange stuff while it should only change the mount point in the share table.
Expected behavior
operation should be super fast.
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
Start by reproducing the move-or-copy operation for a large shared folder in the web interface, then compare when the share appears in the target folder with when the moving notification spinner disappears. Determine whether the delay is in the server operation or only the notification; done means the operation and its notification complete promptly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- full-stack, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100