Uploaded file could not be moved to…

https://www.ads-software.com/search/The+uploaded+file+could+not+be+moved?forums=1

hi monniblog..

we encountered the same problem..
The problem is not in the wordpress code..
Its in the server, your hosting site. One hosting site that i know that this problem would occur is the Media Temple.

What you should do is to manually create the directory.

/home/username/public_html/blogtitle/wp-content/uploads/2008/02.

first is remove or rename the 2008 directory then set the CHMOD to 777.
Then create the 01-12 directories then set the CHMOD to 777.

This problem would actually occur because of the security of the hosting site. WordPress create directories in ur uploads folder but the CHMOD cannot be change even if you will manually change the permission. When you will view the uploads directory on your ftp, u can see the directory created but the thing is its just like a ghost. ITS NOT REALLY THERE!!!…

General question – I’ve seen this fix in a number of places and I’m wondering if it’s a security issue to have all of these folders set to 777? Thanks.

Yes, I also use Media Temple, I was able to fix it just by changing the permissions of the 2008 folder. I’ve also updated the permissions of the parent folder ‘uploads’ which I’m hoping with be inherited next year when the ‘2009’ folder is created? Thanks for the post guys, very helpful.

seanmcauliff asked:

“General question – I’ve seen this fix in a number of places and I’m wondering if it’s a security issue to have all of these folders set to 777? Thanks. “

and I have the same concern. In order to get image uploading to work, I had to manually create an uploads folder and set its permissions to 777. wp-content, its parent folder, is at 755.

I’m uncomofortable with leaving the uploads folder at 777. I don’t know much about chmod or permissions, but it seems like public access means someone could upload a nasty pic with the same name as one of mine, overwrite mine, and thus show the world whatever disgustingness they would like. On my site.

Anyone who knows more about security that can offer an informed opinion?

Thanks.

I’m with Media Temple too and just got onto their (dv) server. I really don’t want to leave my images folder to 777. Is there anything else that is safe?

I’m not with Media Temple, but with NFS (NearlyFreeSpeech.net). I experienced the exact problem, and what I did was:

• copied the 2008 dir to something else (eg. old2008)
• copy old2008 to 2008
• set the owner and group of the new dir to me:web
• give the group ‘web’ permission to write that dir

oh, i did all of this via SSH ??
PS: sorry for my english

I am also struggling with this.

any help would be appreciated.

I reckon I’ve done 20 wordpress installations without any problems, including three on the one server. I’t’s only with WP 2.6.2 that I’ve had this problem. 2.6 is OK. I’m reverting to the server based wordpress install – 2.3 and maybe I’ll try to upgrade from there, but it’s really frustrating having to do all the chmod, .htaccess etc and get nowhere.

It would be nice if someone of superior knowledge could post the most likely causes and the best fixes for each.
Cheers
BillyK

This was my solution:

In the WordPress admin under settings > miscellaneous set the default upload folder to wp-content/uploads. Then make sure the uploads folder exists and set the file permissions on the folder to 777. This should allow WordPress to write images to the wp-content/uploads folder. If you still get the error delete the uploads folder and recreate it manually and reset the permissions to 777.

This happened to me after moving my WP install to a new server. The solution that finally worked was to:

1. rename the uploads folder
2. create a new uploads folder
3. change the permissions on the new folder to 777 (755 might work as well, I haven’t tried that)
4. move my folders from the old uploads folder to the new one
5. Upload a file via WordPress

I should note that my new file I uploaded for the final step was the first one for the current month. The newly uploaded image was able to create a new folder in ‘uploads’ (in my case uploads/2008/11) and save the image there. This after months of toying around with permissions.

Of further note: I am not running PHP in Safe Mode.

MWVD – Thank You!

@ jeremyclark13

https://www.ads-software.com/search/The+uploaded+file+could+not+be+moved?forums=1

What is this supposed to do for us? 255 posts, most not resolved. If you are going to post a link, how about a link to a post with a solution? Most of us got here
with a search…

I was switching my file permissions for the “wp-content/uploads” folder in my ftp client, but it still didn’t work. Eventually I checked the permissions of the folders through my host’s control panel and the permissions were still wrong. After I changed them there (to 777), I could upload again.

After I moved my WordPress installation to a nwe (and faster) server, I also could not upload image to the uploads folders…

I changed permissions to 755, and they still didn’t work.

When I changed to uploads permissions to 777, I could upload again.

I am going to experiment with making as few of the upload folders 777 as possible, so that I can minimize any security issues…