COD support

Cannot create Session because Status field is not accessible

April 13, 2014 - 12:45

The Status field on Session is required, but we're currently hiding it from all users.

Tokens are not being replaced in conference-admin/contact-speakers emails

April 10, 2014 - 11:10

I'm using an older version of COD, and tokens are not being replaced properly in emails sent from conference-admin/contact-speakers

I searched the issue queue but couldn't find any reports about this.
Anyone know when the fix was applied?
Unfortunately I'm stuck on a fork, so wholesale to latest version is not feasible.

Use site's mail in field_registration settings

March 20, 2014 - 23:33

The current settings default for field_registration has a hard-coded value of 'example@example.com' which kind of blows when users forget to actually set this setting, so instead lets use the site's default email and or php's sendmail_from value.

Update conference-admin to handle multi-year

March 16, 2014 - 13:30

It doesn't look like the latest COD alpha (5) includes a way to manage multi-year events under conference-admin. Thus, for example, all the sessions from every year will show up in the conference-admin/unprocessed.

Rather than leave it up to every camp to figure out their own solution (which just engenders frustration of COD not being ready OOB) we should decide on how to handle this (filter on the view) and implement it.

Worth noting there that for nyccamp.org we've created a new group node type, "conference" which we create a single instance of every year. We use the event group node type for all the various events at the annual camp, eg. all the trainings, sprints, summits, keynotes, even the group photo.

Completely remove COD and revert to Drupal 7

March 10, 2014 - 23:33

I have had such a terrible time with COD, I've decided to revert back to basic Drupal. Is there a best way to remove just the COD features? There are so many dependencies that I cannot seem to disable modules. I am getting WSOD in the modules pages and frequently in the Entityreference fields.

I also have an error on a basic page:
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'node.entity_id' in 'where clause': SELECT COUNT(*) AS expression FROM (SELECT 1 AS expression FROM {node} node WHERE (node.nid = :db_condition_placeholder_0) AND (node.type IN (:db_condition_placeholder_1)) AND(( ( EXISTS (SELECT na.nid AS nid FROM {node_access} na WHERE (( (na.gid = :db_condition_placeholder_2) AND (na.realm = :db_condition_placeholder_3) )OR( (na.gid = :db_condition_placeholder_4) AND (na.realm = :db_condition_placeholder_5) )OR( (na.gid = :db_condition_placeholder_6) AND (na.realm = :db_condition_placeholder_7) ))AND (na.grant_view >= :db_condition_placeholder_8) AND (node.entity_id = na.nid) )) AND (node.entity_type = :db_condition_placeholder_9) )OR (node.entity_type <> :db_condition_placeholder_10) )) subquery; Array ( [:db_condition_placeholder_0] => -1 [:db_condition_placeholder_1] => event [:db_condition_placeholder_2] => 0 [:db_condition_placeholder_3] => all [:db_condition_placeholder_4] => 0 [:db_condition_placeholder_5] => content_access_author [:db_condition_placeholder_6] => 1 [:db_condition_placeholder_7] => content_access_rid [:db_condition_placeholder_8] => 1 [:db_condition_placeholder_9] => node [:db_condition_placeholder_10] => node ) in EntityFieldQuery->execute() (line 1140 of /path/cod-7.x-1.x-dev/includes/entity.inc).
but I have no idea why this page views fine to logged-in users but anonymous users are presented with the error message.

Abstract submission with COD

March 3, 2014 - 11:54

I would like to be able to let people submit abstracts with the Conference Organising Distribution. Is there a way already implemented? I did not see this.

The idea would be that people can enter information about themselves, the abstract and upload the .tex file and select the session/track that they want to present in.

AND that we can approve the abstracts and add them to the schedule automatically.

Is there an easy way for this? Seems like a pretty (academic) strandard conference requirement.

Thanks!

Anonymous users can access node/add and node/add forms

February 26, 2014 - 11:13

The bug occurs on both cod-7.x-1.0-alpha4 out of the box and cod-7.x-1.x-dev out of the box. If this bug can be fixed with something from Organic Groups, please let me know. See attached screen shots for more information.

Convert from using Entity Registration to using Ticket module

February 3, 2014 - 20:24

One of the largest issues we've had with COD 7.x is registration. Unfortunately, registration was built for a narrow use case that doesn't easily fit how COD is meant to be used.

After consulting with the maintainers of entity registration, jyee and japerry have taken on re-writing it in a new module called 'ticket'. Many constructs of entity registration are still there, but the architecture is fundamentally different.

Ticket architecture entities:
Ticket type, Ticket Registration, Ticket state (optional)

Ticket Types
These entities describe the type of ticket an event may have. It shows the availability, min/max per order, product, etc. Each product type is defined per event via a product type field. The difference between this and Entity registration is that these settings are part of the entity instead of the field definition. This allows us to make different ticket types per event, which is currently restricted to one with registration module.

Ticket Registration
These are the entities that have definable fields the implement ticket types (first, last, address, etc). Since we have ticket types acting as bundles of ticket registrations, we can create different fields for each type of registration, while still containing the global settings under the ticket types entity.

Ticket State
This is essentially registration state. Much of the code was re-used from Registration state, since its doing the same thing. Its only responsibility is to assign a state for a registration. Ticket types can define the default ticket state that a registration starts with, and other modules can modify them. For instance, in COD we have 'Complete' as a default state for free events, but paid events would alter the default state to say Pending.

Most of the ticket module has been complete, and we will be using this issue to track progress of its inclusion to COD. If anyone wants to write a migration/upgrade path from one to the other, that'd be awesome!

[META] Get COD into Beta!

February 3, 2014 - 20:13

While it may not seem like much code has been churning, there is some behind the scenes things happening with COD.

to get to a beta -- these are the major show stoppers:

1) Convert from Registration to Ticket module #2188193: Convert from using Entity Registration to using Ticket module
2) Complete cod_registration module #1854590: Cod Event and Registration design and upgrade
3) Convert cod_paid_events to use ticket module #1840928: Provide streamlined workflow for editing paid event registration settings
4) Get scheduler branch complete (look at 2009512-scheduler branch) #2009512: Simplify creation of rooms, timeslots, etc
5) Finish default event variable/flag for single event sites #2004080: Select default event on the multi-event dashboard
6) Start/Finish an omega4 base theme #2095793: Default theme

Once these items are done, we should be closer to having a beta released. Once beta is released, we will change from breaking APIs and entities to having upgrade paths. Existing COD sites will need to manually update and test changes, especially if they've been reliant on the registration module in the past.

Request for git push access

February 3, 2014 - 19:38

I've been doing quite a bit of work on COD and related projects (namely Ticket) and would like access to push changes to the repo. I think this will greatly help the speed of progress on getting 7.x-1.x out of beta.

Features overridden on fresh install

January 28, 2014 - 15:37

After creating a fresh install of COD all the features where in 'Overridden' state (Screen Shot 2014-01-28 at 12.16.23 PM.png). I checked one of the features and noticed an error regarding a bad index cod_events_admin (Screen Shot 2014-01-28 at 12.17.04 PM.png). I added a condition to the call and it fixed the issue (Screen Shot 2014-01-28 at 12.17.26 PM.png). Patch attached

Relate sponsors directly to events (allow sponsors without levels)

January 21, 2014 - 18:13

Per the COD user stories document, "Organizers can assign sponsors to events without needing a sponsor level" is desired. This means we'll plan to:

  1. Add an event field to the sponsor content type.
  2. Allow the event field to filter the sponsorship level field so that only levels from the corresponding event appear.
  3. Change the level field to be non-required.
  4. Allow an event to be preselected (via url param). This will hide the event field on the sponsor node add/edit form.
  5. Update the sponsor dashboard view to use the event field (currently relates through level)

Bug in cod_session_sessions_speaker_confirmation

January 10, 2014 - 12:23

When I go to the view cod_session_sessions_speaker_confirmation, I cannot preview due to validation errors.
There are two error messages that say

You must pick a flag to use for the relationship "Flags: (Please select a flag) by current user"

I am not familiar with COD as yet, so I wonder if anyone has fixed this bug, or can help me with it?

Proposed URL paths for events, sessions, bofs, etc

January 10, 2014 - 03:43

Its fairly difficult to figure out the current URL layout. I propose we do the following layout:

mysite.com/
/event-name/
sessions/ => this is a full listing of sessions
bofs/
schedule_item/
schedule/sessions => this is the schedule
schedule/bofs
parties

Therefore an example site:
Session: mysite.com/2014/sessions/my-cool-session
Bof: mysite.com/nwcarcon/bofs/my-awesome-bof
Session Schedule: mysite.com/2014/schedule (which is also default for schedule itself)
Bof Schedule: mysite.com/nwcarcon/bofs

My theory behind not doing schedule/sessions and schedule/bofs is because we don't need to have a 'voting section' for BoFs, therefore mysite.com/2014/bofs should just show the bof schedule. Since we have proposed/accepted/declined sessions in a different section than the schedule, it makes sense to split these out. It also isn't intuitive to have a /program section.

Thoughts?

Session cannot be created in COD 7?

January 9, 2014 - 16:50

It is impossible to create sessions in this COD distro, because the session creation screen offers no way to attach a session to a room or a time slot.

In the session creation screen, the select list for Time Slots says -none-, though I know several time slots exist.

Also, a way to attach a room to a session does not appear anywhere...though the COD 7 documentation says explicitly this is what must be done when creating a session.

If this is happening because I have misconfigured COD somehow, I would to understand why....because otherwise COD is useless unless it can create a schedule of sessions!

--Rick