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

WordPress Trac wp-trac at lists.automattic.com
Fri Jan 8 16:54:46 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 mikeschinkel):

 '''@aaroncampbell I'm addressing persistence by saying that I don't think
 it's needed.'''

 From your perspective of a metabox plugin they are not needed but from my
 perspective of a plugin that lets users add post types and annotate with
 the data they want persistence is a must.  Yes my plugin can add it's own
 persistence but then my plugin is incompatible with someone else's plugin
 that also persists their enhancements.

 '''@aaroncampbell Like Ryan said, persistence could potentially cause all
 sorts of problems.'''

 Besides translated strings breaking serialize() (which can be resolved by
 using an non-serialized persistence structure) what other sorts of
 problems?

 '''@aaroncampbell 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.'''

 And in the real world usage that causes problems why?

 (I agree it's not ideal, but does it really matter?)

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


More information about the wp-trac mailing list