-
Notifications
You must be signed in to change notification settings - Fork 107
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
File permissions revert to 0770 after file modification #530
Comments
I can confirm this. Also, new WordPress sites have all file permissions at 0770 instead of 0660. |
That's not a bug. 660 is correct if you have only one user. Many projects have multiple users working on one site, where group write permissions are needed. |
No, the new files are set at 0770, the same as the folders. The files should be 0660. Just try creating a new WP site, and you'll see. |
I have almost similar issue. changing file permission is not working. it saves but always going back to the previous permission |
I'm trying to understand how the user structure and security is thought of under CloudPanel, and this 0770 global permission per [site] is a bit strange. Please explain why a WordPress website should run under multiple users? The recommended file and folder permissions for WordPress are 755 for directories and 644 for most files. These permissions are necessary for WordPress auto updates to work properly. I understand that for other types of projects (not WordPress) more users may be needed and then they are added to the group. But this raises the risk that a certain user (let's name him HACKER1) will be added to several groups and then we have a big problem. |
CloudPanel version(s) affected
2.4.2
Description
When I make modifications to a file via the file manager, the file permissions that were initially set to 0644 are automatically changed to 0770 after the modification. This behavior causes permission issues, and I would like the permissions to remain unchanged after editing a file.
How to reproduce
You can also test this with a folder:
Possible Solution
A potential fix would be to modify the way file permissions are handled after edits in the file manager, ensuring that the initial permissions remain intact unless explicitly changed by the user.
Additional Context
No response
The text was updated successfully, but these errors were encountered: