Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dev/event#6 Follow the 'same email' participants config setting for backend participants #14884

Merged
merged 1 commit into from
Jul 25, 2019

Conversation

mlutfy
Copy link
Member

@mlutfy mlutfy commented Jul 25, 2019

https://lab.civicrm.org/dev/event/issues/6

Overview

We have the following use-case:

  • Organisation using CiviEvent for a box office, i.e. to sell tickets for concerts
  • People may buy multiple tickets for concerts, and often not at the same time.

For example, they may have bought a ticket during pre-sales, then later bought a ticket as a gift for a friend.

The front-end allows this, thanks for the "allow same participant emails". However the backend does not validate this option. When adding a backend registration, if the participant has already bought a ticket, the admin will get an error message: "This contact has already been assigned to this event."

Looking at Stack Exchange, I found this thread:
https://civicrm.stackexchange.com/questions/15826/enable-multiple-event-registration-for-same-purchaser-participant

Before

Cannot register a contact more than once to the same event.

After

Allow to register.

Technical Details

Needs a test? Also may need a documentation update.

@civibot
Copy link

civibot bot commented Jul 25, 2019

(Standard links)

@civibot civibot bot added the master label Jul 25, 2019
@eileenmcnaughton
Copy link
Contributor

This is just loosening a form rule in a way that makes sense - I feel pretty comfortable with it. If it were post submit I'd be wanting a test

@eileenmcnaughton eileenmcnaughton merged commit f60a3db into civicrm:master Jul 25, 2019
@eileenmcnaughton eileenmcnaughton deleted the event6 branch July 25, 2019 21:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants