Recent Topics

1 Sep 08, 2006 16:44    

I have the new version and installed but I get the following error under the file manager.

The blog's media directory «media/blogs/a/» could not be created, because the parent directory is not writable or does not exist. 
The blog's media directory «media/blogs/b/» could not be created, because the parent directory is not writable or does not exist. 
The blog's media directory «media/blogs/links/» could not be created, because the parent directory is not writable or does not exist. 
You don't have access to any root directory

How do I fix this?

2 Sep 08, 2006 17:55

DUH! nevermind :oops:

3 Sep 08, 2006 22:54

It may seem a bit noobish. But I'm having the same problem and I'm not getting an oh DUH, oops.
What did you do to fix this?
Thanks.

4 Sep 09, 2006 12:56

Well.. the error is saying that your media directory is not writable...
So chmod your media directory to 777

6 Sep 09, 2006 18:09

blueyed wrote:

I'm still not tired of mentioning that chmod 777 would allow users on the same host to delete your media files, if the webserver is not setup securely.

Please try 755 and 775 before.

See http://manual.b2evolution.net/Directory_and_file_permissions

It seems that you are the only one who can work with 755 or 775.
I have not encountered someone else who succeeded.. ;)

7 Sep 09, 2006 19:06

Yeh on my server 775 locks me out as well, with my admin ftp account, althought it still works via php applications, but i'm a ftp user, so i just use 777. *Prepares to get hacked*

8 Sep 10, 2006 15:02

Okay. I tried both 755 and 775 with no success. So I changed it to 777 and the directories were created by b2evo with 755. So Now that they're created I guess I can change the root directory back to 755 as well.

9 Sep 10, 2006 15:07

yes, probably. If you have the "users" and "blogs" directory already therein. If you don't have "users" and don't want/need user media directories, it will be fine, too.


Form is loading...