[wp-hackers] Is there any compelling reason to use a custom post type plugin?

[Brad Williams]

As a developer of one of these plugins (Custom Post Type UI) I would also
agree that for advanced users/setups you should manually register your post
types and taxonomies.  My plugin will never be the end-all solution to
custom post types.  I developed the plugin to help beginners get comfortable
with post types and how they work.

-Brad
@williamsba

-----Original Message-----
From: wp-hackers-bounces at lists.automattic.com
[mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Mike Schinkel
Sent: Saturday, July 24, 2010 12:30 AM
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] Is there any compelling reason to use a custom
post type plugin?

On Jul 23, 2010, at 10:13 PM, Angelia Baladon wrote:
> Does anyone have any compelling argument for why it would be better to
> use a plugin for managing post types and taxonomies, if you are
> capable of doing all of the registrations yourself in your functions
> file?

I've evolved my thinking over the past few month after using custom post
types heavily for several projects.  Here goes:

=========
Pros of Using Admin-console Plugins for Managing Custom Post Types
=========
-- Great for End Users who want to do some basic things and that will never
be able to willing to write code.
-- Great for rapid prototyping, especially face-to-face with a client.
-- Great for themers and developers new to custom post types to get familiar
with the options and what effect each option has.

=========
Pros of Registering Custom Post Types in Code
=========
-- Much easier to deploy .PHP files via FTP than to merge configuration
stored in a MySQL database 
-- Much easier to apply the best practice of source code control with
Subversion or Git
-- Easier for those who are more advanced (text copy/paste then editing is
easier than editing in the admin or trying to export/import MySQL data.)
-- Possible to associate related functionality within a single deployable
unit (i.e. plugin, or theme.)
-- Results in more robust applications (end user admins can't break your app
by changing critical functionality.)
 
In summary, admins console plugins are for learning and prototyping and for
advanced users whereas registering via code are for those who are building
plugins, themes and robust web sites. IMO at least.

Hope this helps.

-Mike
_______________________________________________
wp-hackers mailing list
wp-hackers at lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-hackers