Removing content types from content.module

Events happening in the community are now at Drupal community events on www.drupal.org.
drumm's picture
Posted by drumm on August 28, 2006 at 11:41pm

Drupal core has had configurable content types for awhile now. What is the plan for removing those from CCK and having the field system added via nodeapi or formapi? This really should work well on the next release of Drupal and would provide something better to look at and evaluate for moving fields towards core.

Comments

Patch needs review

Posted by yched on August 29, 2006 at 12:10am
yched's picture

dopry has taken a shot at it there

not just formapi

Posted by moshe weitzman on August 29, 2006 at 2:07am
moshe weitzman's picture

i am not so sure about the nodeapi/formapi approach. it sounds super useful. but cck does a lot of caching which i think will be nullified if it doesn't own the content type ... maybe someone can talk to the performance implications of this.

Well, then the performance

Posted by drumm on August 29, 2006 at 9:51am
drumm's picture

Well, then the performance things need to be in core. The point of putting configurable content types in core is to get the implementations (flexinode and cck) out of contrib so we can concentrate on one place and get things cleaned up for the next feature.