(→Setting File Permissions With FTP: clarification 1and1 and other hosts using suphp may require 766/644 permissions.) |
(added documentation) |
||
| Line 1: | Line 1: | ||
==Set File/Folder Permissions== | <includeonly>==Set File/Folder Permissions== | ||
After the {{lc:{{{1|install}}}}} archive has been uploaded and extracted, you need to set the files' permissions. This is commonly done by use of the Unix utility <b>CHMOD</b>. The correct CHMOD value for SMF folders is either 777, 775 or 755, and 666 or 644 usually for files, depending on your hosting service. There are two methods for this step, the method used depends on the hosting service that you use. <br /> | After the {{lc:{{{1|install}}}}} archive has been uploaded and extracted, you need to set the files' permissions. This is commonly done by use of the Unix utility <b>CHMOD</b>. The correct CHMOD value for SMF folders is either 777, 775 or 755, and 666 or 644 usually for files, depending on your hosting service. There are two methods for this step, the method used depends on the hosting service that you use. <br /> | ||
| Line 25: | Line 25: | ||
'''Please note:''' On some servers, the 777 or 666, permission may cause Internal Server Errors (ISEs) or similar errors. If an ISE or other error has occured on the server, the administrator may change the value one step back, to 755 or 644. In come cases, SMF does not detect the errors that result when the host does not permit 777 or 666 permissions. In such a case, the SMF Package Manager might report the mod install succeeded, but one or more steps did not get done. | '''Please note:''' On some servers, the 777 or 666, permission may cause Internal Server Errors (ISEs) or similar errors. If an ISE or other error has occured on the server, the administrator may change the value one step back, to 755 or 644. In come cases, SMF does not detect the errors that result when the host does not permit 777 or 666 permissions. In such a case, the SMF Package Manager might report the mod install succeeded, but one or more steps did not get done. | ||
If your host uses suphp (hosts such as 1and1.com), then you may be permitted to use CHMOD to set 777/666 permissions on files, but may see 500 errors when SMF attempts to use those files. If your host uses suphp, use permissions of 755 for directories and 644 for files. | If your host uses suphp (hosts such as 1and1.com), then you may be permitted to use CHMOD to set 777/666 permissions on files, but may see 500 errors when SMF attempts to use those files. If your host uses suphp, use permissions of 755 for directories and 644 for files.</includeonly><noinclude>{{Documentation}}</noinclude> | ||
Revision as of 17:11, 30 January 2013
[edit] [] 
Template documentation
Template documentationThis template is meant to be included in articles on installing and upgrading, to provide the information about CHMOD/file permissions. To see it in action, please look at the testcases, or at Special:WhatLinksHere/Template:Set_file_permissions
Examples:
{{Set file permissions|install}}
{{Set file permissions|upgrade}}
- install the word "install" will be inserted at several key points
- update the word "update" will be inserted at several key points
| The above documentation is transcluded from Template:Set file permissions/doc. (edit | history) Editors can experiment in this template's sandbox (edit) and testcases (edit) pages. Please add categories and interwikis to the /doc subpage. Subpages of this template. |
