-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: wrong permissions attributed to a copy of a file #46248
Comments
I also tried removing one such file with: sudo -u www-data php occ files:delete 87859 -f and the answer is File cannot be deleted, insufficient permissions. |
Add |
Thank you @susnux for your suggestion. |
You need something like this:
|
This is exactly what I have already done (but "your" option is last in my array of arguments). |
Then if you now copy a file you should gain all permissions as the copy is now owned by you |
When I now copy a read-only file, the copy is still read-only |
Have you restarted your FPM processes (so the config is reload / not cached)? Because I tested it right now and with this option copies gain all permissions. |
I have no idea how to check this. I am using the docker version of nextcloud+onlyoffice and fpm is not a service. I only know I am using fpm because the image I use is called 29-fpm. |
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions. |
I have restarted the server multiple times since then. I even updated the nextcloud version. My nextcloud version is now 29.0.6 |
Can you post the output of The Docker image uses multiple config files. Maybe something isn't working as expected here. |
|
Bug description
I start with a folder A with read-only sharing for everyone, and add some files including a file B to it.
A and B are created as an admin.
Then, as a normal user, I create a folder C with full-editing sharing with a group, then copy file B into folder C.
The resulting file is D.
The permissions on file D are read-only, and I cannot find a way to remove it.
My expectation is that the user who made the copy should be able to remove it.
The admin account, with which D is shared with full-editing share from folder C, also cannot remove the file, and I think it should also have.
With the outlined process, files are created that noone can get rid of. I believe that is a bug.
Steps to reproduce
Expected behavior
There should be a way for the user who made the copy to remove the file
Installation method
Community Docker image
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Nginx
Database engine version
MariaDB
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?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: