|
National_Travel
|
February 8, 2017 at 5:38 pm
Since EE4 doesn’t include an add-on charge option I am using an additional ticket to handle the add-on charges (not optimal) Using an additional ticket the attendee list goes up for the add-on items, this gets really ugly when the user selects more than one of each ticket to purchase. It is very confusing for them. I need a way to simplify the attendee info. Possibly not list it on certain tickets in the same event.
Can I hide the attendee info on certain tickets? I have looked into this through CSS and cannot see specific classes or selectors per ticket attendee to narrow it down.
OR
Is it possible to have the attendee number restart per ticket on the same purchase? (this makes a lot of sense.)
However a proper add-on charge would be best.
Thanks,
Michael Fry
|
|
Josh
|
February 8, 2017 at 6:00 pm
Each ticket is considered a registration in the system, but there are html/css classes that you can use to hide groups of registration form fields.
You’ll find a live example here:
BROKEN LINK REMOVED
The extra CSS used in the example is:
One of the keys to making this work is you don’t set the “Additional Attendee Information” question groups, unless you need to ask specific questions for the add-on items, which the above example includes a T-shirt size question for the add-on item.
|
|
National_Travel
|
February 8, 2017 at 6:19 pm
But I need all the attendees (1-50) info for the first ticket type, but not the following types.
|
|
National_Travel
|
February 8, 2017 at 6:26 pm
Is it be possible to add a specific / non-random css id per ticket type?
|
|
Josh
|
February 10, 2017 at 9:26 am
Yes it’s possible to use specific CSS selectors for each ticket type, that’s what the example does. One wrinkle that you’ll run into though is all of the tickets will end up requiring name information, and you probably don’t want that.
Another approach that you could take is add a transaction surcharge for each add-on, which involves some PHP programming. There’s an example that shows how to set up some optional transaction surcharges that get added based on the answers to question on the registration form.
Here’s a link to the code for that example:
https://github.com/eventespresso/ee-code-snippet-library/blob/master/checkout/bc_ee_apply_transaction_surcharge.php
|
