|
Michael
|
October 27, 2014 at 10:29 am
Hi! I will be offering 3 ticket types per event (an individual, a bundle, and a donation ticket). When the customer selects 1 of each, the checkout page orders this information strangely.
It puts individual ticket in the Attendee 1 div, the bundle in the Attendee 3 div, and the donation ticket in the Attendee 9 div.
Since I only offer attendee info input to the primary registrant, I was hiding all but the first of these divs with CSS (and formatting the registration emails similarly). But now I see that the other ticket types are in these other attendee divs, so I can’t do that.
Also, each ticket type is getting the Ticket Details header separately. I want each ticket type to be at the top of the page in attendde 1 div, all under the same Ticket Details header.
here’s what I see now:
Event 1 **DUPLICATE**
Ticket Details
Ticket Name and Description Qty Price Total
11-14-14 8am 2 $5.00 $10.00
Attendee #1
Personal Information
First Name*
Last Name*
Email Address*
Attendee #2
This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for it’s registration purposes.
Ticket Details
Ticket Name and Description Qty Price Total
11-14-14 8am (bundle of 6 tix at 15% off) 6 $4.25 $25.50
Attendee #3
This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for it’s registration purposes.
Attendee #4
This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for it’s registration purposes.
Attendee #5
This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for it’s registration purposes.
Attendee #6
This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for it’s registration purposes.
Attendee #7
This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for it’s registration purposes.
Attendee #8
This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for it’s registration purposes.
Ticket Details
Ticket Name and Description Qty Price Total
Donation 2 $1.00 $2.00
Attendee #9
This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for it’s registration purposes.
Attendee #10
This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for it’s registration purposes.
|
|
Dean
|
October 28, 2014 at 6:09 am
Hi,
Can you provide a link to your registration page please?
|
|
Michael
|
October 29, 2014 at 1:21 pm
I am writing to make sure this wasn’t lost in the shuffle. It’s just about the last thing I would like to improve before launch. Thanks
|
|
Lorenzo Orlando Caum
|
October 29, 2014 at 3:44 pm
Hi Michael,
It is currently handled this way as the checkout page needs to account for cases where there are multiple registrants and when there is just a single registrant that is registering for multiple tickets.
Hiding it with CSS is difficult since that is dynamically created.
It may be possible to edit the single page registration checkout process but then your changes will be lost on the next update.
I’ve do know that there have been some changes to the single page registration checkout for a future release of Event Espresso 4 so I’ve created a report to get feedback from the development team on this.
—
Lorenzo
|
|
Michael
|
October 30, 2014 at 5:57 pm
Thanks Lorenzo. It turns out this won’t affect me. I was selling individual tickets and bundles, but now I set the min/max quantities so that nobody would ever buy a combination a both.
|
