The MU forums have moved to WordPress.org

HELP! Unable to create directory Is its parent directory writable by the server? (13 posts)

  1. m1gu3
    Member
    Posted 16 years ago #

    I know this post have been brought up again and again. I'm using media template's dedicated virtual hosting and recently uploaded and installed WPMU and when someone tries to upload a picture into a post we have this message:

    Unable to create directory - Is its parent directory writable by the server?

    Again I just purchased the hosting plan and I'm not that used to use plesk and such, also I'm using cyberduck for mac so if any of you have any answer of what kind of procedures should I follow? (please post below)

    thank you.

  2. MrBrian
    Member
    Posted 16 years ago #

    wp-content/blogs.dir needs to be writable. Chmod to at least 666.

  3. m1gu3
    Member
    Posted 16 years ago #

    I'll try that thank you, will that make the subsequent folders writable too?

    already tried it didn't work :(

  4. m1gu3
    Member
    Posted 16 years ago #

    also tried to edit the permissions to 666 on the folder and subfolders (at the same time) and a error pops up saying the direcotry doesn't exist.

  5. MrBrian
    Member
    Posted 16 years ago #

    Try making wp-content writable also.

  6. m1gu3
    Member
    Posted 16 years ago #

    I'll go for that right now...permissions on /wp-content are 777 also

  7. VentureMaker
    Member
    Posted 16 years ago #

    Don't you think that 777 on live server is kinda security risk? :)
    Try at least 755

  8. andrea_r
    Moderator
    Posted 16 years ago #

    make sure the folders are CHOWNed properly too.

  9. m1gu3
    Member
    Posted 16 years ago #

    How do I do all that :s, i know I'm acting like a noob right now, I have no experience with ssh. I'm checking some tutorials about ssh and terminal hope they work, I'll keep you posted.

  10. m1gu3
    Member
    Posted 16 years ago #

    ok got logged into terminal so what are the permissions and ownerships that I need to set? (almost there)

  11. m1gu3
    Member
    Posted 16 years ago #

    what are the permission and ownerships the folders 'wp-content' and 'blogs.dir' are supposed to have for both of them?

  12. MrBrian
    Member
    Posted 16 years ago #

    they should be writable... 666 or 777, and ownership should match the rest of your wpmu files.

  13. gaganawhad
    Member
    Posted 16 years ago #

    Here's my 2 cents

    666 did not work for me 777 did.

    There are two reasons why we hit this error. One is the permissions, and the other is the ownership. While uploading files, images etc., wordpress tries creating directories which are not owned by the owner for the rest of the directories. For the sake of this discussion let me call him 'own1' and the group "grp1". In my case wordrpess tries creating directories owned by "apache:apache" which, is different from the ownership of the rest of my wpmu files ie own1:grp1

    The error I got is something like ,
    Unable to create directory - .../wp-content/blogs.dir/4/files/ Is its parent directory writable by the server?

    When I sshed, there was no blogs.dir folder created. I changed the permission for wp-content to 777 and tried uploading an image. This time i got the same error ie

    Unable to create directory - .../wp-content/blogs.dir/4/files/ Is its parent directory writable by the server?

    but when i sshed i saw that blogs.dir was created however owned by 'apache:apache' which is why the folder 4 was not getting created.

    I did a 'chown usr1:grp1 blogs.dir' to change the onwership and tried uplaoding again. I got the same error ie

    "Unable to create directory - /wp-content/blogs.dir/4/files/ Is its parent directory writable by the server?",

    but this time the folder 4 was created but owned, again, by apache:apache. Did a 'chown usr1:grp1 4' again to change it and tried uploading an image.

    Now it gave me a different error. it was ...

    The uploaded file could not be moved to the upload folder.

    In the terminal, I saw that "files" folder was created but again owned by apache:apache. I changed that and uploaded an image and this time it worked.

    Thanks guys on top, and hope this helps someone later.

About this Topic

  • Started 16 years ago by m1gu3
  • Latest reply from gaganawhad