|
hawkman
|
August 3, 2015 at 2:11 pm
I use event espresso 4 for class registrations. On a date, you can register for 1 or more classes. I manually registered someone on the backend in wordpress and need to add another ticket to the registration and another student. I dont see a way to do that. I may have a few more students to add before class starts and I don’t want to delete the registration each time and start over.
Is there a way to edit the registration and add another ticket and another student?
Also, when adding in WordPress, it assume student number one is the billing contact and that isn’t correct. It doesnt let me enter the billing party.
|
|
Tony
|
August 4, 2015 at 5:23 am
Is there a way to edit the registration and add another ticket and another student?
Not currently.
To add additional tickets you would need to re-create the registration, selecting the correct number of tickets, inputting the student details and then cancel the original registration.
Also, when adding in WordPress, it assume student number one is the billing contact and that isn’t correct. It doesnt let me enter the billing party.
The info entered for the first ticket (at the top of the registration page) is considered the ‘Primary Registrant’. They are considered the registrant handling all billing currently, they will be the only registrant to receive a payment pending email that allows them to pay.
Do you see something different on your install?
|
|
hawkman
|
August 4, 2015 at 6:26 am
The info entered for the first ticket (at the top of the registration page) is considered the ‘Primary Registrant’. They are considered the registrant handling all billing currently, they will be the only registrant to receive a payment pending email that allows them to pay.
Do you see something different on your install?
On the front-end (website), the first person is the student. When you get to billing, you can enter a different person / address. I have people who register students on their behalf. If I manually register someone, I have to use student 1 as the billing person, but really they aren’t attending class. So it doesn’t match up with how it flows on the website.
|
|
Tony
|
August 4, 2015 at 8:42 am
EE considers all registrations made to be attendees of the event, the ‘Primary Registrant’ (the first set of details entered on the reg form) is the only registrant to receive payment related emails.
There is currently no way to split the Primary registrant from the ‘payee’ but you could collect the first students details as custom questions within the Primary registration. The registration would still show show as being under the name of the payee, but you’ll then be collecting both sets of info at once, would that work? (I can provide further details if so)
That billing info is the information that will be sent to your payment gateway and used for AVS or similar (if enabled within the gateway)
|
|
hawkman
|
August 4, 2015 at 4:18 pm
Yea that doesn’t work for me. Here is the scenario. A person calls and says I would like to send 3 people from my company to your training. We log into WordPress, go to the event date and add a registration. If we add the person calling, it will be 4 students.
Now lets go through the experience on the website. The person who called logs on and selects 3 tickets. They enter the names of the 3 students then proceed. At the billing screen, they enter their name and billing info.
At this point, I’m not sure who gets the receipt, but at least only 3 people are registered for the event.
Maybe what you are saying might work for the WP interface.. can you explain?
|
|
Josh
|
August 5, 2015 at 9:56 am
Hi Shane,
You can capture separate billing contact information by adding billing contact info fields to the the primary registrant’s question group. Then, you can set the messages to be sent to the billing contact’s email address. For example, if you set up a billing contact email field and the field’s name is “Bill to email”, you go to change the registration pending payment email message’s “To:” field to `[RECIPIENT_ANSWER_* Bill to email].
What this will do is change where the registration pending email is sent. Instead of sending it to the registrant, it will send the email to the bill to email address. This will work for other emails as well (like the Payment Received message).
|
|
hawkman
|
August 5, 2015 at 2:26 pm
I’ll try this. What do you think will happen when they pay by credit card and get to that page.. who is going to be pre-filled?
|
|
hawkman
|
August 5, 2015 at 2:33 pm
Josh,
Actually I’m confused on this. I have two question groups by default. Both are used whether you are a primary registrant or an additional attendee. Do I need to create another question group or what? The two groups I have are Address Information and Personal Information. If I add billing info to either one of these, both the attendee and registrant will get it.
You can capture separate billing contact information by adding billing contact info fields to the the primary registrant’s question group.
|
|
hawkman
|
August 6, 2015 at 1:05 pm
Josh,
I did what you suggested after realizing I needed to create new questions and a new group. After that I tested with a credit card payment, and the attendee 1 info is what gets passed to the billing form, not the new “billing contact info”.. so I don’t think this is a good workaround. I think EE needs to allow for separate billing info (you see this as standard practice on check out forms “billing info same as shipping info?” then it can prefill etc.
|
|
Josh
|
August 7, 2015 at 2:21 pm
Hi Shane,
We can add a filter hook that allows for overriding the what gets auto-filled on the credit card billing form. I’ll update this thread when we have something you can use.
|
|
hawkman
|
August 20, 2015 at 10:11 am
Any update on this?
|
|
Lorenzo Orlando Caum
|
August 20, 2015 at 12:23 pm
Hi, this filter has not yet been applied. We’ve been focused on getting Event Espresso 4.8 along with the promotions add-on released.
Now that those are available, we are reviewing additional bug and enhancement tickets.
I’ll add additional feedback to the current request.
—
Lorenzo
|
