Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Thanks everyone at Drupalcon Baltimore for helping get us to a stable release! The 2.0 version of cod_support should help you get started on making your own conference.
This release resolved two major bugs that occur during the install phase. While there are still many bugs and feature requests, this should be stable enough for production use.
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.
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 fixes some outstanding minor bugs, which should calm down the error log using COD.
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 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 fifth alpha release of the cod support modules. This is mainly bug fixes, no major new changes for this release.
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. If you're starting new, use this version of COD.
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.
This is the second alpha release of the drupalcon changes that many people in the 7.x-1.x dev branch have been using with COD.
Major updates here include better timezone handling and the session evaluations feature backported from drupalcon.
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. If you're starting new, use this version of COD.
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.
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 version includes mainly bug fixes and some features around rules and tickets. There is work ongoing with ticket_reservation, which should come in Beta9.
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.
Lots of big changes between Beta5 and Beta6! We're releasing Beta6 now due to some more features coming in Beta7, and we want people to test beta6 more. Compared to previous releases, Beta6 might be a little more unstable than previous betas. However, every bug has an upgrade path, and beta6 has been tested on several production conference sites running Beta 3, 4, and 5.
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.
This is the 5th alpha for cod_support, released before beta comes out.
When is beta?
This is a pre-release before we go with beta. We want to make sure everyone is on the same page with Alpha before we go to Beta. So test this release out and submit your issues! Beta is hopefully just a week (or so) away.
New Features
New Scheduler is in place
Re-shuffled event management under the event node
Replaced registration functions with the ticket module
lots of little bug fixes
re-exported views with new scheduler and session manager
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.
After months of working from forks at the drupal association, linuxfest northwest, thinkShout, etc -- we've come up with an alpha release for COD!
What Does this Alpha Mean?
We have most major features enabled or able to be enabled by default*
Patches that apply from all the various issues have been reviewed and worked into what we see as going forward to drupal7 full release
Users should be able to use this as a starting piece for launching COD sites on drupal 7
* COD Session Video and COD Sponsorship Sales are not ready and not usable in this release. If anyone wants to help port them, check the issue queue!
What Does this Alpha NOT Mean?
Don't expect the information architecture to stay exactly the same. While many will stay the same as we go forth, some will change -- namely the cod_events and registration system as entity registration becomes more stable
No theme. We're using a base adaptive theme, but it could be garland for all we care. If you're interested in helping develop a theme for cod, please help us in the issue queue!
The features you see today are not final. We're looking at using other distro modules whenever it makes sense, in particular seeing where common 'commons' modules work for us
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.