WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Image has failed to upload due to an error. (30 posts)

  1. auelsg
    Member
    Posted 3 years ago #

    I am having this error ever since i updated into 3.0.1.

    “image.jpg” has failed to upload due to an error
    Unable to create directory /home/roborobo/public_html/wordpress/wp-content/upload/2010/10. Is its parent directory writable by the server?

    Can anyone help? I tried editing the htaccess file but I just crash my website. Hope someone can help.

    Thank you.

  2. Try changing the permissions of the /wp-content/uploads/ directory to 777.

  3. auelsg
    Member
    Posted 3 years ago #

    I tried changing, doesn't work either.

  4. In that case, try changing the permissions on the /wp-content/uploads/2010/ directory to 777.

  5. auelsg
    Member
    Posted 3 years ago #

    I changed the settings using a FTP client, is that causing it not to work?

  6. No, that shouldn't be a problem. We might as well go all out with this. Set the following directories to 777:

    /wp-content/
    /wp-content/uploads/
    /wp-content/uploads/2010/

    If that doesn't work, create a /10/ directory in the /2010/ directory like this:

    /wp-content/uploads/2010/10/

    and set that to 777 too.

  7. auelsg
    Member
    Posted 3 years ago #

    I have set everything to 777 and it still doesn't work. I have to set the file permission of the folders right?

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

  8. auelsg
    Member
    Posted 3 years ago #

    or do you think I should roll back to older versions of wordpress?

  9. I think you should contact your hosting provider. The directories now have world-writeable permissions, which means that everything should be able to write to them, even WordPress, but something might be happening at the server-level to prevent this.

  10. auelsg
    Member
    Posted 3 years ago #

    It happens right after I upgraded to 3.0.1, is this one of the problem?

  11. I don't think so. There's a couple million people out there using WP 3.0.1, so if this was a problem with 3.0.1, it certainly would be significantly more widespread.

  12. auelsg
    Member
    Posted 3 years ago #

    So there is nothing else I can try and do?

  13. You could try downloading WordPress again and delete then replace your copies of everything except the wp-config.php file and the /wp-content/ directory with fresh copies from the download, but I doubt that's the problem.

  14. auelsg
    Member
    Posted 3 years ago #

    If I reinstall wordpress again, will it mess up my current settings?

  15. No, your settings and content are safe in the database.

  16. auelsg
    Member
    Posted 3 years ago #

    Thank you for your help and patience, I will try it out and let you know.

  17. Jesson
    Member
    Posted 3 years ago #

    I have the same problem sinds i've installed wordpress 3.0.1
    Contact my host, Didn't knew the answer either.

    So anybody know the answer to this problem??

  18. bobair
    Member
    Posted 3 years ago #

    I fixed this same issue with my wordpress when I changed the default media settings.

    Go to your dashboard, down to "Settings" and choose "media" and change the "Store uploads in this folder" to "wp-content/uploads" .. that solved everything for me. I think it has something to do with my Dreamhost server settings that have recently changed.

    Hope this helps,
    ~ Robby

  19. JonFB
    Member
    Posted 3 years ago #

    I know this might be slightly old but I think it is still relevant. I actually had to delete the folder named 'uploads' and create a new one of the same name. Have no idea why this work but it did for me so I hope this helps somewhat.

    Regards,
    Jon

  20. code001
    Member
    Posted 3 years ago #

    what is strange is a particular detail of the error message, can anyone confirm the same has happened to him?
    My error message has a strange // (double slash) dir name just before wp-content/uploads
    whl.mysite.xxx/nt/blog//wp-content/uploads/2011 (I'm hosted on WH4L)

    I'm an informatic but I do not have sufficient culture on server of this kind, yet I guess that a double slash is not a permitter path.
    Does anyone know how to correct it in the code? because I guess that the problem reside there!

    Thank
    Luca

  21. code001
    Member
    Posted 3 years ago #

    Sorry, the previous post is some unusefull for peoples outside WH4L

    now, I followed the suggestion shown in the two last posts before mine and I fixed it.
    There was a config error in the default dir in Webhost4life site builder, with the relevant dir name carrying the double slash
    the former dir was:
    /home/users/web/bxxxx/whl.yyyyyy/nt/blog//wp-content/uploads/2011/01

    I changed into
    wp-content/uploads

    now is OK

    thank to bobair and JonFB
    Luca

  22. deano_h
    Member
    Posted 3 years ago #

    Having just updated to 3.0.2 and experiencing all sorts of grief with my host not supporting auto updates, backups and restores (that their CP says it does [see my other posts]), I managed to get all back to working and then found I had the same issue as mentioned in this thread. i.e. The upload function of WP media gallery no longer worked.

    I got the same message as stated in the 1st thread of this post, albeit with my own directory path(s) etc.

    I have just tried James' permissions fix and made '/uploads' 777, plus all sub-directories.

    This worked fine. However, I'm a bit concerned at having this directory and it's subdirectories world editable!

    Should I be? Can this be fixed another way?
    It didn't have to be done for my initial install of WP!
    Is there a php file or something that has had it's access to /uploads removed so that it can no longer write to this directory?

    That would seem to make sense as there was no issue previously.

    Curious for any suggestions. Tnks,
    deano.

  23. code001
    Member
    Posted 3 years ago #

    @deano_h
    I guess that the changes you had to make became relevanto to new medias only. The previous ones should be remained the position they had before your update.
    So be quiet and try to discover what happened in your dirs through a File Manager or so
    Luca

  24. deano_h
    Member
    Posted 3 years ago #

    Luca,
    Can you expand a little? I used the host's File Manager, in my control panel to 777 the /uploads dir but this wasn't needed before I u/graded to 3.0.2, before that, they were 755! So what has changed? There must be a back end php or something that the upload media utility uses and this has lost ownership/access to /uploads... that's my guess anyway.

    What do you mean by "be quiet and try to discover what happened in your dirs through a File Manager"

    Thanks
    deano
    (btw: my son's name is Lucas :)

  25. vane.
    Member
    Posted 3 years ago #

    I had the same issue... i fixed this creating another folder inside the directory "uploads"

    Using FTP creating a folder inside "uploads" folder, not create a folder named 2011 or 2010... i tried this, but don't work for me... place anything, such as "media"

    then i changed the "Store uploads in this folder" to "wp-content/uploads/media"

    and works!

  26. code001
    Member
    Posted 3 years ago #

    deano_h
    I'm sorry but my host doesn't permit me to see the permissions, it manages them in a transparent way to me!
    For me it was just an error of dirName. As soon as I changed it I solved all my problems. I don't think it should change the permissions. try to follow vane suggestion in some instance it has done s a similar thing I've done
    Happy you have choosen the right name for your son! :)

  27. milliemay
    Member
    Posted 3 years ago #

    In case this helps anyone, I was getting the same error and finally figured out that I had exceeded my quota for hosting and there was no more free disk space. Hope this helps someone.

  28. besatree
    Member
    Posted 3 years ago #

    Check with your host and find out what version of php you are using.... for me php5 gave issues but php4 works fine.

  29. epot
    Member
    Posted 3 years ago #

    Thank you bobair!

    Very simple and that worked perfectly for me.

  30. kaniuta
    Member
    Posted 3 years ago #

    ive the same problem but I changed what u said and doesnt work
    still the same :
    Unable to create directory /var/www/vhosts/Kaniuta.com/httpdocs/wp-content/uploads/media/2011/08. Is its parent directory writable by the server?

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.