[wp-trac] [WordPress Trac] #9674: Better support for custom post types

WordPress Trac wp-trac at lists.automattic.com
Fri Jan 8 16:44:48 UTC 2010

#9674: Better support for custom post types
 Reporter:  wnorris                 |        Owner:  ryan    
     Type:  task (blessed)          |       Status:  reopened
 Priority:  normal                  |    Milestone:  3.0     
Component:  Administration          |      Version:  2.9     
 Severity:  normal                  |   Resolution:          
 Keywords:  has-patch tested early  |  

Comment(by aaroncampbell):

 Replying to [comment:125 mikeschinkel]:
 @mikeschinkel: I'm addressing persistence by saying that I don't think
 it's needed.  If all content types are registered at init, then by the
 time I get to my options page for my plugin, I can simply access them and
 use them.  If I need a complete list at init, then I simply set the
 priority level to something high (like 100) so that I can be sure that all
 other init functions have already run.  Even without persistence, I have
 access to all content types pretty early in the WordPress loading process.
 Like Ryan said, persistence could potentially cause all sorts of problems.
 So many plugin authors would forget to unregister the content type when
 the plugin is deactivated or uninstalled, then the user has a content type
 they can't actually use.

Ticket URL: <http://core.trac.wordpress.org/ticket/9674#comment:128>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list