The first hyphen means the permission is for a file. The first set represents the user, the second set for group and the third for world.Įach set displays the allowed actions for each user group. The characters that follow are grouped in sets of threes. If it were for a folder – which is often called a directory – there would be a letter “d” instead. The hyphens represent the absence of an action, except for the first character in the sequence which shows the permission is for a file. The first character can have other values, but it’s less likely that you would come across them when working with WordPress. The letters represent the actions for the permission: Read, write and e xecute. They may look something like this: This format of displaying file permissions is actually the same as their numerical counterpart. You may notice that file permissions are written differently when looking at them through FTP or SSH (Shell access). This, however, usually isn’t an ideal permission for WordPress files. The final file permission would become 764 in this example.
#How to edit 644 in filezilla linux how to#
So in today’s Weekend WordPress Project we’ll look at file and folder permissions in detail, and how to change them to improve your site’s security. The WordPress Codex has some information on WordPress file permissions, but it doesn’t go into a whole lot of detail so it can be tough to follow. Setting your file permissions correctly may not save you from all attacks, but it will help make your site a bit more secure, making it a great addition to your current security measures. If your files don’t have the best possible permissions in place, it’s easier for hackers to intrude on your files and your site. This is important, as the Codex explains, because WordPress may need access to write to files in your wp-content directory to enable certain functions. File permissions specify who and what can read, write, modify, and access them.