CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Default Additional Participant's details
Pages: [1]

Author Topic: Default Additional Participant's details  (Read 696 times)

zorgalina

  • I post occasionally
  • **
  • Posts: 34
  • Karma: 0
  • CiviCRM version: 4.3.5
  • CMS version: Drupal 7
  • MySQL version: 5.5
  • PHP version: 5.3
Default Additional Participant's details
November 11, 2013, 03:58:32 pm
Slightly different than a previous poster wrote about where he just needed numbers but no individual participant counts for report:

The client would like to have a participant be able to buy multiple tickets but not have to type in names and emails for each additional participant.

I modified AdditionalParticipants.php (under CRM>Event>Form>Registration) to default additional participants' names and email (using the primary/'paying' first participant's email and having checked the template choice to allow using the same email for all). The additional participants' first and last names are the primary one's names postfixed with _N where N is the participant number, e.g. if Ann Arbor buys tickets for herself and 2 others, the others are Ann_1 Arbor_1 and Ann_2 Arbor_@.
I wanted to add this option as a checkbox in the Event Template and I know this means updating the Event's DAO, adding the element in QuickForm and modifying the .tpl.
 I would contribute this code back, if it is acceptable and someone else wants it.  Is this the wrong approach?  I mean, I know I need to do more than implement a hook to add the element to the form, since this would mean a schema update. I can read documentation on how to package this, as a patch or whatever, but would like to hear whether anyone's interested, and if something I described is not the way to go.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Default Additional Participant's details

This forum was archived on 2017-11-26.