I love the fact that you can now create Custom post Types in WordPress since v3.0.
I can now offer clients the ability to create entities in their WP sites that are actually relevant to their site (eg Case Studies, Team Members etc) without having to give lengthy training sessions in how to tag posts a certain way to make them show on certain pages etc etc.
BUT I recently upgraded ro 3.1 a WP site that had been working fine with these Custom Post Types for months now, and they suddenly stopped working.
By stopped working I mean:
1) The permalinks no longer worked – each post was just using the default permalink settings for posts (and not my slug I had set up in register_post_type)
2) Even stranger, in the Admin panel each post in the custom post list was greyed out, un-editable! Couldn’t even delete them! The only option available was “view” and that didn’t work because of the problem I mentioned above.
I discovered the solution by creating a new post of my custom post type – and yes the permalinks worked – and I could edit/delete it as normal. Woo hoo!
Looking in the database I discovered why:
Custom post type names need to be LOWERCASE!
Once I had changed this in my register_post_type function AND updated my database so that all custom post types had the new name, it seems to work ok now.
I guess the custom post types in WordPress are still in beta after all!