|
charlobaysan
|
July 9, 2016 at 4:55 am
I have a discussion with the Sales Agent on the website chatbox before deciding to purchase the plugin. I told them the ticketing system requirements and I was told that it was possible but I need to create tons of tickets per event and I need a serve that can handle huge amount of page requests since having multiple tickets increase the variable inputs and reaching the PHP Max Execution Time when saving
So the setup it a one Day event will have separate tickets for every 15mins time of the day. So I setup tone of event time and assign ticket for each of them.
Already tried 3 hosting companies including WP Engine but still they can’t meet our requirements.
max_execution_time = Atleast 300seconds
max_input_vars = Around 60,000
Please let us know what hosting you recommend.
Regards
|
|
Lorenzo Orlando Caum
|
July 9, 2016 at 10:24 am
Hello,
I replied that that email and I think there was a misunderstanding. My suggestion was to split up the event into a day and night or another way so that all the ticket options would not be loaded into a single event. The estimate on your example would be 36 ticket options.
How many ticket options are you trying to create in one event?
—
Lorenzo
|
|
charlobaysan
|
July 11, 2016 at 10:05 pm
Hi Lorenzo,
84 Tickets
27 Event Times
Separating the Event Times won’t work since it will be difficult for the users to select the time they want to book a ticket.
http://screencast.com/t/DPs8LieO
Regards
|
|
Tony
|
July 12, 2016 at 5:32 am
Event Espresso 4 does not officially support recurring events like the event you have shown in the image, it can work for some setups but not with large quantities of tickets/datetimes within a single event as they are all pulled from the database at once.
If you can not split the selections into more than a single EE event then with its current features EE may not be the correct choice for your events. 84 Tickets within the ticket selector will also become hard for your attendees to the navigate through without creating your own custom ticket selector.
I need a serve that can handle huge amount of page requests since having multiple tickets increase the variable inputs and reaching the PHP Max Execution Time when saving
Its not just when saving the event (max_input_vars comes into play when saving) but also when pulling the data from the database. Currently EE pulls in all of the tickets and datetimes for the event so with larger amounts of each this takes longer and timeout (either PHP or DB timeout). Multiply that time by X amount of page views at once and you’ll likely run into more problems as more users try to pull all of the information from the DB at the same time.
|
