Wednesday, June 16, 2010

Wordpress The Uploaded File Could Not Be Moved To

SkyHi @ Wednesday, June 16, 2010

On one fateful occasion when I had problem uploading images from the admin dashboard, I wrote a post with the similar title The Uploaded File Could Not Be Moved To [Unsolved] and little did I know that it has become one of the most popular post with the second highest organic traffic based on my last statistics from Google.

I conclude that there are a lot of people out there who are still having similar problem even with the latest WP 2.5.1. It’s just a puzzle why this image uploading error hasn’t been fixed till now. The fact of the matter is that the solution differs from one person to another which means what works for me may not be the solution for others.

So in the spirit of sharing and learning, I’ll highlight some of the possible solutions for the benefits of those who are still struggling to find the fix. I know it’s that much of frustration to be in that kind of situation.

Possible Solutions to Image Upload Error

The following solutions are those that may have worked for some but didn’t quiet fix it for me. Here’s how I fixed the upload issue.

1. Changing file permission

I suppose the very first thing you need to check is whether the correct file permission for /wp-content/uploads/ has been set 777. If you aren’t sure, here’s how to set file permission.

2. Setting the default folder

Go to Settings > Miscellaneous and check that the default folder for uploading is set to /wp-content/uploads/. There are times when the folder is not properly defined.

3. Re-writing .htaccess

Emma from UOTW has shared with us the solution by re-writing your .htaccess to include an additional set of code.

<ifmodule mod_security.c="">
<files async-upload.php="">
SecFilterEngine Off
SecFilterScanPOST Off

It is understood that some plugins may modify your .htaccess and changes can be lost during installation.

4. Re-create /wp-content/uploads/

The other option would be to first delete the folder /uploads/ from /wp-content/ directory and re-create it again and then set its the permission to 777. You’ll surprised that this method seems to work for some people.

5. Enable safe_mode_gid=Off in php.ini

If all the above solutions doesn’t work for you, S├ębastien Wains has a fix by editing the value “safe_mode” to off in /etc/php.ini but if you aren’t not familiar with safe mode, you may not like this idea. In what I have learned, in most cases, your host may not allow you to disable the safe mode for some security reasons.

If everything else fails…

If everything else fails, it’s best to contact your host provider and hope that they even care anything about it which, speaking from my personal experience, they usually couldn’t careless, simply because they are too clueless about it.

As I’ve said earlier, the reason I’m writing this post is to share with my readers out of goodwill some of the possible solutions to image upload problem. Therefore if you have another solution that might work, please do tell us how you fix it and what work for you.

That being said, please correct me if I’m wrong with any of the above solutions. I’m willing to update it for the benefit of others.


Here’s yet another solutions that may work in your favor;

1. Update Flash to new version on the computer used to upload photos, WP uses it.

2. If any plugin(s) won’t work with /wp-content/ or /wp-content/uploads/ chmod 777, as some of them won’t, then sub directories’ folders /wp-content/uploads/2008/07/ for storing uploads etc. can be created and uploaded manually.

Thanks to one of our friends, Rado from Pizza Oven.

More update:

It seems like the image upload problem has been addressed with the recent release WP 2.6. Please let us know if problem still persists.

Have yours been updated with the latest WP 2.6?

Related posts