Ask Agaric: Event Module and Node Types
Q: For the record, what's the difference between a plain vanilla Event and an Event-enabled CCK content type?
A: Event can (more or less) work with any node type. A reason for using a CCK node (say, content_event) instead of the event module's default node type would be the ease of adding fields--
- A small box labeled description in place of the large box labeled body
- A venue field, or a food field
- Most worthwhile reason to switch: a 'price' or 'price range' field
Events are one of the easiest things to both convert to a new type, and to not worry about not converting-- they're future oriented-- and so can be one of the later questions decided during the site configuration process. Usually, the node types that will be used for content are one of the first decisions to make (including possibly making new, different content types which hold the same type of data, but that you want treated differently-- comments enabled or disabled, which categories apply, etc.)
Q: For the record, what's the difference between a plain vanilla Event and an Event-enabled CCK content type?
A: Event can (more or less) work with any node type. A reason for using a CCK node (say, content_event) instead of the event module's default node type would be the ease of adding fields--
- A small box labeled description in place of the large box labeled body
- A venue field, or a food field
- Most worthwhile reason to switch: a 'price' or 'price range' field
Events are one of the easiest things to both convert to a new type, and to not worry about not converting-- they're future oriented-- and so can be one of the later questions decided during the site configuration process. Usually, the node types that will be used for content are one of the first decisions to make (including possibly making new, different content types which hold the same type of data, but that you want treated differently-- comments enabled or disabled, which categories apply, etc.)
Comments
Post new comment