hey @johnregan3, is this what you are talking about?

![screen_shot_2014-01-31_at_12_52_00_pm](https://f.cloud.github.com/assets/522158/2053497/ee9af11c-8aa8-11e3-8e29-77909218b068.png)

1. I think we can remove this bit of code because most of the time this is being caused by serialized options, which #78 addresses.
2. The second reason this would happen is if a proper label did not exist for a post type. I feel like we shouldn't be doing any "automagic" stuff here for this case either. It would be up to the plugin author to fix their mistake, not up to us.

What do you think of this philosophy?