Support

October 19, 2020 at 5:28 am

Hi there,

How many dates/tickets are you loading within a single event?

Depending on the numbers, you may need to break your events down a little, for example using a single event for 1 weeks worth of dates/tickets.

October 19, 2020 at 6:27 am

It varies based on your server but your probably looking about 30-40 ticket types with the current set up.

October 19, 2020 at 3:33 pm

Any way to go around this other than just slicing the events? Server upgrade?

Not really and a server upgrade is only going to get you so far, the current version of Event Espresso is not designed to load high numbers of datetimes/tickets within a single event.

Currently, you can split the events and then using something like the table view template to output a list of those events for the user to select before loading the ticket selector.

Loading the tickets only when the date is selected in the ticket selector? (Honestly this should really be a feature from the start)

Whilst I understand your frustration and no disrespect intended here, everyone wants X feature to be included from the start so if we tried to suit every use case from the beginning we’d never get a version out the door.

The majority of users do not use 100+ ticket types within a single event so Event Espresso wasn’t designed to handle single events with that many. That type of event is what we class as a recurring event and we don’t have a recurring event manager (REM) add-on fro EE4 yet. As time has gone by we’ve had more feature requests for higher numbers of tickets and have taken the feedback onboard. We are currently rewriting the event editor which will allow for a REM add-on and allow you to create higher numbers of tickets without hitting your server max_input_vars setting (which is likely the next thing you’ll hit and need to update) and all of the framework changes required to do that, then we’ll need to investigate how to load those on the front end to prevent the above.

So yes, loading specific tickets on specific pages is the answer but that’s not something you can easily achieve yourself. With the current version, you’ll need to split the events to use a smaller number of tickets/datetimes to prevent longer load times on the ticket selector.

October 20, 2020 at 5:54 am

May I ask where you would have liked for that info to be included on the above locations?

I can pass this onto the team but we don’t have a list of features we don’t support currently so I’m not sure where we would add that in.