I have been trying to figure out something to do with Custom Post type plugins. I’ve not figured it out, so I want to see if someone here can shed some light on it for me.
I had assumed that most custom post / custom taxonomy plugins would be using standard wordpress code insertion to create custom types and taxonomy. For instance, I’ve read the WordPress codex info on how to manually create custom types, etc. I assumed plugins where just providing a coding-free or GUI way to go about making custom types.
Yet I have noticed that NONE of the custom post / taxonomy plugins I have tested (all the most popular ones… at least 8 or more) are cross compatible.
What I mean is this: If I set up a custom type with one plugin, it will not show up in any other custom type plugin I try out. Same goes for custom taxonomies.
My concern is that if I start using a plugin for managing custom types, etc., on my blog, I may be left in the lurch if that plugin ceases to be developed. When hundreds of posts are involved, it could prove to be a major problem, and this concerns me.
I don’t wish to have to write code to manage custom types, nor can I expect my friends/clients to deal with code for custom types, etc. So I was looking to deal with them through the GUI of a suitable plugin. But I don’t want to risk that a year from now a new WP release comes out and my custom types are broken because the plugin I use is not developed to support that WP version.
As mentioned, I would have thought these plugins where just using standard WP protocol to deal with custom types, etc. But then I would have expected that when I set up a custom type in one plugin, it will be visible in any other custom type plugin.
Sorry for being so long-winded.
Can anyone shed some light on what I’ve voiced here?
- The topic ‘Why are custom post type plugins not cross compatible?’ is closed to new replies.