|
John Lynn
|
August 24, 2017 at 3:38 pm
I’m trying to optimize my registration form: http://www.healthitmarketingconference.com/events/2018-health-it-marketing-and-pr-conference
A couple questions:
1. Is there a way to default to the “Super Early Bird Registration” ticket so the radio button for it is already selected?
2. Is there a way to hide the “Qty” header over the radio buttons since that doesn’t make sense when you can’t register multiple people.
3. It’s displaying the description after the ticket selector. Is there a way we can move it above the ticket selector?
Thanks for the help. Even just pointing to the right direction for my developers would be appreciated.
|
|
Josh
|
August 24, 2017 at 4:36 pm
Hi John,
If there’s only one ticket option to select from, the radio button will be automatically selected. Since your event has two options it doesn’t pre-select the first option. This avoids problems where the wrong ticket gets automatically selected.
The QTY header can be hidden with some CSS. You can change this by going to the Appearance -> Customize section of the admin, and there is a tab labeled ‘Additional CSS’. If you go into the customizer, you can add some code like this to hide the QTY header. Please paste the code between the dashed lines into the stylesheet:
—————————————-
.ee-ticket-selector-ticket-qty-th {
visibility:hidden;
}
—————————————-
Please refer to this guide for more detailed information about the CSS customizer: https://codex.wordpress.org/CSS#Custom_CSS_in_WordPress
The elements of the event pages can be re-arranged if you go to Event Espresso > Events > Templates and you’ll see an option Use Custom Display Order?. You set that option to Yes then you drag and drop the items under Display Order. Then you click Save.
|
|
John Lynn
|
August 24, 2017 at 5:22 pm
Ok. I see the issue. What I really want is the “This ticket is required (will appear first in frontend ticket lists).” advanced option so that then the Main registration is required. However, I want them to be able to add on the other pre-conference workshops as well. I can do that, but only if I allow the option to be able to purchase more than 1 ticket (ie. 2) per order. The problem with me allowing 2 tickets per order is that then they can do multiple registrations in one order and I like the cleanliness of 1 transaction/person per order. Although, maybe I should open my mind to allowing them to register multiple people at once. I just think with promo codes and knowing who ordered which tickets could get ugly and have more errors I have to fix. I guess I can just fix the error message and let them have to select it and not have it default for them.
The CSS to hide the QTY worked great. Same with the Custom Display Order for the event. Thanks!
|
|
John Lynn
|
August 24, 2017 at 5:27 pm
I think the unique thing for me that I’m not describing well is that I want the person that buys multiple tickets to be the same person. It’s more like add-on features that they could purchase at the same time.
Framed another way, I’d love to add an option that let’s them check a checkbox and purchase a t-shirt or some other item together with their registration. In the current implementation I have them adding on a pre-conference workshop, but there are a lot of add-on sales I’d love to offer them during registration. Does that make sense?
|
|
Tony
|
August 25, 2017 at 5:49 am
Hi John,
Currently, the best method to do that is to add additional ticket options and allow the users to select them, or you create ‘combined’ ticket selections, for example:
Admission
Admission + T-Shirt
Admission + T-Shirt + Cap
The user then selects a single ticket for everything. One thing to note with this is you need to create 2 sets of ticket if your using ‘Early bird’ tickets as you would need a goupd of tickets for early bird and then another for ‘normal’ ticket.
EE does not officially support ‘add-on’ items using checkboxes at this time although we do have some code examples that can be used, they are intended for developers to use a starting point. For example:
https://github.com/eventespresso/ee-code-snippet-library/blob/master/checkout/bc_ee_apply_transaction_surcharge.php
|
|
John Lynn
|
August 25, 2017 at 3:58 pm
Thanks for the info. The combined ticket is what I’ve basically done. As for the early bird, I was just planning to manually change the price since we have 3 dates when the price changes. That won’t be an issue if I want to just manually change the price higher as the dates pass right?
|
|
Josh
|
August 26, 2017 at 9:33 am
It will not be an issue but you should be aware that when you change the ticket what it will do is archive the original ticket, then make a duplicate of the original ticket and that duplicate will become available for sale. This way the registrations for the original ticket will have the correct ticket price paid information.
|
