Damn, that's two bugs - one that the production site's showing real errors, and that there's a db bug. I think I've now fixed this - can you try again? :)

Oh, and thanks for letting me know :)