|
Bill Querry
|
August 18, 2015 at 12:34 pm
Not to take over someone else’s thread, but I am also trying to figure out how to do something like this with EE4. I want “Parent/Guardian/Coach” information and then 1-15 “multiple attendees” information. The “Parent/Guardian/Coach” does not attend the event, only the attendees. The “Parent/Guardian/Coach” may or may not be the one that pays as well. A plugin? Hooks via the API?
|
|
Lorenzo Orlando Caum
|
August 18, 2015 at 12:49 pm
Hi Bill,
I’ve split your support post reply from the original support post.
If you see an existing support post that sounds like your issue or question, then please create your own support post and then include a link to the support post that you saw. This will help us prevent confusion when multiple members are posting.
Currently, the payee is considered to be the primary attendee which is how the core works. There isn’t currently a way to separate those into different records for billing purposes.
I’ve also added your feedback to the current discussion.
—
Lorenzo
|
|
Bill Querry
|
August 18, 2015 at 1:32 pm
Hi Lorenzo-
Re: Sorry regarding the thread take-over, will do as requested in the future. I was just trying to add a “vote” for the feature being discussed as it is a current IMMEDIATE need of mine as well. And in my opinion, it will be a real need with others as well since anything that involves registering children requires Parent/Guardian information. And since not many kids have credit cards, the Parent/Guardian is usually the one paying. 🙂 SO adding the P/G info as extra fields, and the kids info bevcoming the paying info, just doesn’t work.
Taking the liberty to eloborate a smidgen more, in my scenario the registration checkout process does make the assumption, and limitation, that the same Parent/Guardian and payer are the same for all attendees events:
Event #1
1. Parent/Guardian info (which is usually, but not always the payer info as well)
2. Attendee #1, #2, etc.
Event #2
1. Attendee #1, #2, etc.
Event #N
1. Attendee #1, #2, etc.
Payer informatiom (pre-populated with Parent/Guardian info) but overridable of course.
For me, this is the last obstacle that I have to find a design work-around so I can finally use EE4. Multiple events and promo codes were on the list and now off (thank-you), but I still have to figure this out somehow.
Bill
|
|
Lorenzo Orlando Caum
|
August 20, 2015 at 8:52 am
Hi Bill, that is one of the use cases that we have discussed. The other would be for conferences where an HR representative or billing department is purchasing tickets on behalf of an organization.
—
Lorenzo
|
