David

@Marus, I'm experiencing the same as you. Any progress? Will update here if I learn anything of value.

It was a custom post type in my case, @adamsilverstein, so it sounds like you have a solution. I ended up rolling the basic functionality we needed into the plugin...

By the way, I initially encountered this in version 1.0.1, and have now upgraded to 1.0.5 and still see the issue.