• Hi everyone.

    About a year ago, we had a website developed. It was way more website than my wife and I could maintain. So, we simplified. We wanted to keep the blog, so I did the research, and figured out how to save the WP database from the old server, and load it to the new one. I installed WP, uploaded the database, and things seemed good. Until I tried to upload a photo. Here are all of the symptoms that I can find.

    1. When using the flash loader from Quickpress, or Add New Post, I receive the following error.
    “Unable to create directory /var/www/vhosts/fitglobetrotter.com/httpdocs/wordpress/wp-content/uploads/2009/03. Is its parent directory writable by the server?”

    2. When using the browser uploader from Quickpress, or Add New Post, I get the same error as above.

    3. When using the Flash uploader from the Media library, I get the same error as above.

    4. When I use the Browser uploader from the Media library, it seems to work, then automatically brings up the library, but the photo is not there.

    I have permissions on the wp-content/uploads folder set to 777.

    Any ideas on why the photo upload isn’t working would be greatly appreciated.

Viewing 10 replies - 1 through 10 (of 10 total)
  • “Unable to create directory /var/www/vhosts/fitglobetrotter.com/httpdocs/wordpress/wp-content/uploads/2009/03. Is its parent directory writable by the server?”

    The address above, is that the correct address for your NEW website?
    If so, it seems wordpress can’t write the folders. Try manually making the folder /2009/03 in your wp-content/uploads/2009/03.

    If it works then, then you know something is wrong with permissions.

    BTW, do you have any plugin active? I once had a simular problem, and it was a plugin i was using that conflicted with the image uploads.

    Thread Starter jtbraun

    (@jtbraun)

    I don’t know where “/var/www/vhosts/” comes from in the address. The rest is right, except for the “/2009/03”. I manually added the folders “/2009/03” to uploads, but the loading still doesn’t work.

    I’ve also FTP’d photos into the uploads and the /2009/03 folders, but they do not appear in the WP Media Library.

    All permissions are set to 777. I have no plugins at all.

    Thread Starter jtbraun

    (@jtbraun)

    Could it be a field leftover in a database table that needs to be updated?

    Having the exact same issue, after moving blog to a new server,updating wordpress to the latest release, uploading images gives that same error.

    Moved folders “uploads, 2009 and 03” over from old site with “777” permissions, tried creating new ones, even tried not having them there so wordpress could create them, no luck
    All permissions are set to be writable.

    Hopefully someone might have an idia, maybe that database field mentioned above?
    Even though I went through the “upgrade.php” routine and it said that it updated the database.

    Assuming you do not have any files currently in the uplaod folder, have you tried deleting it and creating a new one?…

    AGAIN THIS ASSUMES YOU HAVE NO EXISTING CONTENT IN THE FOLDER…

    Just a disclaimer before anyone goes deleting content and passing blame..

    Files and folders have ownership, and long story short, sometimes this causes issues.

    If recreating the folder doesn’t help, and you have no content to lose, try removing it again then let WordPress try to create it…

    So to run over what i just said, 2 options, first creating the uplaod folder yourself, by FTP or File Manager, failing that attempting to let WordPress create the folder…

    Failing both of those it may be the inherent permissions of the wp-content folder.

    AGAIN LET ME JUST STRESS, do not try the above if you have content in the folder, rename the folder instead if you wish to try the suggestions, for testing sake, then switch it back if all the above fail…

    Thread Starter jtbraun

    (@jtbraun)

    That seemed to do it! Thank you.

    I deleted the uploads folder (there was nothing in it), recreated the uploads folder, and made the permissions 777. Now it works.

    Again, thank you all.

    This unfortunately doesn’t work for me.
    I have tried every combination posible. Recreating the “uploads” folder, recreating the “2009” folder, recreating the “03” folder. Deleting all of them and letting the program try to create them at different levels. Changing the name of the folder to upload to in the “miscellaneous” section of “settings”. I even recreated the “wp-content” folder.
    tried every permission I can think of, and still, the same error message.
    Anyone have any ideas?
    this install is for a photographer so uploading images is the most important aspect. Very frustrating.

    Resovled.
    here is what worked for me.

    In the “settings”, “miscellaneous” section, “Store uploads in this folder” box, I deleted everything before “wp-content/uploads”.

    From this
    /home/mysite/public_html/blog/wp-content/uploads

    to
    wp-content/uploads

    including the forward slash.
    this is with the “uploads” folder already created by me and given proper permissions.
    Then the program created the “2009” and “03” folders automatically with no issues.

    Hope this helps someone else, I have seen several threads about this error.

    I can see how that would be a problem..

    Mine both show wp-content/uploads , local and live…

    Curious why it had your site path in their…

    Hi Raveneart!

    Your fix of setting “Store uploads in this folder” to wp-content/uploads in the Miscellaneous settings worked for me.

    Mine had changed to a longer path. I spent hours changing permissions and thought that file upload option didn’t work if your WordPress install was on a unix/linux server. It used to upload a single image if I used the url option once in awhile and only for a single image per page. It had me tearing my hair out which I can scare afford. ??

    So a big thank you to you!
    Best regards,
    BlackBeardie

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Problems with pictures.’ is closed to new replies.