Support

August 31, 2016 at 8:04 am

Hi there,

Please excuse me if this has already been answered. I am likely not aware of the correct syntax to use, when trying to search. I’d like to have the Check Out fields (attendee information) expand on the same page, just below, the Ticket selector. Is this possible?

Not without significant customization to the checkout process.

The ticket selector is available on both single event pages, event lists and thorugh a shortcode, it submits the event/ticket details and the registration-checkout page takes over.

Altering that flow to include all of the steps with the ticket selector will take a significant amount of refactoring to the checkout process and is not something we can provide support for.

Also, may I change how the ticket selector looks (remove the table border lines around it, remove the price field all together …pretty much just leaving the name of the ticket/event and the quantity drop down)?

Those changes can be done with CSS, you can simply hide the fields that you don’t want visible.

Can you link me to a pack on your site with the ticket selector please? I’ll give you an example of how you can remove the above.

August 31, 2016 at 8:56 am

Apologies that’s a typo, it should be page, not pack 🙂

th.ee-ticket-selector-ticket-price-th, td.tckt-slctr-tbl-td-price {
    display: none;
}

Removes the price column from the ticket selector.

.tkt-slctr-tbl, 
.tkt-slctr-tbl th, 
.tkt-slctr-tbl tr, 
.tkt-slctr-tbl td {
    border: none;
    border-width: 0px;
    border-collapse: collapse;
}

Removes all board from the ticket selector table.

We recommend using either the My Custom CSS or Reaktiv CSS Builder plugins to add custom styles such as these.

August 31, 2016 at 9:02 am

Yeah if you are using a child theme that’s absolutely fine (its actually preferred).

We simply recommend using the above plugins for the majority of users as they are generally not using a child theme.

September 2, 2016 at 3:35 am

We don’t have any problem with you asking about other plugins but its important to note that any recommendations made on the forums are not ‘official’ EE recommendations, just something we (the support team) may have seen used.

Now having said that I don’t know of a specific plugin you can use, there’s no plugin that will ‘integrate’ with EE4 for donations, however as no plugin actually integrates with EE to create donations there should be no problem using any plugin.

The donations plugin will do its thing, EE will do its own. However you will notice that donations and registrations will be completely separate so if the donations plugin takes the user offsite to make the donation, they will break the flow of the registration and the user may need to restart it. It depends how your using the plugin and what it is your trying to do.

Can you provide some further details of what your looking for?

September 5, 2016 at 2:21 am

It seems that if I can combine purchasing a t-shirt and making a donation, then I’d have just one break up of the flow …from register/registration confirmed completed, to merchant experience of purchase shirt and/or donate, checkout …or from don’t register, to merchant experience of purchase shirt and/or donate, checkout.

So the way I would handle this is to combine the Registration and T-Shirt purchase into EE, so your ticket options could be something like:

Registration - 0.00 (if free)
Registration + T-Shirt = $10 

Were that gets a little tricky is how you manage the T-Shirt sizes, if you need to manage different quantities for the shirts you can do it within the ticket options:

Registration - 0.00 (if free)
Registration + T-Shirt (S) = $10 
Registration + T-Shirt (M) = $11 
Registration + T-Shirt (L)= $12 
Registration + T-Shirt (XL) = $13 

That allows you to set limits on each, if you don’t need that you can just add a custom question to the registration form and then add the size options to that.

Then once registration is complete you can add a donation button/form to the ‘Thank you’ page that will be displayed when the finalized. That way you don’t break the registration flow but still allow for donations at the end.

Would that work?