Benton and Minou have uploaded a bunch of great photos from the Brother Islands performance. Here’s a shot of Ryder and me as ghosts, lying in the leaves on the cold concrete floor of Eyebeam as the audience was getting settled. I shook almost uncontrollably. With what control I had, I stopped periodically to mess with the audience. Some children sitting across from me were very intrigued by Ryder and I.

child: Dad, look! Her leg just fell! [off the edge of the pool]
child: Dad, Dad! He’s shaking! He opened his eyes again!

And here’s the pool by which we lay, from Minou’s photos.

My WordPress installation is still fuxxored in some way. The last few days I’ve been restoring the wp/ directory from a backup, which fixes it, but then it goes back to blank pages overnight. It is to sigh. Advice welcome. This afternoon I’m going to do as clean a reinstall as I can.

Update

I think I fixed it. If you’re getting blank pages after upgrading to WordPress 2.3.1, here’s the solution I found with (too much) digging in the WP wiki. By way of explanation:

“By doing this, two new values, DB_CHARSET and DB_COLLATE, are placed into the wp-config.php file. Those lines should be deleted from your wp-config.php if you are upgrading from a pre-Version 2.2 (like 2.0.10 or 2.1.3) to Version 2.3.1. A detailed explanation about DB_CHARSET and DB_COLLATE can be found in Editing wp-config.php.”

and then on Editing_wp-config.php

Warning for those performing upgrades: If DB_CHARSET and DB_COLLATE do not exist in your wp-config.php file, DO NOT add either definition to your wp-config.php file unless you read and understand Converting Database Character Sets. Adding DB_CHARSET and DB_COLLATE to the wp-config.php file, for an existing blog, can cause problems ?¢‚Ǩ‚Äù as Ryan Boren says, “your queries will go boom!”

ORLY. KTHX 4 TEH INF0.

See, when I upgraded I noticed those new lines in wp-config-sample.php and added them to my wp-config.php. I hope “queries go boom” doesn’t mean my database is fuxxored. I’m going to restore from my backup just in case. In conclusion, take out the db_charset and db_collate lines and your WP install will work again.

Another update

Sigh. Still trying to get this to work. I’ve downgraded to v2.2.3 in the hope that it’s just a 2.3.1 problem.