Title: 3.2.1. Bugs
Last modified: August 20, 2016

---

# 3.2.1. Bugs

 *  Resolved [jruimages](https://wordpress.org/support/users/jruimages/)
 * (@jruimages)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/321-bugs/)
 * Ever since I upgraded to 3.2.1. we can’t insert images into new posts using the
   buttons and links on the Dashboard. I’ve upgraded all my browsers to the very
   latest versions, tried the Dashboard on all four browsers I normally use (Opera,
   Firefox, Chrome, and Safari), tried it on both my Mac and my Windows 7 VAIO and
   I just can’t get it to work.
 * Is this a problem anyone else is having? I’ve been doing work-arounds by inserting
   the HTML directly into my posts but that’s not a good solution. I can do that
   but my blog manager who isn’t supposed to have access to the whole back end can’t.
   I need the interface to work or else I’m stuck with having to do the work of 
   yet another person. Is there a way to downgrade? 3.1.4 was working fine for me…

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Thread Starter [jruimages](https://wordpress.org/support/users/jruimages/)
 * (@jruimages)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/321-bugs/#post-2228090)
 * So in case anyone finds this post because 3.2.1 is a crappy upgrade and it screwed
   up their interface functionality… the problem is that a lot of web hosting providers,
   in my case HostGator, are running PHP 5.2 and haven’t upgraded all their servers
   to anything beyond that yet.
 * As my web host can’t or won’t upgrade me immediately to PHP 5.3 and I need to
   get this monkey of my back right away, I’ve downgraded back to 3.1.4. Check [http://wordpress.org/support/topic/is-rollback-to-314-possible?replies=9](http://wordpress.org/support/topic/is-rollback-to-314-possible?replies=9)
   for how to do that.
 * My recommendation: just because WordPress releases an upgrade and wants you to
   implement it doesn’t mean you should. If your blog is administered by a non-techie
   as in our case, definitely don’t upgrade unless you’ve tested the new version
   on a clone of your site. In fact, I would suggest not ever upgrading unless you
   begin having problems or at least don’t upgrade until a month or two after an
   upgrade is released. WordPress is apparently an open source project managed and
   developed largely by volunteers and not necessarily people who care about the
   needs of professional users. Treat all new releases as unsafe until you know 
   with 100% certainty that your server and OS meet all requirements for the new
   version.
 *  [jingco](https://wordpress.org/support/users/jingco/)
 * (@jingco)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/321-bugs/#post-2228307)
 * You can run PHP 5.3 by adding the following line to your .htaccess file in the
   main folder. I tried it and it worked, I can now upload images and media files:
 * AddHandler application/x-httpd-php53 .php

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘3.2.1. Bugs’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 2 replies
 * 2 participants
 * Last reply from: [jingco](https://wordpress.org/support/users/jingco/)
 * Last activity: [14 years, 8 months ago](https://wordpress.org/support/topic/321-bugs/#post-2228307)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics