|
Steve
|
May 25, 2019 at 4:29 pm
Hi There,
Is there a recommendation for the maximum number of tickets per event? I think I’m going to need what I consider a significant number (probably 20-30), and I’m wondering if this generates any performance or other concerns?
I’d consider splitting across events, but we need to gender balance so this becomes much harder.
Thanks
|
|
Tony
|
May 27, 2019 at 8:42 am
Hi Steve,
Adding DateTime/tickets increases the number of queries needed to construct the ticket selector, so it does increase the load on the server, meaning we can’t give your a ‘safe’ number of tickets you can use as it depends on the server you are using and how its set up.
20-30 tickets is a lot of tickets to display and it’s going to increase the load as mentioned, but another problem is that’s going to start to become more complicated for your visitors to navigate as they try to register.
Have you tested an event with the number of tickets mentioned to see if becomes unmanageable (from a user’s perspective when registering)?
|
|
Steve
|
May 27, 2019 at 12:38 pm
Thanks Tony – Whats driving it is a combo of:
Gendered Tickets plus a Gender Balanced Option
Combined with Early Bird, Late Bird, Really Late Bird pricing.
Combined with Int’l vs Domestic pricing!
As there isn’t a part of the EE Engine which can evaluate conditions and respond, you therefore need ticket types for all these variations.
I have been thinking about separating Int’l and Domestic in separate events, but then I’m manually gender balancing across the two, and it makes checkin a bit more of a pain (two queues!)
Any other thoughts to reduce complexity welcome (This was the reason behind my previous “how do I hide options from the cart”)
|
|
Tony
|
May 28, 2019 at 5:16 am
Combined with Early Bird, Late Bird, Really Late Bird pricing.
Combined with Int’l vs Domestic pricing!
As there isn’t a part of the EE Engine which can evaluate conditions and respond, you therefore need ticket types for all these variations.
That’s correct, but you can hide the upcoming tickets using some CSS, ie if you in ‘Early Bird’ ticketing stage you can hide the options for Late and Really Late which will reduce the options shown to the end user.
That is, assuming your tickets set the ‘sell until’ and ‘on sale from’ dates to cascade. Early bird from A to B, Late from B – C and really late from C -D dates, which I assume they will be?
Do you have an example event I can take a look at?
|
|
Steve
|
May 28, 2019 at 2:26 pm
Thanks Tony, yes, the tickets have time bounds, and this is what we’ve done before, so we know that’ll work OK.
I think the main thing will be if I can hide “int’l” tickets from one page on the site, and then hide UK from another, therefore creating two “flows” in the ticket selector…
|
|
Steve
|
May 28, 2019 at 2:50 pm
While we’re here, following up on this post:
https://eventespresso.com/topic/best-way-to-filter-ticket-selector/
Whats the best way to apply that code to a single page? Ideally, I guess, I would have two URLs / pages, one UK, one Int’l – people are unlikely to be booking both (but if they want to, they can use the event cart).
Another alternative would be a drop down selector I guess but I’m not sure about how easy that would be on mobile…
|
|
Tony
|
May 29, 2019 at 7:38 am
Whats the best way to apply that code to a single page?
So just to clarify, your using the ticket selector shortcode on 2 different pages of the site and want to hide tickets based the page?
If so you’d use is_page() within your function to confirm the page and then do whatever your doing, for example:
is_page('uk-registrations') {
// Do something when on the uk-registration page.
}
Is that what you are looking for?
|
|
Steve
|
May 29, 2019 at 1:51 pm
Thats what I was thinking to reduce the complexity, yes – it might not be ideal, but there you go!
So using the function above, I drop it into a plugin, have two versions one for th eint’l page, one for the UK.
Will go brush up on my PHP… Thanks for your help 🙂
|
|
Tony
|
May 30, 2019 at 5:28 am
You’re most welcome 🙂
|
