tcdisko

I can confirm that I got this same error with WordPress 3.8 and a custom theme.

Enabling the editor fixed it, but this is not ideal since the editor is extraneous for this custom post type.