<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Four O'Clock Project &#187; Wordpress</title>
	<atom:link href="http://www.fouroclockproject.com/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fouroclockproject.com</link>
	<description>Thesis Theme Customizations and Tutorials</description>
	<lastBuildDate>Wed, 26 Aug 2009 11:46:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How I Fought the Wordpress White Screen of Death and Won</title>
		<link>http://www.fouroclockproject.com/2009/how-i-fought-the-wordpress-white-screen-of-death-and-won/</link>
		<comments>http://www.fouroclockproject.com/2009/how-i-fought-the-wordpress-white-screen-of-death-and-won/#comments</comments>
		<pubDate>Mon, 20 Jul 2009 23:41:03 +0000</pubDate>
		<dc:creator>R.J.</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.fouroclockproject.com/?p=383</guid>
		<description><![CDATA[What do you do when your website goes blank and your source code is nowhere to be found?  Find out here and learn how to fix your whitescreen.]]></description>
			<content:encoded><![CDATA[<p></p><p>If you&#8217;ve been to the site over the past ~5 days you might have noticed, well, nothing!  The screen was <strong>blank</strong>, the source code was <strong>empty</strong>.  <span style="text-decoration: line-through;">Crap</span>.  Yikes. To the casual observer it might have looked like I <em>packed</em> my bags, <em>booked</em> my ticket and <em>flew</em> this chicken coop for greener pastures.  I mixed my farm analogies there (sorry <a href="http://www.doublemule.com/">Doublemule</a>) but you get the idea.  I&#8217;m trying to say that the site was broken but now it&#8217;s fixed &#8211; it was dead but now it&#8217;s risen &#8211; it was lost but now it&#8217;s found.</p>
<p>And you can too!</p>
<p>I&#8217;m going to share with you the story of how the site disappeared like an artifact in the Indiana Jones franchise and then reappeared after it was pulled back from the vacuous brink of digital ruin like the ending of every Matrix movie.</p>
<h3>You Call This an Upgrade?</h3>
<p>There are two ways to do an upgrade for wordpress, automatic and manual.  Both have pros and cons.  Lets compare them.</p>
<h4>Automatic Upgrade</h4>
<p>Pros: It&#8217;s fast and you can do it from the safety of your WP dashboard.</p>
<p>Cons: Things can break, horribly.  If you earn a living from your website (like me), then broken money streams are a problem.</p>
<p>So if things can break during the auto upgrade, why not just always do the manual upgrade, right?  Not necessarily.</p>
<h4>Manual Upgrade</h4>
<p>Pros: It&#8217;s safer and more controlled than the auto upgrade, in my opinion.</p>
<p>Cons: It&#8217;s slow and much, much more complicated.  Especially if you&#8217;re not comfortable using an ftp client or your control panel or mysql.</p>
<p>I tried to save some time (hey, I&#8217;m a busy guy) and went with the automatic upgrade last week.</p>
<h3>Then All Hell Broke Loose</h3>
<p>Seconds after my upgrade <strong>failed</strong> I knew I was in trouble,  my plugins began showing error messages on my main site.  Plugins are a common source of headaches during a WP upgrade because if one is not compatible with the new version, it can crash and pull your whole site down with it.  I realize that that is not a very technical explanation, but a ggl search will garner more information if you&#8217;re really interested in the dynamics behind it.</p>
<p>After another site reload, I noticed&#8230;nothing.  I found myself staring at a blank screen &#8211; the wordpress white screen of death.</p>
<p>How embarassing and annoying.  I&#8217;ve worked with plenty of WP sites and never had to deal with this before. Time to fix it.</p>
<h3>Not so Fast</h3>
<p>It was like a perfect storm, not only could I not access my WP dashboard, but my host had also locked off phpmyadmin for EVERYONE using their service while they resolveld some issues.</p>
<p>And so I sat and waited.  And waited.  And waited.</p>
<p>Days went by and my site was blank, which meant that no new tutorials could come out, no one with Thesis Theme questions could ask them, no new clients could find or contact me.</p>
<p>Ouch.</p>
<h3>Things were looking up</h3>
<p>My host enable phpmyadmin.  Great!  That let me log into my account and remove a ridiculously large amount of tweetbacks in my database that I can only assume was a bug.</p>
<p>But that still didn&#8217;t fix my site.  So I exported my mysql database and moved on to trouble shooting my WP install, itself.</p>
<p>Unfortunately my ftp client decided to die on me.</p>
<p>Moving on, I got a new ftp client and logged into my account.  I downloaded WP&#8217;s latest stable version and began replacing all my files EXCEPT wp-config.php and the wp-content folder.  This took a long time.</p>
<p>Once all the new files were uploaded I check FoCP only to find that I <strong>STILL</strong> had a blank screen.</p>
<h3>When will it end?</h3>
<p>On a whim, I tried navigating to my wp-admin.  Once there, it said that it needed upgrade my database.  For whatever reason, that seemed to work.</p>
<h3>Back in Business, Almost</h3>
<p>So my site was back, but my plugins were gone and, therefore, a lot of my site&#8217;s functionality.  I&#8217;ve spent the day manually uploading new plugins to replace those lost.</p>
<p>As of now, I&#8217;m almost back to full functionality, which is exciting.  Now I just have to spend another week rebuilding the traffic that I lost as well as staying put with my schedule of meeting client deadlines etc.</p>
<p><strong>So to recap how I solved the white screen problem:</strong></p>
<p>Removed unnecessary files in my mysql database.<br />
Manually replaced old WP files except wp-config.php and wp-content folder.<br />
Upgraded my database.<br />
Removed broken plugins, added new versions of those broken.</p>
<p>And that did it.  I&#8217;m back in business in every sense of the word.</p>
<h3><em>So what was it like without a site?</em></h3>
<p>Honestly, not that bad.  I mean, it&#8217;s scary to think that there are inevitably clients who want to contact me who are unable to and will probably work with someone else instead.  But at the same time, I stayed busy working on my current projects both online and off, and I got paid today, so it&#8217;s really been no big deal.</p>
<p>I <em>have</em> learned, though, that it&#8217;s important to have a backup, which I will shortly once a new site proprogates.  I&#8217;ve also learned a few things that I&#8217;d like to share regarding financial planning for freelancers.  But that will be another post for another day.</p>
<p>A sincere <strong>Thank You</strong> to those of you who are still around to read this and my my RSS feed and follow my Twitter account.  I can&#8217;t promise that mistakes won&#8217;t ever happen again, but I can promise that whatever I learn from them I&#8217;ll pass right on to you so that you can do better with your own online endeavors.</p>
<p>-Rob</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fouroclockproject.com/2009/how-i-fought-the-wordpress-white-screen-of-death-and-won/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
