Notices Welcome to LinuxQuestions. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.
See full list to Permission Scheme for WordPress Permissions will be different from host to host, so this guide only details general principles.
It cannot cover all cases. This guide applies to servers running a standard setup note, for shared hosting using "suexec" methods, see below. Typically, all files should be owned by your user ftp account on your web server, and should be writable by that account. On shared hosts, files should never be owned by the webserver process itself sometimes this is www, or apache, or nobody user.
Any file that needs write access from WordPress should be owned or group-owned by the user account used by WordPress which may be different than the server account.
For example, you may have a user account that lets you FTP files back and forth to your server, but your server itself may run using a separate user, in a separate usergroup, such as dhapache or nobody.
In the latter case, that would mean permissions are set more permissively than default for example, rather than for folders, and instead of The file and folder permissions of WordPress should be the same for most users, depending on the type of installation you performed and the umask settings of your system environment at the time of install.
If an experienced user installed WordPress for you, you likely do not need to modify file permissions. Unless you are experiencing problems with permission errors, or you want to, you probably should not mess with this.
If you installed WordPress yourself, you likely DO need to modify file permissions. Some files and directories should be "hardened" with stricter permissions, specifically, the wp-config. This file is initially created with permissions, and it's a hazard to leave it like that.
See Security and Hardening. Typically, all core WordPress files should be writable only by your user account or the httpd account, if different.
Sometimes though, multiple ftp accounts are used to manage an install, and if all ftp users are known and trusted, i. Ask your server admin for more info. If you want to use the built-in theme editor, all files need to be group writable. Try using it before modifying file permissions, it should work.
This may be true if different users uploaded the WordPress package and the Plugin or Theme. This wouldn't be a problem for Plugin and Themes installed via the admin.
When uploading files with different ftp users group writable is needed. On shared hosting, make sure the group is exclusive to users you trust In some cases, this may require assigning permissions.Unix/Linux Permissions - a tutorial Table of Contents.
Basic File Attributes - Read, Write and Execute What is needed is a mechanism to prevent any new file from having world write access. To subtract group and world write, must have removed to leave as the permission of the file. For example, to give all users read and write access to schwenkreis.com, run chmod as follows: $$$ chmod a=rw schwenkreis.com And actually, in the interest of full disclosure, if you fail to specify to whom you want the permissions to apply, chmod will automatically apply them to all users.
In Unix-like operating systems, chmod is the command and system call which may change the access permissions to file system objects (files and directories). It may also alter special mode flags. The request is filtered by the umask.
Here are manual pages on chown and chmod (these can also be found by running man chown and man chmod.) I should add you can give groups of users write access as well (examples here and here).
Also beware giving global write access with the chmod command if you have not as trustworthy users/scripts running on the server etc - I recommend. How do I give write permission to file in Linux? Ask Question. chmod u+w But in your C example you're using mode instead of the you've proposed earlier.
That would give everyone write access which most likely is not what the poster wanted. – DarkDust Jul 18 '11 at Issued chmod * in home directory, permissions problems resulted with all files.
since this would effectively just give every user access to read and write perms in my home folder.
I'll just use chown to switch everything back to just my account. Also, I thought chmod would give any user read and write access, so I don't.