# content
Can confirm that this problem does not exist on a clean wordpress install with the current 1.3 release. I'm trying to track down what causes the error to surface.