COD help

For the latest documentation, please visit

COD is the Conference Organizing Distribution, used for building conference and event sites in Drupal. You may first be interested in an overview of its capabilities.

This documentation is based on the packaged COD Alpha 3 downloaded from

Getting started

  1. Create and configure an event node; this is the minimum needed to get people to start signing up
  2. Default home page node is unpublished and inaccessible to non-admins. It will be replaced by new content that is added with 'promote to front page' enabled, or until you create your own home page with Views, Panels or a single node.

Image configuration

  1. Be sure to enable ImageAPI GD2 or ImageAPI ImageMagick
  2. Enable Imagecache UI (optional)
  3. Check permissions

Goal: Get people signing up to the Event

  1. An event needs a title, description, start date/time, end date/time, sku, and a sell price. Everything else is optional.
  2. Configure an Ubercart payment gateway
  3. Check permissions and start promoting

Goal: Get sponsors

  1. Enable the COD sponsors feature (admin/build/modules). This also enables the 'Conference administration' admin menu.
  2. If needed, modify sponsor levels (e.g. platinum) in the allowed values list of the Sponsor content type (admin/content/node-type/sponsor/fields/field_sponsorship_level)
  3. Adjust permissions if you'd like sponsors to create their own sponsor node (it will remain unpublished until an admin approves and publishes it).
  4. Modify Sponsor view if you'd like additional sponsor levels to appear on the Sponsor page (by default, only platinum display)
  5. Or, arrange the blocks (admin/build/block) so the other levels. There are separate sponsor blocks for home page and internal pages
  6. If needed, rename sponsor levels in the view
  7. Assign Sponsor blocks to regions
  8. Check viewing and editing permissions are appropriate for your needs

Goal: Display attendees who have signed up for the event

  1. Enable the COD Attendees feature (admin/build/modules).
  2. Full names and photos of attendees will be displayed.

Goal: Begin accepting sessions

  1. Enable the COD Sessions feature (admin/build/modules). This enables the 'Conference administration' admin menu.
  2. Update the session Track field allowed values in the Session content type (admin/content/node-type/session/fields/field_track)
  3. As sessions are created, visit the Session administration (conference-admin/sessions) to manage sessions; review and publish submitted sessions so they are visible to the public
  4. Encourage session submitters to fill in their profile, so their full name appears in the schedule.

Goal: Allow session voting

  1. Voting usually begins once you've finished accepting new sessions, so votes are applied fairly.
  2. Adjust flag access on the Session vote flag (flags/manage/session_vote) to allow other roles to vote on sessions.
  3. You will probably want to do some additional theming to ensure the "Vote" links are more prominent on session nodes, or build a view that shows all notes that haven't been voted on by the current user, filterable by track/experience level.
  4. Remove the flag access by role (flags/manage/session_vote) when you want to stop allowing people to vote.

Goal: Create the schedule

  1. Create Room and Time slot nodes. These will be the framework for your schedule.
  2. Sessions and Schedule items are different content types. A Schedule item is something like Lunch, that doesn't have a presenter or track, but needs to be assigned a room and time slot.
  3. Sessions and schedule items can be assigned to multiple rooms. Assign an item to all rooms for it span the width of the schedule grid and indicate there are not other sessions planned during that time (e.g. Registration)
  4. Sessions and Schedule items need to have a Room and Time slot assigned to them to appear in the schedule, as well as be Accepted and Published.
  5. You won't be able to schedule two sessions/schedule items in the same time slot and room; a warning message will appear, explaining the conflict.

Community configuration (alpha 3)

  1. The cod_community view displays name, photo and core profile fields of signed up users out of the box, with exposed filters.
  2. A forum menu link also appears