7 Aug
2006
7 Aug
'06
7:30 a.m.
Derek Wright wrote:
fairly sizeable collection of tables. leaving it separate from node.module keeps all the DB install/update stuff out of the way for sites that don't need it. i'd vote for a single content module outside of node for everything CCK-esque going into core (with a bunch of .inc files in the same directory... ahh, i'm so glad we did that). ;)
I ranted about why I thought merging content module into node was the best way (this is how it works in core now) over at http://drupal.org/node/62340#comment-119859. -- Neil Drumm http://delocalizedham.com/