Details
Minor
Description
Several performing arts organizations are using CiviCRM for ticket sales, and in this use case, it's desirable to allow a single contact to have multiple "registrations" (ticket purchases) per event. Someone may purchase tickets and then decide later to purchase additional tickets for the same performance.
In the event "online registration" configuration tab, it seems that checking "allow multiple registrations from the same email address" should enable exactly that, but that check box apparently only works in combination with the "register multiple participants" option.
I've created a patch that makes "allow multiple registrations from the same email address" to work on its own, so that a single contact can register multiple times for the same event – or in this case purchase tickets multiple times.
Patch file is attached.
Attachments
Activity
This is a better patch to allow multiple registrations.
The v2 patch is simpler and doesn't create duplicate contact records.
I've been using this patch on a production server for over a year and with thousands of event registrations. Works great.
Additionally, I would like to point out the this combinations of settings ("register multiple participants" OFF & "allow multiple registrations" ON)
1. Intuitively should work as the patch allows
2. Is of great use to those of us using a ticket model of event registrations
3. Has no other intended purpose
I would very much like to see this incorporated into core and don't quite understand why it keeps getting pushed further into the future.
Here's a more complete patch that:
1) Allows primary participants to create multiple registrations per event if "Allow same e-mail?" is checked in the event config
2) Addresses the "already registered" warning on the event info page
3) Gives a more detailed explanation of the effect of the different same-email / multiple-participant checkbox combinations on the Event config page.
Committed revision 40100.
Thx for the patches! I've updated the help a bit as well.
According to this post: http://forum.civicrm.org/index.php/topic,17248.msg79080.html#msg79080
This patch resolves the issue, but creates duplicate contacts. The post above indicates that there is a better (one line change) that fixes the issue without creating duplicate records.
In the forum, I did question why the "better" patch was not submitted... but am still waiting on a reply