WordPress: Blank Page

    Maintaining a website is a full-time job. And as a full-time student, iPhone developer, and Lab Assistant, I sometimes wonder if it’s too much. But people actually read this website, so I’ve got to keep it up for them. As ashanks04 pointed out to me, my website is down — but what do I care, I’m busy with iPhone apps :)

    Anyway, I got things running again. It seems that there was a problem with cache.php. To be safe, I deleted all the files in the /includes/ directory and replaced them with new files from the latest WordPress 2.7 download.

    Here’s what the Error Logs were showing:

    [19261] EACCELERATOR: PHP crashed on opline 52 of get() at […]/wp-includes/cache.php:322

    Honestly, I’m not sure what that really means. So if you’ve got some PHP-fu and can provide some insight, please do.

    While I was at it, I took a look at my database — about 84 MB now — and optimized all the tables. Only took a couple minutes.

    I have too many comments to moderate. Spam is a real drag, and Akismet is still letting it through.

    P.S. Cross-post from Twitter: Friday is National Freedom Day. What made the USA great: limited government, noninterventionist foreign policy, respect for civil liberties.

    2 Responses to “WordPress: Blank Page”

    1. Funny Stuff says:

      Maintaining a website is really time consuming. I’m trying to do it while maintaining good grades here at school, and it gets tough. You said your database was 84 mb after optimizing it, what was it before the optimization? What might help to clean up some space on it is getting rid of old post revisions.

    2. Jason says:

      Apart from problem with comments, people can also get a blank page on commenting because some of their comments are marked as spam by blog owners. Akismet sends a 403 error along with blank page in this case. You might want to check that out.

    Leave a Reply