I Really Should Have Been a Luddite

← Special Session to Stop Increase in CT Fuel Tax Katrina Cottages Now Available For General Public →

I Really Should Have Been a Luddite

8 June 2008 · 4 Comments

I really should have been a Luddite.  Being a little obsessive-compulsive over one’s personal website, when it inexplicably fails, is madness.

Triskele.com is back, at its original URL, for now.  And, although I am now much more familiar with the intricacies of WordPress’ PHP code, php in general, and MySQL…I still haven’t tracked down what the problem has been.

The workaround is bizarre in its simplicity — to simply remove the </body></html> tags at the end of the php footer files.  However, exactly why I’m getting php errors with the those tags, but not without…it’s still a mystery to me.

So, I’m back…for now, at least…although I’d feel more confident in my return if I knew what the root of the problem was to begin with.

Tags: Actuarial Musings


4 responses so far ↓

  • 1 mrshl // 8 Jun 2008 at 10:09 am

    A few odd questions…

    What version of WP are you using? Have you upgraded to 2.5.1?

    Also, an unrelated question, but do you use a FeedReader, like Google Reader? Or do you have a link blog where you share/collect what you’ve been reading? E.g., Tumblr.com or Friendfeed.com?

    Anyways, keep it up. This is definitely one of my my top 10 blogs out of quite a few.

  • 2 MikeTheActuary // 8 Jun 2008 at 3:38 pm

    I upgraded to 2.5.1 a while ago. I started a thread at wordpress.org which goes into the gory details.

    Re the link blogs — I don’t have a link blog per sé, since that’s partly the role filled by this blog. However, I do use Google reader and my starred and shared items are public.

    The way I use GR, “starred” items are articles I’m considering blogging about. “Shared” are just interesting-looking items which I want to look at later, e.g. when I’m not trying to reduce the unread count while a query is running or spreadsheet is recalculating in another window.

  • 3 MikeTheActuary // 8 Jun 2008 at 7:26 pm

    For anyone who stumbles in via web search — I think I have a final fix in place.

    1. Backup wordpress install
    2. Delete wordpress install files.
    3. Download latest.tar.gz from Wordpress.org, and reinstall.
    4. Restore but do NOT overwrite from the backup in step 1.

    I still have no clue what happened to cause my woes….but I’m happy to get it fixed (for now, at least).

  • 4 mrshl // 9 Jun 2008 at 7:45 pm

    Thanks for the reply. Glad to see you’re a fellow fan of GR.

Leave a Comment