johngalt80

I’m not sure about a Windows server, but usually these kinds of errors are due to some kind of permissions problems or PHP’s “safe mode” may be on. You should probably turn that off anyway, as it has been deprecated as of PHP 5.3.0.

Here’s a page that talks about this and has some references to using Safe Mode and IIS:
http://php.net/manual/en/features.safe-mode.php

If anyone else is running on Plesk and having the image uploads problem (and CHMODing to 777 is not helping or anything else), the following will probably help you… it solved it for me.

In WP admin, go to Settings/Media page and make sure the text box after “Store uploads in this folder” is blank… that causes WP to use the default path, which is “wp-content/uploads”. If you know that your upload path is different than the default, then put it there, but the usual is to leave it blank.

Now, do the following in your Plesk File Manager:
Rename your “uploads” folder to something else, like “uploads_old”. Then create a new folder and name it “uploads”.

Now, go into your WP admin and try uploading an image. It should work. If not, temporarily chmod your new “uploads” folder to 777, then upload. After you get it working, you can chmod it back to 755. (I’m not sure why this worked for me, but it did. It may have just been a lag in the server resetting after creating the new folder and I really didn’t have to chmod to 777).

Now you can upload any other folders and files to your new “upload” folder, but be careful not to overwrite and new folders/files that you just created.

Hope this helps you Plesk users out there or anyone else using a similar system.

If anyone else is running on Plesk and having the image uploads problem (and CHMODing to 777 is not helping or anything else), the following will probably help you… it solved it for me.

In WP admin, go to Settings/Media page and make sure the text box after “Store uploads in this folder” is blank… that causes WP to use the default path, which is “wp-content/uploads”. If you know that your upload path is different than the default, then put it there, but the usual is to leave it blank.

Now, do the following in your Plesk File Manager:
Rename your “uploads” folder to something else, like “uploads_old”. Then create a new folder and name it “uploads”.

Now, go into your WP admin and try uploading an image. It should work. If not, temporarily chmod your new “uploads” folder to 777, then upload. After you get it working, you can chmod it back to 755. (I’m not sure why this worked for me, but it did. It may have just been a lag in the server resetting after creating the new folder and I really didn’t have to chmod to 777).

Now you can upload any other folders and files to your new “upload” folder, but be careful not to overwrite and new folders/files that you just created.

Hope this helps you Plesk users out there or anyone else using a similar system.

I had this same problem while trying to activate eShop 4.3.1. with WP 2.9.1. Reading the above posts gave me the answer that files were probably not being written by the “activate” process. So, I temporarily set my wp-content dir permissions to 777, then Deactivated and re-Activated the eShop plugin. That did the trick!

As Adamsen said above, it would be nice if the plugin stated this like many other plugins do when needing permission changes, either live or in the readme.txt file.

Thanks Adamsen and elfin!