nextcloud / nextcloud/server

[Bug]: Error: You are not permitted to move this file"

Open
#62,396 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 32-feedback bug feature: sharing
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

Full disclosure: I have no access to the server right now, can I update from webview?
Bug: As a User I cannot move some files, but can move some. I had some of the shared, but not all of them, and in the same folder I had another folder which was easily moved. With the others I get "some files could not be move" in webview and "you have no permission to move this file" in mobile. I own the folders and file, dont know what the permission issue could be.
I undid the sharing, reloaded, relogin, no effect.
@Edit: Cant rename them either...
@edit2: New files uploaded in the same folder show no issue, if I copy an old file, the issue preceeds afterwars: no rename or move of copied files

Steps to reproduce

1.Create new Folder
2.Move one old folder/file
3.Error

Expected behavior

The folder should simply be moved.

Nextcloud Server version

32

Operating system

Debian/Ubuntu

PHP engine version

Other

Web server

Other

Database engine version

Other

Is this bug present after an update or on a fresh install?

No response

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
I dont have the info on the questions where "Other" is selected. Installed Nextcloud as AIO wiht Docker
List of activated Apps

Nextcloud Signing status

Nextcloud Logs
No entry.
Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start with the reported reproduction steps, comparing an old or copied file with a newly uploaded file, and inspect the server behavior for move and rename requests; done means affected files can be moved and renamed without permission errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.