URGENT: Do NOT upgrade to WordPress 3.5 on IIS

  • Facebook
  • Twitter
  • Google Plus
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS

WordpressA couple days ago the great people over at WordPress.org released WordPress version 3.5, however there is a bug that seems to be affecting anyone who’s website is running on a Windows server.

Why should you care? If you’re running WordPress on a Windows server and you upgrade to WordPress 3.5, you will find that you will not be able to update themes or plugins, or install any new plugins. Instead, you will get the following error… “Download failed. Destination directory for file streaming does not exist or is not writable.”

The only way to fix this bug it is to manually modify core WordPress files. What is worse is that anyone who has already upgraded to 3.5 will not be able to upgrade their version of WordPress that will have the fix in it due to this same bug.

I have been told by one of the WordPress developers that the fix is indeed in an upcoming patch, version 3.5.1. As mentioned however, if you have already upgraded to WordPress 3.5, you will not be able to use the auto upgrade option in WordPress and will have to do a manual upgrade via FTP or apply the fix yourself, also via FTP.

WordPress 3.5 Manual Fix

Below is the manual fix you can apply to be able to get your WordPress 3.5 install working correctly, there are two options that should work.

1) In the file wp-config.php, add the following line before “That’s all, stop editing”

define( 'WP_TEMP_DIR', ABSPATH . 'wp-content/' );

or

2) In the file /wp-includes/class-http.php comment out lines 144 and 145, which look like the following:

if ( ! is_writable( dirname( $r['filename'] ) ) )
	return new WP_Error( 'http_request_failed', __( 'Destination directory for file streaming does not exist or is not writable.' ) );

After applying one of the above fixes you should be able to add/upgrade your plugins and upgrade your themes, and will allow you to use the auto upgrade feature when WordPress version 3.5.1 is released.

If you would like to speak to the Satori team about developing, hosting or managing your WordPress website or blog, please feel free to contact us. We would be happy to serve you.

  • Facebook
  • Twitter
  • Google Plus
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS

Comments

  1. Thank you. It only took about 3 hours to find this post and resolve our issue. BAD WORDPRESS! :P

  2. Thanks for the tip. The 2nd issue isn’t one I’ve found elsewhere (after 3 hours of seeing the 1st over and over) and it was the one I really needed.

  3. I’m not sure if i have this problem of upgrading to new version (hope this will be available ASAP) but still a couple of bugs are still bothering me.

  4. Awesome! Thanks for the fix. I used the first method and it worked easily. I have WordPress 3.5 running on IIS7.

    RainMaker Martial Arts Software

  5. Thanks for posting! Option 1 worked for me and saved me a bunch of time!

  6. This helps a lot! Thanks!

  7. I tried both options to update from 3.5 to 3.5.1 on a IIS7.5 server. No luck :-(. Also installing the Hotfix plugin does not help. Would manually copying the files from 3.5.1 (as mentioned on the Codex) be a safe solution to do an upgrade to 3.5.1?

    • Absolutely, doing a manual upgrade by overwriting the old files with the new files from 3.5.1 is probably a preferred way to upgrade. Some people are wary of doing it that way, but you should be fine. I highly recommend however, as with any upgrade, to backup your database and your wp-content folder before proceeding, just in case you need to rollback for any reason. Good Luck!

  8. Thanks..its working fine for me…

Trackbacks

  1. [...] I posted last month, the release of WordPress 3.5 introduced a bug that prevented people running on an IIS server (Windows server) from installing new plugins and [...]

Leave a Reply