I thought I’d take this opportunity to share a bit about PHP errors. I often have clients tell me, “My site exploded!” My brain construes an image akin to Ghost Busters where we learn crossing the beams of your proton pack is a bad idea.

*GOODBYE STAY PUFT*

A php error, often obscure (think: parse error) can have a fair bit of helpful information in it.

For example:

This morning my site had an fugly php error at the header.

After a quick look, I can find the following information.

Reason for Fail, File, Directory, and Line.

This tells me something happened with the contruct in line 290. Specifically, if I open the file found in the directory there /pi.twitter_timeline.php I can see it’s the function bringing in the timeline from twitter.

What does this mean to a non-programmer? It means you know what to google to find out how to fix your error.

A quick “Twitter Timeline Plugin ExpressionEngine Error” results in the following blogpost:

Twitter Timeline Plugin and (n)Oath.

You’ll find the resource you need to update your twitter plugin and be on your way.

Replace the existing file with the latest version and rest assured, Stay Puft is taken care of. For now.