Releases for Conference Organizing Distribution Support Modules

Beta4 is an incremental update to Beta3 released in July to support the underlying COD distribution.

It also fixes a security issue where some users could see session evaluations of others. Since this is not covered under the Drupal Security policy, it is not considered a security release.

Changes since 7.x-2.0-Beta3:

Beta2 is an incremental update to Beta1 released in June. Specifically, we remove the ability to use registration panels with page manager, instead relying on panelizer default registration templates to do the task instead.

Important! If you use the registration default page manager panel, make sure to override it in features or export it before applying this version. Otherwise, you'll lose the registration page.

This release is the tested spring release, used on events.drupal.org and linuxfestnorthwest.org. It contains bug fixes, as well as scaffolding for using services for mobile functionality, coming in a future Alpha release.

New sites are urged to use the 2.x branch of cod and cod_support as there is no development occurring on the 1.x branch anymore. For the most part, sites will be able to update from 2.x alpha to alpha, unless noted in the release notes.

This is the third (fourth) alpha release of the cod support modules. Alpha3 was skipped because it was a security release in the upstream distribution.

Major updates since Alpha2 include:

RC1 is an updated tag for Beta12 -- no new changes are happening on the 1.x branch, most of it is now in the 2.x branch.

See https://www.drupal.org/node/2566737 for more release notes.

This is the initial alpha release of the drupalcon changes that many people in the 7.x-1.x dev branch have been using with COD.

If you're using any version of COD for your site before Beta 9.1 or 9, you should stick with the 1.x branch, unless you do extensive testing first. This 2.x can potentially break the upgrade path.

Changes since 2015-04-13:

This is a development snapshot of the Drupal 7 branch of COD 1.x, which is currently moving into long term maintenance support.

This version of Cod 7x-1.0-Beta9 will be the last version of the pre-DA/ticket version of COD coming in Beta 10/RC1.

Most notably, we converted bofs and schedule pages to use panel panes. We also updated ticket module to ticket_reservation, which should provide better UX for end users.

Note: When upgrading, make sure to check over your site locally before pushing to production!

This release of cod support is to remain inline with the profile beta. There are only a few changes to features details, and most do not have an automatic revert. You'll want to review the patches and revert your features accordingly.

This release of COD is mainly an inline release for the profile because of security advisory in Drupal Core. However, there are two advancements related to speaker notification

• Refactored Speaker notification page to use a VBO operation to send E-mails
• Fixed bug where speakers were using old user references (instead of entity reference)

To get the most out of COD Support, its suggested to use the COD profile.

cod_support:

This release is mainly a incremental module update. Two major fixes occurred in this release:

• Timeslots should now properly assign from schedule items and sessions
• Tickets now save an order ID on a ticket for future rules integration

This is a drop-in replacement/upgrade of COD beta2. Download and update, you should be good to go!

Full list of changes since 07-08-2014:

Welcome to COD Beta!

Many big features have changed between the Alpha5 and beta releases, full changelog below. The biggest changes:

• All issues going forward must have an upgrade path.
• Administrative functionality centered around the Event CT
• Tracks are using og vocabulary, field_session_track has been removed
• Better commerce <-> ticket integration with cod paid events

Changes since 2014-05-12:

Release Notes for 7.x-1.0-alpha4

Changes since 10-22-2013:

This version of cod_support is a major re-design of event management under cod. While it is fairly compatible as an upgrade layer to alpha1, there are major changes that require manual intervention

Changes

• Event CT now managed as groups using organic groups
• Timeslots, Rooms, and Sessions all reference an event (group item)
• Users can signup to an event by joining a group (requires external code to register)
• Sponsors are linked to an event via a sponsor level, which is now a taxonomy
• Events now have a dashboard, which is a customizable panel
• Timeslot/Room combo administration moved into the event dashboard

Known Upgrade issues
7.x-1.0-alpha1 to 7.x-1.0-alpha2 Will get "Can't save entity as group, because user admin can't be subscribed to group and become a manager." when creating an Event because the og_user_node field does not get created on the user entity when OG is installed for some unknown reason. Basically, you just have to start fresh with alpha2 because you cannot set the the field to the correct name (it forces it to be prefixed with "field_") when you try to create the OG Reference field manually on the user.

This release fixes #1701466: Profile fields export broken.

Changes since 6.x-1.0-beta1:

• Bug #1102234 by ezra-g: Broken/missing handler in Block:Featured of Sessions view.

Note that the packaged version of COD Beta2 also includes UC_Signup RC3 and Ubercart 6.x-2.6.

Changes since DRUPAL-6--1-0-ALPHA2:

This release probably has some good bugs, but it's necessary to create at least an Alpha so we can use a drupal-org.make file. Also, CCK fields are subject (and almost certain to) change before the next alpha.

As always, don't use Alpha on a production site unless you really know what you are doing.