Manual :: Installation ::
File Permissions
WARNING: This man page is obsolete. The NEW PAGE can be found here.
Link: http://manual.b2evolution.net/Directory_and_file_permissions
[NL]
This page applies to b2evo 0.9
When you upload files to your webserver by FTP, those files are saved on the server with some specific access permissions. Typically, everyone will be able to "read" the files and subdirectories, that is view them through the webserver, but only you and you alone (when you log into the FTP server) will be able to "write' to these files/subdirectories and modify them.
For some specific actions, b2evolution will need to modify some of its files. b2evo will also need to write new files when you use b2evo to upload an image or generate a static .html file. The problem is: b2evo is not you. More specifically: the PHP process that runs b2evo is not you!
Thus you will most likely need to change the permissions on some files and subdirectories in order to allow b2evo to write there and perform the requested actions.
Note: on somehosts, the default permissions already allow your scripts (b2evo in this cse) to change your files on your account. So you can try b2evo without changing any file permission and come back here only if you get a file permission error.
Most webservers runs some variant of UNIX. On these systems, file permissions can be changed via chmod. If you're not familiar with UNIX file permissions and chmod, check out A quick and dirty chmod Tutorial. If your server is running Windows you probably don't need to change anything.
You can change permissions on files/folder either with an FTP client program (like Filezilla), a Unix shell or a web file manager like the one built into cPanel.
What files/subdirectories do need specific permissions?
Let's assume your b2evo is installed under /blogs. Here's what you need to change:
- chmod 666 /blogs/conf/_config.php if you want the installer to be able to automatically update your config based on your input.
- chmod 777 /blogs to allow creation of blog stub files from the admin interface or to generate static pages for your blogs.
- chmod 777 /blogs/media in order to upload images and other media from b2evo's backoffice.
- chmod 666 /blogs/skins/custom/* if you want to use the template editor for the custom skin.
18 comments
Comment from: Mike Wang [Visitor]
In some rare cases you may also need to manually chmod 755 all folders and files contained within them that have .php files. Otherwise you'll have problems. After I changed all the pgp files to 755 it worked like a charm.
2004-07-27 @ 18:33
Comment from: Alan Hefner [Visitor]
The image upload does not give read permissions!! The result is that the image file can't be seen in the posts.I can manually chmod the permission for the image file and all is ok then.
Where is the fix for this? I am not afraid of modifying the upload php file just need to know what and where to make the mod.
BTW I did chmod the files and folders with php files to 755 and the media folder to 777 but still the individual uploads end up set to 700.
Alan
2004-09-28 @ 00:33
When I try to generate a stub file for one of the blogs with permission level 2, I get a "File Cannot Be Written" Message.What is the file that needs the chmod?
Thanks
2004-10-06 @ 19:03
Comment from: Stryder [Visitor]
I would guess if a file can not be written, it's more than likely the folder that the file is suppose to be written to doesn't have the right privilege level, so check what CHMOD the folders that have files written to are.
2004-10-27 @ 17:48
Comment from: Nico [Visitor]
I've got a little problem: I placed my weblog in the root-directory and I can not chmod the root. Are there any workarounds?Thanks
Nico
2004-11-04 @ 15:22
HI,File cannot be written!
You should check the file permissions for [/iSERVER/Cluster/k/kumeir.com/www.kumeir/b.html]. See online manual on file permissions.
WHY? Are you tell me?
Thanks
kumeir
2004-11-14 @ 01:41
It would be useful to have a recommendation of the proper permission mask (775, 755, 666, etc.) that should be applied to all the files in the b2evolution "blogs/" directory tree after install. The above lists some files that need to have specific masks for specific purposes, but does not specify what we should have the rest of our blog set at so that people can't mess with it.
2005-04-17 @ 16:49
Comment from: Manuel [Visitor]
I have the exact problem:The image upload does not give read permissions!! The result is that the image file can't be seen in the posts.
I can manually chmod the permission for the image file and all is ok then.
Where is the fix for this? I am not afraid of modifying the upload php file just need to know what and where to make the mod.
BTW I did chmod the files and folders with php files to 755 and the media folder to 777 but still the individual uploads end up set to 700.
Alan
2005-09-09 @ 00:28
Same problem regarding uploaded file permissions - I can't see any of the images I upload until I manually chmod them. Anyone fixed this yet?
2005-11-02 @ 20:37
Comment from: Fede [Visitor]
I have some permission troubles converting and then saving an iMovie 3 project to iMovie Hd. Can a try to digit "chmod -R 755 Media" in Termina (Apple application) to fix it?Thanks
2005-11-16 @ 12:05
Comment from: Curt Krueger [Visitor]
Hi, I think I figured out code wise how to correct the default CHMOD of 600 to be what ever you want. You have to modify your "b2_upload.php" file.
Starting at line 144:
Change this:
=======================================================================
if (!strlen($imgalt)) {
move_uploaded_file($img1, $pathtofile) //Path to your images directory, chmod the dir to 777
or die( T_('Couldn\'t upload your file to:').' '.$pathtofile);
} else {
rename($img1, $pathtofile)
or die( T_('Couldn\'t upload your file to:').' '.$pathtofile);
}
==========================================================================
To This:
Note: I'm new to PHP, so I'm assuming this is OK. Note the 0644 is the
actual CHMOD value to be set. Hope this saves some hair :)
==========================================================================
if (!strlen($imgalt)) {
if (move_uploaded_file($img1, $pathtofile)) //Path to your images directory, chmod the dir to 777
{
// Read and write for owner, read for everybody else
// echo($pathtofile); debug purposes
chmod($pathtofile, 0644);
}
else
{
die( T_('Couldn\'t upload your file to:').' '.$pathtofile);
}
} else {
rename($img1, $pathtofile)
or die( T_('Couldn\'t upload your file to:').' '.$pathtofile);
====================================================
Regards,
Curt
Faribault Minnesota
2005-11-25 @ 19:25
Comment from: Curt Krueger [Visitor]
Sorry, should of been more clear. The above code is to fix the non-viewable images after you've uploaded them in your blog. By default, the CHMOD value is "600" so they are not viewable. The code I placed above, CHMODs the image to 644 if successfully uploaded so that it can be viewed by default.
Hope this helps!
Curt
Faribault Minnesota
2005-11-25 @ 19:32
My problem is in regards to editing the skin/template. Under templates it says I must change the permissions to 766 in order to edit--which I did. But when I changed it, I got a message saying "permission denied." What must I do in order to be able to edit the template?
2005-12-02 @ 14:46
Comment from: Adam Jaskiewicz [Visitor]
For some reason, only two of my blogs have a [Gen] link for generating a static page in the blogs list. I'm getting a "Permission denied! (blog_genstatic:any:1)" when I try going to the static page generation URL manually (click on one of the existing Gen links and change the blog to another number). The files it is using do indeed exist, and are rw to the web server (666, actually), and I cannot find any difference that would cause it to work for blogs 5 and 6, but not 1, 2, 3, or 4. I tried 777 on my blogs directory, but that didn't help.Any ideas?
2006-04-02 @ 19:24
Adam, you'll have to go to the "Blogs" tabs and give yourself permissions to generate static pages. It's not a chmod issue.
2006-04-04 @ 23:35
Comment from: Thomas Groenbaek [Visitor]
Thank god!!!I have an php upload script, that have been working on another webhotel. On a new webhotel it just could not work - and I spend numberous hours pulling my hair.
Then I found out that only owner had access on uploaded pictures - ok, that was the reason other uses could not se the pictures!!
Then more hours went, cause I could not find any info about how to set there permissions on-the-fly, when i was uploading! After pulling more hair, and almost giving up, I made one last google search and found this site and the saving statement:
chmod($upload_dir.$filename, 0644);
I am now a happy man - again :)
Thanks a lot for this information!!!
/thomas, Denmark
2006-04-22 @ 19:08
Comment from: Ben [Visitor] 
I am having the same problem - do you need to give the full path or not?Running out of hair....
2006-11-02 @ 19:52
Thanks guys, its a greate help...:-)
Comment feed for this post