SUDO CHMOD 777 FULL
SUDO CHMOD 777 WINDOWS

If you do have console or shell access to your web space, you can do this from the Linux command line (executed from your CMSMS site root):Ĭhmod 777 tmp/templates_c tmp/cache uploads uploads/images modules Once you've determined the correct permissions to use, CHMOD the following directories to enable write access for the web server process: A directory must be 'executable' in order to be opened, but you don't normally want EVERY file to have this bit enabled, so you would use 666 for files instead.) (The difference between a '6' and a '7' is the 'execute' bit. You would use 666 to enable write access to an individual file. To ensure write access to directories in most Linux shared hosting environments, 777 are the permissions to use.

SUDO CHMOD 777 FULL

If you are unsure, using 777 works for all cases, but may be a security risk as it allows full access to everyone who gains access to the server to those files or directories. Your hosting provider may also have a web-based file manager as part of its control panel (cPanel, H-Sphere, Plesk, etc) for this task.Īsk your hosting provider or server administrator what file permissions to use to ensure the web server process has write access to files and directories. Most FTP clients allow you to 'CHMOD' files (may be called 'file attributes'), so console or shell access is normally not required to change file permissions.

SUDO CHMOD 777 WINDOWS

Note: If you are running on a Windows server, you can skip to Step 6, Database.įor CMS Made Simple to function properly, it needs to be able to write files to certain directories.ĬHMOD is a tool on Linux (and other Unix-like) servers for setting file permissions. is the skipping to step 6 for Windows 100% accurate in all cases? The one thing I need confirmed because I don't use Windows for anything I don't have to. I've whipped up a draft here that anyone can butcher if they like before edits get posted to the Wiki. This part (steps 4, and perhaps 5) needs to be rewritten for clarity and additional information. i wonder how many people who post questions involving file permissions issues in the forums have used 775 instead of 777 ?!? The text added to the documentation by ljbadenz (above) isn't entirely accurate or applicable to most shared hosting environments. If security of your web site is important, set it these folders to CHMOD 775 or tighter.) (Note: 777 has pontential security risks and may allow hackers to upload files to these directories to run phishing sites etc.

Sudo chmod 777