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)
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jyee’s picture

Patch attached. It should hit all of these, although I had issues updating the admin view to use the field directly on the sponsor node… so that is still relating through the level (which would produce incomplete data in the admin view if the sponsor had an event, but not a level).

jyee’s picture

Assigned: jyee » Unassigned
Status: Active » Needs review
FileSize
18.56 KB

This patch resolves some php notices and should resolve the view. Note there appears to be an issue when using views_ui that it will try to force the event column to relate on authors… so be careful if saving the view via views_ui.

jyee’s picture

japerry’s picture

Status: Needs review » Fixed

This is within the cod_scheduler branch and will be pushed up when the scheduler branch is pushed up.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

  • Commit fcdbac2 on 7.x-1.x, 2009512-scheduler by japerry:
    Issue #2178627 by japerry: Remove the sponsorship level for sponsors who...