WordPress 2.3.2 Internal Server Error Pages

Dec 31, 2007
6 Comments

Warning: strip_tags() expects parameter 1 to be string, array given in /home/michael/public_html/wp-includes/formatting.php on line 664

Okay, this is fun! If you’ve recently upgraded to WordPress 2.3.2 and also the latest version of PodPress 8.8, you may be in for some Internal Server Error page hijinks. As far as I know right now, the only solution is to deactivate the PodPress plugin.

Update: I don’t think PodPress really has anything to do with it, otherwise the problem would’ve stopped when I deactivated PodPress, and it hasn’t. Not sure what’s going on here, since I’ve upgraded other blogs just fine with no problems. Anybody know?

Update 2: There seems to be something in my new theme that was causing internal server errors. I don’t know what, just yet. So, until I have it figured out and fixed, I’ll have to stick with the old theme for a short while longer. Any PHP geniuses out there want to take a crack at it? Email me at michaelmartine@gmail.com and I’ll send you the files.

Update 3: Or, maybe not. I thought that switching back to the old theme would fix the problem, but I’m still getting the internal server error messages. I just upgraded to WordPress 2.3.2 using the WordPress Automatic Upgrade plugin. Does anyone know of any issues with that?

Update 4: Problem solved. It was some code that was a function for a plugin which I had removed. Without the plugin, the code caused an error. I removed the code and the problem is fixed. So now it’s shiny new theme full speed ahead! :)


Warning: strip_tags() expects parameter 1 to be string, array given in /home/michael/public_html/wp-includes/formatting.php on line 664
  • Michael Martine
    The problem was of my own doing. Read the rest of the post updates and comments for more info.
  • Michael:

    I also saw this article and have not yet updated to the newest version. I'm a bit apprehensive about upgrading cuz I'm not a techie.

    Has anyone else experienced problems with updating to the latest version?
  • Michael Martine
    @Russ: check out update 4 added to the original post. The problem wasn't a plugin after all, nor did it have anything to do with the newest version of WordPress. It's always a good idea to be safe and careful, though: back up your WordPress database and back up all of your WordPress site files beforehand, just in case.
  • What plugin caused the problem?

    I was doing some research before upgrading my blog and found your site. It looks like one should wait until the podpress & wp 2.3.2 bugs are ironed out.
  • Michael Martine
    @Pelf: it wasn't the plugin. It was leftover code that was a function that worked with a plugin I had removed. Once I took that out everything was fine.
  • I updated my blogs to WordPress 2.3.2 manually and haven't encountered any problems yet to far. But if you assume that the Automatic Upgrade plugin is the cause of the problem, perhaps contact the author?
blog comments powered by Disqus