WordPress.org

Ready to get started?Download WordPress

Forums

Unable to create directory wp-content/uploads/2013/08. Is its parent directory.. (4 posts)

  1. Soyful
    Member
    Posted 11 months ago #

    Hello
    I have been trying to upload an image into my WordPress dashboard without success. Every time I try to upload the image, I get an error like below:

    Unable to create directory wp-content/uploads/2013/08. Is its parent directory writable by the server?

    I am using CentOS 6.4 with latest WordPress. My WP is located in /dir1/dir2/dir3/wordpress, and below this, wp-content has "uploads" directory and within this 2013/08 directories. Additionally, I had to create uploads/2013/08 as they did not exist in the original installation. I have changed permission and that too did not work. Same upload error shows still.

    This is what I do to see the error from WordPress:
    1. Dashboard --> Pages --> 'Add Media'
    2. Dashboard --> Media --> 'Add New'

    As mentioned, uploading an image shows the error stated above regardless of which image I choose. I have not had any problem installing themes or plugins, just the problem with image upload.

    I have rebooted my host, also, and retired image upload without success.

    In addition, I also tried these as root:
    1. chmod -R 777 /dir1/dir2/dir3/wordpress/wp-content/uploads
    2. chgrp -R apache /dir1/dir2/dir3/wp-contents
    3. chmod -R g+w /dir1/dir2/dir3/wp-contents

    Got directories to look like this:

    drwxrwxrwx 5 apache apache 4096 Aug 10 15:23 wp-content
    drwxrwxrwx 3 apache apache 4096 Aug 10 15:27 uploads
    drwxrwxrwx 3 apache apache 4096 Aug 10 15:27 2013
    drwxrwxrwx 2 apache apache 4096 Aug 10 15:27 08

    ie /dir1/.../wp-content/uploads/2013/08.

    Then retried uploading image again, and still not joy...

    My host has LAMP (CentOS) and WordPress - that's it! This is a new installation.

    Please could you suggest a fix for this kindly.

    Thank you.

    http://wordpress.org/plugins/comments/

  2. bogdanp9
    Member
    Posted 11 months ago #

    I have the same problem on an nginx setup. I suspect this is related to directory ownership, but i guess 777 should have solved that.
    Any hints for solving this?

    Thanks.

  3. sovanbu
    Member
    Posted 11 months ago #

    I'm having the same issue. Even after changing permissions.

  4. bogdanp9
    Member
    Posted 11 months ago #

    I got it sorted out by chmodding wp-content to 777, then to 755. I don' really know why 777 was required first, but it worked.

Reply

You must log in to post.

About this Topic